CentOS 4.2
[root@srv1 certs]# service mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] [root@srv1 certs]# rm -fr /var/lib/mysql/* [root@srv1 certs]# service mysqld start Initializing MySQL database: [ OK ] Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED]
I note that I now have some more <defunct> (zombie) chvt processes
WTF?
Craig
On 12/13/05, Craig White craigwhite@azapple.com wrote:
CentOS 4.2
[root@srv1 certs]# service mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] [root@srv1 certs]# rm -fr /var/lib/mysql/* [root@srv1 certs]# service mysqld start Initializing MySQL database: [ OK ] Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED]
I note that I now have some more <defunct> (zombie) chvt processes
WTF?
An apt question. what's in the logs? Also, does your hostname resolve?
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Tue, 2005-12-13 at 18:47 -0500, Jim Perrin wrote:
On 12/13/05, Craig White craigwhite@azapple.com wrote:
CentOS 4.2
[root@srv1 certs]# service mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] [root@srv1 certs]# rm -fr /var/lib/mysql/* [root@srv1 certs]# service mysqld start Initializing MySQL database: [ OK ] Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED]
I note that I now have some more <defunct> (zombie) chvt processes
WTF?
An apt question. what's in the logs? Also, does your hostname resolve?
---- sure # host srv1.clsurvey.com srv1.clsurvey.com has address 192.168.1.1
# cat /var/log/mysqld.log 051213 16:53:55 mysqld started /usr/libexec/mysqld: Can't create/write to file '/tmp/ibdajdMj' (Errcode: 13) 051213 16:53:55 InnoDB: Error: unable to create temporary file; errno: 13 051213 16:53:55 [ERROR] Can't init databases 051213 16:53:55 [ERROR] Aborting
051213 16:53:55 [Note] /usr/libexec/mysqld: Shutdown complete
051213 16:53:55 mysqld ended
I think you're on to something...
# ls -ld /tmp drwxr-xr-x 51 craig Administrators 4096 Dec 13 16:53 /tmp [root@srv1 certs]# chown root:root /tmp [root@srv1 certs]# chmod 1777 /tmp [root@srv1 certs]# service mysqld start Starting MySQL: [ OK ]
I would never knowingly change owner/permissions on /tmp
I don't know how that came to pass.
Thanks - good catch.
Everytime I tried to run less /var/log/mysqld.log, it would tell me that it's a binary file but I didn't try to 'cat' it until I was going to post it to the list.
Thanks
Craig
Thanks - good catch.
Everytime I tried to run less /var/log/mysqld.log, it would tell me that it's a binary file but I didn't try to 'cat' it until I was going to post it to the list.
Yeah. Sometimes less tries to be too smart for its own good. cat just does what it is told.
Thanks
No problem, I'm glad it worked.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Tue, 2005-12-13 at 19:06 -0500, Jim Perrin wrote:
Thanks - good catch.
Everytime I tried to run less /var/log/mysqld.log, it would tell me that it's a binary file but I didn't try to 'cat' it until I was going to post it to the list.
Yeah. Sometimes less tries to be too smart for its own good. cat just does what it is told.
---- some habits die hard... Funny thing was, I kept trying to use less to read it. It was my second notion...honest. ----
Thanks
No problem, I'm glad it worked.
---- not only did it work, setting privileges back on /tmp fixed a number of issues that were making me crazy...all little things.
I have been searching my mind as to how I could have changed ownership of /tmp like that and I know that there is no way that I did it from the command line. I did do a lot of fooling around with fedora directory server which 'might' have done that, some fooling around with webmin 'LDAP Users and Groups' which probably did that but at no time did I ever set 'craig' to use /tmp as the home directory which is the type of thing that would cause Webmin to set the permissions thusly. I note that none of the other subdirectories in / were changed which tells me webmin was the culprit because I did some mucking with webmin and re-asserting LDAP objectclasses and attributes with Webmin which also will change the users home directory permissions when instructed...I'm gonna have to watch for repeat behavior on this.
Thanks again
Craig