topic Moving data directory - postgresql could not be started in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/moving-data-directory-postgresql-could-not-be-started/m-p/256322#M209452 <HTML><HEAD></HEAD><BODY><SPAN>A background of the situation - We have alfresco 4.0.d set up on ubuntu/tomcat/postgres. Originally, during testing, the contentstore was at /opt/alfresco/alf_data. I copied the directory as a whole to /mnt/alf_data and modified the alfresco-global.properties-&gt;dir.root property to match.</SPAN><BR /><SPAN>This appeared to work - restarted the server, could see the files in the repository and the test spaces which had been setup. It was only later in the day I noticed a red "Could not Retrieve tags" warning. This was accompanied by - </SPAN><PRE class="language-none line-numbers"><CODE>org.alfresco.repo.search.impl.lucene.LuceneQueryParserException: 03110615 Request failed 404 /solr/alfresco/alfresco?q=PATH%3A%22%2Fcm%3Ataggable%22&amp;wt=json&amp;fl=*%2Cscore&amp;rows=2147483647&amp;df=TEXT&amp;start=0&amp;locale=en_US&amp;fq=%7B%21afts%7DAUTHORITY_FILTER_FROM_JSON<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN> when trying to add a tag.</SPAN><BR /><SPAN>I changed /opt/alfresco/alf_data to /opt/alfresco/alf_data-old to see if it was related to the old or the new directory and restarted the server again - big problems. Postgres was unable to start, referring to a missing .conf file. I have found a few possible causes of this issue so far (obviously they weren't the whole problem as it persists) - </SPAN><BR /><BR /><SPAN>1 Permissions - as I used sudo cp to move the files they were all owned by root. In the original location this was actually par for the course, excepting the postgresql directory all the files and folders in alf_data were owned by root. I used "sudo chown -R postgres<img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />ostgres postgresql/" inside the new directory and made sure that it was set up for 0700 permissions.</SPAN><BR /><SPAN>2 postgres configuration - in /opt/alfresco/postgresql/scripts there was a script called ctl.sh which seems to be hardcoded to the original alf_data location. I didn't do the initial install of our setup so unfortunately I can't say for sure where this came from but I'd hazard a guess that it was generated by the web quick start installation. Towards the very top of this file 2 variables are defined - </SPAN><BR /><PRE class="language-none line-numbers"><CODE>POSTGRESQL_PIDFILE=/opt/alfresco/alf_data/postgresql/postmaster.pid<BR /><BR />POSTGRESQL_START="/opt/alfresco/postgresql/bin/postgres -D /opt/alfresco/alf_data/postgresql -p 5432"<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>so I changed this to </SPAN><BR /><PRE class="language-none line-numbers"><CODE>POSTGRESQL_PIDFILE=/mnt/alf_data/postgresql/postmaster.pid<BR /><BR />POSTGRESQL_START="/opt/alfresco/postgresql/bin/postgres -D /mnt/alf_data/postgresql -p 5432"<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>then saved and restarted the server.</SPAN><BR /><BR /><SPAN>It still gives me, in the logs - </SPAN><PRE class="language-none line-numbers"><CODE>/opt/alfresco/postgresql/scripts/ctl.sh : postgresql&nbsp; could not be started<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>I have looked through /postgresql/scripts/ctl.sh and found the command to start postgres - </SPAN><BR /><PRE class="language-none line-numbers"><CODE> su postgres -c "$POSTGRESQL_START &amp;"<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>and tested it </SPAN><BR /><PRE class="language-none line-numbers"><CODE>sudo su postgres -c "/opt/alfresco/postgresql/bin/postgres -D /mnt/alf_data/postgresql -p 5432"<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>which works fine (or at least, does not return an error).</SPAN><BR /><BR /><SPAN>It seems to me that somewhere, in some script, the path to alf_data has been hard coded, rather than referenced from dir.root, however I'm stumped as to where and why it is that postgres cannot start. Any thoughts or pointers appreciated</SPAN><BR /><BR /><SPAN>Edit:</SPAN><BR /><BR /><SPAN>We never fully figured out the problems with pointing the data.dir at another folder. I wouldn't suggest it unless you have a good set of backups at your disposal. What we did to get around this, in case it helps anyone else, was to reinstall alfresco (we used the linux quick installer, if you do too you'll need to select no when it asks at the very end whether you would like to start the alfresco service). After installing, our process was as follows -</SPAN><BR /><SPAN>-mount the network location to be used as data directory in a temporary location. For us, </SPAN><PRE class="language-none line-numbers"><CODE>sudo mount ip.address.of.nas:/alf_data /opt/alfresco-4.0.d/alf_data_mount<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>-copy the files from the installation alf_data to the new data directory. Again, the command for us was - </SPAN><PRE class="language-none line-numbers"><CODE>sudo cp -p -r alf_data/* alf_data_mount/<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>-Make sure the Owner/Group/Permissions match between the two folders (especially /postgres)</SPAN><BR /><SPAN>-unmount the new data dir. ours - </SPAN><PRE class="language-none line-numbers"><CODE>sudo umount ip.address.of.nas:/alf_data<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>-remount it at the original data directory location - </SPAN><PRE class="language-none line-numbers"><CODE>sudo mount ip.address.of.nas:/alf_data /opt/alfresco-4.0.d/alf_data<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><SPAN>-If you are using SOLR, set it up now, following the Wiki. Delete the existing Index stores as it will need to rebuild them on first startup.</SPAN><BR /><SPAN>-Start Alfresco - </SPAN><PRE class="language-none line-numbers"><CODE>sudo ./alfresco.sh start<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>It seems, at least with the quick installer, that a few items are hardcoded to the original alf_data directory. This turned out to be the easiest way (for us) to have a mounted resource as a data directory. I'm sure we could have eventually sorted out the various scripts pointing to this location but I figure this way, from the Alfresco Server's perspective, the data dir will always be the same one it was installed to use.</SPAN></BODY></HTML> Wed, 11 Apr 2012 05:46:26 GMT chrisokelly 2012-04-11T05:46:26Z Moving data directory - postgresql could not be started https://connect.hyland.com/t5/alfresco-archive/moving-data-directory-postgresql-could-not-be-started/m-p/256322#M209452 A background of the situation - We have alfresco 4.0.d set up on ubuntu/tomcat/postgres. Originally, during testing, the contentstore was at /opt/alfresco/alf_data. I copied the directory as a whole to /mnt/alf_data and modified the alfresco-global.properties-&gt;dir.root property to match.This appe Wed, 11 Apr 2012 05:46:26 GMT https://connect.hyland.com/t5/alfresco-archive/moving-data-directory-postgresql-could-not-be-started/m-p/256322#M209452 chrisokelly 2012-04-11T05:46:26Z Re: Moving data directory - postgresql could not be started https://connect.hyland.com/t5/alfresco-archive/moving-data-directory-postgresql-could-not-be-started/m-p/256323#M209453 <HTML><HEAD></HEAD><BODY><SPAN>Related topic that should give an answer: </SPAN><A href="https://forums.alfresco.com/forum/developer-discussions/development-environment/postgresql-not-starting-after-moving-alfdata" rel="nofollow noopener noreferrer">https://forums.alfresco.com/forum/developer-discussions/development-environment/postgresql-not-starting-after-moving-alfdata</A></BODY></HTML> Tue, 15 Sep 2015 07:15:40 GMT https://connect.hyland.com/t5/alfresco-archive/moving-data-directory-postgresql-could-not-be-started/m-p/256323#M209453 mathias_lin 2015-09-15T07:15:40Z