[Spacewalk-list] scheduled rhn_check on Ubuntu failed to configure with dpkg

[Robert Paschedag]

Am 24. Juli 2017 22:01:49 MESZ schrieb Paul-Andre Panon <paul-andre.panon at avigilon.com>:
>Hi,
>
>We did our first major patching run with Spacewalk on a mix of CentOS
>and Ubuntu servers. Normally we've been manually running rhn_check -v
>on the clients, but this time we patched enough servers that a couple
>of Ubuntu servers had rhn_check -v get run by rhnsd before we could get
>around to running them manually. On those servers, the dpkg configure
>stage didn't run and all packages were only in the Unpacked state.
>
>Syslog shows that something wasn't working correctly when it tried to
>run rhn_check -v. Perhaps a slightly different invocation for i/o
>redirection is necessary for background execution by rhnsd in Ubuntu?
>
>Jul 23 10:07:37 dc1-atl-bitbucket rhnsd[14484]: running program
>/usr/sbin/rhn_check with PID 14484
>Jul 23 10:07:53 dc1-atl-bitbucket upstart-socket-bridge[651]:
>Disconnected from Upstart
>Jul 23 10:07:53 dc1-atl-bitbucket upstart-udev-bridge[338]:
>Disconnected from Upstart
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612608] init:
>upstart-udev-bridge main process (338) terminated with status 1
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612618] init:
>upstart-udev-bridge main process ended, respawning
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612707] init:
>upstart-file-bridge main process (442) terminated with status 1
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612712] init:
>upstart-file-bridge main process ended, respawning
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612777] init:
>upstart-socket-bridge main process (651) terminated with status 1
>Jul 23 10:07:53 dc1-atl-bitbucket kernel: [6885730.612782] init:
>upstart-socket-bridge main process ended, respawning
>
>This is on Ubuntu 14.04, but I'm running custom package builds where I
>tried to update to newer Spacewalk rhnsd client source while applying
>Ubuntu 16.04 package diffs. I was hoping to eventually get it working
>with osad the way it works for RedHat/CentOS. 
>
>We had one 16.04 machine running stock 16.04 packages that ran
>rhn_check in the background with no problem, so I'm probably missing a
>necessary diff. Any suggestion as to which files/procs for rhnsd spawn
>rhn_check so that I can double check them for the source of the problem
>in my custom 14.04 packages?
>
>Thanks,
>
>Paul-Andre Panon
>Senior systems administrator
> 
>
>Office: 604.629.5182 ext 2341 Mobile: 604.679.1617
>Support: 888.281.5182 | avigilon.com
>Follow Twitter | Follow LinkedIn
>
>
>_______________________________________________
>Spacewalk-list mailing list
>Spacewalk-list at redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Hi,

I think the problem is that one or more packages are running some  "debconf" with "dialog" frontend that is not catched in background.

I also had this one or two times that I recognized that on some server"rhn_check" was hanging but did not find a solution for that. Fix was to kill the hanging task and run "rhn_check" interactive *I think*.

Could have also been "apt-get install"...

Robert