On 04/29/2015 06:53 PM, Matthias Bodenbinder wrote: > Am 29.04.2015 um 10:32 schrieb Christian Seiler: >> Just use journalctl (without -b) to see all messages (they are >> still in RAM in the journal - as per the log you posted, journald >> will use up to 80 MiB [2] which is more than enough to keep all >> 3000 or so messages). Just look through them (there are going to >> be a lot of debug messages from udev) and look at the timestamps. >> There you'll be able to see where the delay happens - and maybe >> you'll have a chance of figuring out, what the problem is. If >> it's nothing obvious, just post the last 20 or so udev messages >> before the large gap in the timestamps and every udev message >> afterwards. If there is no gap and udev is constantly doing >> something, take a look at what it's actually doing. > > No way. Just using journalctl makes no difference: > > Apr 29 18:45:08 xxx systemd-journal[170]: Forwarding to syslog missed > 3819 messages. > Apr 29 18:45:14 xxx systemd-journal[170]: Suppressed 2818 messages from > /system.slice/systemd-udevd.service > > And this is exactly the time period where I would expect the issue to > pop up.
Ah, I only noticed the first message about syslog forwarding. The second message tells us that rate limiting has kicked in, because udev just generates a TON of messages in a short time. Just for the purpose of debugging, could you increase RateLimitBurst to 10000 or so (i.e. 10x the default value) in /etc/systemd/journald.conf and reboot? (Set it back again after you're done deubgging, else your logs might get flooded.) Christian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55411381.7060...@iwakd.de
