Error in log. How to find what issue actually is?

[Marcin Metter]

I've been seeing the following error recently not sure what is going on. Looks like some file is missing.

I am running mitct02/weewx docker image (/ https://registry.hub.docker.com/r/mitct02/weewx/) on a Synology NAS. It use to work in the past not sure wy it now fails? Any hints on how to debug this?

--- Logging error ---
Traceback (most recent call last):
File "/home/weewx/bin/user/interceptor.py", line 2550, in genLoopPackets
data = self._device.get_queue().get(True, self._queue_timeout)
File "/usr/lib/python3.10/queue.py", line 179, in get raise Empty
_queue. Empty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.10/logging/handlers.py", line 987, in emit self.socket.send(msg)
OSError: [Errno 9] Bad file descriptor

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.10/logging/handlers.py", line 908, in _connect_unixsocket self.socket.connect(address)
FileNotFoundError: [Errno 2] No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.10/logging/handlers.py", line 990, in emit self._connect_unixsocket(self. Address)
File "/usr/lib/python3.10/logging/handlers.py", line 919, in _connect_unixsocket self.socket.connect(address)
FileNotFoundError: [Errno 2] No such file or directory
Call stack:
File "/home/weewx/bin/weewxd", line 249, in main()
File "/home/weewx/bin/weewxd", line 154, in main engine. Run()
File "/home/weewx/bin/weewx/engine.py", line 208, in run for packet in self.console.genLoopPackets():
File "/home/weewx/bin/user/interceptor.py", line 2566, in genLoopPackets logdbg('empty queue')
File "/home/weewx/bin/user/interceptor.py", line 284, in logdbg log. Debug(msg)
Message: 'empty queue'
Arguments: ()

[Graham Eddy]

looks like to separate problems

(1) something in interceptor driver - might be benign (ignorable), or might be serious

(2) logging misconfigured. check the syslog interface mechanism for your specific o/s

⊣GE⊢

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2f40bb32-bb14-4e82-bd47-051629f86de7n%40googlegroups.com.

[vince]

If it used to work and does not work now, you changed something changed in the os or in the docker configuration.  Did you upgrade the os on the NAS ?

Agree with Graham that (2) certainly looks like you are trying to log to a directory that isn't there.   Are you trying to log to a mounted directory that is not currently mounted perhaps ?   Otherwise impossible to tell without more info on your docker configuration and how you are invoking docker to run the image.

[Marcin Metter]

I just added the following to my config file to stop it from trying to write to syslog.

##############################################################################
[Logging]
  [[root]]
    handlers = console,

[Marcin Metter]

It should be all default, but perhaps something wrt directories, etc has changed recently. Will have a hunt around.

I gather it is just trying to log debug and info messages that is all.