-
Notifications
You must be signed in to change notification settings - Fork 14
Description
When opening the output I accidentally stumbled over this log entry, there seems to be an unhandled exception:
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192162111Z During handling of the above exception, another exception occurred:
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192166002Z
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192169899Z Traceback (most recent call last):
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192180333Z File "/usr/lib/python3.10/logging/init.py", line 1103, in emit
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192186058Z stream.write(msg + self.terminator)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192191297Z File "/home/appuser/code/monitor.py", line 83, in reap_children
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192195400Z logging.info(f"Reaped child process with PID {pid}")
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192199611Z File "/usr/lib/python3.10/logging/init.py", line 2138, in info
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192203787Z root.info(msg, *args, **kwargs)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192209165Z File "/usr/lib/python3.10/logging/init.py", line 1477, in info
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192213964Z self._log(INFO, msg, args, **kwargs)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192219000Z File "/usr/lib/python3.10/logging/init.py", line 1624, in _log
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192246690Z self.handle(record)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192251019Z File "/usr/lib/python3.10/logging/init.py", line 1634, in handle
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192254831Z self.callHandlers(record)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192258457Z File "/usr/lib/python3.10/logging/init.py", line 1696, in callHandlers
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192262330Z hdlr.handle(record)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192265944Z File "/usr/lib/python3.10/logging/init.py", line 968, in handle
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192290930Z self.emit(record)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192294784Z File "/usr/lib/python3.10/logging/init.py", line 1108, in emit
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192298443Z self.handleError(record)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192302011Z File "/usr/lib/python3.10/logging/init.py", line 1021, in handleError
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192305691Z sys.stderr.write('--- Logging error ---\n')
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192309346Z RuntimeError: reentrant call inside <_io.BufferedWriter name=''>
netwatch_ssh-attackpod | 2025-03-02T17:56:41.192325971Z Call stack:
netwatch_ssh-attackpod | 2025-03-02T17:56:41.198276797Z File "/home/appuser/code/monitor.py", line 160, in
netwatch_ssh-attackpod | 2025-03-02T17:56:41.198320756Z submit_attack(ip, user, password, evidence, ATTACKPOD_LOCAL_IP)
netwatch_ssh-attackpod | 2025-03-02T17:56:41.198325651Z File "/home/appuser/code/monitor.py", line 65, in submit_attack
netwatch_ssh-attackpod | 2025-03-02T17:56:41.198329935Z logging.info(f"Reported the following JSON to the NetWatch collector: {json}")
Is this related to the API issue? Is this an error worth looking into?