| 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.
|
 | | 
03-02-2006, 05:20 PM
| | |  Cannot access admin console after install on Suse 10x
Install went fine, with the only unresolvable error being a failure to notify Zimbra of the installation.
I am running the freely available version of Suse 10.0, with all the latest online software updates. Zimbra version is the latest Open Source Suse 10.0 binary (3.0.1) available here: http://prdownloads.sourceforge.net/z...0.tgz?download Code: zimbra@mailhost:~> zmcontrol status
Host mailhost.trn.local
antispam Stopped
antivirus Stopped
ldap Running
logger Stopped
mailbox Running
mta Running
snmp Stopped
spell Running At this moment, I am unable to upload attachments to the Zimbra forum for some reason. I will try posting the setup, config, and server logs later.
Last edited by srf21c; 03-02-2006 at 05:23 PM..
|
03-02-2006, 05:22 PM
| | Zimbra Employee | |
Posts: 2,103
| |
If half of the services failed to start, I'd say that notification isn't the only problem.
Looks to me like /var/log/zimbra.log isn't readable by zimbra, and you've got some kind of amavis startup problem.
Not sure what's happening with the admin console - what url did you go to? |
03-03-2006, 10:34 AM
| | |
Quote: |
Originally Posted by marcmac If half of the services failed to start, I'd say that notification isn't the only problem.
Looks to me like /var/log/zimbra.log isn't readable by zimbra, and you've got some kind of amavis startup problem.
Not sure what's happening with the admin console - what url did you go to? | I'd have to agree that half of the services failing to start IS a problem!
URL I'm using to access the admin console is: https://192.168.0.2:7071/zimbraAdmin
Current permissions for zimbra.log are:
-rw-r----- 1 root root 1707404 Mar 3 03:28 zimbra.log
....what should the permissions look like?
Still not able to upload file attachments to forum using either IE 6x or FireFox 1.5
Last edited by srf21c; 03-03-2006 at 10:36 AM..
|
03-03-2006, 10:37 AM
| | Zimbra Employee | |
Posts: 2,103
| |
That's the correct URL - anything in /opt/zimbra/tomcat/log/catalina.out?
/var/log/zimbra.log must be readable by zimbra |
03-03-2006, 12:15 PM
| | |
Quote: |
Originally Posted by marcmac That's the correct URL - anything in /opt/zimbra/tomcat/log/catalina.out?
/var/log/zimbra.log must be readable by zimbra | Yap, contents of catalina.out posted below.
Would a chmod 666 on the zimbra.log file do the trick? Code: zimbra@mailhost:~/tomcat/logs> cat catalina.out
zmtomcatstart: info: stale pid 21142 in pid file: No such process
Mar 3, 2006 3:25:19 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-80
Mar 3, 2006 3:25:21 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-7071
Mar 3, 2006 3:25:21 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2503 ms
Mar 3, 2006 3:25:21 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar 3, 2006 3:25:21 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.7
Mar 3, 2006 3:25:21 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
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
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=1001 gid=1000
Zimbra server process, after change, is running with uid=1001 euid=1001 gid=1000 egid=1000
Mar 3, 2006 3:25:26 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-80
Mar 3, 2006 3:25:27 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-7071
Mar 3, 2006 3:25:27 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 6390 ms
Last edited by srf21c; 03-03-2006 at 12:23 PM..
|
03-03-2006, 12:34 PM
| | | made zimbra.log readable, services still do not stay running
ran a chmod 666 on /var/log/zimbra.log, then stopped and started Zimbra services. See behavior of services pasted down below
Zimbra log should be writable... Code: -rw-rw-rw- 1 zimbra zimbra 0 Mar 3 03:30 zimbra.log But yet it remains empty after the service stop and restart. Code: zimbra@mailhost:~> zmcontrol start
Host mailhost.trn.local
Starting ldap...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting mta...Done.
Starting snmp...Done.
Starting spell...Done.
You have new mail in /var/spool/mail/zimbra
zimbra@mailhost:~> zmcontrol status
Host mailhost.trn.local
antispam Stopped
antivirus Stopped
ldap Running
logger Stopped
mailbox Running
mta Stopped
snmp Stopped
spell Running |
03-03-2006, 01:32 PM
| | Zimbra Employee | |
Posts: 2,103
| |
what's in /tmp/swatch.out, /tmp/logswatch.out?
Is that /var/log/zimbra.log, or /opt/zimbra/log/zimbra.log? |
03-03-2006, 01:51 PM
| | |
Quote: |
Originally Posted by marcmac what's in /tmp/swatch.out, /tmp/logswatch.out?
Is that /var/log/zimbra.log, or /opt/zimbra/log/zimbra.log? | that was /var/log/zimbra.log Code:
zimbra@mailhost:/tmp> cat swatch.out
Can't load '/opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/Time/HiRes/HiRes.so' for module Time::HiRes: /opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/Time/HiRes/HiRes.so: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.7/x86_64-linux-thread-multi/DynaLoader.pm line 230.
at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29
Compilation failed in require at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29.
BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29.
Compilation failed in require at /tmp/.swatch_script.7128 line 29.
BEGIN failed--compilation aborted at /tmp/.swatch_script.7128 line 29. Code: zimbra@mailhost:/tmp> cat logswatch.out
Can't load '/opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/Time/HiRes/HiRes.so' for module Time::HiRes: /opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/Time/HiRes/HiRes.so: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.7/x86_64-linux-thread-multi/DynaLoader.pm line 230.
at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29
Compilation failed in require at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29.
BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Swatch/Actions.pm line 29.
Compilation failed in require at /tmp/.swatch_script.6281 line 29.
BEGIN failed--compilation aborted at /tmp/.swatch_script.6281 line 29.  |
03-03-2006, 02:00 PM
| | Zimbra Employee | |
Posts: 2,103
| |
Look at that. You're running on a 64 bit machine - not supported by zimbra, unless you build from source. |
03-03-2006, 05:30 PM
| | |
Quote: |
Originally Posted by marcmac Look at that. You're running on a 64 bit machine - not supported by zimbra, unless you build from source. | Ahh! I had no idea. 
It's been so long since I've bought a server I didn't even think about whether or not it came with a 64-bit proc.
Will try building from source and giving 'er another run.
Thanks for all your patience and help. | | Thread Tools | Search this Thread | | | | | Display Modes |  Linear Mode | | Why Join? Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.   |
Bugzilla
Wiki
Source
