S3 has no assigned interfaces
andreas
16 Posts
June 11, 2024, 6:42 pmQuote from andreas on June 11, 2024, 6:42 pmWhen I try to assign the S3 service to a node I get the following error:
S3 Error: S3 has no assigned interfaces, please assign interface
What could be wrong?
Thanks for your help.
When I try to assign the S3 service to a node I get the following error:
S3 Error: S3 has no assigned interfaces, please assign interface
What could be wrong?
Thanks for your help.
admin
2,929 Posts
June 12, 2024, 2:08 amQuote from admin on June 12, 2024, 2:08 amYou need to setup S3 service settings under Configuration -> S3 Settings.
You need to setup S3 service settings under Configuration -> S3 Settings.
andreas
16 Posts
June 12, 2024, 4:39 amQuote from andreas on June 12, 2024, 4:39 amThank you for your support. The S3 settings have been configured. There are no error messages.
However, no configured IPs are displayed under "Manage S3 -> Reassign IPs".
Thank you for your support. The S3 settings have been configured. There are no error messages.
However, no configured IPs are displayed under "Manage S3 -> Reassign IPs".
admin
2,929 Posts
June 12, 2024, 7:58 pmQuote from admin on June 12, 2024, 7:58 pmAre the ips showing up under S3 Status page? have you given S3 role to some nodes ? Did you setup your S3 zone under Configiration?
We have an online guide for S3 setup.
Are the ips showing up under S3 Status page? have you given S3 role to some nodes ? Did you setup your S3 zone under Configiration?
We have an online guide for S3 setup.
andreas
16 Posts
June 13, 2024, 5:55 amQuote from andreas on June 13, 2024, 5:55 amFirst I configured the S3 settings. Contrary to the setup guide, we use the backend subnet and have not configured a separate subnet for S3. Furthermore, we do not use TLS. When I try to assign the "S3" role to a node, the error message appears. We were unable to reproduce the problem in a fresh PetaSAN installation.
First I configured the S3 settings. Contrary to the setup guide, we use the backend subnet and have not configured a separate subnet for S3. Furthermore, we do not use TLS. When I try to assign the "S3" role to a node, the error message appears. We were unable to reproduce the problem in a fresh PetaSAN installation.
admin
2,929 Posts
June 13, 2024, 9:39 amQuote from admin on June 13, 2024, 9:39 amJust to clarify: You had 2 issues: the error message of now assigned S3 interfaces and when this was solved you stated a different issue that you do not see ips in the reassign ips page. I understood the first was fixed but not sure if from your last post that the second issue is fixed or not, as you did not mention it again.
To be clear: you need to configure the S3 Settings: interface to use, ips to use for your S3 servers, subnet range/mask of the S3 network. You can use the same interface for S3 as backend, not ptoblem but you have to tell the system this. TLS is optional (it is marked as such) so you can skip it.
Just to clarify: You had 2 issues: the error message of now assigned S3 interfaces and when this was solved you stated a different issue that you do not see ips in the reassign ips page. I understood the first was fixed but not sure if from your last post that the second issue is fixed or not, as you did not mention it again.
To be clear: you need to configure the S3 Settings: interface to use, ips to use for your S3 servers, subnet range/mask of the S3 network. You can use the same interface for S3 as backend, not ptoblem but you have to tell the system this. TLS is optional (it is marked as such) so you can skip it.
andreas
16 Posts
June 18, 2024, 6:09 pmQuote from andreas on June 18, 2024, 6:09 pmSorry for the confusion. After configuring the S3 settings exactly as described, it is not possible to assign the S3 role to a node. I tried it with different nodes and got an error message each time. When I try to assign the S3 role, I get an error message. The fact that no IP addresses are displayed on the reassign ips page is because no node has been assigned the S3 role. So it is not an error. We tested the configuration on several clusters, but it did not work on one cluster even though we always did everything the same.
Sorry for the confusion. After configuring the S3 settings exactly as described, it is not possible to assign the S3 role to a node. I tried it with different nodes and got an error message each time. When I try to assign the S3 role, I get an error message. The fact that no IP addresses are displayed on the reassign ips page is because no node has been assigned the S3 role. So it is not an error. We tested the configuration on several clusters, but it did not work on one cluster even though we always did everything the same.
admin
2,929 Posts
June 18, 2024, 9:16 pmQuote from admin on June 18, 2024, 9:16 pmFor the cluster that has issue , can you confirm/clarify:
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
- You see this error even if you set an interface in the S3 Settings page ?
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
For the cluster that has issue , can you confirm/clarify:
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
- You see this error even if you set an interface in the S3 Settings page ?
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
andreas
16 Posts
June 19, 2024, 6:35 amQuote from andreas on June 19, 2024, 6:35 am
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
Yes, I see this error!
- You see this error even if you set an interface in the S3 Settings page ?
No, Is see "S3 Settings saved successfully."
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
Yes, I double check the network configuration
Today I found some error messages in the log of the node to which I wanted to assign the S3 role. However, I was not able to repeat this error message today.
19/06/2024 06:25:06 INFO GlusterFS mount attempt
18/06/2024 06:25:19 INFO GlusterFS mount attempt
17/06/2024 06:25:30 INFO GlusterFS mount attempt
16/06/2024 06:25:16 INFO GlusterFS mount attempt
15/06/2024 06:25:03 INFO GlusterFS mount attempt
14/06/2024 06:25:12 INFO GlusterFS mount attempt
13/06/2024 15:05:58 INFO sync_replication_node called on non-backup node
13/06/2024 15:05:13 INFO sync_replication_node called on non-backup node
13/06/2024 13:34:17 INFO sync_replication_node called on non-backup node
13/06/2024 13:30:45 INFO sync_replication_node called on non-backup node
13/06/2024 13:29:40 INFO sync_replication_node called on non-backup node
13/06/2024 13:28:22 INFO sync_replication_node called on non-backup node
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 13:14:59 ERROR An error occurred
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 12:44:45 ERROR An error occurred
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
Yes, I see this error!
- You see this error even if you set an interface in the S3 Settings page ?
No, Is see "S3 Settings saved successfully."
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
Yes, I double check the network configuration
Today I found some error messages in the log of the node to which I wanted to assign the S3 role. However, I was not able to repeat this error message today.
19/06/2024 06:25:06 INFO GlusterFS mount attempt
18/06/2024 06:25:19 INFO GlusterFS mount attempt
17/06/2024 06:25:30 INFO GlusterFS mount attempt
16/06/2024 06:25:16 INFO GlusterFS mount attempt
15/06/2024 06:25:03 INFO GlusterFS mount attempt
14/06/2024 06:25:12 INFO GlusterFS mount attempt
13/06/2024 15:05:58 INFO sync_replication_node called on non-backup node
13/06/2024 15:05:13 INFO sync_replication_node called on non-backup node
13/06/2024 13:34:17 INFO sync_replication_node called on non-backup node
13/06/2024 13:30:45 INFO sync_replication_node called on non-backup node
13/06/2024 13:29:40 INFO sync_replication_node called on non-backup node
13/06/2024 13:28:22 INFO sync_replication_node called on non-backup node
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 13:14:59 ERROR An error occurred
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 12:44:45 ERROR An error occurred
S3 has no assigned interfaces
andreas
16 Posts
Quote from andreas on June 11, 2024, 6:42 pmWhen I try to assign the S3 service to a node I get the following error:
S3 Error: S3 has no assigned interfaces, please assign interface
What could be wrong?
Thanks for your help.
When I try to assign the S3 service to a node I get the following error:
S3 Error: S3 has no assigned interfaces, please assign interface
What could be wrong?
Thanks for your help.
admin
2,929 Posts
Quote from admin on June 12, 2024, 2:08 amYou need to setup S3 service settings under Configuration -> S3 Settings.
You need to setup S3 service settings under Configuration -> S3 Settings.
andreas
16 Posts
Quote from andreas on June 12, 2024, 4:39 amThank you for your support. The S3 settings have been configured. There are no error messages.
However, no configured IPs are displayed under "Manage S3 -> Reassign IPs".
Thank you for your support. The S3 settings have been configured. There are no error messages.
However, no configured IPs are displayed under "Manage S3 -> Reassign IPs".
admin
2,929 Posts
Quote from admin on June 12, 2024, 7:58 pmAre the ips showing up under S3 Status page? have you given S3 role to some nodes ? Did you setup your S3 zone under Configiration?
We have an online guide for S3 setup.
Are the ips showing up under S3 Status page? have you given S3 role to some nodes ? Did you setup your S3 zone under Configiration?
We have an online guide for S3 setup.
andreas
16 Posts
Quote from andreas on June 13, 2024, 5:55 amFirst I configured the S3 settings. Contrary to the setup guide, we use the backend subnet and have not configured a separate subnet for S3. Furthermore, we do not use TLS. When I try to assign the "S3" role to a node, the error message appears. We were unable to reproduce the problem in a fresh PetaSAN installation.
First I configured the S3 settings. Contrary to the setup guide, we use the backend subnet and have not configured a separate subnet for S3. Furthermore, we do not use TLS. When I try to assign the "S3" role to a node, the error message appears. We were unable to reproduce the problem in a fresh PetaSAN installation.
admin
2,929 Posts
Quote from admin on June 13, 2024, 9:39 amJust to clarify: You had 2 issues: the error message of now assigned S3 interfaces and when this was solved you stated a different issue that you do not see ips in the reassign ips page. I understood the first was fixed but not sure if from your last post that the second issue is fixed or not, as you did not mention it again.
To be clear: you need to configure the S3 Settings: interface to use, ips to use for your S3 servers, subnet range/mask of the S3 network. You can use the same interface for S3 as backend, not ptoblem but you have to tell the system this. TLS is optional (it is marked as such) so you can skip it.
Just to clarify: You had 2 issues: the error message of now assigned S3 interfaces and when this was solved you stated a different issue that you do not see ips in the reassign ips page. I understood the first was fixed but not sure if from your last post that the second issue is fixed or not, as you did not mention it again.
To be clear: you need to configure the S3 Settings: interface to use, ips to use for your S3 servers, subnet range/mask of the S3 network. You can use the same interface for S3 as backend, not ptoblem but you have to tell the system this. TLS is optional (it is marked as such) so you can skip it.
andreas
16 Posts
Quote from andreas on June 18, 2024, 6:09 pmSorry for the confusion. After configuring the S3 settings exactly as described, it is not possible to assign the S3 role to a node. I tried it with different nodes and got an error message each time. When I try to assign the S3 role, I get an error message. The fact that no IP addresses are displayed on the reassign ips page is because no node has been assigned the S3 role. So it is not an error. We tested the configuration on several clusters, but it did not work on one cluster even though we always did everything the same.
Sorry for the confusion. After configuring the S3 settings exactly as described, it is not possible to assign the S3 role to a node. I tried it with different nodes and got an error message each time. When I try to assign the S3 role, I get an error message. The fact that no IP addresses are displayed on the reassign ips page is because no node has been assigned the S3 role. So it is not an error. We tested the configuration on several clusters, but it did not work on one cluster even though we always did everything the same.
admin
2,929 Posts
Quote from admin on June 18, 2024, 9:16 pmFor the cluster that has issue , can you confirm/clarify:
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
- You see this error even if you set an interface in the S3 Settings page ?
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
For the cluster that has issue , can you confirm/clarify:
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
- You see this error even if you set an interface in the S3 Settings page ?
- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
andreas
16 Posts
Quote from andreas on June 19, 2024, 6:35 am
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
Yes, I see this error!- You see this error even if you set an interface in the S3 Settings page ?
No, Is see "S3 Settings saved successfully."- Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
Yes, I double check the network configurationToday I found some error messages in the log of the node to which I wanted to assign the S3 role. However, I was not able to repeat this error message today.
19/06/2024 06:25:06 INFO GlusterFS mount attempt
18/06/2024 06:25:19 INFO GlusterFS mount attempt
17/06/2024 06:25:30 INFO GlusterFS mount attempt
16/06/2024 06:25:16 INFO GlusterFS mount attempt
15/06/2024 06:25:03 INFO GlusterFS mount attempt
14/06/2024 06:25:12 INFO GlusterFS mount attempt
13/06/2024 15:05:58 INFO sync_replication_node called on non-backup node
13/06/2024 15:05:13 INFO sync_replication_node called on non-backup node
13/06/2024 13:34:17 INFO sync_replication_node called on non-backup node
13/06/2024 13:30:45 INFO sync_replication_node called on non-backup node
13/06/2024 13:29:40 INFO sync_replication_node called on non-backup node
13/06/2024 13:28:22 INFO sync_replication_node called on non-backup node
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 13:14:59 ERROR An error occurred
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 12:44:45 ERROR An error occurred
- Is the error you see "S3 Error: S3 has no assigned interfaces, please assign interface" ? or something else ?
Yes, I see this error! - You see this error even if you set an interface in the S3 Settings page ?
No, Is see "S3 Settings saved successfully." - Is the interface you set in settings, is it physically present on the nodes you try to assign the S3 role ?
Yes, I double check the network configuration
Today I found some error messages in the log of the node to which I wanted to assign the S3 role. However, I was not able to repeat this error message today.
19/06/2024 06:25:06 INFO GlusterFS mount attempt
18/06/2024 06:25:19 INFO GlusterFS mount attempt
17/06/2024 06:25:30 INFO GlusterFS mount attempt
16/06/2024 06:25:16 INFO GlusterFS mount attempt
15/06/2024 06:25:03 INFO GlusterFS mount attempt
14/06/2024 06:25:12 INFO GlusterFS mount attempt
13/06/2024 15:05:58 INFO sync_replication_node called on non-backup node
13/06/2024 15:05:13 INFO sync_replication_node called on non-backup node
13/06/2024 13:34:17 INFO sync_replication_node called on non-backup node
13/06/2024 13:30:45 INFO sync_replication_node called on non-backup node
13/06/2024 13:29:40 INFO sync_replication_node called on non-backup node
13/06/2024 13:28:22 INFO sync_replication_node called on non-backup node
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 13:14:59 ERROR An error occurred
OSError: [Errno 6] No such device or address
logging.debug(f"Benutzer: {os.getlogin()}")
File "/opt/petasan/scripts/backups/sync_replication_node.py", line 35, in main
Traceback (most recent call last):
13/06/2024 12:44:45 ERROR An error occurred