Failed Dependency on setting up network
podilarius
44 Posts
June 6, 2022, 8:45 pmQuote from podilarius on June 6, 2022, 8:45 pmFor status of ifup@eth2.7
Main PID: 3716 (code=exited, status=1/FAILURE)
ifup: failed to bring up eth2.7
ifup@eth2.7.service: Main process exited, code=exited, status=1/FAILURE
ifup@eth2.7.service: Failed with result 'exit-code'.
For status of systemd-networkd: seems to be disabled.
Active: inactive (dead)
For status of networking:
Active: active (exited)
Main PID: 3327 (code=exited, status=0/SUCCESS)
For status of ifup@eth2.7
Main PID: 3716 (code=exited, status=1/FAILURE)
ifup: failed to bring up eth2.7
ifup@eth2.7.service: Main process exited, code=exited, status=1/FAILURE
ifup@eth2.7.service: Failed with result 'exit-code'.
For status of systemd-networkd: seems to be disabled.
Active: inactive (dead)
For status of networking:
Active: active (exited)
Main PID: 3327 (code=exited, status=0/SUCCESS)
podilarius
44 Posts
June 24, 2022, 4:06 pmQuote from podilarius on June 24, 2022, 4:06 pmDo you think I can disable this service to avoid startup problems with the following command?
systemctl disable ifup@eth2.7
Or can it be removed so I don't have to work about it getting activated again?
Do you think I can disable this service to avoid startup problems with the following command?
systemctl disable ifup@eth2.7
Or can it be removed so I don't have to work about it getting activated again?
admin
2,858 Posts
June 25, 2022, 12:35 pmQuote from admin on June 25, 2022, 12:35 pmYes you can disable it. it is not used or enabled by PetaSAN, i checked on some installed systems and it is not enabled.
Yes you can disable it. it is not used or enabled by PetaSAN, i checked on some installed systems and it is not enabled.
podilarius
44 Posts
June 27, 2022, 11:38 pmQuote from podilarius on June 27, 2022, 11:38 pmI tried to disable, but I got back a blank and the service is still loaded.
How is that service registered during installation?
How can I disable this?
I tried to disable, but I got back a blank and the service is still loaded.
How is that service registered during installation?
How can I disable this?
podilarius
44 Posts
June 27, 2022, 11:54 pmQuote from podilarius on June 27, 2022, 11:54 pmHad to use this command instead.
systemctl reset-failed ifup@eth2.7.service
On start up though, this service came back.
This must be called from another startup script somewhere.
This is still causing start up issues.
Is this some sort of legacy way of starting up interfaces?
Had to use this command instead.
systemctl reset-failed ifup@eth2.7.service
On start up though, this service came back.
This must be called from another startup script somewhere.
This is still causing start up issues.
Is this some sort of legacy way of starting up interfaces?
podilarius
44 Posts
June 28, 2022, 2:39 pmQuote from podilarius on June 28, 2022, 2:39 pmSeems to be a deeper problem. This service seems to be loaded by networking in the ifupdown.service as a preload.
It might be startup order. Meaning that if udev has not renamed the interface by the time this service starts, the ifupdown service cannot find eth2.7 and will fail.
This is a working theory, and I am researching more.
Any help will be appreciated.
Seems to be a deeper problem. This service seems to be loaded by networking in the ifupdown.service as a preload.
It might be startup order. Meaning that if udev has not renamed the interface by the time this service starts, the ifupdown service cannot find eth2.7 and will fail.
This is a working theory, and I am researching more.
Any help will be appreciated.
admin
2,858 Posts
June 28, 2022, 8:10 pmQuote from admin on June 28, 2022, 8:10 pmif you can reproduce in another environment, please post the steps and we will try it in our cluster.
if you can reproduce in another environment, please post the steps and we will try it in our cluster.
podilarius
44 Posts
July 3, 2022, 12:23 amQuote from podilarius on July 3, 2022, 12:23 amI will try to replicate this week.
I will try to replicate this week.
tntbizhub
2 Posts
April 10, 2024, 12:57 pmQuote from tntbizhub on April 10, 2024, 12:57 pmHi podilarius!
Any news on this matter? I have the same problem with version 3.2.1, the management is on VLAN 1254 and I keep installing node-1 adding to cluster and as it boots doesn't have connectivy until I do a systemctl networking restart, the networking starts to work but doesn't get available as a node.
Is there a way to restart the the networking and the cluster services? At least for now as I don't figure out whats going on?
Hi podilarius!
Any news on this matter? I have the same problem with version 3.2.1, the management is on VLAN 1254 and I keep installing node-1 adding to cluster and as it boots doesn't have connectivy until I do a systemctl networking restart, the networking starts to work but doesn't get available as a node.
Is there a way to restart the the networking and the cluster services? At least for now as I don't figure out whats going on?
tntbizhub
2 Posts
April 10, 2024, 2:03 pmQuote from tntbizhub on April 10, 2024, 2:03 pmUpdate:
After running /opt/petasan/scripts/start_petasan_services.py and a reboot... magically it started working without the error... later today I will reboot node-1 to see if it keeps working or it fails again...
Update:
After running /opt/petasan/scripts/start_petasan_services.py and a reboot... magically it started working without the error... later today I will reboot node-1 to see if it keeps working or it fails again...
Failed Dependency on setting up network
podilarius
44 Posts
Quote from podilarius on June 6, 2022, 8:45 pmFor status of ifup@eth2.7
Main PID: 3716 (code=exited, status=1/FAILURE)
ifup: failed to bring up eth2.7
ifup@eth2.7.service: Main process exited, code=exited, status=1/FAILURE
ifup@eth2.7.service: Failed with result 'exit-code'.For status of systemd-networkd: seems to be disabled.
Active: inactive (dead)
For status of networking:
Active: active (exited)
Main PID: 3327 (code=exited, status=0/SUCCESS)
For status of ifup@eth2.7
Main PID: 3716 (code=exited, status=1/FAILURE)
ifup: failed to bring up eth2.7
ifup@eth2.7.service: Main process exited, code=exited, status=1/FAILURE
ifup@eth2.7.service: Failed with result 'exit-code'.
For status of systemd-networkd: seems to be disabled.
Active: inactive (dead)
For status of networking:
Active: active (exited)
Main PID: 3327 (code=exited, status=0/SUCCESS)
podilarius
44 Posts
Quote from podilarius on June 24, 2022, 4:06 pmDo you think I can disable this service to avoid startup problems with the following command?
systemctl disable ifup@eth2.7
Or can it be removed so I don't have to work about it getting activated again?
Do you think I can disable this service to avoid startup problems with the following command?
systemctl disable ifup@eth2.7
Or can it be removed so I don't have to work about it getting activated again?
admin
2,858 Posts
Quote from admin on June 25, 2022, 12:35 pmYes you can disable it. it is not used or enabled by PetaSAN, i checked on some installed systems and it is not enabled.
Yes you can disable it. it is not used or enabled by PetaSAN, i checked on some installed systems and it is not enabled.
podilarius
44 Posts
Quote from podilarius on June 27, 2022, 11:38 pmI tried to disable, but I got back a blank and the service is still loaded.
How is that service registered during installation?
How can I disable this?
I tried to disable, but I got back a blank and the service is still loaded.
How is that service registered during installation?
How can I disable this?
podilarius
44 Posts
Quote from podilarius on June 27, 2022, 11:54 pmHad to use this command instead.
systemctl reset-failed ifup@eth2.7.service
On start up though, this service came back.
This must be called from another startup script somewhere.
This is still causing start up issues.
Is this some sort of legacy way of starting up interfaces?
Had to use this command instead.
systemctl reset-failed ifup@eth2.7.service
On start up though, this service came back.
This must be called from another startup script somewhere.
This is still causing start up issues.
Is this some sort of legacy way of starting up interfaces?
podilarius
44 Posts
Quote from podilarius on June 28, 2022, 2:39 pmSeems to be a deeper problem. This service seems to be loaded by networking in the ifupdown.service as a preload.
It might be startup order. Meaning that if udev has not renamed the interface by the time this service starts, the ifupdown service cannot find eth2.7 and will fail.
This is a working theory, and I am researching more.Any help will be appreciated.
Seems to be a deeper problem. This service seems to be loaded by networking in the ifupdown.service as a preload.
It might be startup order. Meaning that if udev has not renamed the interface by the time this service starts, the ifupdown service cannot find eth2.7 and will fail.
This is a working theory, and I am researching more.
Any help will be appreciated.
admin
2,858 Posts
Quote from admin on June 28, 2022, 8:10 pmif you can reproduce in another environment, please post the steps and we will try it in our cluster.
if you can reproduce in another environment, please post the steps and we will try it in our cluster.
podilarius
44 Posts
Quote from podilarius on July 3, 2022, 12:23 amI will try to replicate this week.
I will try to replicate this week.
tntbizhub
2 Posts
Quote from tntbizhub on April 10, 2024, 12:57 pmHi podilarius!
Any news on this matter? I have the same problem with version 3.2.1, the management is on VLAN 1254 and I keep installing node-1 adding to cluster and as it boots doesn't have connectivy until I do a systemctl networking restart, the networking starts to work but doesn't get available as a node.
Is there a way to restart the the networking and the cluster services? At least for now as I don't figure out whats going on?
Hi podilarius!
Any news on this matter? I have the same problem with version 3.2.1, the management is on VLAN 1254 and I keep installing node-1 adding to cluster and as it boots doesn't have connectivy until I do a systemctl networking restart, the networking starts to work but doesn't get available as a node.
Is there a way to restart the the networking and the cluster services? At least for now as I don't figure out whats going on?
tntbizhub
2 Posts
Quote from tntbizhub on April 10, 2024, 2:03 pmUpdate:
After running /opt/petasan/scripts/start_petasan_services.py and a reboot... magically it started working without the error... later today I will reboot node-1 to see if it keeps working or it fails again...
Update:
After running /opt/petasan/scripts/start_petasan_services.py and a reboot... magically it started working without the error... later today I will reboot node-1 to see if it keeps working or it fails again...