@keng-her Thank you. I'll back everything up and try that and report back.
NodeBB wont stay up using systemctl
@julian Agreed... if it is documented, its documented
Thanks @Adam-Poniatowski -- sorry for the delay
@julian not a problem
Duke last edited by Duke
@adam-poniatowski I was thinking about your post and it was bugging me as I was sure i'd seen this command in the docs. Flipping through them, I found the command you describe but its in the wrong spot (install as opposed to auto run). Also realised we never actually tell the user to start Mongod service when describing how to make nodeBB autorun.
Which Ubuntu version? Pretty sure when we wrote up the docs mongod started itself on install.
In any case, we'll get that updated.
Duke last edited by
@julian Ubuntu 16.04.3 LTS
I will update the ticket
@duke The "After=" should be in the [unit] field, as you are specifying it to start after specified services. By default (sort of) it is network.service, so that the service will start, only after the network service has started (however, it does not check if there is network connectivity, just if the service has started).
I hope that clarifies things. Maybe one should add that to the docs, as some people will think that the After=network.service, anyotherservice.service will actually checks network connectivity or that the service is working.
Perhaps it's best if you edit the docs yourself? GitHub has a built-in editor that you can use to make changes
I created a pull request for the additions
teh_g last edited by
The new systemctl block in the documentation works wonderfully.
The ONE time that NodeBB went down on my forums, I was on vacation in Mexico. Logging into the server from my phone was atrocious. Now systemctl can do all the work for me