[SOLVED] daemon quits before logs error .PID File

CleanTestr · Last edited by CleanTestr on Sat Aug 10, 2013 8:09 pm; edited 4 times in total

I've changed the topic title to better reflect what the problem was.

I've got a recent syslog-ng set up with the logging .conf from the Security Howto,
Section 3.d., and I'm seeing kernel Errors (that scroll by at boot-up) going into /var/log/syslog
as expected.

But on the boot-up scrolling screen, I'm seeing some sort of 'long line', possibly
a Warning, from possibly a driver, something about LNXSYSTM/ ... and then some
140 characters, with a BAT0 near the end, which (grep -R BAT0 /var/log/*)
isn't in the logs.

I'd like to see those messages in the logs, so that I can paste them here in the
Forums.
_________________
Stan: A signal? Why didn't you wake me?
790: It was a distress signal. They only lead to trouble, so I always ignore them. --Lexx

quilosaq · Veteran Joined: 22 Dec 2009 Posts: 1521

CleanTestr · Posted: Sat Aug 10, 2013 8:03 pm Post subject:

Ok, the message in question is:

/var/log/syslog:
Aug 10 12:51:26 cleantestee cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:07/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_now (No such file or directory)

These are now showing up in the logs.

It looks to me to have been a mis-configured cpufreqd (running it manually
with -D -V 7 showed that it was exiting around when accessing its /var/run/.pid file,
possibly due to a problem with acpid)

All those issues were fixed, and now it's not exiting, and hence (maybe) getting a chance
to write error messages to the logs (?)

I'm gonna mark this SOLVED.
_________________
Stan: A signal? Why didn't you wake me?
790: It was a distress signal. They only lead to trouble, so I always ignore them. --Lexx