Egroupware-push swoole 502 error

[somogyi]

Hi,

In fresh egroupware install (20201020, ubuntu 20.04-docker), the egroupware-push container started, but the swoole service not start properly. Its not create port and some error in logs:

INFO: Supervisord configuration files copied from folder ‘/etc/supervisor/service.d/’.
INFO Included extra file “/etc/supervisor/conf.d/swoole.conf” during parsing
INFO Set uid to user 0 succeeded
INFO RPC interface ‘supervisor’ initialized
CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
INFO supervisord started with pid 13
INFO spawnerr: no permission to run command '/var/www/server.php’
INFO spawnerr: no permission to run command '/var/www/server.php’
INFO spawnerr: no permission to run command '/var/www/server.php’
INFO spawnerr: no permission to run command '/var/www/server.php’
INFO gave up: swoole entered FATAL state, too many start retries too quickly

Can you help with this?

Thanks,
Z

[RalfBecker]

Can you try a docker restart egroupware-push

Ralf

[somogyi]

I already tried restart container. its not resolve the problem.

If i start manually server.php (in egroupware-push container) with “php server.php” command it start properly.

Z

[somogyi]

Okay, i solved this isseu with zfs exec permission.

But the push still not working, when i create an event it snot updated on the web:

server: handshake success with XXXX, FAILED with unknown sessionid=XXXXXXXXXXXXXXXX

[somogyi]

Update:

After clear browser cache, its working properly.

Thanks for your help.

Z

[RalfBecker]

Okay, i solved this isseu with zfs exec permission.

Can you elaborate what’s wrong and how you fixed it?

Ralf

[somogyi]

On ZFS filesystem, the docker create ZFS mountpoints. If on that mount points are not contain “EXEC=on” parameter, it not allows you to execute scripts on this “partitions”. That was the problem. The server.php in swoole container was not exec permission.

[RalfBecker]

Hmm, exec permission is only needed, if you have a #!/usr/bin/php in it and not calling it via: php server.php as we do.

I don’t mind giving server.php execute permission, if that helps with docker on zfs …

Ralf

[somogyi]

Hmm, exec permission is only needed, if you have a #!/usr/bin/php in it and not calling it via: php server.php as we do.

Yes, the swoole supervisor service only run “./server.php” not “php server.php”:
[program:swoole]
command = /var/www/server.php
user = root
autostart = true
autorestart = true
stdout_logfile=/proc/self/fd/1
stdout_logfile_maxbytes=0
stderr_logfile=/proc/self/fd/1
stderr_logfile_maxbytes=0

And the interpreter: #!/usr/bin/env php

Z