zmcontrol status returns "Cannot determine services - exiting"

[TMH]

[root@bosch zcs]# host `hostname`
Host bosch not found: 3(NXDOMAIN)

No idea why it says this, it's in my hosts file.


[root@bosch zcs]# dig steve.ac

; <<>> DiG 9.2.4 <<>> steve.ac
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7640
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;steve.ac. IN A

;; ANSWER SECTION:
steve.ac. 14096 IN A 207.210.111.143

;; Query time: 0 msec
;; SERVER: 207.210.84.124#53(207.210.84.124)
;; WHEN: Mon Jun 11 10:06:12 2007
;; MSG SIZE rcvd: 42


[root@bosch zcs]# dig steve.ac mx

; <<>> DiG 9.2.4 <<>> steve.ac mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30292
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;steve.ac. IN MX

;; ANSWER SECTION:
steve.ac. 14073 IN MX 2 bosch.steve.ac.
steve.ac. 14073 IN MX 1 steve.ac.

;; Query time: 3 msec
;; SERVER: 207.210.84.124#53(207.210.84.124)
;; WHEN: Mon Jun 11 10:06:45 2007
;; MSG SIZE rcvd: 64


The Java errors are still in my zmsetup log. I'm just going to make some calls and see if someone was lying to me about the amount of RAM on this box. If they were, I can probably get a 512mb VPS slot, would that do? This box only has to serve a few users for now.

free reports this:
[root@bosch zcs]# free -m
total used free shared buffers cached
Mem: 1024 20 1003 0 0 0
-/+ buffers/cache: 20 1003
Swap: 0 0 0

Of course, I doubt this box uses 20mb of RAM, so I suspect free is lying to me.

[phoenix]

The DNS should be OK. I have a feeling that there's something wrong with the amount of memory you have. As I said, 1GB is more than enough to get Zimbra running - you can get it working on 512MB but more is better.

You can check the amount of memory in the various settings with 'zmlocalconfig | grep mem' run as the Zimbra user. What's the output from that?

[TMH]

[zimbra@bosch ~]$ zmlocalconfig | grep mem
mysql_memory_percent = 30
tomcat_java_heap_memory_percent = 40


I haven't received a response back from the server guys yet.

[jholder]

Looks like this is the problem:

Could not create the Java virtual machine.

Typically, this type of problem is caused by low RAM/not enough memory.

You can try to increase the amount allocated to tomcat by running:

zmlocalconfig -e tomcat_java_heap_memory_percent=50

Also, check top (if free -m is lying) to see what it says the free memory is.
You can:

ps auxx

to see what's running and kill anything that you don't need.

Good luck,
jh

[TMH]

Apparently there is 256mb on this VPS. Fantastic. I bet it'll work when I can get them to upgrade it.

Thanks for your help everyone.

[bobby]

VPS probably doesn't give you enough contiguous ram to initialize the JVM ("Could not reserve enough space for object heap").

"support4.liquidsys.com" is the hostname of the machine here used to compile the build of slapd (and the rest of 32-bit RHEL ZCS I guess) in this release.

DNS tools (such as dig) and some zimbra services will use DNS exclusively. Some tools (such as ping) will work through the "hosts:" entries in /etc/nsswitch.conf.

[natrixgli]

Another interesting observation that I have made:

In my zmsetup.log, there are a number of messages that go along these lines:

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

I asked in ##java on freenode, and apparently this means the virtual machine has a set size of memory that there wasn't enough space for. This is odd, as I have 1gb of memory on this machine.

Could the above messages mean that the installation did not actually proceed properly? It would make sense, given that it is mentioning modules that I did not select.

I don't know if anyone helped with this, but I just got Zimbra running on a VPS and had the same problem as you.

The problem is that Java looks at the total memory in the machine, not just the amount allocated to your VPS/node. So you have to change the maximum memory to a smaller percentage (basically divide by the number of VPS on your node.) To find out the total amount of memory in your VPS use the command:

cat /proc/meminfo

Chances are you will need to change the java memory limit (and MySQL) to around 10-15% to stay within allowable limits on your VPS.

I know there's not a lot of help out there for running Zimbra on VPS, I don't think it's quite caught on but I am up and running now at 126 users, all of whom are using the web client. (maybe 30-40 at a time max.)

I probably should have gone with a dedicated server, but we're non-profit and thus cheaper is better. ($70/mo vs. $200+/mo)



-n8