Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra - Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack (1) Thread Tools Display Modes
  #1 (permalink)  
Old 01-27-2007, 08:41 AM
Senior Member
 
Posts: 62
Default mysql.server is not running

Hello everybody,

again I have some problems...
I upgraded from 4.03 to 4.50GA and the upgrade fails while starting the mysqld :-(

Well - I rebooted the system and everything is running except mailbox (because of "mysql.server is not running".
But the apache is able to use the zimbra mysql daemon - so why does the mailbox not?

Is this a "new" problem in this version because of the RAM? I only have 512MB inside - but haven't had any problems with this yet....

Hope anyone could help?!
Reply With Quote
  #2 (permalink)  
Old 01-27-2007, 08:55 AM
Zimbra-Yahoo Consultant
 
Posts: 5,608
Default

Well,
Let's look to see what the problem is. First can we get the segment of the log which show the zcs startup process?

It's located in /var/log/zimbra.log
Reply With Quote
  #3 (permalink)  
Old 01-27-2007, 09:25 AM
Senior Member
 
Posts: 62
Default

Sure....
Quote:
Originally Posted by wannabetenor View Post
It's located in /var/log/zimbra.log
But I don't think that you can do much with it...
Here it is:
Code:
Jan 27 17:12:58 XDOMAINX zimbramon[14348]: 14348:info: 2007-01-27 17:12:06, STATUS: : Cannot: determine
Jan 27 17:14:25 XDOMAINX zimbramon[14401]: 14401:info: 2007-01-27 17:14:07, STATUS: : Cannot: determine
Jan 27 17:15:11 XDOMAINX zimbramon[15150]: 15150:info: Stopping services
Jan 27 17:15:11 XDOMAINX zimbramon[15150]: 15150:info: Stopping mta
Jan 27 17:15:13 XDOMAINX postfix/postfix-script: fatal: the Postfix mail system is not running
Jan 27 17:15:13 XDOMAINX zimbramon[15150]: 15150:info: Stopping spell
Jan 27 17:15:13 XDOMAINX zimbramon[15150]: 15150:info: Stopping snmp
Jan 27 17:15:13 XDOMAINX zimbramon[15150]: 15150:info: Stopping antivirus
Jan 27 17:15:13 XDOMAINX zimbramon[15150]: 15150:info: Stopping antispam
Jan 27 17:15:13 XDOMAINX zimbramon[15150]: 15150:info: Stopping imapproxy
Jan 27 17:15:17 XDOMAINX zimbramon[15150]: 15150:info: Stopping mailbox
Jan 27 17:15:17 XDOMAINX zmtomcatmgr[15270]: threaddump requested
Jan 27 17:15:17 XDOMAINX zmtomcatmgr[15270]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Jan 27 17:15:17 XDOMAINX zmtomcatmgr[15270]: assuming no other instance is running
Jan 27 17:15:17 XDOMAINX zmtomcatmgr[15270]: no manager process is running
Jan 27 17:15:19 XDOMAINX zmtomcatmgr[15277]: stop requested
Jan 27 17:15:19 XDOMAINX zmtomcatmgr[15277]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Jan 27 17:15:19 XDOMAINX zmtomcatmgr[15277]: assuming no other instance is running
Jan 27 17:15:19 XDOMAINX zmtomcatmgr[15277]: no manager process is running
Jan 27 17:15:19 XDOMAINX zimbramon[15150]: 15150:info: Stopping logger
Jan 27 17:15:19 XDOMAINX zimbramon[15150]: 15150:info: Stopping ldap
Jan 27 17:16:06 XDOMAINX zimbramon[15473]: 15473:info: 2007-01-27 17:16:01, STATUS: : Cannot: determine
Jan 27 17:18:08 XDOMAINX zimbramon[17124]: 17124:info: 2007-01-27 17:18:02, STATUS: : Cannot: determine
Jan 27 17:19:04 XDOMAINX zimbramon[18135]: 18135:info: Stopping services
Jan 27 17:19:04 XDOMAINX zimbramon[18135]: 18135:info: Stopping mta
Jan 27 17:19:04 XDOMAINX postfix/postfix-script: fatal: the Postfix mail system is not running
Jan 27 17:19:05 XDOMAINX zimbramon[18135]: 18135:info: Stopping spell
Jan 27 17:19:05 XDOMAINX zimbramon[18135]: 18135:info: Stopping snmp
Jan 27 17:19:05 XDOMAINX zimbramon[18135]: 18135:info: Stopping antivirus
Jan 27 17:19:05 XDOMAINX zimbramon[18135]: 18135:info: Stopping antispam
Jan 27 17:19:05 XDOMAINX zimbramon[18135]: 18135:info: Stopping imapproxy
Jan 27 17:19:08 XDOMAINX zimbramon[18135]: 18135:info: Stopping mailbox
Jan 27 17:19:08 XDOMAINX zmtomcatmgr[18236]: threaddump requested
Jan 27 17:19:08 XDOMAINX zmtomcatmgr[18236]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Jan 27 17:19:08 XDOMAINX zmtomcatmgr[18236]: assuming no other instance is running
Jan 27 17:19:08 XDOMAINX zmtomcatmgr[18236]: no manager process is running
Jan 27 17:19:10 XDOMAINX zmtomcatmgr[18243]: stop requested
Jan 27 17:19:10 XDOMAINX zmtomcatmgr[18243]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Jan 27 17:19:10 XDOMAINX zmtomcatmgr[18243]: assuming no other instance is running
Jan 27 17:19:10 XDOMAINX zmtomcatmgr[18243]: no manager process is running
Jan 27 17:19:10 XDOMAINX zimbramon[18135]: 18135:info: Stopping logger
Jan 27 17:19:10 XDOMAINX zimbramon[18135]: 18135:info: Stopping ldap
Jan 27 17:20:02 XDOMAINX postfix/postqueue[18646]: fatal: Queue report unavailable - mail system is down
Jan 27 17:20:03 XDOMAINX zimbramon[18624]: 18624:info: 2007-01-27 17:20:01, QUEUE: 0 0
Jan 27 17:20:05 XDOMAINX zimbramon[18629]: 18629:info: 2007-01-27 17:20:02, DISK: XDOMAINX.eu: dev: /dev/hda1, mp: /, tot: 16772, avail: 6184
Jan 27 17:20:07 XDOMAINX zimbramon[18631]: 18631:info: 2007-01-27 17:20:02, STATUS: : Cannot: determine
Jan 27 17:22:04 XDOMAINX zimbramon[19578]: 19578:info: 2007-01-27 17:22:01, STATUS: : Cannot: determine
Reply With Quote
  #4 (permalink)  
Old 01-27-2007, 09:39 AM
Zimbra-Yahoo Consultant
 
Posts: 5,608
Default

This appears to be stopping the services. Can you get the services starting up?
Reply With Quote
  #5 (permalink)  
Old 01-27-2007, 09:48 AM
Senior Member
 
Posts: 62
Default

Quote:
Originally Posted by wannabetenor View Post
This appears to be stopping the services. Can you get the services starting up?
How may I do this?
> zmcontrol start
just "starts" everything (looks perfekt), but the "zmcontrol status" still says mysql.server not running...

And as I already said - the mysql server IS running - I can work with it.
Reply With Quote
  #6 (permalink)  
Old 01-27-2007, 10:07 AM
Zimbra-Yahoo Consultant
 
Posts: 5,608
Default

I understand that it's starting, I wanted to see what happens when something tries to connect to it. . .

What happens when you
>su zimbra
>mysql mysql


?
Reply With Quote
  #7 (permalink)  
Old 01-27-2007, 10:18 AM
Senior Member
 
Posts: 62
Default

Quote:
Originally Posted by wannabetenor View Post
I understand that it's starting, I wanted to see what happens when something tries to connect to it. . .

What happens when you
>su zimbra
>mysql mysql
?
zimbra@XDOMAINX:~/bin$ mysql mysql
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4 to server version: 5.0.26-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>
Reply With Quote
  #8 (permalink)  
Old 01-27-2007, 10:22 AM
Zimbra-Yahoo Consultant
 
Posts: 5,608
Default

Okey Dokey,
Have you run a
mysql.server stop
and
mysql.server start

to see if it throws an exception?
Reply With Quote
  #9 (permalink)  
Old 01-27-2007, 10:28 AM
Senior Member
 
Posts: 62
Default

No - not yet... But I can try in a minute...

I think that now not even the tomcat is running :-( I copied my backup in the folder and not even this is now running :-(
Reply With Quote
  #10 (permalink)  
Old 01-27-2007, 10:30 AM
Zimbra-Yahoo Consultant
 
Posts: 5,608
Default

I really need to see that startup log

Here's an easy way to get those results:

zmcontrol stop
ps auxx | grep zimbra
(kill any left over processes by zimbra)
zmcontrol start
tail -125 /var/log/zimbra.log
(post that)
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0