Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slice failed error logged on Centos 8.3 (2011) system #35

Open
schmittst opened this issue Jun 27, 2021 · 1 comment
Open

Slice failed error logged on Centos 8.3 (2011) system #35

schmittst opened this issue Jun 27, 2021 · 1 comment

Comments

@schmittst
Copy link

Dear Hetrixtools team,

I regularly have an error logged by the cron job of the Hextrixtools server agent on different machines running Centos 8.3 (2011).
I the logs, I have the following entries, typically 1-3 per day at different, random time points. All other runs of the job work fine then. User 988 is the user running the agent.

pam_systemd(crond:session): Failed to create session: Start job for unit user-988.slice failed with 'canceled'

PRIORITY 3
SYSLOG_FACILITY 10
SYSLOG_IDENTIFIER crond
SYSLOG_PID 3651537
_AUDIT_LOGINUID 988
_AUDIT_SESSION 19728
_BOOT_ID XXXXXX
_CAP_EFFECTIVE ffffffffff
_CMDLINE /usr/sbin/crond -n
_COMM crond
_EXE /usr/sbin/crond
_GID 0
_HOSTNAME XXXXXX
_MACHINE_ID XXXXXX
_PID XXXXXX
_SELINUX_CONTEXT system_u:system_r:crond_t:s0-s0:c0.c1023
_SOURCE_REALTIME_TIMESTAMP 1624768501880432
_SYSTEMD_CGROUP /user.slice/user-988.slice/session-19728.scope
_SYSTEMD_INVOCATION_ID XXXXXX
_SYSTEMD_OWNER_UID 988
_SYSTEMD_SESSION 19728
_SYSTEMD_SLICE user-988.slice
_SYSTEMD_UNIT session-19728.scope
_SYSTEMD_USER_SLICE -.slice
_TRANSPORT syslog
_UID 0
__CURSOR XXXXXX
__MONOTONIC_TIMESTAMP 1171385443635
__REALTIME_TIMESTAMP 1624768501881002

Do you have any idea were this comes from and how to fix it?
Thanks in advance!

@hetrixtools
Copy link
Owner

Hello,

This seems to be an issue related to CentOS/RedHat in particular, and how the OS generates slices of processes, but not related or caused by our agent code:
https://access.redhat.com/solutions/1564823

An issue regarding this matter is already logged and solved in their system, for the RedHat clients:
https://access.redhat.com/solutions/6099891

I'd suggest contacting the OS support, perhaps they'd have more insight as to what might cause this error on your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants