Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade

On 03/28/2018 03:45 PM, Ken Beck wrote:
> Thanks for both responses -- the file contents I sent were from file
> named postgresql-9.3-main.log.1, and I am assuming this means from the

Well that is an archived log and would show old information. The current 
log would be postgresql-9.3-main.log.

> 9.3, not 9.6. Sorry I did not include that earlier. Starting to sousnds
> like I need to consult Ubuntu user groups.

Not necessarily as there are many Ubuntu users on this list.

Did you try?:

sudo pg_ctlcluster 9.3 main start

> 
> Ken Beck
> Liberty, Utah, USA
> 
> On 03/28/2018 10:46 AM, Moreno Andreo wrote:
>> Il 28/03/2018 18:28, Adrian Klaver ha scritto:
>>> On 03/28/2018 09:24 AM, Moreno Andreo wrote:
>>>> Il 27/03/2018 22:57, Adrian Klaver ha scritto:
>>>>> On 03/27/2018 01:46 PM, Ken Beck wrote:
>>>>>> I am working on two systems, one running in Oracle VirtualBox on my
>>>>>> laptop, the other in a DigitalOcean droplet. I know on one of them I
>>>>>> tried to remove the postgres-9.6, and it must have been my laptop,
>>>>>> here
>>>>>> is the output from pg_lsclusters:
>>>>>>
>>>>>> Ver Cluster Port Status Owner    Data directory Log file
>>>>>> 9.3 main    5432 down   postgres /var/lib/postgresql/9.3/main
>>>>>> /var/log/postgresql/postgresql-9.3-main.log
>>>>>
>>>>> What happens if you do?:
>>>>>
>>>>> sudo pg_ctlcluster 9.3 main start
>>>> If possible, I'll take a look at
>>>> /var/log/postgresql/postgresql-9.3-main.log.
>>>> That may give us a big help to uncover what's goin'on.
>>>
>>> See this post:
>>> https://www.postgresql.org/message-id/5bad1f01-d06a-1526-96d2-c9cfd6062a11%40gmail.com
>>>
>> Yes I saw it, but I can't say if that log was from 9.3 or 9.6
>> cluster... as you can see above he wrote that he had a 9.6, that he
>> tried to remove, and a 9.3, which was not starting. So it's not clear
>> to me if the log he sent was from one version or the another...
>>
>>>
>>>>
>>>> Cheers
>>>>
>>>> Moreno.-
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com