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

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 Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-16-2006, 02:57 PM
Junior Member
 
Posts: 5
Default Tomcat !! Newbee

Hi all !!

I have got some problems with tomcat after rebooting my server!!

and i don't really know what to do (see log). Other services running well.

zmtomcatstart: info: stale pid 32101 in pid file: No such process
16.04.2006 23:24:31 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-80
16.04.2006 23:24:32 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-7071
16.04.2006 23:24:32 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1930 ms
16.04.2006 23:24:32 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
16.04.2006 23:24:32 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
16.04.2006 23:24:33 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
16.04.2006 23:24:34 org.apache.catalina.startup.HostConfig deployDescriptor
WARNUNG: A docBase /opt/zimbra/apache-tomcat-5.5.15/webapps/zimbra inside the host appBase has been specified, and will be ignored
log4j:WARN No appenders could be found for logger
(org.apache.catalina.session.ManagerBase).
log4j:WARN Please initialize the log4j system properly.
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Fatal error: terminating: PrivilegedServlet init failedjava.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java :359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at com.zimbra.cs.util.NetUtil.newBoundServerSocket(Ne tUtil.java:78)
at com.zimbra.cs.util.NetUtil.reserveServerSocket(Net Util.java:101)
at com.zimbra.cs.servlet.PrivilegedServlet.init(Privi legedServlet.java:87)
at javax.servlet.GenericServlet.init(GenericServlet.j ava:211)
at org.apache.catalina.core.StandardWrapper.loadServl et(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(Stan dardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnSta rtup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(Sta ndardContext.java:4176)
at org.apache.catalina.core.ContainerBase.addChildInt ernal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(Co ntainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(Sta ndardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDirec tory(HostConfig.java:910)
at org.apache.catalina.startup.HostConfig.deployDirec tories(HostConfig.java:873)
at org.apache.catalina.startup.HostConfig.deployApps( HostConfig.java:474)
at org.apache.catalina.startup.HostConfig.start(HostC onfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEv ent(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLife cycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1020)
at org.apache.catalina.core.StandardHost.start(Standa rdHost.java:718)
at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(Stan dardEngine.java:442)
at org.apache.catalina.core.StandardService.start(Sta ndardService.java:450)
at org.apache.catalina.core.StandardServer.start(Stan dardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalin a.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootst rap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:413)
Reply With Quote
  #2 (permalink)  
Old 04-16-2006, 03:08 PM
Former Zimbran
 
Posts: 5,606
Default

Hi,
Welcome!

Could you shed a little background on your situation?
What distro of linux are you running, sys specs, zimbra build.

Also, it looks like this only part of the log.

How did you get to where you are?

Thanks,
jh
Reply With Quote
  #3 (permalink)  
Old 04-16-2006, 09:13 PM
Zimbra Employee
 
Posts: 4,792
Default

The log should look like:

Code:
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Looks like something is running on 110, 995, 143, or 993

Are you running an IMAP or POP server?
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #4 (permalink)  
Old 04-17-2006, 03:08 AM
Junior Member
 
Posts: 5
Default

System is a fresh Debian Sarge and the last zimbra version 3.1.0_GA_332.
Preconfigured postfix, proc, clamav, spamassasin. So after installation everything is working fine ,but after rebooting the maschine tomcat will not start (see the log)!!

Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: antispam: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: antivirus: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: ldap: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: logger: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: mailbox: Stopped
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: mta: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: snmp: Running
Apr 17 12:08:04 Cod2boX zimbramon[28688]: 28688:info: 2006-04-17 12:08:02, STATUS: Cod2boX.thelight.servegame.org: spell: Running

zimbra@Cod2boX:~/bin$ zmcontrol status
Host Cod2boX.thelight.servegame.org
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
tomcat is not running
mta Running
snmp Running
spell Running

Last edited by thelight; 04-17-2006 at 03:16 AM..
Reply With Quote
  #5 (permalink)  
Old 04-17-2006, 03:36 AM
Zimbra Consultant & Moderator
 
Posts: 20,312
Default

What does
Quote:
Originally Posted by thelight
Preconfigured postfix, proc, clamav, spamassasin.
mean? Have you removed or disabled those services on your system? After a reboot have you looked to see if there are any other services running? What do the zimbra logs say after the reboot?
__________________
Regards


Bill

Last edited by phoenix; 04-17-2006 at 04:38 AM..
Reply With Quote
  #6 (permalink)  
Old 04-17-2006, 04:12 AM
Junior Member
 
Posts: 5
Default

Hi

no, they are still running. This is the log after reboot.


17.04.2006 13:12:01 org.apache.catalina.startup.HostConfig deployDescriptor
WARNUNG: A docBase /opt/zimbra/apache-tomcat-5.5.15/webapps/zimbra inside the ho
st appBase has been specified, and will be ignored
log4j:WARN No appenders could be found for logger (org.apache.catalina.session.M
anagerBase).
log4j:WARN Please initialize the log4j system properly.
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server process is running as root, changing to user=zimbra uid=1005 gid=1
003
Zimbra server process, after change, is running with uid=1005 euid=1005 gid=1003
egid=1003
Reply With Quote
  #7 (permalink)  
Old 04-17-2006, 04:41 AM
Zimbra Consultant & Moderator
 
Posts: 20,312
Default

So what you're saying is that the versions of postfix, proc, clamav, spamassasin that are installed with your version of linux are still running after a reboot? If that's the case you need to disable them from running at boot time, or have I misunderstood what you've said?
__________________
Regards


Bill
Reply With Quote
  #8 (permalink)  
Old 04-17-2006, 05:15 AM
Junior Member
 
Posts: 5
Default

yes right.
Reply With Quote
  #9 (permalink)  
Old 04-17-2006, 05:32 AM
Zimbra Consultant & Moderator
 
Posts: 20,312
Default

Quote:
Originally Posted by thelight
yes right.

What does that mean, they're still running or that I've misunderstood.

Well, that means you've got to stop those services from starting when you reboot. When you've done that Zimbra should be OK.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 04-17-2006, 08:10 AM
Former Zimbran
 
Posts: 5,606
Default

Hi TheLight,
Phoenix is totally right.
Zimbra comes with its own postfix, proc, clamav, and spamassasin. If you already have one of them installed and running, your going to have a conflict.

You should disable those services, then try again.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
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.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.