Hi Peter

In my case httpd.webservices  was timing out before it finished its startup. On 
timeout systemd would restart it, effectively putting it in an endless restart 
loop.

If you notice the process and container id of httpd.webservices are changing 
every 5 minutes or so this could be what is happening to you too.

If you are having the same problem, two workarounds solved it for me:

Option 1) The quick and dirty fix was to increase TimeoutStartSec in the 
following systemd unit file to something quite high e.g 1800 seconds.

    /lib/systemd/system/packetfence-httpd.webservices.service

then run 'systemctl daemon-reload'

Option 2) In the script /usr/local/pf/containers/pf-apache-wrapper there is a 
command that can sometimes take significantly longer than 5 minutes to complete.

It can be speeded up significantly by rewriting it, i.e. change 

    usermod -o -u $PF_UID -g $PF_GID -d /usr/local/pf pf

to

    usermod -o -u $PF_UID -g $PF_GID pf -d /dev/null pf
    usermod -d /usr/local/pf pf

then rebuild the httpd.webservices container with the command:

    /usr/local/pf/addons/dev-helpers/build-local-container.sh httpd.webservices

Finally, whichever option you chose, restart the service

    /usr/local/pf/bin/pfcmd service httpd.webservices stop
    /usr/local/pf/bin/pfcmd service httpd.webservices start

I have suggested option 2 as potential change for the next version on the pf 
github.

It may also be worth checking if the changes got reversed if you do any pf 
updates.

Kind regards

Ant

On 9 May 2025 at 08:34, Peter Jensen via PacketFence-users 
packetfence-users@lists.sourceforge.net wrote:
Hi

I get these errors with the httpd.webservices, which cannot start.
CLI Logs
#grep 'httpd.webservices' packetfence.log
2025-05-09T09:00:28.588336+02:00 nacsrv01 
httpd.webservices-docker-wrapper[3955586]: Running with args --sig-proxy=true 
--rm --name=httpd.webservices 
--add-host=containers-gateway.internal:host-gateway -h nacsrv01  -v 
/var/lib/mysql:/var/lib/mysql -v /etc/sudoers:/etc/sudoers -v 
/etc/sudoers.d/:/etc/sudoers.d/ -v 
/usr/local/fingerbank/conf:/usr/local/fingerbank/conf -v 
/usr/local/fingerbank/db:/usr/local/fingerbank/db -v 
/usr/local/pf/var/run:/usr/local/pf/var/run -ePF_UID=995 -e PF_GID=993 
-eFINGERBANK_UID=999 -e FINGERBANK_GID=994 -eIS_A_CLASSIC_PF_CONTAINER=yes 
-eTZ=Europe/Copenhagen -p 9090:9090 
-v/usr/local/pf/var/conf/:/usr/local/pf/var/conf/ 
-v/usr/local/pf/conf/:/usr/local/pf/conf/ 
-v/usr/local/pf/raddb/certs:/usr/local/pf/raddb/certs --privileged -v 
/run/systemd/system:/run/systemd/system -v 
/var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket 
-v/usr/local/pf/html/captive-portal/profile-templates:/usr/local/pf/html/captive-portal/profile-templates
2025-05-09T09:00:28.622596+02:00 nacsrv01 
httpd.webservices-docker-wrapper[3955600]: Error response from daemon: No such 
container: httpd.webservices


_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to