Overly verbose logging to journalctl

Abierto
#17 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
backend

Línea de trabajo

Reproduce la transacción de update-manager y compara las entradas duplicadas de AptKit y org.aptkit en journalctl. Rastrea la configuración de logging que produce ambas entradas e inspecciona la ubicación de la advertencia en /usr/lib/python3/dist-packages/aptkit/progress.py:485. Se considera terminado cuando los mensajes duplicados de aptkit se hayan eliminado o se puedan controlar sin cambiar el logging de servicios no relacionados.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

So when I run the update manager, I get this in my journalctl:

Apr 21 13:59:14 Excalibur dbus-daemon[1618]: [system] Activating service name='org.aptkit' requested by ':1.4514' (uid=1000 pid=7195 comm="mintUpdate " label="unconfined") (usi>
Apr 21 13:59:14 Excalibur AptKit[278078]: INFO: Initializing daemon
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit [INFO]: Initializing daemon
Apr 21 13:59:14 Excalibur dbus-daemon[1618]: [system] Successfully activated service 'org.aptkit'
Apr 21 13:59:14 Excalibur AptKit[278078]: INFO: InstallPackages() was called: dbus.Array([dbus.String('libcap2-bin'), dbus.String('libcap2:i386'), dbus.String('libcap2'), dbus.String('libpam-cap'), dbus.String('ntf>
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit [INFO]: InstallPackages() was called: dbus.Array([dbus.String('libcap2-bin'), dbus.String('libcap2:i386'), dbus.String('libcap2'), dbus.String('libpam-c>
Apr 21 13:59:14 Excalibur AptKit.Trans[278078]: INFO: Simulate was called
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit.Trans [INFO]: Simulate was called
Apr 21 13:59:14 Excalibur AptKit.Worker[278078]: INFO: Simulating trans: /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit.Worker [INFO]: Simulating trans: /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:14 Excalibur AptKit.Worker[278078]: WARNING: An additional step to open the cache is required
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit.Worker [WARNING]: An additional step to open the cache is required
Apr 21 13:59:14 Excalibur AptKit.Worker[278078]: INFO: Committing packages: dbus.Array([dbus.String('libcap2-bin'), dbus.String('libcap2:i386'), dbus.String('libcap2'), dbus.String('libpam-cap'), dbus.String('ntfs->
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit.Worker [INFO]: Committing packages: dbus.Array([dbus.String('libcap2-bin'), dbus.String('libcap2:i386'), dbus.String('libcap2'), dbus.String('libpam-cap>
Apr 21 13:59:14 Excalibur AptKit.Trans[278078]: INFO: Queuing transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:14 Excalibur org.aptkit[278078]: 13:59:14 AptKit.Trans [INFO]: Queuing transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:19 Excalibur polkitd[1730]: Operator of unix-session:c2 successfully authenticated as unix-user:qwinn to gain TEMPORARY authorization for action org.aptkit.install-or-remove-packages for system-bus-nam>
Apr 21 13:59:19 Excalibur AptKit.Worker[278078]: INFO: Processing transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:19 Excalibur org.aptkit[278078]: 13:59:19 AptKit.Worker [INFO]: Processing transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:20 Excalibur systemd[6483]: Started pk-debconf-helper.service - debconf communication service.
Apr 21 13:59:27 Excalibur dbus-daemon[1618]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.4520' (uid=0 pid=282881 comm="/usr/bin/gdbus call ->
Apr 21 13:59:27 Excalibur dbus-daemon[1618]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Apr 21 13:59:27 Excalibur org.aptkit[278078]: /usr/lib/python3/dist-packages/aptkit/progress.py:485: Warning: Source ID 34 was not found when attempting to remove it
Apr 21 13:59:27 Excalibur org.aptkit[278078]: GLib.source_remove(id)
Apr 21 13:59:27 Excalibur org.aptkit[278078]: /usr/lib/python3/dist-packages/aptkit/progress.py:485: Warning: Source ID 35 was not found when attempting to remove it
Apr 21 13:59:27 Excalibur org.aptkit[278078]: GLib.source_remove(id)
Apr 21 13:59:27 Excalibur AptKit.Worker[278078]: INFO: Finished transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14
Apr 21 13:59:27 Excalibur org.aptkit[278078]: 13:59:27 AptKit.Worker [INFO]: Finished transaction /org/aptkit/transaction/67229b042b6e48bb80ba8b577b86bd14

Is all this really necessary? For one thing I note that most lines seem to be duplicated, one from org.aptkit and another from either AptKit.Worker or AptKit.Trans. According to AI (which of course could be wrong but if that's the case I'm not sure how I'd go about finding the right answer), the only way to control all this logging to journalctl would be to add a LogLevelMax=error to the org.freedesktop.PolicyKit1 service, which would suppress INFO and WARNING messages for a whole lot of services, not just aptkit. So unless you guys can tone this down somehow or add a configuration option to control it, there's no way a user can control this level of verbosity.

If at least the duplication could be removed, that would help a lot. Preferably removing the ones from org.AptKit as those come up yellow in journalctl even when they are INFO level, the AptKit.Worker/Trans obey normal coloring conventions. Thanks for any help.

Lenguaje dominante
Python
Estrellas
15
Forks
10
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de linuxmint/aptkit

Todos los issues de linuxmint/aptkit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.