failing to start mysql with /var/indimail/bin/svc -u /service/mysql.3306/

[asif]

I just installed indimail-1.8.9-202.1.x86_64 on CentOS release 6.5 (Final) like below using the steps below

http://indimail.blogspot.com/2011/07/indimail-installation-for-newbies-in-10.html

mysqld does not run. I am getting this continuosly

@4000000053b20b4d2fe2b86c /usr/libexec/mysqld: File '/var/indimail/mysqldb/logs/mysql-bin.~rec~' not found (Errcode: 13)

@4000000053b20b4d2fe2c80c 140630 21:13:39 [ERROR] MYSQL_BIN_LOG::open_purge_index_file failed to open register  file.

@4000000053b20b4d2fe2cfdc 140630 21:13:39 [ERROR] MYSQL_BIN_LOG::open_index_file failed to sync the index file.

@4000000053b20b4d2fe2d3c4 140630 21:13:39 [ERROR] Aborting

@4000000053b20b4d2fe2d7ac 

@4000000053b20b4d2fe38b5c 140630 21:13:39 [Note] /usr/libexec/mysqld: Shutdown complete

@4000000053b20b4d2fe3932c 

@4000000053b20b4e30dfd54c /usr/libexec/mysqld: File '/var/indimail/mysqldb/logs/mysql-bin.~rec~' not found (Errcode: 13)

@4000000053b20b4e30dfe104 140630 21:13:40 [ERROR] MYSQL_BIN_LOG::open_purge_index_file failed to open register  file.

@4000000053b20b4e30dfe8d4 140630 21:13:40 [ERROR] MYSQL_BIN_LOG::open_index_file failed to sync the index file.

If I start mysqld manually as defined in /service/mysql.3306/run, it runs OK.

# bash /service/mysql.3306/run 

140630 21:34:39  InnoDB: Initializing buffer pool, size = 8.0M

140630 21:34:39  InnoDB: Completed initialization of buffer pool

140630 21:34:39  InnoDB: Started; log sequence number 0 44233

140630 21:34:39 [Note] Event Scheduler: Loaded 0 events

140630 21:34:39 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.1.73-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

[Manvendra Bhangui]

Looks like you are running into issue with selinux

You can do

# setenforce 0

to put selinux in permissive mode

and also edit /etc/sysconfig/selinux so that selinux remains in permissive mode after reboot

 

[asif]

That was it! Thanks a lot. mysql now starts in supervise mode, no issue.