librenms
Error While Starting Docker Image
I am getting this error when starting the docker image.
chmod: changing permissions of '/var/spool/cron/crontabs/librenms': Bad address
See Below for console log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-fix-logs.sh: executing... [cont-init.d] 00-fix-logs.sh: exited 0. [cont-init.d] 01-fix-uidgid.sh: executing... [cont-init.d] 01-fix-uidgid.sh: exited 0. [cont-init.d] 02-fix-perms.sh: executing... Fixing perms... [cont-init.d] 02-fix-perms.sh: exited 0. [cont-init.d] 03-config.sh: executing... Setting timezone to UTC... Setting PHP-FPM configuration... Setting PHP INI configuration... Setting OpCache configuration... Setting Nginx configuration... Updating SNMP community... Initializing LibreNMS files / folders... Setting LibreNMS configuration... Checking LibreNMS plugins... Fixing perms... Checking additional Monitoring plugins... Checking alert templates... [cont-init.d] 03-config.sh: exited 0. [cont-init.d] 04-svc-main.sh: executing... Waiting 60s for database to be ready... Database ready! Updating database schema...
INFO Nothing to migrate.
INFO Seeding database.
Database\Seeders\DefaultAlertTemplateSeeder ........................ RUNNING
Database\Seeders\DefaultAlertTemplateSeeder ...................... 2 ms DONE
Database\Seeders\ConfigSeeder ...................................... RUNNING
Database\Seeders\ConfigSeeder .................................. 869 ms DONE
Database\Seeders\RolesSeeder ....................................... RUNNING
Database\Seeders\RolesSeeder .................................... 42 ms DONE
Clear cache
INFO Application cache cleared successfully.
INFO Configuration cached successfully.
[cont-init.d] 04-svc-main.sh: exited 0. [cont-init.d] 05-svc-dispatcher.sh: executing... [cont-init.d] 05-svc-dispatcher.sh: exited 0. [cont-init.d] 06-svc-syslogng.sh: executing... [cont-init.d] 06-svc-syslogng.sh: exited 0. [cont-init.d] 07-svc-cron.sh: executing... Creating LibreNMS daily.sh cron task with the following period fields: 15 0 * * * Creating LibreNMS cron artisan schedule:run Fixing crontabs permissions... chmod: changing permissions of '/var/spool/cron/crontabs/librenms': Bad address [cont-init.d] 07-svc-cron.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
I have this same issue.
It does seem like this is a known issue with other containers too https://github.com/linuxserver/docker-swag/issues/514
Thanks for the heads up for using 24.9.1, changing to that worked for me.
I experienced the same issue on both QNAP x86_64-based QTS and QuTS Hero distributions.
Yeah this takes forever on more busy Hypervisors, there must be a better way for this For me it has been taking 20 minutes now, I am considering removing it from the script to speed up the start and then manually running a fix perm once
