Failed to get machine PTY: No such file or directory

Bug
,
6

What happens if you reboot the whole server? Does the bug return?

BTW I was just wondering what systemd version is present on both the main system and the container. This might be a useful information. For anyone who hit this bug please report them with the following commands:

 rpm -q systemd
 rpm --dbpath=/var/lib/machines/nsdc/var/lib/rpm -q systemd
7

The bug returns on rebooted the server and shutting down.

[root@server ~]# rpm -q systemd
systemd-219-19.el7_2.12.x86_64
[root@server ~]# rpm --dbpath=/var/lib/machines/nsdc/var/lib/rpm -q systemd
systemd-219-19.el7_2.12.x86_64
[root@server ~]#
8

  1. Please annotate also the output of

    timedatectl

  2. Also attach the svg file produced by

    systemd-analyze plot > jeff.svg

  3. Could you check your hardware clock from BIOS at boot?

Thanks a lot!

9
  1. [root@server ~]# timedatectl
    Local time: Tue 2016-09-06 09:12:19 PDT
    Universal time: Tue 2016-09-06 16:12:19 UTC
    RTC time: Tue 2016-09-06 09:12:19
    Time zone: America/Los_Angeles (PDT, -0700)
    NTP enabled: yes
    NTP synchronized: yes
    RTC in local TZ: yes
    DST active: yes
    Last DST change: DST began at
    Sun 2016-03-13 01:59:59 PST
    Sun 2016-03-13 03:00:00 PDT
    Next DST change: DST ends (the clock jumps one hour backwards) at
    Sun 2016-11-06 01:59:59 PDT
    Sun 2016-11-06 01:00:00 PST

Warning: The system is configured to read the RTC time in the local time zone.
This mode can not be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
’timedatectl set-local-rtc 0’.

  1. https://drive.google.com/file/d/0BzXWUMaIvtgcQXpDekJrckh0YXc/view?usp=sharing

  2. BIOS hardware clock at boot: 16:17 9-6-2016.

I used to dual-boot for Windows 10 and Mint, and changed the time to local not UTC. All my virtuals were using local time (I think). My real machine was using a second hard drive in this machine and I might have been using local time. I accidentally erase my main drive when I did the real machine and since then put all back. I have not changed the time to local yet. Do you think that is the problem?

Update:

I tried it again and it fails again. Error message.

1 Like
10

It failed again using the UTC and not local.

1 Like
11

Could you attach also the related systemd journals? I hope a redirect to file works:

journalctl > host.journal
journalctl -M nsdc > nsdc.journal
systemd-analyze plot > nsdc.svg
12

I put all the files together in a google link directory.

https://drive.google.com/folderview?id=0BzXWUMaIvtgcWHVTbUhNb1Q5NWM&usp=sharing

1 Like
13

I finally managed to reproduce it! It’s simpler than I have expected :smile:

  • no root ssh sessions: bug is present
  • active root ssh session: bug is not present

I guess it is related to PTY devices allocation and login sessions…

/cc @JeffBales @fasttech @GG_jr

Now we can find a fix for it!

8 Likes
14

1 Like
15

5 Likes
16
17

The bug has now its fix! Those who hit it (@fasttech, @JeffBales, @flatspin, @GG_jr, …) and the whole @quality_team: do you want to test it?

To reproduce the bug after installing nethserver-dc:

  • Close any ssh session

To install the fix:

 yum --enablerepo=nethserver-testing update nethserver-dc-1.0.2-1.13.gd587784.ns7

To properly cover the code changes, re-test the following use cases:

  • user creation/modification/deletion
  • group creation/modification/deletion
  • user password policy change
  • domain password policy change
  • admin-todo reminder on Dashboard for Administrator’s password
2 Likes
18

Come on guys, let’s test it and get back to us! Free bee offered :beers:

1 Like
19

:bee:?? for free?? what an offer! :smile:

Tests are in progress.

user creation/mofdification/deletion so far no errors

group creation/mofdification/deletion so far no errors

user password policy change no errors, but no changes noticeable.
If I change policy I still have to give 1 upper char, 1 number, 1 special char, 1 lower char and 7 in sum.
what’s the difference between strong and non strong. I thought that non strong is tha only 7 char must be set, no matter if upper lower special or what ever. Do I have to reboot ?

admin-todo remember on dash board worked I think. I set the password and than it disappeared

last: how to change domain password policy? :blush:

so far so good.

2 Likes
20

Ahahah :grinning: touchè! Thanks for answering my call friend!

21

By “domain password policy” I meant “Password policies” page!

By “user password policy” I meant the “Enable password expiration” checkbox under “User > Edit” form.

22

o.k. thanks for clarifiing.

domain password policy: as mentioned above, no change noticable…

user password: I get an error when changing exparation, when the user is a member of a group.

Sep 9 12:18:03 newns7 esmith::event[8160]: Event: password-policy-update
Sep 9 12:18:03 newns7 esmith::event[8160]: Action: /etc/e-smith/events/password-policy-update/S10nethserver-sssd-clear-cache SUCCESS [0.076623]
Sep 9 12:18:03 newns7 esmith::event[8160]: Password complexity activated!
Sep 9 12:18:03 newns7 esmith::event[8160]: Password history length changed!
Sep 9 12:18:03 newns7 esmith::event[8160]: Minimum password age changed!
Sep 9 12:18:03 newns7 esmith::event[8160]: Maximum password age changed!
Sep 9 12:18:03 newns7 esmith::event[8160]: All changes applied successfully!
Sep 9 12:18:03 newns7 esmith::event[8160]: Action: /etc/e-smith/events/password-policy-update/S30nethserver-dc-password-policy SUCCESS [0.492689]
Sep 9 12:18:03 newns7 esmith::event[8160]: Event: password-policy-update SUCCESS
Sep 9 12:18:17 newns7 esmith::event[8238]: Event: user-modify user1@jeckel.lan Testuser 1 /bin/bash
Sep 9 12:18:17 newns7 esmith::event[8238]: Action: /etc/e-smith/events/user-modify/S40nethserver-dc-user-modify SUCCESS [0.18315]
Sep 9 12:18:17 newns7 esmith::event[8238]: Action: /etc/e-smith/events/user-modify/S90nethserver-sssd-clear-cache SUCCESS [0.083343]
Sep 9 12:18:17 newns7 esmith::event[8238]: Event: user-modify SUCCESS
Sep 9 12:18:18 newns7 esmith::event[8260]: Event: group-modify netusers@jeckel.lan user2 user1 domain users s-1-5-4 s-1-5-11
Sep 9 12:18:18 newns7 esmith::event[8260]: ERROR(exception): Failed to remove members “S-1-5-4,S-1-5-11,Domain,Users” from group “netusers” - Unable to find “Domain”. Operation cancelled.
Sep 9 12:18:18 newns7 esmith::event[8260]: File “/usr/lib64/python2.7/site-packages/samba/netcmd/group.py”, line 278, in run
Sep 9 12:18:18 newns7 esmith::event[8260]: add_members_operation=False)
Sep 9 12:18:18 newns7 esmith::event[8260]: File “/usr/lib64/python2.7/site-packages/samba/samdb.py”, line 274, in add_remove_group_members
Sep 9 12:18:18 newns7 esmith::event[8260]: raise Exception(‘Unable to find “%s”. Operation cancelled.’ % member)
Sep 9 12:18:19 newns7 esmith::event[8260]: Added members to group netusers
Sep 9 12:18:19 newns7 esmith::event[8260]: [ERROR] Failed to update the members list of group netusers at /etc/e-smith/events/group-modify/S40nethserver-dc-group-modify line 80.
Sep 9 12:18:19 newns7 esmith::event[8260]: Action: /etc/e-smith/events/group-modify/S40nethserver-dc-group-modify FAILED: 1 [1.135775]
Sep 9 12:18:19 newns7 esmith::event[8260]: Action: /etc/e-smith/events/group-modify/S90nethserver-sssd-clear-cache SUCCESS [0.173449]
Sep 9 12:18:19 newns7 esmith::event[8260]: Event: group-modify FAILED
Sep 9 12:18:19 newns7 esmith::event[8311]: Event: password-policy-update user1@jeckel.lan yes
Sep 9 12:18:19 newns7 esmith::event[8311]: Action: /etc/e-smith/events/password-policy-update/S10nethserver-sssd-clear-cache SUCCESS [0.299921]
Sep 9 12:18:20 newns7 esmith::event[8311]: Expiry for user ‘user1’ set to 180 days.
Sep 9 12:18:20 newns7 esmith::event[8311]: Action: /etc/e-smith/events/password-policy-update/S30nethserver-dc-password-policy SUCCESS [0.486807]
Sep 9 12:18:20 newns7 esmith::event[8311]: Event: password-policy-update SUCCESS
Event: password-policy-update SUCCESS

something wrong with cn=domain or something like this?

If the user is no member of a group, no error apears.

If a empty group is created, message: “Task completed with errors” apears. But I think this is ment to this way (or better: this would be logical :vulcan:)

3 Likes
23

Seems like a space is not preserved :thinking:

BTW, @flatspin: do you have a GitHub account? Could you set the issue #5103 assigned to you?

24

You must have one! As brand new quality team member! :imp:

25

ehhhh, nope. how to?