thomas i'm out of my mind. something else is running on 110, not the web port
Yes, it seems so but for the life of me I can't find anything running on port 110. Know of any commands I can run to check? I don't see anything from netstat.
I think we found it.
netstat -anp |grep ":110"
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 1828/dovecot
Stopping Dovecot Imap: [ OK ]
Thanks for your help, I guess when the server rebooted/upgraded dovecot got reinstalled. We uinstalled it and I think a Redhat update reinstalled it. Wow, what a day. Thanks again.
I have exactly same problems.
After changeing memory in vmware and reboot
tomcat refuses to stay up.
chmod zimbra:zimbra /opt/zimbra/ -R
I got tomcat to stay up a little while but now it's down again.
Nothing is running on port 110
It's probably the redo.log permissions..
Search the forum, it's covered pretty extensivly.
If not that, then the next most likely thing would be mysql passwords
Not a file permission problem since I chown/chmod:ed whol zimbra folder to zimbra:zimbra & 775
How can I check for the sql permissions?
This is what I get...
[zimbra@mail root]$ zmcontrol stop
[zimbra@mail root]$ zmcontrol start
[zimbra@mail root]$ zmcontrol status
tomcat is not running
Yeah, but I have had a couple cases where you still had to explicitly chown the redo log.
Just try it:
chown zimbra:zimbra /opt/zimbra/redolog/redo.log
Some days ago we had problems with webmail connectivity.
I used browser and changed Webmail MTA global hostname setting from localhost to mail.server.com, saved and webmail connectivity worked again.
Could this have screwed the tomcat on the next reboot?
Does someone know to what configuration files this affects and can the change be reversed after the fact?
There are currently 1 users browsing this thread. (0 members and 1 guests)