zmcontrol status

[tbullock]

Hi everyone,

This is the expected results from a zmcontrol status command as posted in the Quick Start Guide:

[root@infodev ~]# su - zimbra
[zimbra@infodev ~]$ zmcontrol status
Calling GetServiceInfoRequest (mailhost.maildomain.com)
RESPONSE: (serviceInfo)
antispam
status Running
antivirus
status Running
ldap
status Running
mailbox
status Running
mta
status Running
snmp
status Running
host
ip 10.10.130.161
name mailhost.maildomain.com

These are my results for the same command:

[zimbra@mail root]$ zmcontrol status
Calling GetServiceInfoRequest (mail.zimbra.avmax.ca)

RESPONSE: (Zimbra::Mon::serviceInfo)
host
ip 127.0.0.1
name mail.zimbra.avmax.ca


Obviously a huge difference but I am at a loss as to why.

Any ideas?

Cheers,

Travis

[Viper_iii]

You running Fedora Core 3 or 4?

I noticed that I couldn't get the darn thing running on FC4 at all. Too many errors.

Installed FC 3 and it fired right up.

I did have to make some dns edits on my internal dns servers that I use to point towards the demo domain.

Once the DNS was right everything worked great. Just need collaboration calendaring - public folders type of system to share calendars and restrict permissions according to who needs access.

[tbullock]

FC3.....I have done so many installs/un-installs I am getting dizzy....

For each uninstall I run: ./install.sh -u

Is that the best way to do it? Is this uninstall clearing "everything"...or is there a few more options I could use to ensure a complete "clean"?

Cheers,

Travis

[KevinH]

Originally Posted by tbullock

FC3.....I have done so many installs/un-installs I am getting dizzy....

For each uninstall I run: ./install.sh -u

Is that the best way to do it? Is this uninstall clearing "everything"...or is there a few more options I could use to ensure a complete "clean"?

Cheers,

Travis

You can run "ps -ef | grep zimbra" and kill anything left. Also may want to "rm -rf /opt/zimbra". This will be fully clean.

Please post your install log after your next clean install. My guess is we'll find something wrong in there.

/tmp/install.log.