search

ossobv / gocollect

Data collector using go, periodically posts json to a REST api
GNU General Public License v3.0
6 stars 1 forks source link

dpkg failure during regular upgrade from 0.5.0-1 to 0.5.0-2 on trusty #25

Closed wdoekes closed 7 years ago

wdoekes commented 7 years ago 
Unpacking gocollect-osso (0.5.0-2~ubu14.04) over (0.5.0-1~ubu14.04) ...
Selecting previously unselected package linux-image-4.4.0-62-generic.
Preparing to unpack .../linux-image-4.4.0-62-generic_4.4.0-62.83~14.04.1_amd64.deb ...
Done.
...
Preparing to unpack .../linux-headers-generic-lts-xenial_4.4.0.62.48_amd64.deb ...
Unpacking linux-headers-generic-lts-xenial (4.4.0.62.48) over (4.4.0.59.46) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
gocollect: unrecognized service
E: Sub-process /usr/bin/dpkg exited unexpectedly

Unrecognised service failure in post-install trigger? Causing install to fail?

# service gocollect status
gocollect: unrecognized service
# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
iU  gocollect                           0.5.0-2~ubu14.04                  amd64        Collect rarely changing system info for server mapping.
iU  gocollect-osso                      0.5.0-2~ubu14.04                  all          OSSO-specific configuration files for GoCollect

dpkg --reconfigure -a fixed things...

wdoekes commented 7 years ago

If we fix #23 by not doing a postinst restart, this is probably auto-fixed as well...