Not being a network expert… I’d tend to tell you that yes, my problems are resolved since my connection works fine (surfing / downloads), my IPTV no longer cuts out every 2min, etc..
But I may be wrong… I don’t know how to verify it.
Did you restart your server running Gladys since you fixed the issue?
Otherwise, if I were you I’d run tests in the CLI on your Linux machine — I’m not a network expert either so I asked ChatGPT for a set of Linux commands to check that everything is okay on your side (it’s a start; there are surely other tools to find on the internet):
1. Checking network settings
Check network interfaces
Check the network interfaces to ensure they are correctly configured.
ip aCheck DHCP settings
Make sure the Linux server is correctly obtaining an IP address. If you use DHCP, check the status of the DHCP client.
sudo systemctl status dhclientDisplay IP settings
Check that the IP address, gateway and DNS servers are correctly configured.
ip route cat /etc/resolv.conf2. Logging and diagnostics
Check system logs
Examine the system logs for error messages or alerts related to the network.
sudo journalctl -xe sudo dmesg | grep -i networkCheck network connections
Check active network connections to see if there are any suspicious or unauthorized connections.
netstat -tulnp3. Connectivity tests
Ping the gateway
Make sure the Linux server can reach the default gateway.
ping -c 4 <adresse_de_la_passerelle>Ping the DNS servers
Check connectivity to the configured DNS servers.
ping -c 4 8.8.8.8 # Example with Google DNSTraceroute
Use
tracerouteto diagnose the path taken by packets to a given destination.traceroute google.com4. Network settings and services
Restart network services
Sometimes, a simple restart of network services can resolve issues.
sudo systemctl restart networking sudo systemctl restart NetworkManagerConfigure network interfaces
Check that the network interface configuration files are correct. On Debian-based distributions this is usually found in
/etc/network/interfacesor/etc/netplanfor newer Ubuntu versions.Example for
/etc/network/interfaces:auto eth0 iface eth0 inet dhcp5. Other diagnostic tools
ifconfigandethtoolUse
ifconfigto display interface configurations andethtoolfor advanced information.ifconfig sudo ethtool eth0
I’m bumping this thread because I’m still experiencing my problem.
A priori @pierre-gilles and I are leaning toward a network issue at my place.
While waiting to continue my tests, I asked ChatGPT to help me set up log monitoring, but not in real time because my disconnections happen very often at night.
It suggests an ELK stack (if anyone’s familiar).
For that I need to restart my Gladys container with arguments that send the logs to Logstash.
But I have doubts… Could someone tell me if this command to run Gladys looks correct?
docker run -d \
--name gladys \
--privileged \
--restart always \
--log-driver gelf \
--log-opt gelf-address=udp://adresse_de_logstash:12201 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db \
-e NODE_ENV=production \
-e SERVER_PORT=80 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladysassistant:/var/lib/gladysassistant \
-v /dev:/dev \
-v /run/udev:/run/udev:ro \
gladysassistant/gladys:v4 \
Launching an ELK stack just to view Gladys logs seems overkill to me ![]()
Aren’t the current logs sufficient?
Besides, in your case I’m not sure you’ll find the answer in Gladys, since the issue seems to be system-wide (I think it’s a network or DNS problem); you’ll find the answer more in the system logs, and for that you don’t need an ELK stack either ^^
Oh, you know me, I do what ChatGPT suggests… Overkill or not, I don’t care since I’ll delete everything afterwards ![]()
I’m going to start by inspecting my DNS resolutions all over my network anyway!
Yes, but essentially that won’t add anything for you…
You already see the logs by doing docker logs gladys, you won’t see anything more by