View Single Post
  #2  
Old 17th October 2012, 03:55
MrCompTech MrCompTech is offline
Member
 
Join Date: Jul 2010
Posts: 92
Thanks: 1
Thanked 20 Times in 9 Posts
Default

Got the idea to run the script but pipe it 'more' and now can see that it says

17.10.2012-00:33 - WARNING - DB::query(INSERT INTO sys_log (server_id,datalog_id,loglevel,tstamp,message) VALUES ('1',0,'0','1350434020','There is already a lockfile set. Waiting another 10 seconds...')) -> mysql_query Table './dbispconfig/sys_log' is marked as crashed and should be repaired

Used locate command to find table "sys_log":
[root@prl-ofc-s01 dbispconfig]# locate sys_log
/var/lib/mysql/dbispconfig/sys_log.MYD
/var/lib/mysql/dbispconfig/sys_log.MYI
/var/lib/mysql/dbispconfig/sys_log.frm

CD to /var/lib/mysql/dbispconfig/

ran command "myisamchk -r sys_log.MYI" to fix table.

No more repeating backslashes! YEAH!

But still no database creates.
But now when try to run server.sh script get:
- DEBUG - There is already an instance of server.php running. Exiting.

Guessing there must be a lock file that is still set. Found lock file in '/usr/local/ispconfig/server/temp/' and deleted it.

But every time I try to run the server.sh or if I wait a couple of minutes for it to run on it's own the lock file doesnt' get deleted and the backslashes are back.

Had to run the command "myisamchk -r sys_log.MYI" twice to fix the dbispconfig:sys_log.MYI table.

Now the database was created and no more back slashes.

Hope this helps somebody.
__________________
MrCompTech.com
Reply With Quote