The entire error below. I've been searching for some clues, but coming up empty handed and hoping someone can help. This is a fresh install on a debian 10 server.
2020-04-17T16:33:02.636Z [26376] - error: [build] admin control panel styles build failed 2020-04-17T16:33:02.639Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} ==================================================================================================================================== 2020-04-17T16:33:02.647Z [26376] - error: resource 'https://fonts.googleapis.com/css?family=Roboto:300,400,500,700' gave this Error: Error: socket hang up {"type":"File","filename":"/var/www/nodebb/nodebb/public/less/admin/paper/bootswatch.less","index":87,"line":5,"column":0,"callLine":null,"extract":["","@import url(\"https://fonts.googleapis.com/css?family=Roboto:300,400,500,700\");",""]} (node:26376) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:26376) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.Upgrade Problem from 1.12.2 to 1.13.3 build process never ends
-
Hi guys,
I tried to upgrade Nodebb from v1.12.2 to v1.13.3. After./nodebb upgradeeverything is fine except the build process, see screenshot for details. The process never ends after templates. I had a look in the folder and the data is there, but if I stop the process the frontend is broken.
The road to this point was quite bumpy. It took 3-4 attempts to come to this points. I had to clear a few npm-errors with missing dependencies. I tried to roll back completely from a backup, but the result is the same. I tried to upgrade to v1.14.x but the result is still the same.
System data:
OS: CentOS 7
Node v12.19.0
npm 6.14.8Does anybody know how to resolve this problem?
Thanks for any help!
Christian -
Hi @baris!
Great, the build fininshed with./nodebb build --series. Thanks!I will keep this command. After that I tried again
./nodebb upgradeand monitored withtopthe ram an CPU usage. The build process broke with an error
Error occurred during upgrade: Error: ENOMEM: not enough memory, read
I got this error the first time. In all my other attemps no error occured.How much ram is recommended for the usage of nodebb?
-
@suparomana Define "Usage"
How much provisioning did you allocate? In my experience, one needs a fair bit more RAM for builds than day to day operations. Ditto CPU horsepower. The --series flag is news to me as well. If that still takes too long to build: Do you have the ability to scale up provisioning for builds and then scale back down for day to day operations?
-
@baris 1gb ram is a lot.. we are running our forum on a shared host, so I can not increase the amount of ram.
Nodebb is running very smoothly and super fast there and we get a lot of positive feedback from our users. Our complete userbase is about 600 users big and we never had a performance issue in about 3 years.
I assume that the needed ram could be a problem for a lot of nodebb users. Do you think it would be possible to make the
--seriesoption available for thebuildfunction./nodebb build --series? If yes, where should I place this request?
-
@suparomana what are you asking for? Doesn't
./nodebb build --seriesalready work?If you're asking to make it the default, there's also the option of placing
"series": truein your config.json -
@pitaj great! This is what I am looking for.
And you understood it even though I wrote it wrong. 
Actually I would ask for ./nodebb upgrade --seriesbut a config option is much better. Thank you!
It would be great if you could include this option in the documentation.
