nginx unit php server stops responding when using supervisor #1310

kapyaar · 2024-06-10T01:51:57Z

kapyaar
Jun 10, 2024

I have an nginx Unit+Php container with the following docker file

FROM unit:1.32.1-php8.2
RUN apt-get update && apt-get install -y supervisor
EXPOSE 80
WORKDIR /var/www/html/
COPY config.json /docker-entrypoint.d/config.json

And If I run this, it works fine, index.php loads correctly. Now, I want to use supervisor to start a php script to run as daemon. This is a kafkaConsumer with a while loop. Below are the files

[supervisord]
nodaemon=true

[program:nginx-unit]
command=unitd --no-daemon
stdout_logfile_maxbytes = 0
stderr_logfile_maxbytes = 0
stdout_logfile=/var/log/unit.log
stderr_logfile=/var/log/unit.log
autostart=true
autorestart=true


[program:kafkaTestConsumer]
command=php /var/www/html/PhpScriptThatRunsContinuously.php
autostart=true
directory=/var/www/html/
autorestart=true
stdout_logfile=/dev/stdout
stderr_logfile=/dev/stderr
stdout_maxbytes=0 # need these lines due to [https://github.com/Supervisor/supervisor/issues/935][1]
stderr_maxbytes=0
stdout_logfile_maxbytes = 0
stderr_logfile_maxbytes = 0

And a simple php script for testing.

<?php
while(1){
	sleep(3);
	echo ".";
}
?>

However, If I add the following line to Dockerfile to start supervisor,

CMD ["/usr/bin/supervisord", "-c", "/etc/supervisor/conf.d/supervisord.conf"]

Then, the daemon php script does start, but the php server (http://localhost/) stops responding, with the following message

localhost didn’t send any data.
ERR_EMPTY_RESPONSE

Any help much appreciated.

Answered by lcrilly

Jun 10, 2024

OK, looks like unitd is running :)

But there's no sign of any configuration being applied. I would expect to see

phpApp  | 2024/06/10 13:17:16 [info] 2915#16842233 "php" application started

I suspect that when you added

CMD ["/usr/bin/supervisord", "-c", "/etc/supervisor/conf.d/supervisord.conf"]

it replaced the default CMD which is to run the Unit entrypoint script.

So now you have both services but Unit has an empty configuration. Confirm by running

docker exec -ti <CONTAINER_ID> curl --unix-socket /var/run/control.unit.sock _/config

To resolve this, you'll need to apply the configuration in the Dockerfile. I recommend

COPY config.json init.json
RUN nohup /bin/sh -c "unitd --no-daemo…

View full answer

lcrilly · 2024-06-10T06:56:48Z

lcrilly
Jun 10, 2024
Collaborator

Which service is listening on port 80?

Can you share your Unit configuration?

0 replies

kapyaar · 2024-06-10T11:48:15Z

kapyaar
Jun 10, 2024
Author

Sorry, I should have added it in the first place.

{
  "listeners": {
    "*:80": {
      "pass": "applications/php"
    }
  },
  "applications": {
    "php": {
      "type": "php",
      "root": "/var/www/html/",
      "processes": 1,
      "index":"index.php"
    }
  }
}

Compose

services:
  php:
    build:
      context: .
      dockerfile: Dockerfile
    working_dir: /var/www/html/
    container_name: phpApp
    ports:
      - 80:80
    volumes:
      - .:/var/www/html/

1 reply

lcrilly Jun 10, 2024
Collaborator

How do you know that Unit started successfully?
Is supervisord running as root and starting unitd as root?

Suggest examining the container logs.

kapyaar · 2024-06-10T12:18:11Z

kapyaar
Jun 10, 2024
Author

I tried with user=root, www-data, unit, etc in the supervisord. If I specified user, and it was anything other than root, then the log would show permission denied, so I just left it without specifying the user.

And for how I knew the daemon php was running? My original phpdaemon is a bit longer, with a function that writes some text with timestamp to a txt file on each iteration, and I can do cat someTextFile.txt from inside the container, and see that the file keeps getting new lines with timestamps.

5 replies

kapyaar Jun 10, 2024
Author

Also, In the supervisord logs, It does says user 0. I am not sure if this should be saying "root"?


2024-06-10 12:25:03,813 INFO Set uid to user 0 succeeded
2024-06-10 12:25:03,820 INFO supervisord started with pid 1
2024-06-10 12:25:04,823 INFO spawned: 'nginx-unit' with pid 7
2024-06-10 12:25:04,826 INFO spawned: 'kafkaTestConsumer' with pid 8
2024-06-10 12:25:05,841 INFO success: kafkaTestConsumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-10 12:25:14,853 INFO success: nginx-unit entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

