Help NodeBB doesn't work after upgrade to 1.3.0

[Master]

@PitaJ!

[PitaJ]

@Master oh shit sorry I should have said git reset --hard origin/v1.x.x

Luckily it doesn't look like any changes were made to the database.

[Master]

I made database backup before update

[Master]

@PitaJ

[Master]

Finally I updated the nodebb but still doesn't work.

[Master]

please can someone help me ?

[yariplus]

It looks like you may have too many processes running. Have you tried rebooting your system or increasing the processes limit?

[Master]

@yariplus

I asked support and they said it's only 8 tasks running and application even doesn't start, because nothing is listening on the port, which is directed on vhost domain.

[Bri]

@Master what is the output of:

free -m

[Master]

[PitaJ]

@Master that looks like your problem right there. 128 MB of RAM likely isn't enough. Unless I'm misreading and it's really 128 GB of ram.

[Master]

@PitaJ

Again i asked support and they said there is much ram.

Fragment error log Apache:

[Sun Nov 20 16:03:19.831365 2016] [proxy:error] [pid 10714:tid 140663819409152] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4567 (127.0.0.1) failed
[Sun Nov 20 16:03:19.831388 2016] [proxy:error] [pid 10714:tid 140663819409152] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sun Nov 20 16:03:19.831392 2016] [proxy_http:error] [pid 10714:tid 140663819409152] [client 163.172.66.81:59430] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Sun Nov 20 16:03:19.831424 2016] [proxy:error] [pid 10714:tid 140663819409152] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:03:42.597237 2016] [proxy:error] [pid 10714:tid 140663685125888] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:03:42.597297 2016] [proxy:error] [pid 10714:tid 140663685125888] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:03:43.159781 2016] [proxy:error] [pid 3918:tid 140663811016448] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4567 (127.0.0.1) failed
[Sun Nov 20 16:03:43.159802 2016] [proxy:error] [pid 3918:tid 140663811016448] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sun Nov 20 16:03:43.159820 2016] [proxy_http:error] [pid 3918:tid 140663811016448] [client 107.152.234.82:58716] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Sun Nov 20 16:03:43.159853 2016] [proxy:error] [pid 3918:tid 140663811016448] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:04:52.394293 2016] [proxy:error] [pid 10714:tid 140663962085120] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4567 (127.0.0.1) failed
[Sun Nov 20 16:04:52.394317 2016] [proxy:error] [pid 10714:tid 140663962085120] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sun Nov 20 16:04:52.394324 2016] [proxy_http:error] [pid 10714:tid 140663962085120] [client 91.189.140.211:54375] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Sun Nov 20 16:04:52.394368 2016] [proxy:error] [pid 10714:tid 140663962085120] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:04:52.606426 2016] [proxy:error] [pid 3918:tid 140663718696704] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4567 (127.0.0.1) failed
[Sun Nov 20 16:04:52.606447 2016] [proxy:error] [pid 3918:tid 140663718696704] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sun Nov 20 16:04:52.606451 2016] [proxy_http:error] [pid 3918:tid 140663718696704] [client 91.189.140.211:54374] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Sun Nov 20 16:04:52.606483 2016] [proxy:error] [pid 3918:tid 140663718696704] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:04:52.968425 2016] [proxy:error] [pid 10714:tid 140664079582976] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:04:52.968477 2016] [proxy:error] [pid 10714:tid 140664079582976] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:06:34.877612 2016] [proxy:error] [pid 10714:tid 140664012441344] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4567 (127.0.0.1) failed
[Sun Nov 20 16:06:34.877636 2016] [proxy:error] [pid 10714:tid 140664012441344] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sun Nov 20 16:06:34.877640 2016] [proxy_http:error] [pid 10714:tid 140664012441344] [client 83.20.140.21:41345] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Sun Nov 20 16:06:34.877675 2016] [proxy:error] [pid 10714:tid 140664012441344] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.354414 2016] [proxy:error] [pid 10714:tid 140664012441344] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.354476 2016] [proxy:error] [pid 10714:tid 140664012441344] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.354535 2016] [proxy:error] [pid 10714:tid 140664171902720] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.354569 2016] [proxy:error] [pid 10714:tid 140664171902720] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.361511 2016] [proxy:error] [pid 10714:tid 140663811016448] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.361514 2016] [proxy:error] [pid 10714:tid 140664071190272] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.361550 2016] [proxy:error] [pid 10714:tid 140663811016448] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.361555 2016] [proxy:error] [pid 10714:tid 140664071190272] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.368608 2016] [proxy:error] [pid 10714:tid 140663735482112] AH00940: HTTP: disabled connection for (127.0.0.1)
[Sun Nov 20 16:07:01.368660 2016] [proxy:error] [pid 10714:tid 140663735482112] AH00940: HTTP: disabled connection for (127.0.0.1)

[PitaJ]

@Master well how much RAM do you have? Because that readout clearly says 128 MB, which isn't enough.

Of course your apache log is gonna fail to connect. We've already established that the NodeBB thread isn't starting up.

[Master]

@PitaJ Its 128 GB

[PitaJ]

@Master that's an insane amount. Like an entire physical server's worth of RAM. It would cost a fortune, and is likely completely unnecessary. I'm very skeptical.

But let's assume you do have 128GB. The log says that 118 GB is currently in use. What's using all of that memory? Whatever process is doing that must be also bogging down your CPU with a ton of threads as well, which is likely blocking out node.js from working.

[Master]

@PitaJ It is a shared hosting(www) ram is distributed to all users.

[PitaJ]

@Master try running top and show the output here

[Master]

@PitaJ

[PitaJ]

@Master try killing those node processes

[Master]

@PitaJ said in Help NodeBB doesn't work after upgrade to 1.3.0:

i love you bro