On Tue, 15 Nov 2011 18:29:12 -0500
Alex wrote:

> How do I troubleshoot this? How do I determine why a service managed
> by systemd didn't start? Why is there nothing written to syslog
> regarding this?

did you run sensors-detect as root to setup the modules
lm_sensors needs to load on your system?

You can also fiddle /etc/systemd/system.conf to set the
logging level.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Hi,

>> How do I troubleshoot this? How do I determine why a service managed
>> by systemd didn't start? Why is there nothing written to syslog
>> regarding this?
>
> did you run sensors-detect as root to setup the modules
> lm_sensors needs to load on your system?
>
> You can also fiddle /etc/systemd/system.conf to set the
> logging level.

Yes, I've done that, and have also run sensors-detect successfully. A
few "coretemp" and modules loading messages are printed in syslog, but
that's it:

Nov 15 21:30:43 mail01 kernel: [190985.265634] coretemp coretemp.1:
Using relative temperature scale!
Nov 15 21:30:43 mail01 kernel: [190985.275732] coretemp coretemp.0:
Using relative temperature scale!
Nov 15 21:30:43 mail01 kernel: [190985.285607] coretemp coretemp.1:
Using relative temperature scale!
Nov 15 21:30:43 mail01 kernel: [190985.295303] coretemp coretemp.0:
Using relative temperature scale!
Nov 15 21:30:43 mail01 kernel: [190985.304782] coretemp coretemp.1:
Using relative temperature scale!
Nov 15 21:30:43 mail01 kernel: [190985.316279] w83627hf: w83627hf:
Found W83627HF chip at 0x290
Nov 15 21:30:43 mail01 kernel: [190985.396073] w83793 5-002f:
Registered watchdog chardev major 10, minor: 212

It used to be there was a script that you could trace for debugging,
but I don't understand how the new system works.

I've set the following in system.conf:

[Manager]
LogLevel=info
LogTarget=syslog-or-kmsg

Is there something more I can do to troubleshoot this?

Thanks,
Alex
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

On Tue, Nov 15, 2011 at 4:29 PM, Alex <mysqlstudent@gmail.com> wrote:
> Hi,
>
> I have a fedora15 system and I'm having trouble trying to figure out
> why a few services don't start through systemd. Specifically,
> lm_sensors:
>
> # service lm_sensors restart
> Redirecting to /bin/systemctl *restart lm_sensors.service
>
> # service lm_sensors status
> Redirecting to /bin/systemctl *status lm_sensors.service
> lm_sensors.service - Initialize hardware monitoring sensors
> * * * * *Loaded: loaded (/lib/systemd/system/lm_sensors.service)
> * * * * *Active: active (exited) since Tue, 15 Nov 2011 18:25:52 -0500; 7s ago
> * * * * Process: 1151 ExecStop=/sbin/modprobe -qabr $BUS_MODULES
> $HWMON_MODULES (code=exited, status=0/SUCCESS)
> * * * * Process: 1157 ExecStart=/usr/bin/sensors -s (code=exited,
> status=0/SUCCESS)
> * * * * Process: 1155 ExecStart=/sbin/modprobe -qab $BUS_MODULES
> $HWMON_MODULES (code=exited, status=0/SUCCESS)
> * * * * *CGroup: name=systemd:/system/lm_sensors.service

AFAICT sensors isn't supposed to stick around. This is reflected
properly in it's systemd unit file by it being configured
"Type=oneshot".

"man sensors" says the following about the "-s" switch:
"Evaluate all `set' statements in the configuration file and exit. You
must be `root' to do this. If this parameter is not specified, no
`set' statement is evaluated."

modprobe is completing successfuly, as is "sensors -s", so everything
should be copacetic.

-T.C.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Hi,

>> # service lm_sensors restart
>> Redirecting to /bin/systemctl *restart lm_sensors.service
>>
>> # service lm_sensors status
>> Redirecting to /bin/systemctl *status lm_sensors.service
>> lm_sensors.service - Initialize hardware monitoring sensors
>> * * * * *Loaded: loaded (/lib/systemd/system/lm_sensors.service)
>> * * * * *Active: active (exited) since Tue, 15 Nov 2011 18:25:52 -0500; 7s ago
>> * * * * Process: 1151 ExecStop=/sbin/modprobe -qabr $BUS_MODULES
>> $HWMON_MODULES (code=exited, status=0/SUCCESS)
>> * * * * Process: 1157 ExecStart=/usr/bin/sensors -s (code=exited,
>> status=0/SUCCESS)
>> * * * * Process: 1155 ExecStart=/sbin/modprobe -qab $BUS_MODULES
>> $HWMON_MODULES (code=exited, status=0/SUCCESS)
>> * * * * *CGroup: name=systemd:/system/lm_sensors.service
>
> AFAICT sensors isn't supposed to stick around. *This is reflected
> properly in it's systemd unit file by it being configured
> "Type=oneshot".
>
> "man sensors" says the following about the "-s" switch:
> "Evaluate all `set' statements in the configuration file and exit. You
> must be `root' to do this. If this parameter is not specified, no
> `set' *statement is evaluated."
>
> modprobe is completing successfuly, as is "sensors -s", so everything
> should be copacetic.

Yes, thanks for spending the time to explain. It's working correctly.

There appears to be several voltages that are out of normal range, but
I think it just needs to tuning.

Thanks again,
Alex
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines