MySQL goes to improper state after consequtive start
All,
When we start MySQL when it is already running, MySQL ends up in going to some improper state. See the sequence of steps as below
{
[veechand@Veerabahu ~]$ sudo /etc/init.d/mysql start
Starting MySQL.. [ OK ]
[veechand@Veerabahu ~]$ sudo /etc/init.d/mysql status
MySQL running (16322) [ OK ]
[veechand@Veerabahu ~]$ sudo /etc/init.d/mysql start
Starting MySQL [ OK ]
[veechand@Veerabahu ~]$ sudo /etc/init.d/mysql status
/etc/init.d/mysql: line 363: test: 16948: binary operator expected
MySQL is running but PID file could not be found [FAILED]
}
To recover from this we need to kill MySQL process manually and then start again.
Can you let me know the reason for the same.
Environment details
Linux - RHEL 5 update 4. 64 bit version
mysql Ver 14.14 Distrib 5.5.10, for Linux (x86_64)
TIA,
Veerabahu
Subject
Written By
Posted
MySQL goes to improper state after consequtive start
June 24, 2011 12:22PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.