Quote:
|
Originally Posted by wannabetenor Looks like something is already running on port 110
Make sure that all zimbra services are stopped.
ps auxww | grep zimbra or ps auxww | grep tomcat
Kill any left over processes,
Then check to see if something is running on port 110
netstat -s -a
or
telnet hostname.domain.com 110
john |
Hi...
I did all of the above prior to installing the upgrade....as well when I re-installed the upgrade.......
I then tried something off the wall.....I stopped zimbra using zmcontrol stop...I stopped the portmap service.....and I then started zimbra using the zmcontrol start.....which worked....
....and I then started the portmap service.....
....So.....what exactly does the portmap service do....and why would it lock port 110.....?????
I don't know....but it worked......more importantly......zmcontrol can now start and stop zimbra and tomcat is now behaving normally......?????
Thanks for replying....