Apache2 and PAM Limits: Difference between revisions
From WikiMLT
m Стадий: 5 [Фаза:Утвърждаване, Статус:Авторизиран]; Категория:Web Servers |
m Стадий: 6 [Фаза:Утвърждаване, Статус:Утвърден]; Категория:Web Servers |
||
| Line 23: | Line 23: | ||
| Прндл = Web Servers | | Прндл = Web Servers | ||
| Прндл1 = Linux Server | | Прндл1 = Linux Server | ||
| Стадий = | | Стадий = 6 | ||
| Фаза = Утвърждаване | | Фаза = Утвърждаване | ||
| Статус = | | Статус = Утвърден | ||
| ИдтПт = Spas | | ИдтПт = Spas | ||
| РзбПт = Spas | | РзбПт = Spas | ||
Latest revision as of 11:03, 2 August 2022
Within the output of the command systemctl status apache2.service was found the following error messages:
pam_limits(sudo:session): Could not set limit for 'core' to soft=0, hard=-1: Operation not permitted; uid=33,euid=0
pam_limits(sudo:session): Could not set limit for 'nofile' to soft=1024, hard=1048576: Operation not permitted; uid=33,euid=0
The solution is provided within the answers of the question How to set ulimit value permanently? at Server Fault. The applied steps are shown below, and of course the server was restarted.
sudo nano /etc/pam.d/common-session
# https://serverfault.com/questions/610130/how-to-set-ulimit-value-permanently
session required pam_limits.so
sudo nano /etc/security/limits.conf
# https://serverfault.com/questions/610130/how-to-set-ulimit-value-permanently
* soft core 0
* hard core -1
* soft nofile 65535
* hard nofile 1048576
