Description of problem: For some reason MonitoringScout -> NPBootstrap service is not starting after upgrade from Satellite 5.3.0 to 5.7.0: Status: '403 Forbidden'. Beside all upgrade steps, I have done `setenforce 0` before `/usr/share/spacewalk/setup/upgrade/rhn-enable-monitoring.pl --enable-scout` step. Monitoring was working on 5.3.0, probes were recording data. Version-Release number of selected component (if applicable): Satellite-5.7.0-RHEL6-re20141128.0 rhn-upgrade-5.7.0.8-1.el6sat.noarch How reproducible: 2 of 2 attempts Steps to Reproduce: 1. Setup Satellite 5.3.0 on RHEL5 with embedded Oracle and Monitoring 2. Upgrade to 5.7.0 on RHEL6 with external PostgreSQL (but seen this on scenario with embedded DB as well) 3. # setenforce 0 # /usr/share/spacewalk/setup/upgrade/rhn-enable-monitoring.pl --enable-scout Actual results: MonitoringScout -> NPBootstrap service is not starting Expected results: All Monitoring and MonitoringScout services should be starting and Monitoring should be functional.
Upstream work spacewalk.git: 4c8a12a7789b0a7bef51e68dd0bb2ef18285df6f 1170064 - equality is too strict
Seems like this is linked to IPv6. Disabling IPv6 in OS did not help (changed error message to "(socket: Address family not supported by protocol)"). Disabling AAAA record made Perl library use IPv4 and it worked. Example workaround: add line for `$(hosntame)` to `/etc/hosts` (IPv4) and in `/etc/nsswith.conf` change hosts to not use dns. # hosts: files dns hosts: files (check with `host $(hostname)` that you gen only IPv4 record. After that try restart, NPBootstrap should start.
Reported bug 1264580 when i have seen this again recently.
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. We believe this bug has been fixed in the latest Satellite 5 version (5.8) (monitoring has been completely removed form the product), so closing the bug as CURRENTRELEASE. Please feel free to re-open in case you discover any issues.