Ubuntu 16.04 Error After Reboot

[Christopher Bruder]

I'm running Ubuntu 16.04.  Al we did was a reboot of the server and it died.  If I do sudo supervisorctl status:


username@server:~$ sudo supervisorctl status
geoloc                           RUNNING   pid 1120, uptime 0:03:25
honeymap                         RUNNING   pid 1124, uptime 0:03:25
hpfeeds-broker                   FATAL     Exited too quickly (process log may have details)
mhn-celery-beat                  RUNNING   pid 1117, uptime 0:03:25
mhn-celery-worker                FATAL     Exited too quickly (process log may have details)
mhn-collector                    FATAL     Exited too quickly (process log may have details)
mhn-uwsgi                        RUNNING   pid 1121, uptime 0:03:25
mnemosyne                        FATAL     Exited too quickly (process log may have details)

So I did some googling and found a solution for the mhn-celery-worker:

cd /var/log/mhn/
sudo chown www-data mhn.log
sudo supervisorctl start mhn-celery-worker

But everything else is still showing FATAL no matter what I tried for them

username@server:~$ sudo supervisorctl status
geoloc                           RUNNING   pid 1120, uptime 0:03:25
honeymap                         RUNNING   pid 1124, uptime 0:03:25
hpfeeds-broker                   FATAL     Exited too quickly (process log may have details)
mhn-celery-beat                  RUNNING   pid 1117, uptime 0:03:25
mhn-celery-worker                RUNNING   pid 1122, uptime 0:03:25
mhn-collector                    FATAL     Exited too quickly (process log may have details)
mhn-uwsgi                        RUNNING   pid 1121, uptime 0:03:25
mnemosyne                        FATAL     Exited too quickly (process log may have details)



Any ideas?

[Brady Sullivan]

'sudo systemctl start mongodb'
'sudo supervisorctl restart all'

This should start most of them up again. mhn-celery-worker is still
fatal on my end so I'll post a solution for that one when I figure it
out.

> --
> You received this message because you are subscribed to the Google Groups
> "Modern Honey Network" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to modern-honey-net...@googlegroups.com.
> To post to this group, send email to modern-hon...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/modern-honey-network/3893a747-06c8-49f1-ae7e-32034204f27c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Christopher Bruder]

Looks like that worked some what, but it broke mhn-celeary-worker now.  Looking forward to your fix when you fix it :)

username@server:~$ sudo systemctl start mongodb
[sudo] password for username:

username@server:~$ sudo supervisorctl restart all
mhn-celery-beat: stopped
geoloc: stopped
mhn-uwsgi: stopped
honeymap: stopped
mhn-celery-worker: stopped
mhn-celery-worker: ERROR (spawn error)
mhn-celery-beat: started
hpfeeds-broker: started
mnemosyne: started
geoloc: started
mhn-uwsgi: started
mhn-collector: started
honeymap: started

> email to modern-honey-network+unsub...@googlegroups.com.

[Brady Sullivan]

Also, consider 'sudo systemctl enable mongodb' to enable mongodb on startup.

>> > email to modern-honey-net...@googlegroups.com.

>> > To post to this group, send email to modern-hon...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/modern-honey-network/3893a747-06c8-49f1-ae7e-32034204f27c%40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>
>

> --
> You received this message because you are subscribed to the Google Groups
> "Modern Honey Network" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to modern-honey-net...@googlegroups.com.

> To post to this group, send email to modern-hon...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/modern-honey-network/e790247e-3592-459c-a99f-280a2bae7775%40googlegroups.com.

[Christopher Bruder]

Done :)

[Christopher Bruder]

Thanks to Brady, the fix is:

sudo systemctl start mongodb
sudo supervisorctl restart all

sudo systemctl enable mongodb