So my heroku app crashes with h10 codes and description is "app crashed". No more information. I will attach a screenshot about this (there is like 800 critical errors I can see in my heroku dashboard, and after deployment before a point it doesn't get any errors, then for some reason it starts having these critical errors then shuts down.)
Restarting the server fixes this but after a while it will crash again so I want to fix this properly.
https://imgur.com/22Uhcra Here is three of the errors with the "/" and favicon being more prominent.
An "app crashed" means the process running your app has crashed. This is probably an unhandled NodeJS exception crashing the process.
When this happens, Heroku will automatically restart the app, up to a certain point (apps restarting too often leads to capacity issues).
You should inspect your app's logs (a log retention add-on such as logentries will help there), and see where the first H10 is.
Right before that first H10, there will probably be a stacktrace showing where in your code the crash happens.
If you are using MYSQL make sure you have your connection set with createPool and not createConnection.
CreatePool dynamically creates db connections per your need, whereas createConnection will crash when overloaded.
Related
I have triggered a build for my app in jenkins and it got failed by returning the following error
hudson.AbortException: Ansible playbook execution failed
Then I have reverted my changes and triggered it again even then the same error appeared with status fail.
Then I have triggered a build for other branch of the same project but it got success. I am new to Jenkins. Can anyone please help me understand the situation?
First of all, Ansible playbooks can be very resource intensive. Especially when running against many hosts and/or using process forks, caching, etc.
It's common to see Ansible process allocating a lot of system memory. This can lead to an out-of-memory situation. Then the operating system picks and kills a running process in order to free the memory. This might affect your running Jenkins or Ansible.
Check your system logs for these out-of-memory exceptions.
For Linux use dmesg -T | grep "Out of memory" to filter out the relevant exceptions.
In my Heroku dashboard or on my command, when I try to open my logs i get a 503 Service Unavailable and I can't file a support ticket because I am using a free account. Does anyone know why this would be happening? The Heroku status monitor also says that Heroku services are all good https://status.heroku.com/. My app is also currently running and it does not seem to be affected. I am pretty sure this is an issue with Heroku but I can't get any support due to being a free account.
I am facing this problem from last two weeks.
I am accessing and running server from puTTy terminal. Earlier i was facing problem that when i close my puTTy terminal the website showed 503 error, despite of using 'nohup' command.
nohup npm start --production &
Then i tried using 'Screen' , now if i close my terminal , the website is still live but after some hours (20-24) the Screen is dead and the server is also down.
Please give me a solution to run node.js app in production without the hassle of this 503 error
I have used node/Express framework before and I am trying to launch an old webApp that I have used before. Whenever I type ./bin/www nothing happens.. Usually it would say "listening on port 3000" but absolutely nothing happens. I go to the site and there is no connection. No error messages or anything. Does anyone know why this might be happening? I have done it before on another Ubuntu operating system and I am now just trying to launch it on Xubuntu
I am also setting the debug to ./bin/www by inputting:
DEBUG = ./bin/www
EDIT: Found the problem... Apparently I had to install node-legacy instead
I am running Node.js and Socket.io for online chat.
I have created a file in:
/etc/init/example.conf
it has two lines:
start on startup
exec forever start /var/www/example.com/html/server.js //location of server file.
Whenever I start file upload in chat application, it crashes but instantly restarts.
Whenever I kill node process though, and start it manually - it works fine.
I also can't get any logs or anything from terminal as when it's auto started - it doesn't print me anything to terminal.
I am still new to Node.js and Linux in general.
Node.js is running on Express + Jade.
How do I determine specific cause?
I managed to solve my problem, after a bit of searching around I found out about tail command.
My issue was a bit harder to trace because Node.js was a process started by autostart so when I launched terminal and connected to server, process was just running in background basically and I wouldn't get any output (including exception messages).
Anyway, solution that worked for me was:
I typed
ps aux | grep node //to find PID of node process
then I went to following directory
cd /proc/[pid of running node service]/fd
In fd directory there are few objects you can get output from but if you want to attach and listen to servers output including uncaught exceptions, you need 1.
So:
tail -f 1
that way I was able to cause website to crash and see the output.