Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Cannot access admin console after install on Suse 10x

  1. #1
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default 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 06:23 PM.

  2. #2
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    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?

  3. #3
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default

    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 11:36 AM.

  4. #4
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    That's the correct URL - anything in /opt/zimbra/tomcat/log/catalina.out?

    /var/log/zimbra.log must be readable by zimbra

  5. #5
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default

    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 01:23 PM.

  6. #6
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default 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

  7. #7
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    what's in /tmp/swatch.out, /tmp/logswatch.out?

    Is that /var/log/zimbra.log, or /opt/zimbra/log/zimbra.log?

  8. #8
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default

    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.

  9. #9
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    Look at that. You're running on a 64 bit machine - not supported by zimbra, unless you build from source.

  10. #10
    Join Date
    Mar 2006
    Posts
    11
    Rep Power
    9

    Default

    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.

Similar Threads

  1. Silly mistake -- now cant log into admin console
    By animasana in forum Administrators
    Replies: 10
    Last Post: 07-05-2007, 05:00 AM
  2. Install on (64bit !) SUSE Linux Entreprise Server 10
    By fillide in forum Installation
    Replies: 1
    Last Post: 07-04-2007, 10:06 AM
  3. Can't Access to Admin Console
    By GameSky in forum Installation
    Replies: 32
    Last Post: 05-26-2007, 01:25 AM
  4. Access to admin only after rebooting
    By josus in forum Administrators
    Replies: 0
    Last Post: 11-03-2006, 02:06 AM
  5. Fedora Core 3, Clean Install - Not working!
    By pcjackson in forum Installation
    Replies: 17
    Last Post: 03-05-2006, 07:38 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •