The current log is 0 length, and indeed empty. I just tried 'sudo pg_ctlcluster 9.3 main start' and got the following error: Error: Config owner (kcb:1000) and data owner (postgres:116) do not match, and config owner is not root Changed to user postgres, tried again and got: Warning: the cluster will not be running as a systemd service. Consider using systemctl: sudo systemctl start postgresql@9.3-main Removed stale pid file. Next tried the suggestion: sudo systemctl start postgresql@9.3-main, but the system failed to accept the password for user postgres. That is NOT something I changed during the Ubuntu upgrade process, so that has been a puzzle as well. My main login, user kcb is OK, password still works. So I change back to user kcb and try the suggestion again: kcb: jobs(0)$ sudo systemctl start postgresql@9.3-main Job for postgresql@9.3-main.service failed because the control process exited with error code. See "systemctl status postgresql@9.3-main.service" and "journalctl -xe" for details. kcb: jobs(0)$ systemctl status postgresql@9.3-main.service ● postgresql@9.3-main.service - PostgreSQL Cluster 9.3-main Loaded: loaded (/lib/systemd/system/postgresql@.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-03-28 19:51:50 MDT; 47s ago Process: 2960 ExecStart=postgresql@%i --skip-systemctl-redirect %i start (code=exited, status= Mar 28 19:51:50 kcb-VirtualBox systemd[1]: Starting PostgreSQL Cluster 9.3-main... Mar 28 19:51:50 kcb-VirtualBox postgresql@9.3-main[2960]: Error: Config owner (kcb:1000) and dat Mar 28 19:51:50 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Control process exited, Mar 28 19:51:50 kcb-VirtualBox systemd[1]: Failed to start PostgreSQL Cluster 9.3-main. Mar 28 19:51:50 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Unit entered failed stat Mar 28 19:51:50 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Failed with result 'exit Is it possible a big problem is that the password for user postgres not longer works for some reason, not sure why. It appears the password can not be rest or changed without knowing the original, and what I thought was the original no longer works. Output of that is in the attached file; On 03/28/2018 04:58 PM, Adrian Klaver wrote: > 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.- >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> >> > >
Mar 28 20:05:01 kcb-VirtualBox CRON[3050]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 28 20:05:01 kcb-VirtualBox CRON[3051]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 28 20:05:01 kcb-VirtualBox CRON[3050]: pam_unix(cron:session): session closed for user root Mar 28 20:06:31 kcb-VirtualBox sudo[3073]: kcb : TTY=pts/2 ; PWD=/home/kcb ; USER=root ; COMMAND=/bin/systemctl start postgresql@9.3-main Mar 28 20:06:31 kcb-VirtualBox sudo[3073]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 28 20:06:31 kcb-VirtualBox systemd[1]: Starting PostgreSQL Cluster 9.3-main... -- Subject: Unit postgresql@9.3-main.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postgresql@9.3-main.service has begun starting up. Mar 28 20:06:31 kcb-VirtualBox postgresql@9.3-main[3076]: Error: Config owner (kcb:1000) and data owner (postgres:116) do not match, and config owner is not root Mar 28 20:06:31 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Control process exited, code=exited status=1 Mar 28 20:06:31 kcb-VirtualBox systemd[1]: Failed to start PostgreSQL Cluster 9.3-main. -- Subject: Unit postgresql@9.3-main.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postgresql@9.3-main.service has failed. -- -- The result is failed. Mar 28 20:06:31 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Unit entered failed state. Mar 28 20:06:31 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Failed with result 'exit-code'. Mar 28 20:06:31 kcb-VirtualBox sudo[3073]: pam_unix(sudo:session): session closed for user root Mar 28 20:08:33 kcb-VirtualBox sudo[3100]: kcb : TTY=pts/2 ; PWD=/home/kcb ; USER=root ; COMMAND=/bin/systemctl start postgresql@9.3-main Mar 28 20:08:33 kcb-VirtualBox sudo[3100]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 28 20:08:33 kcb-VirtualBox systemd[1]: Starting PostgreSQL Cluster 9.3-main... -- Subject: Unit postgresql@9.3-main.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postgresql@9.3-main.service has begun starting up. Mar 28 20:08:34 kcb-VirtualBox postgresql@9.3-main[3103]: Error: Config owner (kcb:1000) and data owner (postgres:116) do not match, and config owner is not root Mar 28 20:08:34 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Control process exited, code=exited status=1 Mar 28 20:08:34 kcb-VirtualBox systemd[1]: Failed to start PostgreSQL Cluster 9.3-main. -- Subject: Unit postgresql@9.3-main.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postgresql@9.3-main.service has failed. -- -- The result is failed. Mar 28 20:08:34 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Unit entered failed state. Mar 28 20:08:34 kcb-VirtualBox systemd[1]: postgresql@9.3-main.service: Failed with result 'exit-code'. Mar 28 20:08:34 kcb-VirtualBox sudo[3100]: pam_unix(sudo:session): session closed for user root