lcrilly Jun 10, 2024
Collaborator

Do you have any evidence of unitd starting? You might want to try command=unitd --no-daemon --log /dev/stderr

kapyaar Jun 10, 2024
Author

It did say so in the supervisord logs. but I tried what you suggested,

[program:nginx-unit]
command=unitd --no-daemon --log /dev/stdout

and on build,

Attaching to phpApp
phpApp  | 2024-06-10 13:17:15,644 INFO Set uid to user 0 succeeded
phpApp  | 2024-06-10 13:17:15,647 INFO supervisord started with pid 1
phpApp  | 2024-06-10 13:17:16,651 INFO spawned: 'nginx-unit' with pid 8
phpApp  | 2024-06-10 13:17:16,653 INFO spawned: 'kafkaTestConsumer' with pid 9
phpApp  | 2024/06/10 13:17:16 [info] 8#8 unit 1.32.1 started
phpApp  | 2024/06/10 13:17:16 [info] 10#10 discovery started
phpApp  | 2024/06/10 13:17:16 [notice] 10#10 module: php 8.2.20 "/usr/lib/unit/modules/php.unit.so"
phpApp  | 2024/06/10 13:17:16 [info] 8#8 controller started
phpApp  | 2024/06/10 13:17:16 [notice] 8#8 process 10 exited with code 0
phpApp  | 2024/06/10 13:17:16 [info] 12#12 router started
phpApp  | 2024/06/10 13:17:16 [info] 12#12 OpenSSL 1.1.1w  11 Sep 2023, 1010117f
phpApp  | 2024-06-10 13:17:17,667 INFO success: kafkaTestConsumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
phpApp  | .Data appended to the file successfully..Data appended to the file successfully..Data appended to the file successfully.2024-06-10 13:17:26,682 INFO success: nginx-unit entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

kapyaar Jun 10, 2024
Author

I would think

INFO success: nginx-unit entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

looks like unitd is running? A lingering thought I have is, without the CMD[..] for supervisord, nginx unitd starts based on config.json. When supervisord does another unitd --no-daemon may be it is conflicting with an already running unitd? Just a wild thought. Sorry, I am not expert on this.

kapyaar Jun 10, 2024
Author

If it helps, here is the folder. If your time permits, kindly give it a shot. May be it is something on my setup, who knows.
UnitD-Test.zip

lcrilly · 2024-06-10T13:39:24Z

lcrilly
Jun 10, 2024
Collaborator

OK, looks like unitd is running :)

But there's no sign of any configuration being applied. I would expect to see

phpApp  | 2024/06/10 13:17:16 [info] 2915#16842233 "php" application started

I suspect that when you added

CMD ["/usr/bin/supervisord", "-c", "/etc/supervisor/conf.d/supervisord.conf"]

it replaced the default CMD which is to run the Unit entrypoint script.

So now you have both services but Unit has an empty configuration. Confirm by running

docker exec -ti <CONTAINER_ID> curl --unix-socket /var/run/control.unit.sock _/config

To resolve this, you'll need to apply the configuration in the Dockerfile. I recommend

COPY config.json init.json
RUN nohup /bin/sh -c "unitd --no-daemon --pid init.pid --log /dev/stdout --control unix:init.unit.sock &" && \
    curl -fsX PUT [email protected] --unix-socket init.unit.sock _/config && \
    rm init.*

8 replies

lcrilly Jun 10, 2024
Collaborator

Could it be as simple as a missing file extension (.pem) on

curl -fsX PUT --data-binary @cert-bundle --unix-socket init.unit.sock /certificates/cert-bundle

kapyaar Jun 10, 2024
Author

I had the extension originally, but since the config file only takes the name (without the extension), I was trying it without the extension too. The one below also fails (along with the rest of the original from you)

curl -fsX PUT --data-binary @cert-bundle.pem --unix-socket init.unit.sock /certificates/cert-bundle.pem && \

I tried a bunch of iterations with logging, delay, etc (as per chatgpt suggestions) but all seems to fail. Here is the last one I tried.

RUN mkdir -p /certificates && \
    chmod 644 cert-bundle.pem && \
    cat cert-bundle.pem && \
    nohup /bin/sh -c "unitd --no-daemon --pid init.pid --log /dev/stdout --control unix:init.unit.sock &" && \
    sleep 2 && \
    ls -l init.unit.sock && \
    curl -v --unix-socket init.unit.sock http://localhost/ || { echo 'Server status check failed'; exit 1; } && \
    curl -v -H "Content-Type: application/octet-stream" -fsX PUT --data-binary @cert-bundle.pem --unix-socket init.unit.sock /certificates/cert-bundle.pem || { echo 'Certificate upload failed'; exit 1; } && \
    curl -v -fsX PUT [email protected] --unix-socket init.unit.sock _/config || { echo 'Configuration upload failed'; exit 1; } && \
    rm init.*

And here is the output

 => CACHED [php 13/16] COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf                                                                       0.0s
 => CACHED [php 14/16] COPY config/cert-bundle.pem cert-bundle.pem                                                                                         0.0s
 => CACHED [php 15/16] COPY config.json init.json                                                                                                          0.0s
 => ERROR [php 16/16] RUN mkdir -p /certificates &&     chmod 644 cert-bundle.pem &&     cat cert-bundle.pem &&     nohup /bin/sh -c "unitd --no-daemon -  2.3s
------
 > [php 16/16] RUN mkdir -p /certificates &&     chmod 644 cert-bundle.pem &&     cat cert-bundle.pem &&     nohup /bin/sh -c "unitd --no-daemon --pid init.pid --log /dev/stdout --control unix:init.unit.sock &" &&     sleep 2 &&     ls -l init.unit.sock &&     curl -v --unix-socket init.unit.sock http://localhost/ || { echo 'Server status check failed'; exit 1; } &&     curl -v -H "Content-Type: application/octet-stream" -fsX PUT --data-binary @cert-bundle.pem --unix-socket init.unit.sock /certificates/cert-bundle.pem || { echo 'Certificate upload failed'; exit 1; } &&     curl -v -fsX PUT [email protected] --unix-socket init.unit.sock _/config || { echo 'Configuration upload failed'; exit 1; } &&     rm init.*:
0.212 -----BEGIN PRIVATE KEY-----
0.212 MIIJQQIBADANBgkqhkiG9w0BAQEFAASCCSswggknAgEAAoICAQDzW7+SwVudvkjW
0.212 PSSza66M07T1qojFqRfkFPDxcn7PyrVqouXNfOina+YpQrV7UI11wlY/TwlsLykk
----more lines.......
0.212 J0NOHfL3nNYybj5fObMejjywsFyl
0.212 -----END PRIVATE KEY-----
0.212
0.212 -----BEGIN CERTIFICATE-----
0.212 MIIFlzCCA38CFD9632h52T2z5SNOd0zyH0svRKLVMA0GCSqGSIb3DQEBCwUAMIGH
0.212 MQswCQYDVQQGEwJVUzELMAkGA1UECAwCTlkxEDAOBgNVBAcMB0JVRkZBTE8xEDAO
------morelines......
0.212 e6i+KMOesypmxE+BMQVtQyOXIjsaNW54xHieUZJJlkqX7HxVU+vPuuX8Ag==
0.212 -----END CERTIFICATE-----
0.217 2024/06/10 18:21:27 [info] 11#11 unit 1.32.1 started
0.218 2024/06/10 18:21:27 [info] 13#13 discovery started
0.227 2024/06/10 18:21:27 [notice] 13#13 module: php 8.2.20 "/usr/lib/unit/modules/php.unit.so"
0.228 2024/06/10 18:21:27 [info] 11#11 controller started
0.228 2024/06/10 18:21:27 [notice] 11#11 process 13 exited with code 0
0.228 2024/06/10 18:21:27 [info] 15#15 router started
0.230 2024/06/10 18:21:27 [info] 15#15 OpenSSL 1.1.1w  11 Sep 2023, 1010117f
2.217 srw------- 1 root root 0 Jun 10 18:21 init.unit.sock
2.224 *   Trying init.unit.sock:0...
2.224   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
2.224                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (init.unit.sock.tmp) port 80 (#0)
2.224 > GET / HTTP/1.1
2.224 > Host: localhost
2.224 > User-Agent: curl/7.74.0
2.224 > Accept: */*
2.224 >
2.224 * Mark bundle as not supporting multiuse
2.224 < HTTP/1.1 200 OK
2.224 < Server: Unit/1.32.1
2.224 < Date: Mon, 10 Jun 2024 18:21:29 GMT
2.224 < Content-Type: application/json
2.224 < Content-Length: 303
2.224 < Connection: close
2.224 <
2.224 { [303 bytes data]
100   303  100   303    0     0   295k    {
2.224   "certificates": {},
2.224   "js_modules": {},
2.224   "config": {
2.224           "listeners": {},
2.224           "routes": [],
2.224           "applications": {}
2.224   },
2.224
2.224   "status": {
2.224           "connections": {
2.224                   "accepted": 0,
2.224                   "active": 0,
2.224                   "idle": 0,
2.224                   "closed": 0
2.224           },
2.224
2.224           "requests": {
2.224                   "total": 0
2.224           },
2.224
2.224           "applications": {}
2.224   }
2.224 }
2.224   0 --:--:-- --:--:-- --:--:--  295k
2.224 * Closing connection 0
2.229 * Closing connection -1
2.229 Certificate upload failed
------
failed to solve: process "/bin/sh -c mkdir -p /certificates &&     chmod 644 cert-bundle.pem &&     cat cert-bundle.pem &&     nohup /bin/sh -c \"unitd --no-daemon --pid init.pid --log /dev/stdout --control unix:init.unit.sock &\" &&     sleep 2 &&     ls -l init.unit.sock &&     curl -v --unix-socket init.unit.sock http://localhost/ || { echo 'Server status check failed'; exit 1; } &&     curl -v -H \"Content-Type: application/octet-stream\" -fsX PUT --data-binary @cert-bundle.pem --unix-socket init.unit.sock /certificates/cert-bundle.pem || { echo 'Certificate upload failed'; exit 1; } &&     curl -v -fsX PUT [email protected] --unix-socket init.unit.sock _/config || { echo 'Configuration upload failed'; exit 1; } &&     rm init.*" did not complete successfully: exit code: 1

The way you are applying the init.json, Is it the /config folder that saves the config? I tried putting _/config as the target foldr for the cert-bundle.pem upload line, but that did nt seem to help either.

kapyaar Jun 10, 2024
Author

Just in case it helps, attaching the cert file (renamed as .txt for attach purposes)
cert-bundle.txt

lcrilly Jun 11, 2024
Collaborator

You need the underscore (or something to represent the hostname) for every curl command.

Try this

COPY cert-bundle.pem init.pem
COPY config.json init.json
RUN nohup /bin/sh -c "unitd --no-daemon --pid init.pid --log /dev/stdout --control unix:init.unit.sock &" && \
    curl -fsX PUT --data-binary @init.pem --unix-socket init.unit.sock _/certificates/cert-bundle && \
    curl -fsX PUT [email protected] --unix-socket init.unit.sock _/config && \
    rm init.*

kapyaar Jun 11, 2024
Author

Thank you again! It is working as expected.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

nginx unit php server stops responding when using supervisor #1310

{{title}}

Replies: 4 comments 14 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

nginx unit php server stops responding when using supervisor #1310

kapyaar Jun 10, 2024

Replies: 4 comments · 14 replies

lcrilly Jun 10, 2024 Collaborator

kapyaar Jun 10, 2024 Author

lcrilly Jun 10, 2024 Collaborator

kapyaar Jun 10, 2024 Author

kapyaar Jun 10, 2024 Author

lcrilly Jun 10, 2024 Collaborator

kapyaar Jun 10, 2024 Author

kapyaar Jun 10, 2024 Author

kapyaar Jun 10, 2024 Author

lcrilly Jun 10, 2024 Collaborator

lcrilly Jun 10, 2024 Collaborator

kapyaar Jun 10, 2024 Author

kapyaar Jun 10, 2024 Author

lcrilly Jun 11, 2024 Collaborator

kapyaar Jun 11, 2024 Author

kapyaar
Jun 10, 2024

Replies: 4 comments 14 replies

lcrilly
Jun 10, 2024
Collaborator

kapyaar
Jun 10, 2024
Author

lcrilly Jun 10, 2024
Collaborator

kapyaar
Jun 10, 2024
Author

kapyaar Jun 10, 2024
Author

lcrilly Jun 10, 2024
Collaborator

kapyaar Jun 10, 2024
Author

kapyaar Jun 10, 2024
Author

kapyaar Jun 10, 2024
Author

lcrilly
Jun 10, 2024
Collaborator

lcrilly Jun 10, 2024
Collaborator

kapyaar Jun 10, 2024
Author

kapyaar Jun 10, 2024
Author

lcrilly Jun 11, 2024
Collaborator

kapyaar Jun 11, 2024
Author