has anyone been able to use the new Zenoss 4.2 VMware image? I can't get it to go past the first user setup page. I used the VMware standalone converter to convert the machine to ESX instead of following the instructions in the guide. Should that make a difference?
Is this the CentOS 5.2 OS with Zenoss Core 4.2.0 VM Appliance?
I was able to get it to work with VMWare Server 2.0.2; without much difficulty, I believe the only modification I had was some additional vmx configuration options to pin the memory (must also have parameter enabled on vmware server):
sched.mem.pshare.enable = "FALSE"
MemTrimRate = 0
prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100"
I have the same issue as well. Downloaded the 4.2.3 VM today. Looks like it's exactly the same issue. As the last post was from October, that's almost 4 months with no resolution.
Just to add to the issue description. I can force it to the second wizard screen by changing the URL to "qs-step2" and then clicking the "Finish" button works. However that doesn't seem to get "something" completely configured. While that drops me to the main Zenoss webpage, if I try to submit any jobs they simply sit in the pending queue forever. If I try to add a location, that doesn't seem to go into the pending queue but simply pops up an error window stating that it can't connect to the "server" without any specific details about which process it's having issues with.
Just to complete the details, I also used the VMWare converter to deploy the VM into ESX 4.1. I saw another issue related to changing the hostname and rabbitmq, so all I've done is change the ifcfg-eth0 network script to make the vm static and supply an ip address, mask and gateway. I left all other configuration untouched. The VM is fully accessible from other computers on the network. And as others have tried, I have tried to use multiple vendors with the same results.
Any suggestions are more than welcome.
We don't use Zenoss anymore/at all - but I did figure out why I was having this issue.
I was changing the IP address of the server. I don't remembe the specifics of the problem, but I remember if I never changed the IP - or changed the IP back to the original, then it would work properly.
Somethign about an IP address causing some services not to start correctly or something.
Again this was months ago and I don't use the product, but for me it was because I was changning an IP.
From what you are describing, there may be an error in the /opt/zenoss/log/event.log file with more details on the problem. Can you post any tracebacks from that log file here so we can further analyze it? I think it may have something to do with RabbitMQ changing the location of its database files when the IP address changes.
I did get it to work. It is related to rabbitmq and is dicussed in this post:
It's also discussed in the Rlease Notes for 4.2.3 for changing the hostname. They don't give very good details though.
Here's what I did to get it working:
1. Create the /etc/rabbitmq/rabbitmq-env.conf file
2. The only item I have in the file is "NODENAME=<new hostname>"
3. Reboot the VM
4. Once the instance is back up fully, execute the command from the Release Notes. Just for completeness they are:
rabbitmqctl add_vhost "$VHOST"
rabbitmqctl add_user "$USER" "$PASS"
rabbitmqctl set_permissions -p "$VHOST" "$USER" '.*' '.*' '.*'
5. Stop Zenoss - service zenoss stop
6. Start Zenoss - service zenoss start
Once I did the above, the "Getting Started" wizard works without issue as did adding new locations and systems to the configuration.