For some reason mysql wont start, i have tried restarting mysql but it wont, it says FAILED. The mysql.sock file seems to have disappeared and i cannot find it anywhere.
My vps is run well, then i reboot and i see mysql no longer working. I check in WHM mysql (5.0.67-community) failed
And when restart (by WHM )
Restarting MySQL Server
whmappname='Restarting Service'; if (self['update_ui_status']) { update_ui_status('MySQL Server'); } Waiting for mysql to restart..............finished.
mysqld_safe (/bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server.xxxx.com.pid) running as root with PID 5275
mysql has failed, please contact the sysadmin (result was "mysql has failed").
I am not being able to restart the server, or MySQL or httpd via SSH.
PHP Code:
root@server [~]# /etc/init.d/httpd fullstatusLooking up localhostMaking HTTP connection to localhostAlert!: Unable to connect to remote host.lynx: Can't access startfile http://localhost/server-statusroot@server [~]#
PHP Code:
root@server [~]# /etc/init.d/mysql reload/etc/init.d/mysql: line 244: kill: (3375) - No such processtouch: cannot touch `/var/lib/mysql/server.lubnan.us.pid': Read-only file system
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.
What could I fix by trying to start mysql server, recieve following errors:
plesk interface:
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 directory shared by NFS on server1 this directory mounted at startup on server2. problem happened when twice servers restarted and server2 started before server1. directory not mounted I must mount it manually.
I get the following message via SSH when i try named restart
named: symbol lookup error: named: undefined symbol: dns_resolver_setudpsize
All my sites are currently down but the server is up and bind wont restart either in WHM or SSH
i am using WHM 10.6.0 cPanel 10.8.0-R8 CentOS 4.3 i686 - WHM X v3.1.0 Linux ***.server.com 2.6.9-11.EL #1 Wed Jun 8 16:59:52 CDT 2005 i686 i686 i386 GNU/Linux
I spoke to live support at nexpoint but they told me to email their dedicated server support but I havent had a reply in the last few hours.
I have 8 apache servers that is sharing one httpd.conf file... When changes made in the httpd.conf, you have you restart httpd... How can I restart all 8 servers at the same time instead of logging into each server and do it manually?
I was asked to restart lighthttpd at my friend host, he has 6 sites running, and of the site is down, host has asked him to restart the server, as he is away, he wanted me to restart, but I have no clue how to restart lighthttpd,
It will be really helpful if u can guide me for : if possible for the domain alone, else for the entire server
current options available : lxadmin - hypervm ssh connection
We are unable to restart apache on our server, as a result no sites are accessible in the browser. Our host states we need to clear out the following files:
after restarting my server i tried to start my shoutcast servers whicj right now its not working...i am getting an error when i am trying to start them again "error opening source socket! FATAL ERROR! Some other process is using this port!"
I have a few domains in a DA server whose stats stop working for a few months, any idea how to restart these few domains Webalizer? The rest of the domains' stats are working properly though
I just bought new DS 3 days ago : Intel Core2Duo 2.33 GHz, 2GB DDR2 RAM , 250 GB.
Today mysql automatic stop and not auto restart :|
I checked cron job: has no cron job there. I have just only one site on this server.
I check Check mysql error log:
081115 10:47:52 [Note] /usr/sbin/mysqld: Normal shutdown 081115 10:47:52 InnoDB: Starting shutdown... 081115 10:47:54 InnoDB: Shutdown completed; log sequence number 0 72782 081115 10:47:54 [Note] /usr/sbin/mysqld: Shutdown complete 081115 10:47:54 mysqld ended 081115 10:47:55 mysqld started /usr/sbin/mysqld: File '/var/log/mysql-slow-queries.log' not found (Errcode: 13) 081115 10:47:55 [ERROR] Could not use /var/log/mysql-slow-queries.log for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it. 081115 10:47:55 InnoDB: Started; log sequence number 0 72782 081115 10:47:56 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.51a-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
I have no trouble logging in through SSH Also no problem accessing webmin on port 10000
I've tried to restart Apache httpd And tried to reboot the server...
Nothing.
I recently did a Yum Update, also removed ISPconfig - it's probably the latter thats the problem, although I haven't used it - at all - just playing around setting up PHPmyadmin, Squirrelmail and a couple of email accounts.
But the only error log output I get is that there are no virtual servers for 88.198.81.186:80 and 88.198.81.187:80 and Unable to open logs | unable to start piped log program
Since the update and removal of ISPconfig 4-5 days ago there hasn't been any issues. I haven't done anything. Yet I do think might be some of the old ISPconfig settings acting up.
I'm on my first VPS with Virtuozzo / WHM and I'm wondering about what some general guidelines regarding best practices are in regards to restarting services and or the server. Specifically, I'm wondering what a good time frame it to restart the server and sevices.
I've been told VZ doesn't need to be restarted, but I figured that by restarting VZ, I restart everything at once... is this bad? How often should I do this or not do this?
Alternatively, if I just restart specific services, what is your experience on a good timeline and what services are important to restart?
I've read that mysql doesn't need to be restarted, but am wondering EXIM, http server, dns server, pop3 server, imap server, etc.... specifically what good schedule would be regarding restarting.
I'm simply trying to avoid issues that may occur due to not restarting and trying to be proactive as my clients are extremely important to me... ...
I'm having problems with Apache 2.0.54 on my Debian server. The command "apache2ctl restart" will not work properly. Let me explain. Whenever I run "apache2ctl restart" Apache will tell me it's running with no problems while it actually isn't. I run "apache2ctl start" and it tells me that httpd is already running according to a PID.
When I need to restart Apache I need to go and run "apache2ctl stop" and "apache2ctl start" which seems to work effectively. I tried recoding the system to run these two commands in the Perl backend of my web hosting control panel, but these two commands don't work since they seem to run at the same time.
So my question is this: how can I get the "apache2ctl restart" command to work again? Or better yet, how do I get Perl to run the "apache2ctl stop" and "apache2ctl start" commands without having them being run simultaneously?
1) Restore system to mbox (non-maildir) state. 2) Request Technical Support 3) Convert partially converted mail accounts *) Exit Enter Selection---] 3 quotaoff: quotactl on /dev/sda3 [/]: No such process
The above just freezes and does nothing, had to manually stop after 5 minutes.
Restarting pop3 via whm gives this error:
cppop has failed, please contact the sysadmin.
Restart imap gives this:
imap has failed, please contact the sysadmin (result was "couriertcpd is not runningauthdaemond is not running").
I ran: /scripts/courierup --force /scripts/eximup --force
Did nothing, still cannot restart pop3/imapd
root@server [~]# /scripts/restartsrv_cppop /etc/init.d/courier-imap: line 19: /usr/lib/courier-imap/etc/imapd: No such file or directory /etc/authlib/authdaemonrc does not exist, forgot make install-configure? root@server [~]# /scripts/restartsrv_imap /etc/init.d/courier-imap: line 19: /usr/lib/courier-imap/etc/imapd: No such file or directory /etc/authlib/authdaemonrc does not exist, forgot make install-configure?
I changed maildir=1 to 0 in cpanel.config file and ran convert2maildir again,
I got at the very end when it halted: Unable to install courier. at /usr/local/cpanel/bin/maildirupdate line 51.
I tried to restart exim:
root@server [~]# /scripts/restartsrv_exim Starting clamd: [ OK ] Starting exim: 2007-03-11 10:25:37 Exim configuration error in line 670 of /etc/exim.conf: option "maildir_format" unknown [FAILED] Starting exim-smtps: 2007-03-11 10:25:37 Exim configuration error in line 670 of /etc/exim.conf: option "maildir_format" unknown [FAILED] Starting antirelayd: [ OK ] Starting antirelayd: [ OK ]
We changed our SSH port (for the slight added security that this offers) and updated our CSF config with the new port so that we can accept connections on this port.
We restarted CSF and we could connect successfully on the new port. When the server is rebooted connections are refused on the port until we *RESTART* CSF then it's all good again.
I would think being that we opened the port in CSF's config that on reboot the port would be opened back up but this is not happening and any time the server is rebooted we have to restart the firewall.
Does anybody have any suggestions on how to "fix" this or at least make it so we don't have to manually restart the firewall?