continuous timeout DEBUG messages in comitup.log #179
Unanswered
mennamorato
asked this question in
Q&A
Replies: 1 comment 4 replies
-
The debug message is fine - it's just saying that it's checking that the connection is where it is supposed to be. I haven't seen the restart before. There should be either a "Stopping comitup" INFO entry before it, or a Traceback in comitup.log or another. Systemd is configured to restart the service. I have a current debug logging session on a connected one-interface system that is three days old, with no restart. I just set verbose on a connected router install (on a Pi Zero W). Prior to that, the router occasionally lost the upstream connection, but there were no restarts. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For some reason, yesterday, my /var/log/comitup.log file started filling up with this DEBUG message every 3 minutes on my RaspberryPi Zero W: (comitup v1.29)
2021-06-01 17:57:22,623 - comitup - DEBUG - connected_timeout comparing xxxxxxxx to xxxxxxxx (same SSID)
eventually there was a
2021-06-02 07:55:14,181 - comitup - INFO - Starting comitup followed by more of the same DEBUG messages.
something to worry about ? how to debug more ?
thanks
Beta Was this translation helpful? Give feedback.
All reactions