Stops forwarding after "Failed to get cursor" with a large journal backlog
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- c, linux
- Área
- backend, networking
Línea de trabajo
Start by reproducing the failure with a large journal backlog and the supplied systemd-netlogd configuration, then trace journal iteration and cursor persistence, especially the state file at /var/lib/systemd/journal-netlogd/state. Compare the behavior with issues #14 and #17. Done means the backlog is forwarded once, forwarding continues for new entries, and the cursor errors no longer occur.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
systemd-netlogd version
Output of systemd-netlogd --version:
1.4.4 (Debian package 1.4.4-1)
OS and systemd version
- Distribution: Debian 13 (trixie)
- systemd version (
systemctl --version): systemd 257 (257.13-1~deb13u1)
Configuration
[Network]
Address=127.0.0.1:5140
Protocol=tcp
LogFormat=rfc5424
Describe the bug
When netlogd starts with a large backlog in the journal, it stops forwarding after a few seconds, with "Failed to get cursor: Cannot assign requested address". Before it stops, it sends many entries more than once.
Steps to reproduce
- Write about 100,000 entries to the journal, e.g.
seq 100000 | systemd-cat -t loadtest. - Remove
/var/lib/systemd/journal-netlogd/stateand run a TCP listener on 127.0.0.1:5140 that counts the lines it receives. - Start systemd-netlogd.
- After it stops, write a few more entries with
logger.
Expected behavior
All journal entries are forwarded once, and forwarding continues with new entries.
Actual behavior
- Forwarding stops about 10 seconds after start.
- About 340,000 lines are received, while the journal has about 100,000 entries.
- When new entries are written, netlogd sends the whole journal again from the beginning and stops again.
- With a small journal (about 3,000 entries written at a steady rate), all entries arrive once and no errors are logged.
Logs
Failed to get cursor: Cannot assign requested address
Failed to get cursor: Cannot assign requested address
...
Failed to iterate through journal: Invalid argument
Failed to get cursor: Invalid argument
Additional context
- Same behavior with netlogd 1.4.4 on IncusOS 202611080229, sending to a remote host over TCP.
- Looks similar to #14 and #17.
- Lenguaje dominante
- C
- Estrellas
- 99
- Forks
- 35
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de systemd/systemd-netlogd
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 77/100
systemd/systemd-netlogd#150 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
systemd/systemd-netlogd#149 · 1 comentario ·
Todos los issues de systemd/systemd-netlogd
Issues similares
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ChupathingyCE/chupathingyce#1366 ·
Los mantenedores suelen responder en 1 día
-
slice track:dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Life-Framework/Life-Framework#1831 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
-
bug intrinsic low priority wrong result
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día