Apache2 and PAM Limits: Difference between revisions
From WikiMLT
m Стадий: 1 [Фаза:Идентифициране, Статус:Създаване]; Категория:Web Servers |
m Стадий: 2 [Фаза:Разработване, Статус:Създаден]; Категория:Web Servers |
||
| Line 29: | Line 29: | ||
{{devStage | {{devStage | ||
| Прндл = Web Servers | | Прндл = Web Servers | ||
| Стадий = | | Стадий = 2 | ||
| Фаза = | | Фаза = Разработване | ||
| Статус = | | Статус = Създаден | ||
| ИдтПт = {{REVISIONUSER}} | | ИдтПт = Spas | ||
| ИдтДт = {{Today}} | | РзбПт = {{REVISIONUSER}} | ||
| ИдтРв = {{REVISIONID}} | | ИдтДт = 2.08.2022 | ||
| РзбДт = {{Today}} | |||
| ИдтРв = [[Special:Permalink/29689|29689]] | |||
| РзбРв = {{REVISIONID}} | |||
}} | }} | ||
</div> | </div> | ||
</noinclude> | </noinclude> | ||
Revision as of 11:01, 2 August 2022
References
- …
- …
Section 1
…
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
