Hi Ike,
For you last issue with service that is not starting (which is different than the eap tls issue). It looks like the service did not stop properly. It happens rarely but it happens. ``` Nov 30 09:05:33 XXXXX httpd.webservices-docker-wrapper[4988]: docker: Error response from daemon: Conflict. The container name "/httpd.webservices" is already in use by container "f29a4d6f043cdc4116d5f84c02253bb9b0b149cbcd98f133ff> ``` You need to stop the container with the httpd.webservice name. Something like: `docker stop httpd.webservice ; docker rm httpd.webservice` Then restart the service. Thank you for using PacketFence Regards Jeremy Goimard Senior Software Engineer [signature_117474225] Akamai Technologies - Inverse 145 Broadway Cambridge, MA 02142 Connect with Us: [signature_1388875202]<https://community.akamai.com/> [signature_3364560605] <http://blogs.akamai.com/> [signature_2499095976] <https://twitter.com/akamai> [signature_3425345268] <http://www.facebook.com/AkamaiTechnologies> [signature_4082763092] <http://www.linkedin.com/company/akamai-technologies> [signature_1928680685] <http://www.youtube.com/user/akamaitechnologies?feature=results_main> ________________________________ From: Ike Klar via PacketFence-users <packetfence-users@lists.sourceforge.net> Sent: Saturday, November 30, 2024 3:11:53 AM To: packetfence-users@lists.sourceforge.net Cc: Ike Klar Subject: Re: [PacketFence-users] PF 14.0 / An error occured while sending a JSONRPC request: Hello everyone Update: It looks like the web services are not starting. . . but I'm not quite sure why. . . (see logs below) I have completely reinstalled PF from the ISO (not XEN) and only configured it for EAP-TLS (incl. SSL certificates). ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hello everyone Update: It looks like the web services are not starting... but I'm not quite sure why... (see logs below) I have completely reinstalled PF from the ISO (not XEN) and only configured it for EAP-TLS (incl. SSL certificates). Again the same behavior. Nov 30 09:05:32 XXXXX systemd[1]: Starting packetfence-httpd.webservices.service - PacketFence Webservices Apache HTTP Server... ░░ Subject: A start job for unit packetfence-httpd.webservices.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ A start job for unit packetfence-httpd.webservices.service has begun execution. ░░ ░░ The job identifier is 164. Nov 30 09:05:32 XXXXX packetfence[4959]: -e(4959) INFO: generating /usr/local/pf/var/conf/ssl-certificates.conf (pf::services::manager::httpd::generateCommonConfig) Nov 30 09:05:32 XXXXX packetfence[4959]: -e(4959) INFO: generating /usr/local/pf/var/conf/captive-portal-common (pf::services::manager::httpd::generateCommonConfig) Nov 30 09:05:33 XXXXX httpd.webservices-docker-wrapper[4966]: Running with args --sig-proxy=true --rm --name=httpd.webservices --add-host=containers-gateway.internal:host-gateway -h XXXXX -v /var/lib/mysql:/var/lib/mysql -v> Nov 30 09:05:33 XXXXX httpd.webservices-docker-wrapper[4988]: docker: Error response from daemon: Conflict. The container name "/httpd.webservices" is already in use by container "f29a4d6f043cdc4116d5f84c02253bb9b0b149cbcd98f133ff> Nov 30 09:05:33 XXXXX httpd.webservices-docker-wrapper[4988]: See 'docker run --help'. Nov 30 09:05:33 XXXXX systemd[1]: packetfence-httpd.webservices.service: Main process exited, code=exited, status=125/n/a ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ An ExecStart= process belonging to unit packetfence-httpd.webservices.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 125. Nov 30 09:05:33 XXXXX systemd[1]: packetfence-httpd.webservices.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ The unit packetfence-httpd.webservices.service has entered the 'failed' state with result 'exit-code'. Nov 30 09:05:33 XXXXX systemd[1]: Failed to start packetfence-httpd.webservices.service - PacketFence Webservices Apache HTTP Server. ░░ Subject: A start job for unit packetfence-httpd.webservices.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ A start job for unit packetfence-httpd.webservices.service has finished with a failure. ░░ ░░ The job identifier is 164 and the job result is failed. Nov 30 09:05:33 XXXXX systemd[1]: packetfence-httpd.webservices.service: Scheduled restart job, restart counter is at 1. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ Automatic restarting of the unit packetfence-httpd.webservices.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Nov 30 09:05:33 XXXXX systemd[1]: Stopped packetfence-httpd.webservices.service - PacketFence Webservices Apache HTTP Server. ░░ Subject: A stop job for unit packetfence-httpd.webservices.service has finished ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ A stop job for unit packetfence-httpd.webservices.service has finished. ░░ ░░ The job identifier is 1121 and the job result is done. Nov 30 09:05:33 XXXXX systemd[1]: Starting packetfence-httpd.webservices.service - PacketFence Webservices Apache HTTP Server... ░░ Subject: A start job for unit packetfence-httpd.webservices.service has begun execution ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support<https://urldefense.com/v3/__https://www.debian.org/support__;!!GjvTz_vk!VKkcf9_8RaarpW6Os8xNSP5n7cvsVqFRJ5HGa_mkVTTTfJK7ROlm1yBPq_FBXbazsCwRUaTRW1w8rDL25znjYvQyYC33XC3MMtjqFQ$> ░░ ░░ A start job for unit packetfence-httpd.webservices.service has begun execution. ░░ ░░ The job identifier is 1121. Nov 30 09:05:34 XXXXX packetfence[5034]: -e(5034) INFO: generating /usr/local/pf/var/conf/ssl-certificates.conf (pf::services::manager::httpd::generateCommonConfig) Nov 30 09:05:34 XXXXX packetfence[5034]: -e(5034) INFO: generating /usr/local/pf/var/conf/captive-portal-common (pf::services::manager::httpd::generateCommonConfig) Nov 30 09:05:34 XXXXX httpd.webservices-docker-wrapper[5067]: Running with args --sig-proxy=true --rm --name=httpd.webservices --add-host=containers-gateway.internal:host-gateway -h XXXXX -v /var/lib/mysql:/var/lib/mysql -v> Nov 30 09:05:34 XXXXX httpd.webservices-docker-wrapper[5078]: Error response from daemon: No such container: httpd.webservices Nov 30 09:05:34 XXXXX httpd.webservices-docker-wrapper[5078]: Error response from daemon: No such container: 1 Nov 30 09:05:34 XXXXX httpd.webservices-docker-wrapper[5086]: Changing GID of user pf Nov 30 09:05:34 XXXXX httpd.webservices-docker-wrapper[5086]: Changing UID of user pf Am Fr., 29. Nov. 2024 um 20:11 Uhr schrieb Ike Klar <ikekla...@gmail.com<mailto:ikekla...@gmail.com>>: Hello everyone We already have a few PF installations running, but none with 14.0 yet. Here we have an error that is driving us crazy. There is an error entry in the log for every DHCPAck and the DHCP entries are not saved in the database (see below). We already had the same thing in a cluster and the error was issued when syncing the config files. This made the cluster unusable because no more config changes were possible. This is now a completely new installation via image without cluster. Does anyone have any ideas? 2024-11-29T20:06:25.680009+01:00 XXXXX pfqueue-backend[4005]: pfqueue(2515) INFO: [mac:unknown] Calling api task process_dhcpv4 (pf::task::api::doTask) 2024-11-29T20:06:25.680198+01:00 XXXXX pfqueue-backend[4013]: pfqueue(2515) INFO: [mac:unknown] Running task api (main::process_data) 2024-11-29T20:06:25.680274+01:00 XXXXX pfqueue-backend[4013]: pfqueue(2515) INFO: [mac:unknown] Calling api task process_dhcpv4 (pf::task::api::doTask) 2024-11-29T20:06:25.682180+01:00 XXXXX pfqueue-backend[4013]: pfqueue(2515) INFO: [mac:unknown] DHCPACK from X.X:X.X (00:09:0f:09:00:07) to host 38:c0:ea:69:30:a8 (172.18.59.71) for 300 seconds (pf::dhcp::processor_v4::parse_dhcp_ack) 2024-11-29T20:06:25.682245+01:00 XXXXX pfqueue-backend[4013]: pfqueue(2515) INFO: [mac:unknown] The listener process is NOT on the same server as the DHCP server. (pf::dhcp::processor_v4::pf_is_dhcp) 2024-11-29T20:06:25.701845+01:00 XXXXX pfqueue-backend[4005]: pfqueue(2515) ERROR: [mac:unknown] An error occured while sending a JSONRPC request: 35 SSL connect error gnutls_handshake() failed: The TLS connection was non-properly terminated. (pf::api::jsonrpcclient::notify) 2024-11-29T20:06:25.722820+01:00 XXXXX pfqueue-backend[4005]: pfqueue(2515) ERROR: [mac:unknown] An error occured while sending a JSONRPC request: 35 SSL connect error gnutls_handshake() failed: The TLS connection was non-properly terminated. (pf::api::jsonrpcclient::notify)
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
