New 5.5 install not copying config to nuxeo.xml
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.
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.
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
You mean “not being copied to nuxeo.conf”. Try to manually edit the nuxeo.conf file.
templates/postgresql/nuxeo.defaults?<br> If so, then run "./bin/nuxeoctl -d configure" and please post your "log/console.log" file (on some site such as http://friendpaste.com/).<br> Maybe post also the result of "tree".
Nuxeo home: /nuxeo<br> Nuxeo configuration: /nuxeo/bin/nuxeo.conf<br> Log level set to DEBUG for: org.nuxeo<br> Include template: /nuxeo/templates/common<br> Include template: /nuxeo/templates/default<br> Include template: /nuxeo/templates/postgresql<br> Detected Tomcat server.<br> Configuration files generation (nuxeo.force.generation=true)…<br> Configuration files generated.
conf/server.xml. What is the configuration of the "jdbc/nuxeo" resource?<br> You didn't say if you checked the "postgresql.target" value (must equal ".") in