Web is not starting up after upgrading to latest docker image

[rvbaast]

Hi,

I recently updated my docker image to the latest version. ( Did a fresh install, so no old config files were present, totally recreated the container ). And since then the Kerberos web interface isn't reachable for me.

The logs don't really give me much info about what is going on. :

Config files are missing, copying from template., 2020-04-21 20:47:18,649 INFO Set uid to user 0 succeeded, 2020-04-21 20:47:18,812 INFO RPC interface 'supervisor' initialized, 2020-04-21 20:47:18,812 CRIT Server 'unix_http_server' running without any HTTP authentication checking, 2020-04-21 20:47:18,813 INFO supervisord started with pid 17, 2020-04-21 20:47:19,817 INFO spawned: 'machinery' with pid 20, 2020-04-21 20:47:20,375 INFO spawned: 'nginx' with pid 21, 2020-04-21 20:47:20,902 INFO spawned: 'php-fpm' with pid 22, 2020-04-21 20:47:21,562 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:47:21,562 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:47:21,562 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), Config files are available., 2020-04-21 20:56:50,250 INFO Set uid to user 0 succeeded, 2020-04-21 20:56:50,579 INFO RPC interface 'supervisor' initialized, 2020-04-21 20:56:50,580 CRIT Server 'unix_http_server' running without any HTTP authentication checking, 2020-04-21 20:56:50,638 INFO supervisord started with pid 16, 2020-04-21 20:56:51,643 INFO spawned: 'machinery' with pid 18, 2020-04-21 20:56:51,647 INFO spawned: 'nginx' with pid 19, 2020-04-21 20:56:51,651 INFO spawned: 'php-fpm' with pid 20, 2020-04-21 20:56:52,976 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:56:52,985 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:56:52,985 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:58:35,458 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 20:58:36,648 INFO spawned: 'machinery' with pid 59, 2020-04-21 20:58:37,887 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 20:59:38,826 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 20:59:38,829 INFO spawned: 'machinery' with pid 92, 2020-04-21 20:59:39,929 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:00:50,263 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 21:00:51,268 INFO spawned: 'machinery' with pid 131, 2020-04-21 21:00:52,308 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:02:54,759 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 21:02:55,764 INFO spawned: 'machinery' with pid 190, 2020-04-21 21:02:56,810 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:04:16,845 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 21:04:17,850 INFO spawned: 'machinery' with pid 227, 2020-04-21 21:04:18,890 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:05:49,072 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 21:05:50,099 INFO spawned: 'machinery' with pid 269, 2020-04-21 21:05:51,140 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:09:02,183 INFO exited: machinery (terminated by SIGABRT; not expected), 2020-04-21 21:09:03,187 INFO spawned: 'machinery' with pid 315, 2020-04-21 21:09:04,248 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), Config files are available., 2020-04-21 21:14:47,295 INFO Set uid to user 0 succeeded, 2020-04-21 21:14:47,624 INFO RPC interface 'supervisor' initialized, 2020-04-21 21:14:47,625 CRIT Server 'unix_http_server' running without any HTTP authentication checking, 2020-04-21 21:14:47,724 INFO supervisord started with pid 16, 2020-04-21 21:14:48,728 INFO spawned: 'machinery' with pid 18, 2020-04-21 21:14:48,732 INFO spawned: 'nginx' with pid 19, 2020-04-21 21:14:48,736 INFO spawned: 'php-fpm' with pid 20, 2020-04-21 21:14:50,095 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:14:50,096 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:14:50,096 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), Config files are available., 2020-04-21 21:35:45,989 INFO Set uid to user 0 succeeded, 2020-04-21 21:35:46,305 INFO RPC interface 'supervisor' initialized, 2020-04-21 21:35:46,305 CRIT Server 'unix_http_server' running without any HTTP authentication checking, 2020-04-21 21:35:46,366 INFO supervisord started with pid 16, 2020-04-21 21:35:47,370 INFO spawned: 'machinery' with pid 18, 2020-04-21 21:35:47,374 INFO spawned: 'nginx' with pid 19, 2020-04-21 21:35:47,378 INFO spawned: 'php-fpm' with pid 20, 2020-04-21 21:35:48,732 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:35:48,732 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs), 2020-04-21 21:35:48,733 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs),

[cedricve]

Hey can you give some more information? Which machine / architecture, which docker image? Command you are using.

[rvbaast]

I'm running this on my Western Digital PR2100 NAS which has a x86 cpu architecture. I am using this docker image : https://hub.docker.com/r/kerberos/kerberos

I created the container like this :

docker create --name=k_garagecam -v /mnt/HD/HD_a2/Apps/Kerberos/Garagecam/capture:/etc/opt/kerberosio/capture -v /mnt/HD/HD_a2/Apps/Kerberos/Garagecam/cameraconfig:/etc/opt/kerberosio/config -v /mnt/HD/HD_a2/Apps/Kerberos/Garagecam/logs:/etc/opt/kerberosio/logs -v /mnt/HD/HD_a2/Apps/Kerberos/config:/var/www/web/config -p 9901:80 -p 8889:8889 kerberos/kerberos

I must add that the web interface wasn't reachable when i changed the internal portnumber to another number then 80. Changing it back to port 80 like in the command above, shows the following error when trying to reach the web interface:

"Whoops, looks like something went wrong"

[cedricve]

just tested again, can you try and do a pull again?

docker pull kerberos/kerberos

[rvbaast]

It seems I already got the latest image:

[cedricve]

That is not latest image, can you remove the image and pull again?

[rvbaast]

Ok, Done, however same sha256 :

And same issue after starting the container.

Shouldn't I see a nginx config file appear in the container here : /var/www/web/config

That directory stays empty after starting the docker container for the 1st time.

[cedricve]

Hmm, indeed just noticed it myself there is a bug. Will need to fix to copy the files in there. Can you try without mounting the webconfig?

On 22 Apr 2020, at 10:05, Rob notifications@github.com wrote:

Ok, Done, however same sha256 :

https://user-images.githubusercontent.com/14869671/79956114-fbe4a480-847f-11ea-8569-ca59073e71f9.png And same issue after starting the container.

Shouldn't I see a nginx config file appear in the container here : /var/www/web/config

That directory stays empty after starting the docker container for the 1st time.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kerberos-io/web/issues/160#issuecomment-617620467, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALZUG56SCSKVILUXC44M6LRN2QLHANCNFSM4MNUL2DA.

[rvbaast]

Without mounting the webconfig it appears to work indeed. Thanks for you assistance. Let me know if you want me to help test a new version.

[cedricve]

Yes, creating a new build right now.

[cedricve]

@rvbaast can docker pull again, and give it another try this time with the webconfig.

[rvbaast]

Done, and it is working a expected! Thanks for the quick responses and the awesome piece of software!