Hi Sopa, the actual terminal log of DPKG was not attached so I have to guess a lot here.
I found this in your journal error log: Mar 04 19:37:24 hostname systemd[1]: Failed to start PostgreSQL Cluster 10-main. Mar 04 19:37:24 hostname systemd[1]: NetworkManager-wait-online.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. Mar 04 19:40:42 hostname sudo[13993]: pam_unix(sudo:auth): conversation failed Mar 04 19:40:42 hostname sudo[13993]: pam_unix(sudo:auth): auth could not identify password for [postgres] Mar 04 19:40:42 hostname sudo[13993]: postgres : user NOT in sudoers ; TTY=pts/3 ; PWD=/var/lib/postgresql ; USER=root ; COMMAND=/etc/init.d/postgresql status Mar 04 19:40:45 hostname systemd[1]: Failed to start PostgreSQL Cluster 10-main. Mar 04 19:40:49 hostname systemd[1]: Failed to start PostgreSQL Cluster 10-main. And AFTER that the failed upgrade of the package. That lets me assume that postgres configuration was in a state that does not allow to (re)start the server. But on an upgrade that is required. You'd have to fix up your local config to let porstgres start to be able to upgrade. If you don't have custom config consider purging the config of postgres and a clean reinstall of the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753245 Title: package postgresql-10 10.3-1 failed to install/upgrade: installed postgresql-10 package post-removal script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1753245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
