Monitoring : Data not yet avalaible

Ask questions about your setup or get help installing ZCS server (ZD section below).
Post Reply
s3nz3x
Posts: 33
Joined: Fri Sep 12, 2014 10:01 pm

Monitoring : Data not yet avalaible

Post by s3nz3x »

in the webconsole/server stats, I've got everywhere : "Data not yet avalaible".

for the last 30/60/365 days I think I do now why ;) but it's been some time now that i should see something in 48h ? Also I don't see anything inothers tabs (messaeg count, etcÂ…).

Could this be because:

1) I crashed & forced reboot ?

2) bad permissions ?
maybe is it "not yet implemented"
marcmac
Elite member
Elite member
Posts: 2091
Joined: Fri Sep 12, 2014 9:53 pm

Monitoring : Data not yet avalaible

Post by marcmac »

s3nz3x
Posts: 33
Joined: Fri Sep 12, 2014 10:01 pm

Monitoring : Data not yet avalaible

Post by s3nz3x »

I'll look at thisÂ…

thx
s3nz3x
Posts: 33
Joined: Fri Sep 12, 2014 10:01 pm

Monitoring : Data not yet avalaible

Post by s3nz3x »

hum, Sorry I check out the link, but didn't really helped me find out.

mysql seems to be fine, tomcat too. but no logs.
AS it seems to be somewhat linked to java version and that I'm on MacosX, I did some tricks lately like changing java_home with speed improvments


but">http://www.zimbra.com/forums/showpost.p ... stcount=16
but it didn't changed the logs in admin console.
some log in particular that I should look ?
marcmac
Elite member
Elite member
Posts: 2091
Joined: Fri Sep 12, 2014 9:53 pm

Monitoring : Data not yet avalaible

Post by marcmac »

s3nz3x
Posts: 33
Joined: Fri Sep 12, 2014 10:01 pm

Monitoring : Data not yet avalaible

Post by s3nz3x »

my system just crashed AGAIN. I really don't understand what's going on.

the good thing is that I was just there and saw it about few minutes after.

Just had the time to restart the server (properly) this time (no force reboot)

zimbralog:

Dec 1 00:59:49 zimbra sudo: zimbra : TTY=unknown ; PWD=/opt/zimbra ; USER=root ; COMMAND=/opt/zimbra/postfix-2.2.3/sbin/postalias /etc/aliases

Dec 1 00:59:51 zimbra postfix/postalias[1046]: fatal: bad numerical configuration: message_size_limit =

Dec 1 00:59:52 zimbra sudo: zimbra : TTY=unknown ; PWD=/opt/zimbra ; USER=root ; COMMAND=/opt/zimbra/postfix-2.2.3/sbin/postfix reload norewrite

Dec 1 00:59:52 zimbra postfix[1048]: fatal: bad numerical configuration: message_size_limit =

Dec 1 00:00:00 zimbra postfix/postqueue[1063]: fatal: bad numerical configuration: message_size_limit =

--

I've already seen this "fatal: bad numerical configuration:" I thought I entered bad size so I've put 0 in the config (unlimited). didn't change as I still have this "fatal: bad numerical configuration:"

--

so I looked at other logs like clamd: it stops randomly and I don't know why:

clamd log:

Wed Nov 30 23:56:16 2005 -> +++ Started at Wed Nov 30 23:56:16 2005

Wed Nov 30 23:56:16 2005 -> clamd daemon 0.87.1 (OS: darwin8.3.0, ARCH: ppc, CPU: powerpc)

Wed Nov 30 23:56:16 2005 -> Log file size limited to 20971520 bytes.

Wed Nov 30 23:56:16 2005 -> Reading databases from /opt/zimbra/clamav/db

Wed Nov 30 23:56:20 2005 -> Protecting against 34867 viruses.

Wed Nov 30 23:56:20 2005 -> Bound to port 3310

Wed Nov 30 23:56:20 2005 -> Setting connection queue length to 15

Wed Nov 30 23:56:20 2005 -> Archive: Archived file size limit set to 104857600 bytes.

Wed Nov 30 23:56:20 2005 -> Archive: Recursion level limit set to 8.

Wed Nov 30 23:56:20 2005 -> Archive: Files limit set to 1000.

Wed Nov 30 23:56:20 2005 -> Archive: Compression ratio limit set to 250.

Wed Nov 30 23:56:20 2005 -> Archive support enabled.

Wed Nov 30 23:56:20 2005 -> Archive: RAR support disabled.

Wed Nov 30 23:56:20 2005 -> Portable Executable support enabled.

Wed Nov 30 23:56:20 2005 -> Mail files support enabled.

Wed Nov 30 23:56:20 2005 -> OLE2 support enabled.

Wed Nov 30 23:56:20 2005 -> HTML support enabled.

Wed Nov 30 23:56:20 2005 -> Self checking every 1800 seconds.

Thu Dec 1 00:46:09 2005 -> Pid file removed.

Thu Dec 1 00:46:09 2005 -> Exiting (clean)

Thu Dec 1 00:46:09 2005 -> --- Stopped at Thu Dec 1 00:46:09 2005

Thu Dec 1 00:47:23 2005 -> +++ Started at Thu Dec 1 00:47:23 2005

Thu Dec 1 00:47:23 2005 -> clamd daemon 0.87.1 (OS: darwin8.3.0, ARCH: ppc, CPU: powerpc)

Thu Dec 1 00:47:23 2005 -> Log file size limited to 20971520 bytes.

Thu Dec 1 00:47:23 2005 -> Reading databases from /opt/zimbra/clamav/db

Thu Dec 1 00:47:30 2005 -> Protecting against 34867 viruses.

Thu Dec 1 00:47:30 2005 -> Bound to port 3310

Thu Dec 1 00:47:30 2005 -> Setting connection queue length to 15

Thu Dec 1 00:47:30 2005 -> Archive: Archived file size limit set to 104857600 bytes.

Thu Dec 1 00:47:30 2005 -> Archive: Recursion level limit set to 8.

Thu Dec 1 00:47:30 2005 -> Archive: Files limit set to 1000.

Thu Dec 1 00:47:30 2005 -> Archive: Compression ratio limit set to 250.

Thu Dec 1 00:47:30 2005 -> Archive support enabled.

Thu Dec 1 00:47:30 2005 -> Archive: RAR support disabled.

Thu Dec 1 00:47:30 2005 -> Portable Executable support enabled.

Thu Dec 1 00:47:30 2005 -> Mail files support enabled.

Thu Dec 1 00:47:30 2005 -> OLE2 support enabled.

Thu Dec 1 00:47:30 2005 -> HTML support enabled.

Thu Dec 1 00:47:30 2005 -> Self checking every 1800 seconds.

Thu Dec 1 00:59:49 2005 -> Pid file removed.

Thu Dec 1 00:59:49 2005 -> Exiting (clean)

Thu Dec 1 00:59:49 2005 -> --- Stopped at Thu Dec 1 00:59:49 2005

---Didn't stop it.
catalina.log:

zmtomcatstart: info: stale pid 340 in pid file: No such process

Dec 1, 2005 12:47:30 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-80

Dec 1, 2005 12:47:32 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-7071

Dec 1, 2005 12:47:32 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 4406 ms

Dec 1, 2005 12:47:32 AM org.apache.catalina.core.StandardService start

INFO: Starting service Catalina

Dec 1, 2005 12:47:32 AM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/5.5.7

Dec 1, 2005 12:47:32 AM org.apache.catalina.core.StandardHost start

INFO: XML validation disabled

Dec 1, 2005 12:47:35 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deploying web application archive service.war

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

Zimbra server reserving server socket port=995 bindaddr=null

Zimbra server reserving server socket port=143 bindaddr=null

Zimbra server reserving server socket port=993 bindaddr=null

Zimbra server process is running as root, changing to user=zimbra uid=502 gid502

Zimbra server process, after change, is running with uid=502 euid=502 gid=502 egid=502

Dec 1, 2005 12:47:44 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deploying web application archive zimbraAdmin.war

Dec 1, 2005 12:47:45 AM org.apache.catalina.core.ApplicationContext log

INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]

Dec 1, 2005 12:47:45 AM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-80

Dec 1, 2005 12:47:45 AM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-7071

Dec 1, 2005 12:47:45 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 13270 ms
I also have this errors regarding postfix:

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.2.3/conf/main.cf

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./anvil

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./bounce

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./cleanup

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./discard

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./error

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./flush

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./lmtp

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./local

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./master

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./nqmgr

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./oqmgr

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./pickup

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./pipe

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./proxymap

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./qmgr

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./qmqpd

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./scache

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./showq

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./smtp

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./smtpd

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./spawn

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./tlsmgr

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./trivial-rewrite

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./verify

Dec 1 00:47:38 zimbra postfix/postfix-script: warning: group or other writable: /opt/zimbra/postfix-2.2.3/libexec/./virtual

Dec 1 00:47:38 zimbra postfix/postfix-script: starting the Postfix mail system

Dec 1 00:47:38 zimbra postfix/master[526]: daemon started -- version 2.2.3, configuration /opt/zimbra/postfix-2.2.3/conf

Dec 1 00:47:38 zimbra zimbramon[220]: 220:info: Starting snmp

--
despite all this I've also noticed that the anti virus tries to connect to clam server. The point is that none of my computer (server or client) are connected to the Internet; I wonder if this couldn't be a starting point to my freezes ?? Can I change something so clam won't try to update definitions?.
basically my feeling is that the server comes to be full (memory ? or something and then hangs up) NB (the server is 2x1,25Ghz - 1,25Gb RAM);
Another thing is: I sometime suspect the disc itself to freezeÂ… but I ran a test block by block and nothing was reported. Should try another disc?
I'm frustrated, got my StartupItems right, everything's fine except that it can't hold a complete day, even hours ??
this peharps stupid asking but I also have another question :when I launch (Activity monitor aka TOP) I see lots of "duplicate" process to zimbra user, like:

1045 perl zimbra

1046 perl zimbra

1042 perl zimbra

Â…

560 httpd zimbra

561 httpd zimbra

562 httpd zimbra

563 httpd zimbra

554 httpd zimbra

Â…

553 tail zimbra

540 saslauthd zimbra

539 saslauthd zimbra

538 saslauthd zimbra

537 saslauthd zimbra

536 saslauthd zimbra

Â…

389 mysqld zimbra

343 mysqld zimbra

Â… some process by postfix

344 java zimbra (81.29 mb Real Memory)

---

I've put lots of stuff here but really don't know where to find the Crash-Freeze reason.

I test this to 'present' it to a friend-client, wishing to get them to the zimbra-network pack. they have tons of daily mail are on 'beurk' windoze.

And I can't afford to go there each time. If I get this email stuff going good, I may take care of the rest of their networkÂ… I'm desperate here ;)
waiting if macman the Man, has got a clue with all this, and in the same time I'm right now going to do a clean install of OsX 10.4.3 on another partition (on the same disk) to see if changes something or not. If not well that maybe the disc ?
please find me the faulty stuff hereÂ…
marcmac
Elite member
Elite member
Posts: 2091
Joined: Fri Sep 12, 2014 9:53 pm

Monitoring : Data not yet avalaible

Post by marcmac »

Do you know what time, exactly, the server crashed? Open up the log console (Applications/Utilities, I think) and see if the system log says anything.
It's not the message_size_limit error - that's a known issue. Likewise, the other postfix warnings won't cause a crash.
Clamd looks like it was shut down, not crashed - so I don't think it caused the crash.
To shut down the AV updates, kill freshclam, and comment it out of zmantivirusctl.
THe multiple processes are normal - some of the daemons start several children to process requests.
You mentioned disk - is zimbra on a local disk, or a network volume, a SAN, ???
s3nz3x
Posts: 33
Joined: Fri Sep 12, 2014 10:01 pm

Monitoring : Data not yet avalaible

Post by s3nz3x »

so reactiveÂ… thx
Ok I understood and I'm gonna to see if I can determine @ what time it crashes. I don't really think it's a specific time. it seems it's more like after 'some uptime' more or less 2 to 4 hours I think.
The disc is local. It was first on a firewire800 disk, I though this could be the pb so I've installed it as an internal disc. Both way it's local; NO san nor network disc.

I've repartionning the 'original disc' to make a second partition. and I'm currently installing OSX on it. I think an hour or two And I'll be starting a second zimbra (zimbra#1).

I'll let you know asap about logs, as right now, I've no access to the 'zimbra#1' while installing my 'zimbra#2'.

thx again for clarification, I'll do what you suggest for antivirus checking.

(sorry for some 'silly' questions hereÂ…).
Post Reply