Am Dienstag, 20. August 2019 schrieb Stefan Krusche:

Am Dienstag, 20. August 2019 schrieb Stefan Krusche:

...

/var/log/tdm.log gets filled up with hundreds of thousands of this particular message:

unable to receive message unable to receive message unable to receive message unable to receive message […]

After a couple of weeks not being rotated it has grown up to more than 100MB.

Where does this message come from, TDE or any other program?

What could be the solution to remedy that behaviour?

Thank you for any hints.

Adding system information:

TDE PSB R14.0.7

$ apt-cache policy tdm-trinity tdm-trinity: Installed: 4:14.0.7~pre28-0debian9.0.0+6 Candidate: 4:14.0.7~pre28-0debian9.0.0+6 Version table: *** 4:14.0.7~pre28-0debian9.0.0+6 500 500 http://mirror.xcer.cz/trinity-sb stretch/main-r14 amd64 Packages 100 /var/lib/dpkg/status

…running on Devuan ascii

There are also a lot messages of the following form in /var/log/tdm.log (but not in Xorg.0.log): […] no db file to read /run/udev/data/+hwmon:hwmon0: No such file or directory no db file to read /run/udev/data/+platform:floppy.0: No such file or directory no db file to read /run/udev/data/+platform:i8042: No such file or directory no db file to read /run/udev/data/+serio:serio0: No such file or directory no db file to read /run/udev/data/+serio:serio1: No such file or directory no db file to read /run/udev/data/+platform:microcode: No such file or directory […]

which led me to have a look at udevd (which on this system is eudev 3.2.2-13).

For some reason, I now don't remember no more, I had "udev_log=debug" in /etc/udev/udev.conf instead the default "=info".

So this is, how I stopped both kinds of messages:

1.) I changed udev_log back to "info".

2.) I updated udev's database with:

$ udevadm hwdb --update

3.) I updated initrd to make the changes take effect at boot time:

$ update-initramfs -u

Thanks for your time, Stefan

Anno domini 2019 Tue, 20 Aug 13:12:33 +0200 Stefan Krusche scripsit:

Am Dienstag, 20. August 2019 schrieb Dr. Nikolaus Klepp:

...

Which system? Looks like dbus problem to me.

Hi Nik,

thanks. I have been guessing that, too, but I don't know how to debug further.

You might check if dbus is running, which user ist belongs, ... Sorry, these are problems I never saw on non-systemd systems (I have moved all systems away from systemd a long time ago)

System information has been send in a different mail (just before you sent yours).

Yep, received it just after I sent mine :) Nik

Regards, Stefan

---

To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting