@pitaj

Maybe Heroku doesnt allow the parameters like --no-silent --no-daemon

I think I should start nodeBB on my local server

@pitaj said in nodeBB crashed in Heroku:

Instead of using npm start try using node loader.js --no-silent --no-daemon

I have to create a Procfile since it's a mechanism for declaring what commands are run by the application's dynos on the Heroku platform.

Now restarted and run... still same error

2018-02-20T03:10:18.341534+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-20T03:10:18.341536+00:00 app[web.1]: > node loader.js
2018-02-20T03:10:18.341538+00:00 app[web.1]:
2018-02-20T03:10:17.893754+00:00 app[web.1]: [heroku-exec] Starting
2018-02-20T03:10:19.090256+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-20T03:10:19.091122+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-20T03:10:19.074011+00:00 heroku[web.1]: Process exited with status 0
2018-02-20T03:10:24.535096+00:00 heroku[web.1]: Starting process with command npm start
2018-02-20T03:10:26.340273+00:00 app[web.1]: [heroku-exec] Starting
2018-02-20T03:10:26.825112+00:00 app[web.1]:
2018-02-20T03:10:26.825145+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-20T03:10:26.825147+00:00 app[web.1]: > node loader.js
2018-02-20T03:10:26.825148+00:00 app[web.1]:
2018-02-20T03:10:27.504470+00:00 heroku[web.1]: Process exited with status 0
2018-02-20T03:10:27.621319+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-20T03:10:29.416802+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=dogforum.herokuapp.com request_id=5511f63d-f94e-41f1-985d-ddab4ebcbe4a fwd="68.105.135.152" dyno= connect= service= status=503 bytes= protocol=https
2018-02-20T03:10:30.711111+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=dogforum.herokuapp.com request_id=4e9ac226-3624-4641-ba5b-46feec970ef0 fwd="68.105.135.152" dyno= connect= service= status=503 bytes= protocol=https

@pitaj It's empty

I already did git pull

@pitaj

2018-02-17T01:46:46.323202+00:00 app[web.1]:
2018-02-17T01:46:46.970061+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-17T01:46:46.869023+00:00 heroku[web.1]: Process exited with status 0
2018-02-17T04:35:26.507307+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-17T04:35:31.798205+00:00 heroku[web.1]: Starting process with command npm start
2018-02-17T04:35:33.892913+00:00 app[web.1]:
2018-02-17T04:35:33.892943+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-17T04:35:33.892944+00:00 app[web.1]: > node loader.js
2018-02-17T04:35:33.892946+00:00 app[web.1]:
2018-02-17T04:35:34.509936+00:00 heroku[web.1]: Process exited with status 0
2018-02-17T04:35:34.524093+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-17T10:12:43.975257+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-17T10:12:50.463973+00:00 heroku[web.1]: Starting process with command npm start
2018-02-17T10:12:52.927234+00:00 app[web.1]:
2018-02-17T10:12:52.927249+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-17T10:12:52.927251+00:00 app[web.1]: > node loader.js
2018-02-17T10:12:52.927252+00:00 app[web.1]:
2018-02-17T10:12:53.673524+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-17T10:12:53.659530+00:00 heroku[web.1]: Process exited with status 0
2018-02-17T16:05:02.593814+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-17T16:05:09.530086+00:00 heroku[web.1]: Starting process with command npm start
2018-02-17T16:05:11.899798+00:00 app[web.1]:
2018-02-17T16:05:11.899817+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-17T16:05:11.899818+00:00 app[web.1]: > node loader.js
2018-02-17T16:05:11.899820+00:00 app[web.1]:
2018-02-17T16:05:12.769362+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-17T16:05:12.755323+00:00 heroku[web.1]: Process exited with status 0
2018-02-17T21:49:27.178136+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-17T21:49:35.939805+00:00 heroku[web.1]: Starting process with command npm start
2018-02-17T21:49:38.732697+00:00 app[web.1]:
2018-02-17T21:49:38.732715+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-17T21:49:38.732717+00:00 app[web.1]: > node loader.js
2018-02-17T21:49:38.732718+00:00 app[web.1]:
2018-02-17T21:49:39.655337+00:00 heroku[web.1]: Process exited with status 0
2018-02-17T21:49:39.674116+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-18T03:25:53.852201+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-18T03:26:01.695730+00:00 heroku[web.1]: Starting process with command npm start
2018-02-18T03:26:06.687406+00:00 app[web.1]:
2018-02-18T03:26:06.687431+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-18T03:26:06.687433+00:00 app[web.1]: > node loader.js
2018-02-18T03:26:06.687435+00:00 app[web.1]:
2018-02-18T03:26:09.088048+00:00 heroku[web.1]: Process exited with status 0
2018-02-18T03:26:09.098907+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-18T09:18:13.099574+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-18T09:18:19.198728+00:00 heroku[web.1]: Starting process with command npm start
2018-02-18T09:18:21.928046+00:00 app[web.1]:
2018-02-18T09:18:21.928079+00:00 app[web.1]:
2018-02-18T09:18:21.928076+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-18T09:18:21.928078+00:00 app[web.1]: > node loader.js
2018-02-18T09:18:22.616013+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-18T09:18:22.598117+00:00 heroku[web.1]: Process exited with status 0
2018-02-18T15:02:37.141844+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-18T15:02:44.682893+00:00 heroku[web.1]: Starting process with command npm start
2018-02-18T15:02:47.503713+00:00 app[web.1]:
2018-02-18T15:02:47.503737+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-18T15:02:47.503739+00:00 app[web.1]: > node loader.js
2018-02-18T15:02:47.503740+00:00 app[web.1]:
2018-02-18T15:02:48.576244+00:00 heroku[web.1]: Process exited with status 0
2018-02-18T15:02:48.710504+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-18T20:31:01.055167+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-18T20:31:06.797386+00:00 heroku[web.1]: Starting process with command npm start
2018-02-18T20:31:08.891992+00:00 app[web.1]:
2018-02-18T20:31:08.892010+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-18T20:31:08.892011+00:00 app[web.1]: > node loader.js
2018-02-18T20:31:08.892013+00:00 app[web.1]:
2018-02-18T20:31:09.692891+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-18T20:31:09.677780+00:00 heroku[web.1]: Process exited with status 0
2018-02-19T02:07:18.249009+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-19T02:07:23.486623+00:00 heroku[web.1]: Starting process with command npm start
2018-02-19T02:07:25.193135+00:00 app[web.1]:
2018-02-19T02:07:25.193249+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-19T02:07:25.193251+00:00 app[web.1]: > node loader.js
2018-02-19T02:07:25.193253+00:00 app[web.1]:
2018-02-19T02:07:25.712206+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-19T02:07:25.700496+00:00 heroku[web.1]: Process exited with status 0
2018-02-19T07:59:38.405975+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-19T07:59:47.322557+00:00 heroku[web.1]: Starting process with command npm start
2018-02-19T07:59:50.342438+00:00 app[web.1]:
2018-02-19T07:59:50.342473+00:00 app[web.1]: > node loader.js
2018-02-19T07:59:50.342471+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-19T07:59:50.342474+00:00 app[web.1]:
2018-02-19T07:59:51.522117+00:00 heroku[web.1]: Process exited with status 0
2018-02-19T07:59:51.536913+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-19T14:07:54.826635+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-19T14:08:01.752853+00:00 heroku[web.1]: Starting process with command npm start
2018-02-19T14:08:04.987083+00:00 app[web.1]:
2018-02-19T14:08:04.987104+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-19T14:08:04.987105+00:00 app[web.1]: > node loader.js
2018-02-19T14:08:04.987107+00:00 app[web.1]:
2018-02-19T14:08:05.981558+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-19T14:08:05.969143+00:00 heroku[web.1]: Process exited with status 0
2018-02-19T20:00:22.269283+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-19T20:00:29.926317+00:00 heroku[web.1]: Starting process with command npm start
2018-02-19T20:00:33.133632+00:00 app[web.1]:
2018-02-19T20:00:33.133649+00:00 app[web.1]: > nodebb@1.5.3 start /app
2018-02-19T20:00:33.133651+00:00 app[web.1]: > node loader.js
2018-02-19T20:00:33.133652+00:00 app[web.1]:
2018-02-19T20:00:34.327517+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-19T20:00:34.310839+00:00 heroku[web.1]: Process exited with status 0
2018-02-19T21:46:58.490964+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=dogforum.herokuapp.com request_id=f1fc9e09-efcd-46ad-8fca-3b9a48e2b603 fwd="68.105.135.152" dyno= connect= service= status=503 bytes= protocol=https
2018-02-19T21:46:59.430161+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=dogforum.herokuapp.com request_id=78404713-1dfc-4876-a072-fbe8aca26906 fwd="68.105.135.152" dyno= connect= service= status=503 bytes= protocol=https

Bump, need to get this done

Ah I see, then it seems it's related to 503 error, not sure it happens to routes or database connection. Is there another way to check real logs?

EDIT: I found this page it's related to issue, but I dont understand this solution

https://github.com/NodeBB/NodeBB/issues/2131

StewartNoyce created this issue in NodeBB/NodeBB

closed Heroku install issue - app immediately crashes with H10 error code #2131

I followed this guide: https://nodebb.readthedocs.io/en/latest/installing/cloud/heroku.html

Apparently, build is succeded then I open this page and it says it's app error. I had no idea why and there are no details.

Then I went to check logs using CLI "heroku logs"

It seems it crashed, I dont know why it happened