Error Apache on Container

[Aditya Wirawan]

Hello,

my server installed proxmox 5.4. and i create many container inside it.
today some container had a problem in apache2 service,. after i check status apache service, there is notification below :

May 24 08:35:23 sismadak systemd[1]: Starting The Apache HTTP Server...
May 24 08:35:23 sismadak apachectl[117]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
May 24 08:35:23 sismadak apachectl[117]: Setting ulimit failed. See README.Debian for more information.
May 24 08:35:23 sismadak systemd[1]: Started The Apache HTTP Server.


please help to fix my problem,i try to restart service apache and restart container is still error, web still can not access from client

 

[oguz]

hi,

my server installed proxmox 5.4. and i create many container inside it.

latest version is 6.4 and 5.4 has been End-Of-Life for a while, so you should update to the latest version if possible [0]

May 24 08:35:23 sismadak systemd[1]: Starting The Apache HTTP Server...
May 24 08:35:23 sismadak apachectl[117]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
May 24 08:35:23 sismadak apachectl[117]: Setting ulimit failed. See README.Debian for more information.
May 24 08:35:23 sismadak systemd[1]: Started The Apache HTTP Server.

but it looks like the service is started?
you can check if the port is listening: ss -antlp | grep apache

can you post the container configuration: pct config CTID

[0]: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

 

[Aditya Wirawan]

Hello,

this i screenshot of ss -antlp | grep apache



ant this is screenshot of container config

 

[oguz]

according to your screenshot the apache server has started and the port is open and listening.

today some container had a problem in apache2 service

what problem did you have exactly?

web still can not access from client

the ulimit error message can be ignored -- your service is running. if you cannot access it then i would guess it's likely because of networking.

if you run curl 172.20.20.14 from your PVE server do you get a response? if yes then the container is accessible (from your PVE).