FYI

I have played around starting the server without root permissions.

I have set the whole rhq directory to rhq.rhq ownership, and modified the init script by inserting "su - rhq -c " before the invocation of start scripts

looked pretty fine, no other errors then originally. Afterall, to see the results I have also started once with "service rhq console", end aw interesting error messages. There was no storage started at all.

So I have started the storage by hand, then also the agent, and finally the server (using rhqctl)...

and VOILA, the server's up and running... Can someone find any reason, what on earth did happen to the system, that the init script which had work for weeks, could not start the system? Anyway, I am pretty sure, that I have also tried the same earlier, but while playing around, I have also noticed a warning: a request to resolv "rhqserver". I have created an alias in /etc/hosts (I usually create such, could not frame until how these enrties vanishes with time). It's also possible that there's a connection.

It's not mentioned in bin/rhq-server.properties..

A

2013/12/2 Attila Heidrich attila.heidrich@gmail.com

Something has happened to several of my RHQ servers. The 4.10 snapshot show the same for ages, but now I see the same on the test version of the 4.9 as well.

I found other guys with the same problem, but found no solution untill now.

https://access.redhat.com/site/solutions/625983

Any ide how to solve this?

I have tried to change the listen address from 0.0.0.0 to a more specific one, but this is in rhq-server.properties, so I guess it is just taken at install.

I have tried to remove the rhq-server java properties from root's home, and restart the server (since "rhqctl install" didn't do anything), but the listener address of the JBoss server is still the same: 0.0.0.0.

Attila