Hello Fabrice, Thank you on your promptly answer. Yes static content is not working. httpd.dispatcher was not running. And I could not start it, it was failing. Can you point me where I can find more info about httpd.dispatcher and its purpose, or if you can write briefly its purpose. Unfortunately I haven't had more time for troubleshooting, so I have rolled back the VM from backup to the state before OS update, to ensure Packetfence runs correctly.
Thank You. ---- On Wed, 15 May 2019 14:48:28 +0200 Fabrice Durand via PacketFence-users <[email protected]> wrote ---- > Hello Kalcho, > > it looks to be the static content that is not working. > > Can you check if httpd.dispatcher is running correctly ? > > Regards > > Fabrice > > > Le 19-05-15 à 03 h 16, Kalcho via PacketFence-users a écrit : > > Hello, > > > > I have packetfence 8.1 running on CentOS 7, after last CentOS update, > > captive portal does not work. It just shows message "an error occurred". I > > see that captive portal resource files can not be obtained the HTTP error > > 503 received. > > > > When trying to access packetfence/captive-portal the haproxy_portal.log > > shows next messages: > > > > May 15 06:46:57 packetfence haproxy[6857]: 172.25.0.245:36436 > > [15/May/2019:06:46:54.699] portal-https-172.18.0.22~ proxy/<NOSRV> > > 0/0/-1/-1/3005 503 212 - - SC-- 3/2/0/0/3 0/0 "GET / HTTP/1.1" > > May 15 06:47:00 packetfence haproxy[6857]: 172.25.0.245:36438 > > [15/May/2019:06:46:57.893] portal-https-172.18.0.22~ static/<NOSRV> > > 0/0/-1/-1/3005 503 212 - - SC-- 2/1/0/0/3 0/0 "GET /favicon.ico HTTP/1.1" > > May 15 06:47:06 packetfence haproxy[6857]: 172.25.0.245:36440 > > [15/May/2019:06:47:05.954] portal-https-172.18.0.22~ > > 172.18.0.22-backend/127.0.0.1 0/0/0/257/257 200 4382 - - ---- 3/2/0/0/0 > > 0/0 "GET /captive-portal HTTP/1.1" > > May 15 06:47:09 packetfence haproxy[6857]: 172.25.0.245:36442 > > [15/May/2019:06:47:06.286] portal-https-172.18.0.22~ static/<NOSRV> > > 0/0/-1/-1/3005 503 212 - - SC-- 6/5/4/0/3 0/0 "GET /common/styles.css > > HTTP/1.1" > > > > I have also applied packetfence maintenance patch, but error stays. I have > > investigated what means this HAProxy error and apparently SC flag means: > > > > "This is a problem with your back-end server, or a network issue between > > HAProxy and the back-end... not on the front side, and not related to the > > IP address of the connecting client. > > From "Session state at disconnect" in the docs: > > SC The [back-end] server or an equipment between it and haproxy explicitly > > refused the TCP connection (the proxy received a TCP RST or an ICMP > > message in return). Under some circumstances, it can also be the network > > stack telling the proxy that the server is unreachable (eg: no route, or > > no ARP response on local network). When this happens in HTTP mode, the > > status code is likely a 502 or 503 here." > > > > Regarding this explanation I see that the problem lays between haproxy and > > captive-portal httpd server communication. Both are running on the same > > server. Httpd is listening on the 127.0.0.1:80 when checked using netstat. > > I do not know what to troubleshoot next? > > > > > > > > _______________________________________________ > > PacketFence-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > -- > Fabrice Durand > [email protected] :: +1.514.447.4918 (x135) :: www.inverse.ca > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence > (http://packetfence.org) > > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
