RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
service lm_sensor cannot be started on the latest rhel7.
are there wrong parameters?

Version-Release number of selected component (if applicable):

lm_sensors-3.3.2-2.el7.ppc64
kmod-7-2.el7.ppc64
systemd-44-12.el7.ppc64


How reproducible:
deterministic

Steps to Reproduce:
1. service lm_sensors start

  
Actual results:
# systemctl start lm_sensors.service
Job failed. See system journal and 'systemctl status' for details.

# systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
	  Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; disabled)
	  Active: failed (Result: exit-code) since Thu, 21 Jun 2012 17:47:35 +0900; 4s ago
	 Process: 3807 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
	 Process: 3805 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/lm_sensors.service

Jun 21 17:47:35 MY.X.Y.Z.redhat.com modprobe[3805]: Error: missing parameters. See -h.


Expected results:
service is started

Additional info:

Ahoj Petře.

It seems you haven't run the sensors-detect script in order to generate the variables. This also happens when no sensors are detected by the script.

It's questionable if this is a correct behaviour or not. It has no sense to start the service without configuring it first. And it has no sense to run the service when there are no sensors detected.

Please, check that and let me know.

Thanks,
Jaromir.

As Petr stated, he hadn't configured the sensors when he tried to start the service. But we agreed that the error message is pretty confusing. The service file needs to be redesigned in order to tell users the real reason why it fails and what to do in order to prevent that from happening.

Ahoj Petře.

Please, test, whether the latest build behaves like expected.
Thanks in advance.

Regards,
Jaromir.

Thanks ... closing.