I have a node.js server (with socket.io) running using upstart and monit. My problem is my server becomes inaccessible (usually happens when im offline), and the monit is unable to restart the process. The server only reactivates or awakened if i login into the ftp using filezilla.
This is my monit configuration:
set logfile /var/log/monit.log
check process mynode with pidfile /home/mylocation/pid/node-app.pid
start program = "/etc/init.d/node-app start" uid nobody and gid nobody
stop program = "/etc/init.d/node-app stop"
if failed port 8000 protocol HTTP
request /
with timeout 10 seconds
then restart
Any ideas?
I was able to solve my issue,. it was server software versions. If anyone still bumped into this problem, just upgrade to latest stable software versions. Mine works fine in ubuntu 12.04
Related
I have an issue installing Kibana/elasticsearch/logstash.
I followed the instructions for the download and the install of each. From the Admin CMD line, I ran the elasticsearch.bat for elasticsearch. The script ran, but just hung and never fully completed. However, when testing on my localhost 9200, it showed ES installed correctly. I did the same with Kibana and had the same result. The script never fully completed, however, I was able to open the web app on port 5601. I also completed the install for logstash – the script never fully completed. When I manually exited each script by exiting the cmd window, I lost connection to the localhost. "This site can't be reached."
Has anyone had this issue or know what might be happening here?
I am connecting to a remote machine through SSH client. Both SSH server and client are on windows OS.
I usually run tomcat 7 from such ssh session. But, as soon as I end the session, tomcat server shuts down as well. I run tomcat7.exe directly from its installation folder.
I have used &! at the end of the command to ensure that the process doesn't get attached to the terminal. But, couldn't achieve the desired result.
Kindly suggest how to detach such processes from the ssh client.
tomcat7.exe start and tomcat7.exe stop
these two commands ensure that tomcat starts as a service. Worked like a charm for me.
I am using Kali linux
I am unable to run Apache2, i tried so many ways to fix it .., i successful installed xampp and apache2 but dont know why apache not running, mysql and proFTD is running
When i run code to to check the status of apache in lampp it show that another web server is already running.
(another web server already runing)
write this code in terminal
/opt/lampp/xampp disablessl
then check for the apache
sudo /opt/lampp/xampp start
Starting XAMPP for Linux 7.2.5-0...
XAMPP: Starting Apache...ok.
XAMPP: Starting MySQL...already running.
XAMPP: Starting ProFTPD...already running.
I am trying to document my React Components and I am running styleguidist server along side with Laravel development server but the styleguidist server crashes with this error.
You have another server running at port 6060 somewhere, shut it down first
You can change the port using the `serverPort` option in your style guide config:
https://react-styleguidist.js.org/docs/configuration.html
I have configured the styleguidist server to run at port 6060 as to resolve this issue and succeeded to run the server only once. After that I am getting this issue again.
How can i resolve this??
The error is saying you have something else running at that port. Have you tried a different one? If you are running a UNIX system, you can see what is running on that port with:
lsof -i tcp:6060
The message i see when i try to run Integrated Weblogic server is
Port conflicts have been detected and the affected ports have been automatically reassigned to available ports.
Then I am unable to start my server. I have tried restarting the server but it did not help.
Windows
Press Ctrl+Shft+Esc click on Processes, End the JDeveloper(jDev64W.exe in my case) and Java instances(java.exe in my case). Now restart the JDeveloper and try running the Integrated Weblogic Server again.
Linux
Use the command jps -l. Select the process id corresponding to weblogic.server.
Use kill -9 <process-id> to kill the running instance
If it still does not work, restart the computer to ensure all the ports have been released.