A tip on resolving celery-mhn-beat fatal error

[usman habib]

Hi,

Please see below to on how to resolve mhn-celery-beat fatal error.

root@mhn-server:~# supervisorctl status
geoloc                           RUNNING    pid 2262, uptime 0:00:23
honeymap                         RUNNING    pid 2248, uptime 0:00:24
hpfeeds-broker                   RUNNING    pid 2284, uptime 0:00:22
hpfeeds-logger-splunk            RUNNING    pid 2241, uptime 0:00:25
mhn-celery-beat                  FATAL      Exited too quickly (process log may
have details)
mhn-celery-worker                RUNNING    pid 2087, uptime 0:11:56
mhn-collector                    RUNNING    pid 2278, uptime 0:00:22
mhn-uwsgi                        RUNNING    pid 2271, uptime 0:00:22
mnemosyne                        RUNNING    pid 2252, uptime 0:00:23

root@mhn-server:~# tail /var/log/mhn/mhn-celery-beat.err
ERROR: Pidfile (celerybeat.pid) already exists.
Seems we're already running? (pid: 1176)
ERROR: Pidfile (celerybeat.pid) already exists.
Seems we're already running? (pid: 1176)
ERROR: Pidfile (celerybeat.pid) already exists.
Seems we're already running? (pid: 1176)
ERROR: Pidfile (celerybeat.pid) already exists.
Seems we're already running? (pid: 1176)
ERROR: Pidfile (celerybeat.pid) already exists.
Seems we're already running? (pid: 1176)

root@mhn-server:~# kill -9 1176

root@mhn-server:~# supervisorctl start mhn-celery-beat
mhn-celery-beat: started

root@mhn-server:~# supervisorctl status
geoloc                           RUNNING    pid 2262, uptime 0:14:35
honeymap                         RUNNING    pid 2248, uptime 0:14:36
hpfeeds-broker                   RUNNING    pid 2284, uptime 0:14:34
hpfeeds-logger-splunk            RUNNING    pid 2241, uptime 0:14:37
mhn-celery-beat                  RUNNING    pid 2313, uptime 0:13:40
mhn-celery-worker                RUNNING    pid 2087, uptime 0:26:08
mhn-collector                    RUNNING    pid 2278, uptime 0:14:34
mhn-uwsgi                        RUNNING    pid 2271, uptime 0:14:34
mnemosyne                        RUNNING    pid 2252, uptime 0:14:35

Hopefully, it'll resolve your issue.

[Gabe]

Awesome thanks. Solved the issue.