What could I fix by trying to start mysql server, recieve following errors:
Code: Failed to restart the "mysql" service. Cannot start/stop/restart service: Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql restart Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the stop(8) and then start(8) utilities, e.g. stop mysql ; start mysql. The restart(8) utility is also available. start: Job failed to start
from the console:
Code: sudo service mysql start start: Job failed to start
Code: mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) output of plesk_11.5.30_reset_instance_data.log:
I have upgraded my Redmine installation for my site using SVN. After that i have restarted mongrel and it failed. It is never starting again. ====================== I used this command -- mongrel_rails start -d
The error reported is :--
Path to log file not valid: log/mongrel.log PID file log/mongrel.pid does not exist. Not running?
The mongrel.log file and mongrel.pid file are present in :--
So, pid file do exist.
My port where mongrel is acting up is 3000. =========================== ------------- I also used the exhaustive command --
mongrel_rails start -e production -p 3000 -d -l /home/cwleader/redmine-0.8/log ------------- It specifies the port and full path of pid and mongrel log. Still error appears.
I have a lot of tables, being that I host multi forums. One thing I noticed when doing a mysql start up or restart is that it takes at least 15 minutes to do it. The server isn't bad, it's a Pentium D with 3GB of RAM and it runs perfectly fine. What I noticed is that after I do an SQL restart, I checked "top." The command that was running is "chown" and it sat at the top of the list, and kept going. Until finally mysql started and it stopped.
I imagine that all of the files in the data folder are being CHOWNed... and that's why it takes forever. If this is the case, how can I stop this, if at all? I don't see why they need to be CHOWNed?
Anyone know a good script that I can run with cron or something? Mysql seems to be the #1 problem with a lot of my web sites, a restart usually fixes it right away for me, but I can't keep restarting my servers everyday manually.
/etc/init.d/sw-cp-server restart Restarting sw-cp-server (via systemctl): Job for sw-cp-server.service failed. See 'systemctl status sw-cp-server.service' and 'journalctl -xn' for details. [FAILED]
tail -f /var/log/sw-cp-server/error_log
2014/11/26 03:06:10 [emerg] 520#0: invalid number of arguments in "fastcgi_buffers" directive in /etc/sw-cp-server/config:31 2014/11/26 03:06:11 [emerg] 874#0: invalid number of arguments in "fastcgi_buffers" directive in /etc/sw-cp-server/config:31
Fehler: f2bmng failed: Job for fail2ban.service failed. See 'systemctl status fail2ban.service' and 'journalctl -xn' for details. ERROR:f2bmng:Failed to start fail2ban service
-- Unit fail2ban.service has failed. -- -- The result is failed.
Aug 20 14:22:13 noreply.flusiserver.de systemd: Unit fail2ban.service entered failed state. Aug 20 14:22:14 noreply.flusiserver.de agetty: /dev/hvc0: No such file or directoryClick to expand...