Bug#883692: systemd: pam_systemd(su:session): Failed to create session

[Francesco Potortì]

As asked, following up to 883347 at bugs.debian.org

>> After an upgrade two days ago, I get errors in system logs shortly after
>> midnight.  I was not able to understand what program exactly has
>> problems, so I am not able to repsoduce this from the command line.
>
>From which version did you upgrade?

I upgraded to 235-3 from 235-2 on 4 December.

>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883347#10

I can try commenting LockPersonality and IPAddressDeny.  Should I
restart any service afterwards?

>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883347#15

Sorry, I'm completely ignorant about LSM.  How do I check if any
security module is enabled and how can I disable them?  I observe this:

# /etc/init.d/apparmor status
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2017-11-22 11:43:44 CET; 2 weeks 0 days ago
     Docs: man:apparmor(7)
           http://wiki.apparmor.net/
 Main PID: 2426 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/apparmor.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.