mariadb failed to start mysql.pid FILE SIZE EQUALS ZERO

I have mariadb columnstore installed on Amzaon EC2 instance. Our mariadb stopped working PM service up and running where as UM service is not starting. Centos = 7

cat info.log Jul 5 12:46:46 ip-172-16-10-27 ProcessMonitor[1340]: 46.697394 |0|0|0| I 18 CAL0000: MSG RECEIVED: Stop All process request... Jul 5 12:46:46 ip-172-16-10-27 ProcessMonitor[1340]: 46.697776 |0|0|0| I 18 CAL0000: STOPALL: ACK back to ProcMgr, STATUS_UPDATE only performed Jul 5 12:46:47 ip-172-16-10-27 ProcessMonitor[1340]: 47.698421 |0|0|0| I 18 CAL0000: MSG RECEIVED: Stop All process request... Jul 5 12:46:48 ip-172-16-10-27 ProcessMonitor[1340]: 48.844815 |0|0|0| I 18 CAL0000: STOPALL: ACK back to ProcMgr, return status = 0 Jul 5 12:46:57 ip-172-16-10-27 ProcessMonitor[1340]: 57.584789 |0|0|0| I 18 CAL0000: MSG RECEIVED: Shutdown Module request... Jul 5 12:46:57 ip-172-16-10-27 ProcessMonitor[1340]: 57.584894 |0|0|0| I 18 CAL0000: SHUTDOWNMODULE: ACK back to ProcMgr, return status = 0 Jul 5 12:47:42 ip-172-16-10-27 ProcessMonitor[30970]: 42.318944 |0|0|0| I 18 CAL0000: Jul 5 12:47:42 ip-172-16-10-27 ProcessMonitor[30970]: 42.319014 |0|0|0| I 18 CAL0000: **Process Monitor Started** Jul 5 12:48:25 ip-172-16-10-27 ProcessMonitor[30970]: 25.672306 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:25 ip-172-16-10-27 ProcessMonitor[30970]: 25.672802 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:26 ip-172-16-10-27 ProcessMonitor[30970]: 26.674408 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:26 ip-172-16-10-27 ProcessMonitor[30970]: 26.674851 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:27 ip-172-16-10-27 ProcessMonitor[30970]: 27.675776 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:27 ip-172-16-10-27 ProcessMonitor[30970]: 27.676099 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:28 ip-172-16-10-27 ProcessMonitor[30970]: 28.678249 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:28 ip-172-16-10-27 ProcessMonitor[30970]: 28.678585 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:29 ip-172-16-10-27 ProcessMonitor[30970]: 29.680066 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:29 ip-172-16-10-27 ProcessMonitor[30970]: 29.680407 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:30 ip-172-16-10-27 ProcessMonitor[30970]: 30.681526 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:30 ip-172-16-10-27 ProcessMonitor[30970]: 30.681966 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:31 ip-172-16-10-27 ProcessMonitor[30970]: 31.682826 |0|0|0| I 18 CAL0000: MSG RECEIVED: Configure Module Jul 5 12:48:31 ip-172-16-10-27 ProcessMonitor[30970]: 31.686100 |0|0|0| I 18 CAL0000: CONFIGURE: ACK back to ProcMgr, return status = 0 Jul 5 12:48:39 ip-172-16-10-27 ProcessMonitor[30970]: 39.746537 |0|0|0| I 18 CAL0000: MSG RECEIVED: Get Calpont Software Info Jul 5 12:48:39 ip-172-16-10-27 ProcessMonitor[30970]: 39.746642 |0|0|0| I 18 CAL0000: GETSOFTWAREINFO: ACK back to ProcMgr with 1.2.21 Jul 5 12:48:40 ip-172-16-10-27 ProcessMonitor[30970]: 40.747287 |0|0|0| I 18 CAL0000: MSG RECEIVED: Update Calpont Config file Jul 5 12:48:40 ip-172-16-10-27 ProcessMonitor[30970]: 40.747666 |0|0|0| I 18 CAL0000: UPDATECONFIGFILE: Completed Jul 5 12:48:45 ip-172-16-10-27 ProcessMonitor[30970]: 45.757970 |0|0|0| I 18 CAL0000: MSG RECEIVED: Start All process request... Jul 5 12:48:46 ip-172-16-10-27 oamcpp[30970]: 46.848238 |0|0|0| E 08 CAL0000: *mysql.pid FILE SIZE EQUALS ZERO Jul 5 12:48:46 ip-172-16-10-27 ProcessMonitor[30970]: 46.848362 |0|0|0| C 18 CAL0000: STARTALL: MySQL failed to start, start-module failure Jul 5 12:48:46 ip-172-16-10-27 ProcessMonitor[30970]: 46.849567 |0|0|0| I 18 CAL0000: STARTALL: ACK back to ProcMgr, return status = 1

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.