On Sat, Apr 5, 2025 at 9:04 PM ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi All,
Fedora 41
I have a customer I set up a Fedora 41 server.
Problem: about once a week, its networking dies. All
network services are dead, xrdp, ssh, samba, etc..
All of them. Console logins work fine.
The solution is to call the customer and have him
log in at the console and issue a shutdown. On
power up, all work again.
That is a workaround -- solution would keep network alive.
What I would like to do, is to set up a cron
job to test the networking (ping firewall)
and restart/correct the network if I find
it down.
Start by checking journalctl for details of the network shutting down.
Now I do know about
# systemctl restart systemd-networkd.service
But is that enough? What do I need to do to
put the network into the same state as after
a fresh reboot?
The answer depends on what causes the network to shut down.
I have seen similar issues in the past where the solution came after
collecting detailed stats for the times of shutdowns. In one case,
the outlet used for a PC was on a circuit used to power an exhaust fan
with a timer -- when fan started, voltage dropped to 90V which caused
connected gear to reset.
George N. White III
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
