Event log fetching syslog messages

Setup, Configuration and Use Beginners
,
1
  • Platform information:
    • Hardware: RasPI 2
    • OS: Debian Linux 8.0
    • openHAB version: 2.1
  • Issue of the topic:
    Since some time, I don’t know when exactly, I receive syslog messages in the openhab2/events.log file.
    I have no idea, when and how I introduced this.
    Besides that this is making the events.log sometimes more difficult to read, it just flushes the log and makes it too big.
    Anyone any idea?

Example:

Nov 20 21:15:02 raspberrypi CRON[24117]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Nov 20 21:15:02 raspberrypi CRON[24121]: (www-data) CMD (php -f /var/www/owncloud/cron.php > /dev/null 2>&1)
Nov 20 21:15:04 raspberrypi CRON[24117]: pam_unix(cron:session): session closed for user www-data
2017-11-20 21:15:06.847 [ItemStateChangedEvent ] - currentDate changed from 2017-11-20T21:14:06.817+0100 to 2017-11-20T21:15:06.817+0100
2017-11-20 21:15:06.858 [ItemStateChangedEvent ] - currentTime changed from 2017-11-20T21:14:06.817+0100 to 2017-11-20T21:15:06.817+0100
2017-11-20 21:15:07.973 [ItemStateChangedEvent ] - Leistung changed from 49.920 to 0.000
2017-11-20 21:16:06.844 [ItemStateChangedEvent ] - currentDate changed from 2017-11-20T21:15:06.817+0100 to 2017-11-20T21:16:06.817+0100
2017-11-20 21:16:06.861 [ItemStateChangedEvent ] - currentTime changed from 2017-11-20T21:15:06.817+0100 to 2017-11-20T21:16:06.817+0100
Nov 20 21:17:01 raspberrypi CRON[24172]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 20 21:17:01 raspberrypi CRON[24176]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 20 21:17:01 raspberrypi CRON[24172]: pam_unix(cron:session): session closed for user root

2

If you are on a raspberry pi or some other such board computer and running off of an SD card I’m going to guess that your SD card is failing.

If not it is a mystery. It shouldn’t be possible for two systems (i.e. openHAB and syslog) to have a write lock on the same file at the same time.

3

Thanks for the hint.
Anyway, I checked the file system and found everything ok so far.

Probably, I will monitor this behavior, and see what is going on …

4

Back again with this issue.
The service systemd-journald is messing up my openHAB logs.
Basically things like this getting posted into the logs:

2018-06-12 14:50:00.154 [INFO ] [me.model.script.leistungsdaten.rules] - Differenz bei Ausschalten: 4.0
Jun 12 14:54:51 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Jun 12 14:54:53 raspberrypi sudo:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/sbin/service systemd-journald status
Jun 12 14:54:53 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Jun 12 14:54:54 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Jun 12 14:55:45 raspberrypi sudo:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/sbin/service systemd-journald stop
Jun 12 14:55:45 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by pi(uid=0)

While this is no OpenHAB problem by nature, I’m wondering if anyone else has seen this issue.
Once turning off systemd-journald everything back pretty. But that shouldn’t be the solution.
My OS data:

PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian

Any hints welcome!