Movary is not restarting/starting

[yasirbilgic]

Hello!
When I deploy Movary there is no problem but when I try to restart it, it gives me that error.
Can you help me with that?

-> Executing /opt/docker/provision/entrypoint.d/05-permissions.sh

-> Executing /opt/docker/provision/entrypoint.d/20-nginx.sh

-> Executing /opt/docker/provision/entrypoint.d/20-php-fpm.sh

-> Executing /opt/docker/provision/entrypoint.d/20-php.sh

-> Executing /opt/docker/bin/service.d/supervisor.d//10-init.sh

2023-10-29 07:51:27,740 INFO Included extra file "/opt/docker/etc/supervisor.d/cron.conf" during parsing

2023-10-29 07:51:27,740 INFO Included extra file "/opt/docker/etc/supervisor.d/dnsmasq.conf" during parsing

2023-10-29 07:51:27,740 INFO Included extra file "/opt/docker/etc/supervisor.d/movary.conf" during parsing

2023-10-29 07:51:27,740 INFO Included extra file "/opt/docker/etc/supervisor.d/nginx.conf" during parsing

2023-10-29 07:51:27,741 INFO Included extra file "/opt/docker/etc/supervisor.d/php-fpm.conf" during parsing

2023-10-29 07:51:27,741 INFO Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing

2023-10-29 07:51:27,741 INFO Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing

2023-10-29 07:51:27,741 INFO Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing

2023-10-29 07:51:27,741 INFO Set uid to user 0 succeeded

2023-10-29 07:51:27,746 INFO RPC interface 'supervisor' initialized

2023-10-29 07:51:27,746 INFO supervisord started with pid 1

2023-10-29 07:51:28,749 INFO spawned: 'syslogd' with pid 64

2023-10-29 07:51:28,752 INFO spawned: 'nginxd' with pid 65

2023-10-29 07:51:28,755 INFO spawned: 'php-fpmd' with pid 66

2023-10-29 07:51:28,757 INFO spawned: 'crond' with pid 69

2023-10-29 07:51:28,760 INFO spawned: 'movary' with pid 70

-> Executing /opt/docker/bin/service.d/syslog-ng.d//10-init.sh

-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh

2023-10-29 07:51:28,761 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2023-10-29 07:51:28,761 INFO success: php-fpmd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2023-10-29 07:51:28,762 INFO success: crond entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

[SYSLOG] syslog-ng[64]: syslog-ng starting up; version='4.1.1'

[2023-10-29T07:51:28.764087] WARNING: Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats_freq', change='Use the stats() block. E.g. stats(freq(1));', location='/etc/syslog-ng/syslog-ng.conf:19:5'

[2023-10-29T07:51:28.767162] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;

nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /opt/docker/etc/nginx/vhost.ssl.conf:1

-> Executing /opt/docker/bin/service.d/cron.d//10-init.sh

-> Executing /opt/docker/bin/service.d/php-fpm.d//10-init.sh

Setting php-fpm user to 1000

[29-Oct-2023 07:51:28] NOTICE: fpm is running, pid 66

[29-Oct-2023 07:51:28] NOTICE: ready to handle connections

2023-10-29 07:51:28:931062 - Processing job...

2023-10-29 07:51:28:932747 - Nothing to process.

2023-10-29 07:51:28:932804 - Sleeping for 14.998232 seconds to reach min runtime...

2023-10-29 07:51:29,934 INFO success: syslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-10-29 07:51:29,934 INFO success: movary entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-10-29 07:51:43,945 INFO exited: movary (exit status 0; expected)

2023-10-29 07:51:44,949 INFO spawned: 'movary' with pid 91

2023-10-29 07:51:45:106435 - Processing job...

2023-10-29 07:51:45:107989 - Nothing to process.

2023-10-29 07:51:45:108063 - Sleeping for 14.998346 seconds to reach min runtime...

2023-10-29 07:51:46,109 INFO success: movary entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[php-fpm:access] 127.0.0.1 -  29/Oct/2023:07:51:50 +0000 "GET /index.php" 303 /app/public/index.php 61.854 4096 80.84%

85.153.232.185 - - [29/Oct/2023:07:51:50 +0000] "GET / HTTP/1.1" 303 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0"

[php-fpm:access] 127.0.0.1 -  29/Oct/2023:07:51:50 +0000 "GET /index.php" 200 /app/public/index.php 288.176 4096 93.69%

85.153.232.185 - - [29/Oct/2023:07:51:50 +0000] "GET /users/yasirbilgic/dashboard HTTP/1.1" 200 82730 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0"

85.153.232.185 - - [29/Oct/2023:07:51:50 +0000] "GET /images/favicon.ico HTTP/1.1" 200 15086 "http://212.24.99.52:49156/users/yasirbilgic/dashboard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0"

2023-10-29 07:51:59,559 WARN received SIGQUIT indicating exit request

2023-10-29 07:51:59,559 INFO waiting for syslogd, nginxd, php-fpmd, crond, movary to die

2023-10-29 07:51:59,563 WARN stopped: movary (terminated by SIGTERM)

2023-10-29 07:52:01,569 WARN stopped: crond (terminated by SIGTERM)

[29-Oct-2023 07:52:01] NOTICE: Terminating ...

[29-Oct-2023 07:52:01] NOTICE: exiting, bye-bye!

2023-10-29 07:52:01,600 INFO stopped: php-fpmd (exit status 0)

2023-10-29 07:52:01,648 INFO stopped: nginxd (exit status 0)

[SYSLOG] syslog-ng[64]: syslog-ng shutting down; version='4.1.1'

2023-10-29 07:52:02,651 INFO waiting for syslogd to die

2023-10-29 07:52:02,754 INFO stopped: syslogd (exit status 0)

error: failed switching to "root": operation not permitted

error: failed switching to "root": operation not permitted

error: failed switching to "root": operation not permitted

[leepeuker]

Hey, this (sadly) a known issue and will be fixed in the future.

You can see further discussion about this issue here and how to fix here

[leepeuker]

This should no longer happen with the 0.63.0 release.