Trouble daemonizing crono on production Ubuntu server #21

New Issue

2025-12-29T00:21:22+01:00

adam commented

2025-12-29 00:21:22 +01:00

Originally created by @Epigene on GitHub (Jun 18, 2015).

If I run bundle exec crono -e production in project root on production server, it works.
ps aux | grep crono also returns the process

However, if I try to daemonize the process (so I can write mina deployment task), it fails silently.
I have tried:

bundle exec crono -e production -d
bundle exec crono -e production -d true
bundle exec crono -e production --daemonize
bundle exec crono -e production --daemonize true
bundle exec crono -d -e production
bundle exec crono -d true -e production
bundle exec crono --daemonize -e production
bundle exec crono --daemonize true -e production

ps aux | grep crono returns only the grep process after every one of those commands.
What is going on?

Originally created by @Epigene on GitHub (Jun 18, 2015). If I run `bundle exec crono -e production` in project root on production server, it works. `ps aux | grep crono` also returns the process However, if I try to daemonize the process (so I can write mina deployment task), it fails silently. I have tried: ``` bundle exec crono -e production -d bundle exec crono -e production -d true bundle exec crono -e production --daemonize bundle exec crono -e production --daemonize true bundle exec crono -d -e production bundle exec crono -d true -e production bundle exec crono --daemonize -e production bundle exec crono --daemonize true -e production ``` `ps aux | grep crono` returns only the grep process after every one of those commands. What is going on?

adam closed this issue

2025-12-29 00:21:22 +01:00

adam commented

2025-12-29 00:21:22 +01:00

@plashchynski commented on GitHub (Jun 23, 2015):

Hello @Epigene
Could you check the log located at log/crono.log. Thank you.

@plashchynski commented on GitHub (Jun 23, 2015): Hello @Epigene Could you check the log located at `log/crono.log`. Thank you.

adam commented

2025-12-29 00:21:23 +01:00

@Epigene commented on GitHub (Jun 25, 2015):

Right, No such file or directory @ rb_sysopen ...
Crono could not access the default pidfile location at tmp/pids/crono.pid

Changed command to

bundle exec crono -e production -d --pidfile ../../shared/pids/crono.pid

@Epigene commented on GitHub (Jun 25, 2015): Right, `No such file or directory @ rb_sysopen ...` Crono could not access the default pidfile location at tmp/pids/crono.pid Changed command to ``` bundle exec crono -e production -d --pidfile ../../shared/pids/crono.pid ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/crono#21