[SOLVED] After 6.0.5 upgrade stats shown as not running

[lytledd]

I upgraded as well, everything seems to be okay, but checking the web interface shows that stats isn't running. I did a vmcontrol stop;vmcontrol start last night (Monday) and got home today to see that it's not running again.

Anybody else notice their stats service is stoppped?

I'm running on Ubuntu 8.04 LTS

[y@w]

Yeah.. I've noticed stats stopping seemingly randomly on 5.0 as well. You don't need to restart all of Zimbra. A simple 'zmstatctl start' will usually start them up again for you.

[lytledd]

Didn't work and now even stopping and starting everything, stats fail. There are also a few stacktrace files in the /opt/zimbra/log directory. One with the time/date stamp of me doing a restart this evening. Should I open a bug?

At the bottom of the trace:

"Surrogate Locker Thread (CMS)" daemon prio=10 tid=0x080e1000 nid=0x24e4 waiting on condition [0x00000000]
java.lang.Thread.State: RUNNABLE

"Finalizer" daemon prio=10 tid=0x080cd800 nid=0x24db in Object.wait() [0x84aea000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x8fd010e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue .java:118)
- locked <0x8fd010e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue .java:134)
at java.lang.ref.Finalizer$FinalizerThread.run(Finali zer.java:159)

"Reference Handler" daemon prio=10 tid=0x080cc000 nid=0x24d9 in Object.wait() [0x84b2b000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x8fd013d8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:485)
at java.lang.ref.Reference$ReferenceHandler.run(Refer ence.java:116)
- locked <0x8fd013d8> (a java.lang.ref.Reference$Lock)

"VM Thread" prio=10 tid=0x080c8000 nid=0x24d6 runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x0806bc00 nid=0x24d3 runnable
"VM Periodic Task Thread" prio=10 tid=0x080ea400 nid=0x24ea waiting on condition

[Hatrix]

Hi,

check this thread, around page 6 is a possible solution for your problem:

upgrade to 6.0.2 stats and status no longer working

Hope this will help yeah, if this fixes your problem, please vote on the bug in the bugtracker.

best
Ray

[kbsu]

Check the owner in zmstat directory.

[lytledd]

[QUOTE=Hatrix;171042]Hi,

check this thread, around page 6 is a possible solution for your problem:


Ubuntu uses syslogd, not rsyslog, following the thread, everything was as it should be. Thanks for the input though.

Doug

[lytledd]

Originally Posted by kbsu

Check the owner in zmstat directory.

Several of the sub directories were owned by root. Even the newly created directory from yesterday was owned by root. What process creates these directories and how can I correct the permissions that it's assigning?

The stats service is now running.

Doug

[kbsu]

Two day ago have the same problem

Receive the mesage from zimbramon:
14772:err: Service status change: ... stats changed from running to stopped

I do the following:
1) zmstatctl stop
2) change owner to zmstat recursively to zimbra
3) zmstatctl start
4) check service status (all running)

five minutes later zimbramon send me email:
4824:err: Service status change: ... stats changed from stopped to running

The problem happened at midnight maybe it's a BUG.

[lytledd]

Originally Posted by kbsu

Two day ago have the same problem

The problem happened at midnight maybe it's a BUG.

Sounds like it. If it happens to me tonight, I'll search the bug tracker for something similar, if I don't find anything, I'll open a bug report.

Doug

[lytledd]

Checking the zmstat directory this morning shows that yesterday's stats directory is now owned by zimbra:zimbra. So far, so good.

Doug