# Failed to create session: Connection timed out **URL:** \ **Category:** General Discussion\ **Created:** [December 2, 2020, 1:09pm UTC](https://forums.suse.com/t/failed-to-create-session-connection-timed-out/35405 "2020-12-02T13:09:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![locky](https://avatars.discourse-cdn.com/v4/letter/l/2bfe46/32.png) [@locky](https://forums.suse.com/u/locky)\ **Post date:** [December 2, 2020, 1:09pm UTC](https://forums.suse.com/t/failed-to-create-session-connection-timed-out/35405/1 "2020-12-02T13:09:06Z")
Hello, i have a lot of SLES 12SP5 and SP4 Servers, they get all few days the same error message. Message: Dec 02 00:01:01host-A cron[25325]: pam\_unix(crond:session): session opened for user root by (uid=0) Dec 02 00:01:26 host-A cron[25325]: pam\_systemd(crond:session): Failed to create session: Connection timed out Dec 02 00:05:50 host-A CRON[25325]: pam\_unix(crond:session): session closed for user root Dec 02 12:25:01 host-B cron[6867]: pam\_unix(crond:session): session opened for user root by (uid=0) Dec 02 12:25:26 host-B cron[6867]: pam\_systemd(crond:session): Failed to create session: Connection timed out Dec 02 12:25:26 host-B CRON[6871]: (root) CMD (/bin/sh /root/countstreams.sh \>/dev/null 2\>&1) Dec 02 12:25:26 host-B CRON[6867]: pam\_unix(crond:session): session closed for user root … Dec 02 12:26:27 host-B systemd[1]: Created slice User Slice of root. Dec 02 12:26:27 host-B systemd[1]: Starting User Manager for UID 0… Dec 02 12:26:27 host-B systemd[1]: session-50113.scope: Failed to add PIDs to scope’s control group: No such process Dec 02 12:26:27 host-B systemd[1]: Failed to start Session 50113 of user root. Dec 02 12:26:27 host-B systemd[1]: session-50113.scope: Unit entered failed state. All other Server with SP3 has no Problems. i have no idea what could it be. Thank’s in advance! ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [December 2, 2020, 1:36pm UTC](https://forums.suse.com/t/failed-to-create-session-connection-timed-out/35405/2 "2020-12-02T13:36:02Z")
@locky Hi and welcome to the Forum 🙂 By the look of that output, some failing cron job on host-B, suggest inspect the crontab and the scripts running. Maybe environment variables not set? Or perhaps expect is running and not getting input so it times out. ---
**Author:** ![locky](https://avatars.discourse-cdn.com/v4/letter/l/2bfe46/32.png) [@locky](https://forums.suse.com/u/locky)\ **Post date:** [December 3, 2020, 7:31am UTC](https://forums.suse.com/t/failed-to-create-session-connection-timed-out/35405/3 "2020-12-03T07:31:23Z")
Thank for you response. and which environment can it be? It may be, but I checked that no Cronjobs are installed on this host for any user. Maybe a System Cronjob, bat i cant find no one Job for this Time range, about 12h or larger. i have been observing this phenomenon since upgrade to SP4. ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [December 3, 2020, 3:08pm UTC](https://forums.suse.com/t/failed-to-create-session-connection-timed-out/35405/4 "2020-12-03T15:08:08Z")
@locky The cron job knows nothing of the shell environment variables, eg $PATH so if your running a script for say the `echo` command it won’t work if PATH is not set first, or you use the full path eg `/usr/bin/echo`. So no user cron jobs, then as root user run `crontab -l` or the files/directories `ls /etc/cron*`. It could also be a systemd timer, or do you have a remote user/probe hitting the box?