[GH-ISSUE #1304] mapping log file to host: can start cypht container, but nginx exit #623

New issue

Closed

opened 2026-02-25 21:35:31 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:35:31 +03:00

Owner

Originally created by @europacafe on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1304

Originally assigned to: @SKB-TECH on GitHub.

💬 Question

I've been running Cypht 2.4.0 successfully, without mapping log file to host. However, when I map the /var/log to my host folder, Cypht can start but the supervisord.log file on my host indicates that nginx has exited.

I did this because my docker image built cypht from master can't start and I want to see the log file for inspection, so I tried mapping its log files with the working cypht/cypht:2.4.0 first.

2024-10-29 01:14:10,570 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-10-29 01:14:10,583 INFO supervisord started with pid 19
2024-10-29 01:14:11,587 INFO spawned: 'nginx' with pid 20
2024-10-29 01:14:11,591 INFO spawned: 'php-fpm' with pid 21
2024-10-29 01:14:11,617 WARN exited: nginx (exit status 1; not expected)
2024-10-29 01:14:12,728 INFO spawned: 'nginx' with pid 24
2024-10-29 01:14:12,729 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-29 01:14:12,745 WARN exited: nginx (exit status 1; not expected)
2024-10-29 01:14:14,751 INFO spawned: 'nginx' with pid 25
2024-10-29 01:14:14,766 WARN exited: nginx (exit status 1; not expected)
2024-10-29 01:14:17,773 INFO spawned: 'nginx' with pid 26
2024-10-29 01:14:17,788 WARN exited: nginx (exit status 1; not expected)
2024-10-29 01:14:18,789 INFO gave up: nginx entered FATAL state, too many start retries too quickly

Originally created by @europacafe on GitHub (Oct 29, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1304 Originally assigned to: @SKB-TECH on GitHub. ## 💬 Question I've been running Cypht 2.4.0 successfully, without mapping log file to host. However, when I map the /var/log to my host folder, Cypht can start but the supervisord.log file on my host indicates that nginx has exited. I did this because my docker image built cypht from master can't start and I want to see the log file for inspection, so I tried mapping its log files with the working cypht/cypht:2.4.0 first. ![image](https://github.com/user-attachments/assets/b3c550ce-c81b-4aaf-bd8d-f2c61bffc16a) ``` 2024-10-29 01:14:10,570 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2024-10-29 01:14:10,583 INFO supervisord started with pid 19 2024-10-29 01:14:11,587 INFO spawned: 'nginx' with pid 20 2024-10-29 01:14:11,591 INFO spawned: 'php-fpm' with pid 21 2024-10-29 01:14:11,617 WARN exited: nginx (exit status 1; not expected) 2024-10-29 01:14:12,728 INFO spawned: 'nginx' with pid 24 2024-10-29 01:14:12,729 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-29 01:14:12,745 WARN exited: nginx (exit status 1; not expected) 2024-10-29 01:14:14,751 INFO spawned: 'nginx' with pid 25 2024-10-29 01:14:14,766 WARN exited: nginx (exit status 1; not expected) 2024-10-29 01:14:17,773 INFO spawned: 'nginx' with pid 26 2024-10-29 01:14:17,788 WARN exited: nginx (exit status 1; not expected) 2024-10-29 01:14:18,789 INFO gave up: nginx entered FATAL state, too many start retries too quickly ```