On 03/08/2017 10:12 AM, John Iliffe wrote:
> I think you may have hit it but I'm even more confused now.
>
> I looked at the running Postgesql on the current server and there is a 5th
> sub-directory called /data. That is on the same level as the /bin, /share,
> etc. In this new installation it is not present and neither is the
> postgresql.conf file, nor are the hba files that restrict logins.
/data would be your Postgres data directory.
In your new install you put that here:
/usr/pgsql_tablespaces
When you did the initdb it created the files there. So look there for
postgresql.conf and pg_hba.conf
>
> So, my question: is this a change between version 9.2.1 and 9.6.2 and if
> so where is the postgresql.conf file (I can't find it on a scan but it could
> be renamed I suppose)?
No change those files follow the data directory.
>
> Or, is there something wrong with the installation? I went by the
> successful conclusion message from make install and assumed everything
> would be as expected in the directories.
>
> Any ideas as to what may have happened?
>
> John
> =========================================
> On Wednesday 08 March 2017 10:11:44 Melvin Davidson wrote:
>> On Wed, Mar 8, 2017 at 10:00 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> John Iliffe <john.iliffe@iliffe.ca> writes:
>>>> When the programme exited it left another postmaster.pid file so I
>>>
>>> deleted
>>>
>>>> that one too.
>>>
>>> You haven't shown us the program actually exiting, and basically the
>>> only way to get the postmaster to exit without removing its pid file
>>> is to kill -9 it. Now I am suspicious that you in fact haven't
>>> killed any postmasters, but only removed their pidfiles out from
>>> under them, which is an incredibly dangerous thing to do. Check "ps
>>> ax" output to see if any postgres processes are lurking in
>>> background.
>>>
>>> regards, tom lane
>>>
>>> --
>>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-general
>>
>> Hey, looking closer, I see this in your original log
>>
>> LOG: database system is ready to accept connections
>> LOG: autovacuum launcher started
>>
>> That means Postgres WAS started, just that the postgres port was unable
>> to be opened.
>> So if you do a pg_ctl stop, change the port in postgresql.conf to 5433
>> (or 5434) and then attempt
>> to restart, is your problem resolved?
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com