01-26-2012 07:29 PM
I've been having trouble getting a new 5.5 install to connect to my PostgreSQL server and I tracked it down to the config parameters not being copied to nuxeo.xml. Any suggestions on what to do?
Using CentOS 6.2.
02-03-2012 07:16 PM
I got this solved.
Apparently, the xml file doesn't get updated with the postgresql settings if the database can't be reached. So this was a symptom, not the cause.
The cause turned out to be a simple firewall rule that was incorrect. In testing I had added rules to allow all traffic, but that wasn't sufficient. Once I completely disabled the firewall, nuxeo was able to connect to the database and everything worked great. Then we were able to recognize the bad rule.
01-28-2012 01:39 PM
I had a similar problem when I updated my template to 5.5. In the nuxeo.defaults
file inside your template you must set the installation target according to the name of your template. For example, my custom template is called ima
, so I have a setting in templates/ima/nuxeo.defaults
which is ima.target=.
02-03-2012 07:16 PM
I got this solved.
Apparently, the xml file doesn't get updated with the postgresql settings if the database can't be reached. So this was a symptom, not the cause.
The cause turned out to be a simple firewall rule that was incorrect. In testing I had added rules to allow all traffic, but that wasn't sufficient. Once I completely disabled the firewall, nuxeo was able to connect to the database and everything worked great. Then we were able to recognize the bad rule.
02-03-2012 07:44 PM
Thanks for the feedback, I'll try to reproduce in order to make the cause being properly detected and logged.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.