Andrew Clayton

Couple of quick questions 1) Is Unit running as a **daemon**? I.e **without** the *--no-daemon* command line argument. 2) Does the *unit* user have write access to those log files?

Please remove the **--no-daemon** option. The stdout/stderr options only take effect when running as a daemon. (~Yes, our documentation is wrong!~ now fixed).

Closing as NOTABUG. Feel free to re-open if you're still having issues.

Also change the **Type** from simple to **forking** That works for me on Fedora... (**NOTE:** You should probably copy /usr/lib/systemd/system/unit.service into **/etc/systemd/system/** and edit that one instead which will override...

@yosefy I currently see no reason why we shouldn't switch back to _forking_. However in the meantime, create the file ```/etc/systemd/system/unit.service``` with the following contents ``` [Unit] Description=NGINX Unit Wants=network-online.target...

Re-opening to raise visibility...

Are you able to run Unit as a [daemon(7)](https://man7.org/linux/man-pages/man7/daemon.7.html)? I.e _without_ the `--no-daemon` option. If not, is there some fundamental reason why?

Are you saying that at some point Unit stops serving requests? Also, JFYI, this doesn't do what I'm _guessing_ you think it does ```json "isolation": { "namespaces": { "cgroup": true...

On Tue, 05 Dec 2023 01:17:58 -0800 owan ***@***.***> wrote: > yes, my unit stops serving requests If you're able to distil this down to a simple reproducer that would...

On Tue, 05 Dec 2023 17:43:36 -0800 owan ***@***.***> wrote: > I don't know how to do simple reproducer > because this problem is not always happen > does ther...