Global Moderators

@sampo2910 yeah it sounds like you definitely have a service running. What OS are you using?

@sampo2910 please try killing all node processes as described in this thread:

And do so as root

@sampo2910 said in New Install - Plugin Page Freezes:

OMG how stupid do I feel now with the mail 'problem'. It was off! I toggled to on and email success and it came through.

In my defence I was also thinking that needed to be on if i used Gmail,Yahoo i.e. external email server. Of course how you read it. Happy that that side of live is working.

It enables the SMTP transport. It's necessary no matter what service you choose, including a custom one.

@sampo2910

Even if I reboot the machine this 'rogue' process will start again? How can I prevent that ?

The only way this could happen is if you have a service set up or something. What OS are you on?

@sampo2910 as I said, it looks like you have a rogue process. Sometimes one gets left behind and ./nodebb stop can't kill it. You'll need to manually kill it instead. It's easiest to kill all node processes. Then you'll be able to start it back up.

@phenomlab glad that'll work for you.

Would you mind participating in some more debug for this down the line? There's an alternative package for starting the daemon that I'm wondering might work for you.

@phenomlab ./nodebb slog just runs ./nodebb start then shows the log with tail. Nothing fancy. When you quit the command, you're just exiting tail, NodeBB isn't stopped.

The "production" equivalent of ./nodebb dev is node app. There are many ways you can set it up to run as a daemon. For instance, setting up a systemd service.

@phenomlab it must be something to do with the daemon stuff.

https://github.com/NodeBB/NodeBB/blob/ac1b9692f2bccbf8420224f152535c238404ef53/loader.js#L217

Can you try adding console.logs through there to try and find where the script stops executing for you?

Does it still work with daemon:false or does that no longer help?

@phenomlab I don't know what to tell you. It's not lying about the address being in use.

Does it work if you run node app? If not, it's definitely a rogue process left running on that port.