👀 Views: 58 💬 Answers: 1 📅 Created: 2025-06-18

linux ubuntu syslog bash

I'm stuck on something that should probably be simple... I've recently noticed that after updating my Ubuntu 20.04 server, the `rsyslog` daemon has been consuming an unusually high amount of CPU resources, peaking at 95% during certain periods. This behavior started immediately following the system update that included several kernel and package updates. I checked the logs and found nothing particularly unusual, but the `syslog` and `kern.log` were filled with repetitive entries about a specific process. I believe this might relate to some misconfiguration or an scenario with log rotation. Here are the relevant entries from `syslog`: ``` Oct 14 12:00:01 server rsyslogd: action 'action 2' suspended, next retry after 5 seconds Oct 14 12:00:01 server rsyslogd: action 'action 7' suspended, next retry after 5 seconds ``` I attempted to restart the `rsyslog` service with `sudo systemctl restart rsyslog`, but the CPU usage remains high. I also tried disabling the logging of certain services that were flooding the logs by adding them to the `/etc/rsyslog.conf`, like so: ``` *.*;auth,authpriv.none -/var/log/syslog ``` Unfortunately, this did not resolve the scenario. Finally, I attempted to modify the log retention settings in `/etc/logrotate.d/rsyslog` to keep fewer logs, but again, that did not help. Is there any known fix or workaround for this scenario? Could it be related to a specific configuration in `rsyslog` or perhaps an external factor I am overlooking? Any insight would be greatly appreciated. This is happening in both development and production on macOS. What's the correct way to implement this? The project is a microservice built with Bash. I'd really appreciate any guidance on this.