Quote:
Originally Posted by phoenix You should be able to view the logfiles as root or the zimbra user.What are the permissions on the Zimbra log files? Run an 'ls -l filename' for the logfile that trying to view.
Have you had any system problems such as the root partition becoming full? |
Hi phoenix, thanks for joining in.
I did my homework and figured out how to change the permissions, so I believe I can access the logs now.
Might help if I describe the events that led to the problem. I wanted to be able to access our mail through Outlook, using IMAP. In Admin console I saw that IMAP service was disabled - at the time I didn't realize that this was intentional - so I enabled it in server and in global settings. That's when things went wrong. After a reboot, none of us could get access through the browser interface and I could no longer log in the Admin console.
After some digging through the forum search pages, I found out that Tomcat can stop if there is a service running on port 143/IMAP. Initially I was able to get it restarted with zmcontrol, logged back into Admin console and stop the IMAP service. Things went OK for a while, then I got creative (duh) and thought I could still use IMAP if I changed the ports to something other than 143, so I used 5143 and restarted the IMAP services.
After another server restart, mailbox & tomcat both failed to start again, and this time 'zmcontrol start' would not get things going again.
I tried 'zmperditionctl stop' (after reading a forum thread), which appeared to stop the IMAP/POP services, but then zmcontrol still failed to start the mailbox due to tomcat not running.
So that's basically where I'm at now, except that zmcontrol start does get any further than ldap running, as sldap fails now (see previous post)
I guess the good thing is I'm learning a lot more about Linux & Zimbra as I go through this!