Rant Posted January 4 Share Posted January 4 Account: runningantdev I have just re-read the terms of service and there is nothing in there which I can see being relevant to why my account was suspended. I have received no correspondence from you indicating why either. I can't even think of any potential reason - its a simple nodejs app that talks to a postgres database - I am building and testing a concept which I intend at some point to embed in a mobile app, its not even something that is to be accessible to the general public - its for my own testing purposes. Can I have someone review this please and at least get back to me to explain what the problem is. Quote Link to comment Share on other sites More sharing options...
MoneyBroz Posted January 4 Share Posted January 4 You were suspended for high server load. The limit is 100gb of memory in 24hrs. Your account had 130.52 GB of memory usage before 24hrs. Make sure to keep the load under 100GB of memory and 10k CPU usage. You can keep track of your load at https://heliohost.org/dashboard/load/ Unsuspended. Quote Link to comment Share on other sites More sharing options...
Rant Posted January 4 Author Share Posted January 4 Thanks for your reply. I can't explain that mem usage - I can only guess it's related to multiple instances of the node app running - I had some issues trying to get it running due to environment differences - e.g. sqlite not working, and issues with connection pools. Quote Link to comment Share on other sites More sharing options...
Rant Posted January 4 Author Share Posted January 4 (edited) I am still waiting for the site to be accessible - it's still saying it's suspended, however the load chart is showing 6GB of mem usage since you reactivated just before. If it's not the running site using memory then what is? Is there any way to get a more granular view of what is using the mem? If nodejs is the issue then is it just not practical in your hosting environment to use it? When setting up this site I disabled PHP and everything else I could find to disable except for nodejs. It's not even a complex app - it's just a thin layer that takes web requests and updates a postgres database. I am not seeing any abnormal mem usage when running locally. EDIT: its now up to 18GB usage ... simple just to have a response that shows the word "running": app.get("/", async (req, resp) => { resp.send("<html><body>running</body></html>"); }); Edited January 4 by Rant Quote Link to comment Share on other sites More sharing options...
Rant Posted January 4 Author Share Posted January 4 (edited) Alright, I've hacked back the app to this simple example and restarted node. Will keep an eye on this but if mem usage keeps growing then this is going to be a problem beyond my code/app and something infrastructure related. "use strict"; const express = require("express"); const app = express(); const port = 80; app.get("/", async (req, resp) => { resp.send("<html><body>running - testing mem usage</body></html>"); }); // start server app.listen(port, () => { console.log(`⚡️[server]: Server is running at http://localhost:${port}`); }); PLEASE NOTE: I've created the following ticket to investigate this further: https://helionet.org/index/topic/58640-unexplained-nodejs-mem-usage/ Edited January 4 by Rant Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.