Description of problem: I need to increase my process limit and can't Version-Release number of selected component (if applicable): systemd.x86_64 - 231-14.fc25 How reproducible: Always Steps to Reproduce (and steps, etc.) I am trying to allow the process limit for my login session to be higher than the default (near as I can tell 1024). As I understand it, this is now under the control of systemd, but to be sure I added: * soft nproc 4096 * hard nproc 4096 to /etc/security/limits.conf. I then put DefaultLimitNPROC=4096 in /etc/systemd/user.conf. None of this seemed to help me get the limit I wanted witnessed by: $ ulimit -u 1024 I then created /etc/systemd/system/user@.service.d/local.conf: $ cat /etc/systemd/system/user@.service.d/local.conf[Service] LimitNPROC=8192 LimitNOFILE=16000 (the NOFILE just to make sure I could see something additional). Again, no luck. Interestingly, if I do: $ systemd-cgls Control group /: -.slice ├─user.slice │ ├─user-1000.slice │ │ ├─session-5.scope ... │ └─user │ │ ├─gnome-terminal-server.service │ │ │ ├─ 3400 /usr/libexec/gnome-terminal-server │ │ │ ├─ 3451 bash followed by: systemctl show user | egrep 'Path|NOFILE|NPROC' LimitNOFILE=16000 LimitNOFILESoft=16000 LimitNPROC=8192 LimitNPROCSoft=8192 FragmentPath=/usr/lib/systemd/system/user@.service DropInPaths=/etc/systemd/system/user@.service.d/local.conf However, when I do $ cat /proc/3451/limits | grep 'proc|open' Max processes 1024 1024 processes Max open files 16000 16000 files Which indicates to me that somehow the whole nproc limit is ignored. Note that I can in the shell in question do: $ ulimit -S -n 10000 $ ulimit -a | egrep 'proc|open' open files (-n) 10000 max user processes (-u) 1024 But: $ ulimit -S -u 2048 bash: ulimit: max user processes: cannot modify limit: Invalid argument $ ulimit -a | egrep 'proc|open' open files (-n) 10000 max user processes (-u) 1024 Running: $ cat /etc/system-release Fedora release 25 (Twenty Five) $ sudo dnf list systemd Installed Packages systemd.x86_64 231-14.fc25 @updates I have tried to apply the fix suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1341829#c36 but that did not seem to help. This seems like a bug to me, but perhaps I am missing something elementary? Thanks
Upgraded to F26. Same problem.
Still a problem with systemd-233-6.fc26. Tried to turn off selinux with no luck. Did a strace on systemd and it appears the NPROC value does not get propagated.
Can you try a fresh Fedora system in a VM and see what you see there? on a system where I haven't modified anything, I see: $ cat /etc/system-release Fedora release 26 (Twenty Six) $ ulimit -u 77888 So I'm not sure where the small limit you are seeing is coming from - perhaps there's something you have modified in the system configuration or some leftover from an upgrade.
Well, I started a liveCD on a different box and get: [liveuser@localhost-live ~]$ cat /etc/system-release Fedora release 26 (Twenty Six) [liveuser@localhost-live ~]$ ulimit -u 63764 [liveuser@localhost-live ~]$ I'm pretty sure I tried this on the box in question with a LiveCD with F25 and it had the same problem, but I'm not near that particular system, so I won't be able to boot that one with a LiveCD until tomorrow. However, I have another F26 box sitting here with the same problem, so let me boot that one up with the LiveCD and see what it does. For the record, both have been upgraded and doing a clean install would be painful at best, so I'd like to track down what is actually causing this. I'll be back...
Booting up the system that also has the problem with a LiveCD results in: [liveuser@localhost-live ~]$ cat /etc/system-release Fedora release 26 (Twenty Six) [liveuser@localhost-live ~]$ ulimit -u 30453 [liveuser@localhost-live ~]$ So it would appear this is some sort of configuration of my current installation(s). I'm open to any suggestions that would help me find it. For now I'll also remove all of the config stuff I put into the /etc/systemd directory.
After removing all customizations and rebooting, I'm back to square 1 (or perhaps square 1024). Logging in with SSH results in the same, using the text console results in the same. Turned selinux to permissive, and it result in the same. I'm lost. If there are no suggestions I guess I'll just rebuild the system from scratch.
Well, re-built the system(s) keeping the user files only and the problem went away. Something must have been interfering, though I still don't know what.