I'm a bit new to the Linux environment but manage to get most of what I need through Googling and reading loads of information.
But.. I can't figure this one out.
I'm tailing daemon.log (which is growing rapidly by the way - currently at 4GB and have been growing since June 3 -2021) and I just deleted the old daemon.log.1 which was about 17GB. Also tailing syslog which is about 4GB as well.
Both log files seems to be getting information intended for Homeseer logging.
Below is just a few lines. It fills quickly.. Adding a few lines per second.
Don't focus on the content of what what's happening in the Homeseer environment per se.. The intention was to show that it looks to me as if mono is logging information to both daemon.log and syslog. Both files get the same information logged.
EXAMPLE OF LOG:
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6008:[Z-Wave]->ApplicationCommandHandler from Network: E9DC3BB6 Node: 52 HANDLING: COMMAND_CLASS_MULTI_CHANNEL_V2 Frame(7)=13
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6079:[Z-Wave]->Frame: 60-0D-01-00-32-02-21-74-00-0C-49-30-00-00-00-00-00-00-C3-00-78
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6291:[Z-Wave]->Payload1: 32-02-21-74-00-0C-49-30-00-00-00-00-00-00-C3-00-78
Is this how it should be? Can I do something about the excessive logging?
Everything is Homeseer information that is logged.
Tried to add StandardOutput=null and StandardError=null in the systemd override file for homeseer.service - but that didn't do anything to help me. Also tried to stop logging in Homeseer, but that only stopped Homeseer from being able to see the log. The daemon.log and syslog still filled up with the same information even if Homeseer couldn't see it after disabling the log.
Why is this?
I'd be very happy if someone could give me a hint so that I can get the system a bit more healthy. It's lagging right now.
Looking at the processor usage, mono is constantly at 10% basically. Quite a lot isn't it?
Thanks in advance!
/Peter
But.. I can't figure this one out.
I'm tailing daemon.log (which is growing rapidly by the way - currently at 4GB and have been growing since June 3 -2021) and I just deleted the old daemon.log.1 which was about 17GB. Also tailing syslog which is about 4GB as well.
Both log files seems to be getting information intended for Homeseer logging.
Below is just a few lines. It fills quickly.. Adding a few lines per second.
Don't focus on the content of what what's happening in the Homeseer environment per se.. The intention was to show that it looks to me as if mono is logging information to both daemon.log and syslog. Both files get the same information logged.
EXAMPLE OF LOG:
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6008:[Z-Wave]->ApplicationCommandHandler from Network: E9DC3BB6 Node: 52 HANDLING: COMMAND_CLASS_MULTI_CHANNEL_V2 Frame(7)=13
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6079:[Z-Wave]->Frame: 60-0D-01-00-32-02-21-74-00-0C-49-30-00-00-00-00-00-00-C3-00-78
Jun 18 02:25:01 raspberrypi mono[477]: 02:25:01:6291:[Z-Wave]->Payload1: 32-02-21-74-00-0C-49-30-00-00-00-00-00-00-C3-00-78
Is this how it should be? Can I do something about the excessive logging?
Everything is Homeseer information that is logged.
Tried to add StandardOutput=null and StandardError=null in the systemd override file for homeseer.service - but that didn't do anything to help me. Also tried to stop logging in Homeseer, but that only stopped Homeseer from being able to see the log. The daemon.log and syslog still filled up with the same information even if Homeseer couldn't see it after disabling the log.
Why is this?
I'd be very happy if someone could give me a hint so that I can get the system a bit more healthy. It's lagging right now.
Looking at the processor usage, mono is constantly at 10% basically. Quite a lot isn't it?
Thanks in advance!
/Peter
Comment