Topics created by LJedi

@Sebastian-Roth Thanks again. I created an new image without that VPN software installed and everything is working as it should. Sorry about this and thanks again for all your help and time.

The password is not encrypted anymore. This is not a bug, it’s expected behavior.

With that said, we did add some to the code to make sure that the password isn’t simply displayed in the plain text.

You’d need to install the dev-branch version though.

@Tom-Elliott Thanks for the information.

@george1421 Alright. Ran the test again and got the logs.

Apache Log (sample)

[Thu Aug 23 14:52:54.299174 2018] [proxy_fcgi:error] [pid 12423] [client 172.25.49.13:37260] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:54.299174 2018] [proxy_fcgi:error] [pid 12367] [client 172.25.49.13:36928] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:54.299296 2018] [proxy_fcgi:error] [pid 12423] (104)Connection reset by peer: [client 172.25.49.13:37260] AH01075: Error dispatching request to : [Thu Aug 23 14:52:54.299333 2018] [proxy_fcgi:error] [pid 12367] (104)Connection reset by peer: [client 172.25.49.13:36928] AH01075: Error dispatching request to : [Thu Aug 23 14:52:56.343241 2018] [proxy_fcgi:error] [pid 12314] [client 172.25.49.13:37312] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:56.343242 2018] [proxy_fcgi:error] [pid 12324] [client 172.25.49.13:37154] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:56.343334 2018] [proxy_fcgi:error] [pid 12314] (104)Connection reset by peer: [client 172.25.49.13:37312] AH01075: Error dispatching request to : [Thu Aug 23 14:52:56.343372 2018] [proxy_fcgi:error] [pid 12324] (104)Connection reset by peer: [client 172.25.49.13:37154] AH01075: Error dispatching request to : [Thu Aug 23 14:52:58.391273 2018] [proxy_fcgi:error] [pid 13269] [client 172.25.49.13:37284] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:58.391305 2018] [proxy_fcgi:error] [pid 13263] [client 172.25.49.13:37244] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:58.391279 2018] [proxy_fcgi:error] [pid 13261] [client 172.25.49.13:37238] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:58.391286 2018] [proxy_fcgi:error] [pid 13266] [client 172.25.49.13:37274] AH01067: Failed to read FastCGI header [Thu Aug 23 14:52:58.391432 2018] [proxy_fcgi:error] [pid 13269] (104)Connection reset by peer: [client 172.25.49.13:37284] AH01075: Error dispatching request to : [Thu Aug 23 14:52:58.391447 2018] [proxy_fcgi:error] [pid 13263] (104)Connection reset by peer: [client 172.25.49.13:37244] AH01075: Error dispatching request to : [Thu Aug 23 14:52:58.391502 2018] [proxy_fcgi:error] [pid 13266] (104)Connection reset by peer: [client 172.25.49.13:37274] AH01075: Error dispatching request to : [Thu Aug 23 14:52:58.391486 2018] [proxy_fcgi:error] [pid 13261] (104)Connection reset by peer: [client 172.25.49.13:37238] AH01075: Error dispatching request to : [Thu Aug 23 14:53:02.487262 2018] [proxy_fcgi:error] [pid 12363] [client 172.25.49.116:40982] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:02.487262 2018] [proxy_fcgi:error] [pid 12364] [client 172.25.49.108:52168] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:02.487356 2018] [proxy_fcgi:error] [pid 12363] (104)Connection reset by peer: [client 172.25.49.116:40982] AH01075: Error dispatching request to : [Thu Aug 23 14:53:02.487391 2018] [proxy_fcgi:error] [pid 12364] (104)Connection reset by peer: [client 172.25.49.108:52168] AH01075: Error dispatching request to : [Thu Aug 23 14:53:04.535082 2018] [proxy_fcgi:error] [pid 13249] [client 172.25.49.13:37160] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:04.535082 2018] [proxy_fcgi:error] [pid 13250] [client 172.25.49.13:37162] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:04.535187 2018] [proxy_fcgi:error] [pid 13249] (104)Connection reset by peer: [client 172.25.49.13:37160] AH01075: Error dispatching request to : [Thu Aug 23 14:53:04.535208 2018] [proxy_fcgi:error] [pid 13250] (104)Connection reset by peer: [client 172.25.49.13:37162] AH01075: Error dispatching request to : [Thu Aug 23 14:53:06.583087 2018] [proxy_fcgi:error] [pid 12425] [client 172.25.49.13:37266] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:06.583115 2018] [proxy_fcgi:error] [pid 12430] [client 172.25.49.13:37302] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:06.583115 2018] [proxy_fcgi:error] [pid 12427] [client 172.25.49.13:37268] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:06.583111 2018] [proxy_fcgi:error] [pid 12429] [client 172.25.49.13:37304] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:06.583162 2018] [proxy_fcgi:error] [pid 12425] (104)Connection reset by peer: [client 172.25.49.13:37266] AH01075: Error dispatching request to : [Thu Aug 23 14:53:06.583202 2018] [proxy_fcgi:error] [pid 12427] (104)Connection reset by peer: [client 172.25.49.13:37268] AH01075: Error dispatching request to : [Thu Aug 23 14:53:06.583190 2018] [proxy_fcgi:error] [pid 12430] (104)Connection reset by peer: [client 172.25.49.13:37302] AH01075: Error dispatching request to : [Thu Aug 23 14:53:06.583230 2018] [proxy_fcgi:error] [pid 12429] (104)Connection reset by peer: [client 172.25.49.13:37304] AH01075: Error dispatching request to : [Thu Aug 23 14:53:10.679240 2018] [proxy:error] [pid 12279] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679240 2018] [proxy:error] [pid 12301] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679240 2018] [proxy:error] [pid 12365] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679270 2018] [proxy:error] [pid 13228] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679404 2018] [proxy_fcgi:error] [pid 12279] [client 172.25.49.13:37034] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679423 2018] [proxy_fcgi:error] [pid 12301] [client 172.25.49.13:37050] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679469 2018] [proxy_fcgi:error] [pid 12365] [client 172.25.49.155:54020] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679490 2018] [proxy_fcgi:error] [pid 13228] [client 172.25.49.13:36996] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679852 2018] [proxy:error] [pid 12277] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679852 2018] [proxy:error] [pid 12272] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679931 2018] [proxy_fcgi:error] [pid 12277] [client 172.25.49.13:37012] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679912 2018] [proxy:error] [pid 12304] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679912 2018] [proxy:error] [pid 12278] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.679948 2018] [proxy_fcgi:error] [pid 12272] [client 172.25.49.13:37014] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.680005 2018] [proxy_fcgi:error] [pid 12278] [client 172.25.49.13:37018] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.679992 2018] [proxy_fcgi:error] [pid 12304] [client 172.25.49.13:37056] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.680241 2018] [proxy:error] [pid 12271] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.680240 2018] [proxy:error] [pid 12303] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.680304 2018] [proxy_fcgi:error] [pid 12271] [client 172.25.49.13:37002] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.680316 2018] [proxy_fcgi:error] [pid 12303] [client 172.25.49.13:37054] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.680510 2018] [proxy:error] [pid 12302] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.680573 2018] [proxy_fcgi:error] [pid 12302] [client 172.25.49.13:37036] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.680804 2018] [proxy:error] [pid 12275] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.680881 2018] [proxy_fcgi:error] [pid 12275] [client 172.25.49.13:37004] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:10.681115 2018] [proxy:error] [pid 12273] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:10.681182 2018] [proxy_fcgi:error] [pid 12273] [client 172.25.49.13:36994] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727045 2018] [proxy:error] [pid 12315] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727052 2018] [proxy:error] [pid 12310] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727052 2018] [proxy:error] [pid 12313] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727168 2018] [proxy_fcgi:error] [pid 12315] [client 172.25.49.13:37110] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727193 2018] [proxy_fcgi:error] [pid 12310] [client 172.25.49.13:37094] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727202 2018] [proxy_fcgi:error] [pid 12313] [client 172.25.49.13:37106] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727191 2018] [proxy:error] [pid 12323] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727316 2018] [proxy_fcgi:error] [pid 12323] [client 172.25.49.13:37148] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727431 2018] [proxy:error] [pid 12418] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727475 2018] [proxy_fcgi:error] [pid 12418] [client 172.25.49.13:37214] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727455 2018] [proxy:error] [pid 11819] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727510 2018] [proxy_fcgi:error] [pid 11819] [client 172.25.49.13:37146] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.727726 2018] [proxy:error] [pid 12309] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.727785 2018] [proxy_fcgi:error] [pid 12309] [client 172.25.49.13:37098] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728015 2018] [proxy:error] [pid 12311] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728064 2018] [proxy_fcgi:error] [pid 12311] [client 172.25.49.13:37092] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728060 2018] [proxy:error] [pid 12317] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728108 2018] [proxy_fcgi:error] [pid 12317] [client 172.25.49.13:37120] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728268 2018] [proxy:error] [pid 12307] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728317 2018] [proxy_fcgi:error] [pid 12307] [client 172.25.49.13:37084] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728317 2018] [proxy:error] [pid 12316] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728369 2018] [proxy_fcgi:error] [pid 12316] [client 172.25.49.13:37112] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728546 2018] [proxy:error] [pid 12305] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728596 2018] [proxy_fcgi:error] [pid 12305] [client 172.25.49.13:37076] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728584 2018] [proxy:error] [pid 12308] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728634 2018] [proxy_fcgi:error] [pid 12308] [client 172.25.49.13:37078] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728826 2018] [proxy:error] [pid 12412] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728856 2018] [proxy:error] [pid 12306] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.728879 2018] [proxy_fcgi:error] [pid 12412] [client 172.25.49.13:37200] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.728927 2018] [proxy_fcgi:error] [pid 12306] [client 172.25.49.13:37068] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.729140 2018] [proxy:error] [pid 12410] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.729163 2018] [proxy:error] [pid 12417] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.729192 2018] [proxy_fcgi:error] [pid 12410] [client 172.25.49.13:37196] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.729214 2018] [proxy_fcgi:error] [pid 12417] [client 172.25.49.13:37212] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.729445 2018] [proxy:error] [pid 12413] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.729495 2018] [proxy_fcgi:error] [pid 12413] [client 172.25.49.13:37172] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.729717 2018] [proxy:error] [pid 12414] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.729768 2018] [proxy_fcgi:error] [pid 12414] [client 172.25.49.13:37170] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.729985 2018] [proxy:error] [pid 12408] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.730035 2018] [proxy_fcgi:error] [pid 12408] [client 172.25.49.13:37166] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:12.732232 2018] [proxy:error] [pid 12320] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:12.732257 2018] [proxy_fcgi:error] [pid 12320] [client 172.25.49.13:37142] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:14.775041 2018] [proxy:error] [pid 13267] (110)Connection timed out: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [Thu Aug 23 14:53:14.775162 2018] [proxy_fcgi:error] [pid 13267] [client 172.25.49.13:37278] AH01079: failed to make connection to backend: 127.0.0.1 [Thu Aug 23 14:53:18.871129 2018] [proxy_fcgi:error] [pid 12359] [client 172.25.49.182:38394] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:18.871206 2018] [proxy_fcgi:error] [pid 12359] (104)Connection reset by peer: [client 172.25.49.182:38394] AH01075: Error dispatching request to : [Thu Aug 23 14:53:18.871368 2018] [proxy_fcgi:error] [pid 12362] [client 172.25.49.111:48116] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:18.871408 2018] [proxy_fcgi:error] [pid 12362] (104)Connection reset by peer: [client 172.25.49.111:48116] AH01075: Error dispatching request to : [Thu Aug 23 14:53:20.919068 2018] [proxy_fcgi:error] [pid 12419] [client 172.25.49.13:37216] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:20.919070 2018] [proxy_fcgi:error] [pid 12420] [client 172.25.49.13:37230] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:20.919067 2018] [proxy_fcgi:error] [pid 12415] [client 172.25.49.13:37210] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:20.919067 2018] [proxy_fcgi:error] [pid 12421] [client 172.25.49.13:37228] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:20.919151 2018] [proxy_fcgi:error] [pid 12419] (104)Connection reset by peer: [client 172.25.49.13:37216] AH01075: Error dispatching request to : [Thu Aug 23 14:53:20.919161 2018] [proxy_fcgi:error] [pid 12420] (104)Connection reset by peer: [client 172.25.49.13:37230] AH01075: Error dispatching request to : [Thu Aug 23 14:53:20.919193 2018] [proxy_fcgi:error] [pid 12415] (104)Connection reset by peer: [client 172.25.49.13:37210] AH01075: Error dispatching request to : [Thu Aug 23 14:53:20.919205 2018] [proxy_fcgi:error] [pid 12421] (104)Connection reset by peer: [client 172.25.49.13:37228] AH01075: Error dispatching request to : [Thu Aug 23 14:53:22.967076 2018] [proxy_fcgi:error] [pid 12434] [client 172.25.49.13:37316] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:22.967076 2018] [proxy_fcgi:error] [pid 12435] [client 172.25.49.13:37318] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:22.967146 2018] [proxy_fcgi:error] [pid 12434] (104)Connection reset by peer: [client 172.25.49.13:37316] AH01075: Error dispatching request to : [Thu Aug 23 14:53:22.967157 2018] [proxy_fcgi:error] [pid 12435] (104)Connection reset by peer: [client 172.25.49.13:37318] AH01075: Error dispatching request to : [Thu Aug 23 14:53:25.015166 2018] [proxy_fcgi:error] [pid 12436] [client 172.25.57.80:51375] AH01067: Failed to read FastCGI header, referer: http://172.25.49.13/fog/management/index.php?node=task&sub=active [Thu Aug 23 14:53:25.015312 2018] [proxy_fcgi:error] [pid 12436] (104)Connection reset by peer: [client 172.25.57.80:51375] AH01075: Error dispatching request to : , referer: http://172.25.49.13/fog/management/index.php?node=task&sub=active [Thu Aug 23 14:53:51.639042 2018] [proxy_fcgi:error] [pid 12276] [client 172.25.49.13:37010] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:51.639052 2018] [proxy_fcgi:error] [pid 12274] [client 172.25.49.13:37008] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:51.639117 2018] [proxy_fcgi:error] [pid 12276] (104)Connection reset by peer: [client 172.25.49.13:37010] AH01075: Error dispatching request to : [Thu Aug 23 14:53:51.639142 2018] [proxy_fcgi:error] [pid 12274] (104)Connection reset by peer: [client 172.25.49.13:37008] AH01075: Error dispatching request to : [Thu Aug 23 14:53:53.687052 2018] [proxy_fcgi:error] [pid 12411] [client 172.25.49.13:37206] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:53.687094 2018] [proxy_fcgi:error] [pid 12416] [client 172.25.49.13:37186] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:53.687149 2018] [proxy_fcgi:error] [pid 12411] (104)Connection reset by peer: [client 172.25.49.13:37206] AH01075: Error dispatching request to : [Thu Aug 23 14:53:53.687168 2018] [proxy_fcgi:error] [pid 12416] (104)Connection reset by peer: [client 172.25.49.13:37186] AH01075: Error dispatching request to : [Thu Aug 23 14:53:55.735175 2018] [proxy_fcgi:error] [pid 12431] [client 172.25.49.13:37310] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:55.735256 2018] [proxy_fcgi:error] [pid 12431] (104)Connection reset by peer: [client 172.25.49.13:37310] AH01075: Error dispatching request to : [Thu Aug 23 14:53:55.735258 2018] [proxy_fcgi:error] [pid 13265] [client 172.25.49.13:37272] AH01067: Failed to read FastCGI header [Thu Aug 23 14:53:55.735499 2018] [proxy_fcgi:error] [pid 13265] (104)Connection reset by peer: [client 172.25.49.13:37272] AH01075: Error dispatching request to : [Thu Aug 23 14:54:10.071304 2018] [proxy_fcgi:error] [pid 12438] [client 172.25.49.103:4802] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:10.071391 2018] [proxy_fcgi:error] [pid 12438] (104)Connection reset by peer: [client 172.25.49.103:4802] AH01075: Error dispatching request to : [Thu Aug 23 14:54:14.167115 2018] [proxy_fcgi:error] [pid 12439] [client 172.25.49.184:1025] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:14.167187 2018] [proxy_fcgi:error] [pid 12439] (104)Connection reset by peer: [client 172.25.49.184:1025] AH01075: Error dispatching request to : [Thu Aug 23 14:54:14.167431 2018] [proxy_fcgi:error] [pid 12437] [client 172.25.49.200:57962] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:14.167476 2018] [proxy_fcgi:error] [pid 12437] (104)Connection reset by peer: [client 172.25.49.200:57962] AH01075: Error dispatching request to : [Thu Aug 23 14:54:14.167472 2018] [proxy_fcgi:error] [pid 12328] [client 172.25.49.171:5606] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:14.167537 2018] [proxy_fcgi:error] [pid 12328] (104)Connection reset by peer: [client 172.25.49.171:5606] AH01075: Error dispatching request to : [Thu Aug 23 14:54:24.407081 2018] [proxy_fcgi:error] [pid 12329] [client 172.25.49.149:27292] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:24.407174 2018] [proxy_fcgi:error] [pid 12329] (104)Connection reset by peer: [client 172.25.49.149:27292] AH01075: Error dispatching request to : [Thu Aug 23 14:54:34.647026 2018] [proxy_fcgi:error] [pid 12374] [client 172.25.57.80:51444] AH01067: Failed to read FastCGI header, referer: http://172.25.49.13/fog/management/index.php?node=task&sub=active [Thu Aug 23 14:54:34.647069 2018] [proxy_fcgi:error] [pid 12381] [client 172.25.49.168:12119] AH01067: Failed to read FastCGI header [Thu Aug 23 14:54:34.647107 2018] [proxy_fcgi:error] [pid 12374] (104)Connection reset by peer: [client 172.25.57.80:51444] AH01075: Error dispatching request to : , referer: http://172.25.49.13/fog/management/index.php?node=task&sub=active

PHP-fpm Error Log (Sample)

[23-Aug-2018 10:33:37] NOTICE: systemd monitor interval set to 10000ms [23-Aug-2018 12:23:53] NOTICE: [pool www] child 740 exited with code 0 after 6616.766926 seconds from start [23-Aug-2018 12:23:53] NOTICE: [pool www] child 16544 started [23-Aug-2018 12:23:54] NOTICE: [pool www] child 742 exited with code 0 after 6617.066685 seconds from start [23-Aug-2018 12:23:54] NOTICE: [pool www] child 16595 started [23-Aug-2018 12:24:26] NOTICE: [pool www] child 838 exited with code 0 after 6641.945870 seconds from start [23-Aug-2018 12:24:26] NOTICE: [pool www] child 16758 started [23-Aug-2018 12:25:56] NOTICE: [pool www] child 741 exited with code 0 after 6739.049484 seconds from start [23-Aug-2018 12:25:56] NOTICE: [pool www] child 16890 started [23-Aug-2018 12:26:56] NOTICE: [pool www] child 739 exited with code 0 after 6799.084111 seconds from start [23-Aug-2018 12:26:56] NOTICE: [pool www] child 16965 started [23-Aug-2018 12:27:06] NOTICE: [pool www] child 743 exited with code 0 after 6809.011899 seconds from start [23-Aug-2018 12:27:06] NOTICE: [pool www] child 16972 started [23-Aug-2018 12:30:26] NOTICE: [pool www] child 2261 exited with code 0 after 6995.000073 seconds from start [23-Aug-2018 12:30:26] NOTICE: [pool www] child 17204 started [23-Aug-2018 12:31:36] NOTICE: [pool www] child 2260 exited with code 0 after 7065.031347 seconds from start [23-Aug-2018 12:31:36] NOTICE: [pool www] child 17285 started [23-Aug-2018 12:32:16] NOTICE: [pool www] child 2088 exited with code 0 after 7105.962251 seconds from start [23-Aug-2018 12:32:16] NOTICE: [pool www] child 17333 started [23-Aug-2018 14:23:47] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 16 total children [23-Aug-2018 14:23:48] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 21 total children [23-Aug-2018 14:23:49] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 26 total children [23-Aug-2018 14:23:50] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 31 total children [23-Aug-2018 14:23:51] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 36 total children [23-Aug-2018 14:26:37] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 17 total children [23-Aug-2018 14:26:38] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 22 total children [23-Aug-2018 14:26:39] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 27 total children [23-Aug-2018 14:26:40] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 32 total children [23-Aug-2018 14:26:41] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 37 total children [23-Aug-2018 14:26:42] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 42 total children [23-Aug-2018 14:45:58] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 17 total children [23-Aug-2018 14:45:59] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 22 total children [23-Aug-2018 14:46:00] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 27 total children [23-Aug-2018 14:46:01] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 32 total children [23-Aug-2018 14:46:02] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 37 total children [23-Aug-2018 14:46:03] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 42 total children [23-Aug-2018 14:46:04] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 47 total children [23-Aug-2018 14:46:05] WARNING: [pool www] server reached pm.max_children setting (50), consider raising it```

I know this is a very old topic but it seems like people find this and follow it blindly. Please be aware that using the installer parameter -C (or --recreate-CA in long form) will overwrite your FOG internal certificate authority and break all fog-client installs because of this. The fog-client is pinned to this CA when installing the software on the machine and you need to re-install fog-client (or magically exchange the CA cert) on all your machines!

Please see:
https://forums.fogproject.org/topic/10768/can-t-add-location-under-location-managment/2

@Tom-Elliott Thanks Tom. I went ahead and deleted all the columns and just left the <mac> and <hostname> and they imported successfully.

I had the same issue. I changed the “HOST EFI Exit Type” for the host to “REFIND_EFI”. After rebooting, when you go to boot from HDD, you will get proceed to a screen titled “rEFInd - Initializing” and “Hit any key to continue”.

After hitting enter, I boot right into Windows no problem.

alt text

@LJedi Could you please upgrade to the latest trunk and see if the d1.fixed_size_partitions is now created properly in your case?

Thanks Tom for looking into this and fixing it!

@LJedi First thing is to update to the latest, on all nodes - master first. Second is to review permissions, interfaces, IP addresses, storage groups, just going through it all.

Can you post the replication log? Also telling us which Image you updated recently. The output of ls -lahRt /images from the main server might reveal something.

Also, ensure all your fields for the storage node are filled out, such as web root, images path, ftp path, etc.

@Joe-Schmitt said in Fog Client Disjoin From Domain Feature:

Could there be an on-demand unjoin task?

Powershell can do that. Why make a custom task? It can be done with a simple snapin and powershell file.

Although I suppose even that is easy to overlook, because if it’s left associated, it’ll run on next image deployment and might un-do the client’s work, causing the client to join the domain twice, and reboot twice as much as it already is.

Bottom line I guess from this thread and multiple others of similar nature is pay attention to what you’re doing, and what’s going on in your environment.

Things can be implimented and safeguarded, but too much of that hinders everything else.

Thanks @george1421 and @Sebastian-Roth for your help. For now I did what Sebastain mentioned and moved the images and that worked. George, when I get more time I will review your documentation and see if that is something that I would want to do in the future.

Once again thanks!

@Kiweegie said in Snapin Questions:

While Jbobs description of snapins as files which get executed remotely is spot on, the real benefit of using snapins is in conjunction with silent switches so the installation happens without your users seeing anything going on. This avoids them having to call the Helpdesk because “some weird screen just popped up on my 'puter!”

I wanted to say that if you’re using the new FOG Client, there will never be a display from a snapin - ever. At least not directly. This is because all snapins with the new FOG Client run as the SYSTEM user, which is prohibited from displaying anything to the user at all in Windows. This is by design of Windows itself. If your snapin isn’t silent, or properly configured to run silently, your snapin will infinitely hang. Hanging is a sure sign of a snapin waiting for input that will never come.

Marking as resolved due to the update.

Thank you for your suggestions. We will test and report back.

Verified that it is working. Thanks Tom!