AlmaLinux / AlmaLinux/build-system

Fix logging errors in sign-file

Offen
#446 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug good first issue
Vorherrschende Sprache
Keine Sprachdaten
Sterne
32
Forks
11
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I pulled the last version of albs-sign-file and I'm seeing the following logging errors:

```
sign_file-1 | INFO: Application startup complete.
sign_file-1 | --- Logging error ---
sign_file-1 | Traceback (most recent call last):
sign_file-1 | File "/usr/lib64/python3.9/logging/handlers.py", line 978, in emit
sign_file-1 | self.socket.send(msg)
sign_file-1 | OSError: [Errno 9] Bad file descriptor
sign_file-1 |
sign_file-1 | During handling of the above exception, another exception occurred:
sign_file-1 |
sign_file-1 | Traceback (most recent call last):
sign_file-1 | File "/usr/lib64/python3.9/logging/handlers.py", line 899, in _connect_unixsocket
sign_file-1 | self.socket.connect(address)
sign_file-1 | FileNotFoundError: [Errno 2] No such file or directory
sign_file-1 |
sign_file-1 | During handling of the above exception, another exception occurred:
sign_file-1 |
sign_file-1 | Traceback (most recent call last):
sign_file-1 | File "/usr/lib64/python3.9/logging/handlers.py", line 981, in emit
sign_file-1 | self._connect_unixsocket(self.address)
sign_file-1 | File "/usr/lib64/python3.9/logging/handlers.py", line 910, in _connect_unixsocket
sign_file-1 | self.socket.connect(address)
sign_file-1 | FileNotFoundError: [Errno 2] No such file or directory
sign_file-1 | Call stack:
sign_file-1 | File "", line 1, in
sign_file-1 | File "/usr/lib64/python3.9/multiprocessing/spawn.py", line 116, in spawn_main
sign_file-1 | exitcode = _main(fd, parent_sentinel)
sign_file-1 | File "/usr/lib64/python3.9/multiprocessing/spawn.py", line 129, in _main
sign_file-1 | return self._bootstrap(parent_sentinel)
sign_file-1 | File "/usr/lib64/python3.9/multiprocessing/process.py", line 315, in _bootstrap
sign_file-1 | self.run()
sign_file-1 | File "/usr/lib64/python3.9/multiprocessing/process.py", line 108, in run
sign_file-1 | self._target(*self._args, **self._kwargs)
sign_file-1 | File "/usr/local/lib/python3.9/site-packages/uvicorn/subprocess.py", line 76, in subprocess_started
sign_file-1 | target(sockets=sockets)
sign_file-1 | File "/usr/local/lib/python3.9/site-packages/uvicorn/server.py", line 68, in run
sign_file-1 | return asyncio.run(self.serve(sockets=sockets))
sign_file-1 | File "/usr/lib64/python3.9/asyncio/runners.py", line 44, in run
sign_file-1 | return loop.run_until_complete(main)
sign_file-1 | File "/usr/local/lib/python3.9/site-packages/uvicorn/server.py", line 86, in serve
sign_file-1 | await self.startup(sockets=sockets)
sign_file-1 | File "/usr/local/lib/python3.9/site-packages/uvicorn/server.py", line 97, in startup
sign_file-1 | await self.lifespan.startup()
sign_file-1 | File "/usr/local/lib/python3.9/site-packages/uvicorn/lifespan/on.py", line 59, in startup
sign_file-1 | self.logger.info("Application startup complete.")
sign_file-1 | Message: 'Application startup complete.'
sign_file-1 | Arguments: ()
```

Looks like a problem when attaching the SysLog handler

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.