Red Hat Bugzilla – Bug 1272093
upstart plugin does not collect any useful data
Last modified: 2015-10-16 04:06:03 EDT
Description of problem:
On RHEL 7, sosreport's upstart plugin has been largely replaced by the systemd plugin. From the log, it does not seem to collect any relevant data: none of the referenced files exist and the commands, if executed at all, produce a useless output (such as "init: unrecognized option '--version'" or "ls: cannot access /etc/init/: No such file or directory").
Is there any reason to keep it in sos, even if disabled be default?
Version-Release number of selected component (if applicable):
We support more than a dozen different distributions from the same upstream codebase: some use classical SysV init, some use Upstart, others systemd.
This not a bug any more than e.g. the existence of a Red Hat specific plugin would be in a CentOS, Debian or Ubuntu environment.
Also, I don't see why this is running on your system at all - the plugin will only trigger if a package named 'upstart' exists:
20 class Upstart(Plugin, RedHatPlugin, DebianPlugin, UbuntuPlugin):
21 """Upstart init system
24 plugin_name = 'upstart'
25 profiles = ('system', 'services', 'boot')
26 packages = ('upstart',)
Is that the case on your system? Or is it being force-enabled via the command line?
(In reply to Bryn M. Reeves from comment #3)
> Is that the case on your system? Or is it being force-enabled via the
> command line?
Force-enabled indeed. Sorry about the fuss.