On 7 Apr 2025 at 10:59, ToddAndMargo via users wrote: Date sent: Mon, 7 Apr 2025 10:59:29 -0700 Subject: Re: I need to monitor a dead network To: users@xxxxxxxxxxxxxxxxxxxxxxx Send reply to: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> From: ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> Copies to: ToddAndMargo <ToddAndMargo@xxxxxxxx> > On 4/5/25 5:03 PM, ToddAndMargo via users 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. > > > > 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. > > > > 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? > > > > Many thanks, > > -T > > > Update: > > The network froze again. > > I had the customer issue a > > # systemctl stop systemd-networkd.service > # sleep 5s > # systemctl start systemd-networkd.service > > No joy. > > Then I had the customer issue > # reboot > > No joy. > > Then I had him issue a > # poweroff > and power back on > > Joy. Just something you might work, but would require changes. I have a number of machines with turbo vnc, but have one machine that sometimes has the port go to closed state. Restarting the service gets it running again. use nmap to check the vnc port and it if it finds it closed, it restarts the service. #!/usr/bin/bash x=$(nmap 192.168.10.78 -p 5978 | grep close); if [ -n "$x" ] ; then systemctl restart tvncserver; fi Could also get info from the network card to see if it has lost the IP address, or if it has gone down. Could also try a reboot using systemctl reboot Probable be best to find exactly what is going down. Good Luck. > > > I just ordered out an Intel I210-T1 Network Adapter > > -T > > > -- > _______________________________________________ > 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 +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@xxxxxxxx mailto:msetzerii@xxxxxxxxx mailto:msetzerii@xxxxxxx Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+ -- _______________________________________________ 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
