I thought it would be helpful to post a status update on things that have changed today...
First, we determined we had a failed zimlet upgrade issue during the install, so from the cli we undeployed and (re)deployed several zimlets to match the zimlets installed in our test box, a ZCS 6.0.4 system installed fresh at 6.0.2. We are having a Jetty problem with the Social zimlet, but everything else end-user facing is OK. (Only one of our hosted clients is clamoring for the Social zimlet, and several do not want it).
Second, we are missing Server Statistics and Certificates in the left-vertical nav bar of the Admin Console, and there is no License tab in Global Settings. On initial login to the Admin Console we are greeted with a full set of red X's, even though Zimbra on all of the servers is running fine. This thread shows something similar:
ZCS 6.0.2 Admin Interface Missing Features and/or Broken
Third, the whole logger/stats thing is, we think, a combination of several things (at least for us). See
upgrade to 6.0.2 stats and status no longer working for example.
After reading that thread carefully, I think our case is related, but there are at least two things going on here: 1) we use syslog-ng not syslogd, and 2) I don't think the updated syslogging portion of the installer completed successfully, though there is nothing in the logs we can see to confirm that.
Syslogging is not fully functional on our system just yet in that we can't get syslog-ng (remember, we are a SuSE shop and SuSE installs syslog-ng by default) to start with the Zimbra-supplied new 6.0 settings. So for the moment we are using the 5.0 settings in
/etc/syslog-ng/syslog-ng.conf:
Code:
#ZCS 5.0 Syslogging code
filter f_local0 { facility(local0); }; # zimbra
destination zmail { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_mail); destination(zmail); }; # zimbra
destination local0 { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_local0); destination(local0); }; # zimbra
filter f_auth { facility(auth); }; # zimbra
destination zmauth { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_auth); destination(zmauth); }; # zimbra
#ZCS 6.0 Syslogging code
#Syslog won't start with this Zimbra-supplied line below; syslog-ng complains of a syntax error.:
#source zimbra_src { unix-stream("/dev/log"; keep-alive(yes); max-connections(20););}; # zimbra
#Syslog will start with this modified line below
#source zimbra_src { unix-stream("/dev/log"); }; # zimbra
#filter zimbra_local0 { facility(local0); }; # zimbra
#filter zimbra_local1 { facility(local1); }; # zimbra
#filter zimbra_auth { facility(auth); }; # zimbra
#filter zimbra_mail { facility(mail); }; # zimbra
#destination zimbra_mail { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
#destination zimbra_local1 { file("/var/log/zimbra-stats.log" owner("zimbra")); }; # zimbra
#destination zimbra_local0 { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
#destination zimbra_auth { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
#log { source(zimbra_src); filter(zimbra_mail); destination(zimbra_mail); }; # zimbra
#log { source(zimbra_src); filter(zimbra_local0); destination(zimbra_local0); }; # zimbra
#log { source(zimbra_src); filter(zimbra_local1); destination(zimbra_local1); }; # zimbra
#log { source(zimbra_src); filter(zimbra_auth); destination(zimbra_auth); }; # zimbra Even when syslog-ng was started successfully with the amended ZCS 6.0 code, /var/log/zimbra-stats.log failed to populate.
Further, we have no /opt/zimbra/logger/db/data directory; I am going to try to create the directory and initialize the sqllite db as per this thread and see what happens:
upgrade to 6.0.2 stats and status no longer working
More to come!
Any tips/suggestions appreciated!
With best regards to all,
Mark