mirror of
https://github.com/mthenw/frontail.git
synced 2026-04-26 02:05:57 +03:00
[GH-ISSUE #233] daemonize mode causes error on startup #152
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/frontail#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Mar 25, 2021).
Original GitHub issue: https://github.com/mthenw/frontail/issues/233
Hello,
we run frontail using following parameters:
-d option causes following error at startup:
log file (/tmp/frontail.log) is created, but empty,
pid file (/tmp/frontail.pid) isn't created at all,
I don't know it is connected, but very often daemonized frontail dies with no trace.
Btw. we use jetty+frontail in dockerized container based on Centos 8
@BauerPh commented on GitHub (Sep 16, 2021):
same here... somone has a fix for this?
Edit:
I've found a workaround:
start it with pm2
pm2 start frontail -- /var/log/logfile.log -t dark@ghost commented on GitHub (Sep 20, 2021):
Unfortunately project looks like a bit dead :/.
@lamuertepeluda commented on GitHub (Nov 10, 2021):
The fix is trivial... just stringify this line https://github.com/mthenw/frontail/blob/master/lib/daemonize.js#L68
e.g. from
to
@lamuertepeluda commented on GitHub (Nov 10, 2021):
While somebody takes care of this fix, I have found a workaround for daemonizing it in a Linux environment
damonize_frontail.shlaunch daemon:
damonize_frontail.sh <logfile>lately you can kill it like this
kill_frontail.shNon-linux user should find a similar workaround for their OSes.