first one would be pretty interesting, very blog-y
Looks great!! A few questions
Keep in mind the home page of the admin panel has a restart button
Carl last edited by
Ah yes I tried it but there seems to be a problem, it seems to stop nodebb but doesn't start it back up.
@Carl Thought it was just me this happened to. Clicking restart only stops it, nothing in the logs about it going down etc, have to run ./nodebb start for it to come back. Even with forever running.
Carl last edited by
Have you ever got this error when starting it back up
throw er; // Unhandled 'error' event
Error: write after end
at writeAfterEnd (_stream_writable.js:133:12)
at WriteStream.Writable.write (_stream_writable.js:181:5)
at write (_stream_readable.js:583:24)
at flow (_stream_readable.js:592:7)
at Socket.pipeOnReadable (stream_readable.js:624:5)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable (_stream_readable.js:408:10)
at emitReadable (_stream_readable.js:404:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)"
@Carl Not that I can recall, starts up fine when I run
./nodebb start, but the restart button just shuts it down.
@a_5mith How are you starting it in the first place?
./nodebb startshould set it up so the restart button works, hm...
@julian That's the one, ./nodebb start gets it going, clicking the restart button just kills it, sometimes putty drops the connection, sometimes it doesn't. Going back into SSH and running ./nodebb start again sets it up. Doesn't tell me the address is in use or anything like that. I haven't tested it since I imported 23k posts though, so not sure if that's got something to do with it. It's not a huge issue for me, I don't plan on restarting that often, and if I restart, it's not an issue to run nodebb start again from in SSH.
Thanks @Kamal-Patel @a_5mith That's really weird, since it works properly here... unless this is a new regression... has this only started happening recently?
@julian I just spun mine up two days ago, so yup, just started happening
@Kamal-Patel @a_5mith Should be fixed in latest code (and backported to v0.4.2)