MAMP 6.7 on MacOS 13.1 (Intel). Starting the servers works as expected and pages in the document root are displayed correctly from localhost:8888. After selecting "Stop" the icon begins to cycle between its Orange and Green states and the WebStart icon switches between dimmed and solid states.
Checking Activity Monitor, I can see that MAMP starts an httpd process (and its expected child processes). Selecting "Stop" does not stop these processes (bash processes and their child mysqld processes die and restart).
If the MAMP application is quit, the httpd process continues using the same PID that was reported while MAMP was active.
I've tried deleting and reinstalling MAMP. The problem persists. Restarting the machine kills the httpd process as expected but upon starting it in MAMP and attempting to stop, it continues to persist.
Related
The mongoDB service shuts down every 24 hours or so and despite having the error response in windows service set to restart it will shutdown and remain offline. I also have only found 1 log and the log itself seems to state that the windows service manager is the one shutting it down.
Ive mainly tried to get windows to automatically restart it, however that did not change a thing.
i have a Centos 5 server which hosted asterisk 13.
server works fine last week but now top command always show me a process with large amount of CPU usage. when i kill the process a few second later another command with large CPU usage started. many times processes command is ".syslog" but have other command like "qjennjifes", "vnvebynufu" and another unknown commands like that.
1) Check you have firewall and fail2ban recomended settings
2) Check you have no DoS/DDoS by "sip show channels"
3) Check your system not hacked/no broken soft on your host.
After recently updating nodejs to v9.5.0 as part of bumping dependencies for an ionic project I am seeing periodic connection attempts to registry.npmjs.org even when ionic is not running.
The moment when I get the connection alert (from a firewall app) I can see that there are 3 node and npm processes in the Activity Monitor, but even after I kill them (with pkill node) after about 10 or 20 minutes I see again node processes attempting to connect to registry.npmjs.org.
The actual command that I see being run with ionic as the parent process:
81830 /usr/local/Cellar/node/9.5.0/bin/node /usr/local/lib/node_modules/npm/node_modules/update-notifier/check.js {"pkg":{"name":"npm","version":"5.6.0"}}
Is there a way to control this periodic update check by ionic?
One of the mongo nodes in the replica set went down today. I couldn't find what happened but when i checked the logs on the server, I saw this message 'mongod main process killed by KILL signal'. I tried googling for more information but failed. Basically i like to know what is KILL signal, who triggered it and possible causes/fixes.
Mongo version 3.2.10 on Ubuntu.
The KILL signal means that the app will be killed instantly and there is no chance left for the process to exit cleanly. It is issued by the system when something goes very wrong.
If this is the only log left, it was killed abruptly. Probably this means that your system ran out of memory (I've had this problem with other processes before). You could check if swap is configured on your machine (by using swapon -s), but perhaps you should consider adding more memory to your server, because swap would be just for it not to break, as it is very slow.
Another thing worth looking at is the free disk space left and the syslog (/var/log/syslog)
I want to implement a automatic service restarting for several tomcat applications, applications that do take a lot of time to start, even over 10 minutes.
Mainly the test would check if the application is responding on HTTP with a valid response.
Still, this is not the problem, the problem is how to prevent this uptime check to fail while the service is under maintenance, scheduled or not.
I don't want for this service to be started if it was stopped manually, with `service appname stop".
I considered creating .maintenance files on stop or restart actions of the daemon and checking for them before triggering an automated restart.
So far the only problem that I wasn't able to properly solve was, how to detect that the app finished starting up and remove the .maintenance file, so the automatic restart would work properly.
Note, an init.d script is not supposed to wait, so the daemon should start a background command that solves this problem.