We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've just upgraded running Librenms setup to latest docker images and the LibrNMS failed to start
Smooth upgrade
Crash
Client: Docker Engine - Community Version: 26.1.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.14.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.27.0 Path: /usr/libexec/docker/cli-plugins/docker-compose Server: Containers: 19 Running: 18 Paused: 0 Stopped: 1 Images: 30 Server Version: 26.1.1 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: e377cd56a71523140ca6ae87e30244719194a521 runc version: v1.1.12-0-g51d5e94 init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 5.15.0-101-generic Operating System: Ubuntu 22.04.4 LTS OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 23.47GiB Name: ubuntu-node ID: 3e31da33-2f40-4e5d-b55e-7c0d4f2ce2c6 Docker Root Dir: /var/lib/docker Debug Mode: false Username: vladaman Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Default Address Pools: Base: 10.10.0.0/16, Size: 24
No response
ibrenms | Clear cache librenms | librenms | INFO Application cache cleared successfully. librenms | librenms | librenms | INFO Configuration cached successfully. librenms | librenms | [cont-init.d] 04-svc-main.sh: exited 0. librenms | [cont-init.d] 05-svc-dispatcher.sh: executing... librenms | [cont-init.d] 05-svc-dispatcher.sh: exited 0. librenms | [cont-init.d] 06-svc-syslogng.sh: executing... librenms | [cont-init.d] 06-svc-syslogng.sh: exited 0. librenms | [cont-init.d] 07-svc-cron.sh: executing... librenms | Creating LibreNMS daily.sh cron task with the following period fields: 15 0 * * * librenms | Creating LibreNMS cron artisan schedule:run librenms | Fixing crontabs permissions... librenms | [cont-init.d] 07-svc-cron.sh: exited 0. librenms | [cont-init.d] 08-svc-snmptrapd.sh: executing... librenms | [cont-init.d] 08-svc-snmptrapd.sh: exited 0. librenms | [cont-init.d] ~-socklog: executing... librenms | [cont-init.d] ~-socklog: exited 0. librenms | [cont-init.d] done. librenms | [services.d] starting services librenms | crond: crond (busybox 1.36.1) started, log level 8 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: using the "epoll" event method librenms | 2024/07/21 20:36:32 [notice] 1072#1072: nginx/1.24.0 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: OS: Linux 5.15.0-101-generic librenms | 2024/07/21 20:36:32 [notice] 1072#1072: getrlimit(RLIMIT_NOFILE): 1048576:1048576 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: start worker processes librenms | 2024/07/21 20:36:32 [notice] 1072#1072: start worker process 1089 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: start worker process 1090 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: start worker process 1091 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: start worker process 1092 librenms | [services.d] done. librenms | crontab: can't open 'root': No such file or directory librenms | [21-Jul-2024 20:36:32] NOTICE: fpm is running, pid 1069 librenms | [21-Jul-2024 20:36:32] NOTICE: ready to handle connections librenms | [cmd] crontab exited 1 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: signal 15 (SIGTERM) received from 1063, exiting librenms | 2024/07/21 20:36:32 [notice] 1090#1090: exiting librenms | 2024/07/21 20:36:32 [notice] 1092#1092: exiting librenms | 2024/07/21 20:36:32 [notice] 1089#1089: exiting librenms | [21-Jul-2024 20:36:32] NOTICE: Terminating ... librenms | 2024/07/21 20:36:32 [notice] 1091#1091: exiting librenms | [21-Jul-2024 20:36:32] NOTICE: exiting, bye-bye! librenms | 2024/07/21 20:36:32 [notice] 1091#1091: exit librenms | 2024/07/21 20:36:32 [notice] 1090#1090: exit librenms | 2024/07/21 20:36:32 [notice] 1092#1092: exit librenms | 2024/07/21 20:36:32 [notice] 1089#1089: exit librenms | 2024/07/21 20:36:32 [notice] 1072#1072: signal 17 (SIGCHLD) received from 1091 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: worker process 1091 exited with code 0 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: signal 29 (SIGIO) received librenms | [cont-finish.d] executing container finish scripts... librenms | [cont-finish.d] done. librenms | [s6-finish] waiting for services. librenms | 2024/07/21 20:36:32 [notice] 1072#1072: signal 17 (SIGCHLD) received from 1092 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: worker process 1089 exited with code 0 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: worker process 1090 exited with code 0 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: worker process 1092 exited with code 0 librenms | 2024/07/21 20:36:32 [notice] 1072#1072: exit librenms | s6-svwait: fatal: supervisor died librenms | [s6-finish] sending all processes the TERM signal. librenms | s6-log: warning: unable to read from stdin: Bad file descriptor librenms | [s6-finish] sending all processes the KILL signal and exiting.
The text was updated successfully, but these errors were encountered:
Any workarounds?
Sorry, something went wrong.
No branches or pull requests
Support guidelines
I've found a bug and checked that ...
Description
I've just upgraded running Librenms setup to latest docker images and the LibrNMS failed to start
Expected behaviour
Smooth upgrade
Actual behaviour
Crash
Steps to reproduce
Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: