I upgraded our Zimbra M1 system and now got an error?
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException sesame.wdm.com:389)
Any ideas why?
...
Type: Posts; User: aws; Keyword(s):
I upgraded our Zimbra M1 system and now got an error?
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException sesame.wdm.com:389)
Any ideas why?
...
Thanks as that is a good addition. :-)
-Dee
I was looking through the forum for other posts related to the issue here and found an answer, or at least partially.
I issues as the zimbra user, zmsmnpinit and then zmswatchctl start and SNMP...
Thanks! I really like this package. Now I need to know if the rrdtools package is hosed.
/opt/zimbra/conf/swatchrc
[zimbra@sesame ~]$ zmcontrol status
Calling GetServiceInfoRequest...
I killed all related processes and un-installed zimbra. The upon the fresh re-install:
nstalling packages
zimbra-core......zimbra-core-3.0.M1_21.FC3-20050920155949_.i386.rpm...done
...
OK, I'll try again later and then let you know. My anniversay is tomorrow so I'll out of pocket for a couple days. :-)
-Dee
[root@sesame zcs]# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 19:10 ? 00:00:01 init [3]
root 2 1 0 19:10 ? 00:00:00 [ksoftirqd/0]...
I forgot to post this also:
root@sesame conf]# netstat -a | grep smtp
[root@sesame conf]#
So no postfix gets started.
-Dee
We have a fresh install of FC3 with no extras installed. Turned off sendmail also. Did a no problem install of zibra from rpms. Reboot shows:
Oct 4 20:42:08 sesame zimbra: Calling startup...