rsyslogd: run failed with error -3000

Latest response

-- The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.
Jun 08 00:33:03 mainserver.com sshd[12607]: Failed password for root from 112.85.42.187 port 18141 ssh2
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Jun 08 00:33:03 mainserver.com systemd[1]: Stopped System Logging Service.
-- Subject: Unit rsyslog.service has finished shutting down
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit rsyslog.service has finished shutting down.
Jun 08 00:33:03 mainserver.com systemd[1]: Starting System Logging Service...
-- Subject: Unit rsyslog.service has begun start-up
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit rsyslog.service has begun starting up.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service: main process exited, code=exited, status=1/FAILURE
Jun 08 00:33:03 mainserver.com systemd[1]: Failed to start System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit rsyslog.service has failed.

-- The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.
Jun 08 00:33:03 mainserver.com sshd[12607]: Received disconnect from 112.85.42.187 port 18141:11: [preauth]
Jun 08 00:33:03 mainserver.com sshd[12607]: Disconnected from 112.85.42.187 port 18141 [preauth]
Jun 08 00:33:03 mainserver.com sshd[12607]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Jun 08 00:33:03 mainserver.com systemd[1]: Stopped System Logging Service.
-- Subject: Unit rsyslog.service has finished shutting down
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit rsyslog.service has finished shutting down.
Jun 08 00:33:03 mainserver.com systemd[1]: start request repeated too quickly for rsyslog.service
Jun 08 00:33:03 mainserver.com systemd[1]: Failed to start System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit rsyslog.service has failed.

-- The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.

Responses

Hi Shashank,

Check if the solution provided in this KB helps you : https://access.redhat.com/solutions/3693211

All the best!

How did this go Shashank?

See Sadashiva Murthy M's solution above - is this a good fit for your issue?

Regards,
RJ

Hi RJ,

I have tried that solution but that issue didn't resolved.

Hi Sadashiva,

Thanks for your support, I have tried that solution but it didn't work.

Shashank Pandey,

Are you using an external server to send rsyslog logs to? Generally, if this is done, it does not require password authentication. I happened to notice password failures.

Consider running journalctl -xeu rsyslog and scroll up/down for anything that seems to be an issue. Additionally, you've probably ran systemctl status -l rsyslog, correct? Just as a test temporarily run setenforce 0;getenforce then attempt to start rsyslog. If it works, then examine SELinux contexts.

Consider opening a case with Red Hat support.

Regards,
RJ

Shashank Pandey,

Additionally, run

df -klh 

and determine if any file systems are full. If you find any full file systems, resolve whatever is filling it and retry.

Regards,
RJ