@Sebastian-Roth Hi, Yep and it was very helpful for me, just execute the last command after coming back to the snapshot and all is good now :-).

Thanks a lot to Tom Elliot for this post.

Have a nive day

@maxi-mumm Any errors you get in the apache error log when scheduling a group task?

Ok, the file is pretty big, so if you want i can upload the whole thing. That said, this is what i picked out from it:

The following packages will be REMOVED:
curl libcurl4 php7.1-curl
The following NEW packages will be installed:
libcurl13

The following additional packages will be installed:
libcurl4
The following packages will be REMOVED:
libcurl3
The following NEW packages will be installed:
libcurl4 php7.1-curl
0 upgraded, 2 newly installed, 1 to remove and 145 not upgraded.

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libcurl3 : Conflicts: libcurl4 but 7.58.0-2ubuntu3.2 is to be installed
libcurl4 : Conflicts: libcurl3 but 7.58.0-2ubuntu2 is to be installed
E: Broken packages
ii apache2 2.4.33-1+ubuntu17.10.1+deb.sury.org+1 amd64 Apache HTTP Server
ii bc 1.07.1-2 amd64 GNU bc arbitrary precision calculator language
ii build-essential 12.4ubuntu1 amd64 Informational list of build-essential packages
ii cpp 4:7.3.0-3ubuntu2 amd64 GNU C preprocessor (cpp)

So, maybe i have too new a version of curl installed? I’m not sure how that would happen, we don’t use this server for anything but fog. Would that cause the installer to fail this way?

@Sebastian-Roth Ctrl+C doesn’t work either. Yeah we have 35+ sites that have PBX’s on older machines. We are in the middle of a tech refresh right now and and we are replacing them with servers that have ILO’s so this won’t be an issue in the future. For now what I do is ship the site a remote KVM so I can at least perform maintenance without user interaction. It was over the weekend so all site personnel were gone. This issue can be closed now. I had someone just press the power button this morning. I was just trying to find another way over the weekend.

@imagingmaster21 Well I’m still suspecting that the linux user fog’s password as been reset/out of sync with what FOG’s configuration thinks it is. Your screen shot of the error is almost 100% proof. Also if you inspect /images/dev directory on the fog server you should see one or more directories in there that are named similar to mac addresses.

Please follow the steps here to resync the linux user fog’s password with the web ui: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

@Basavarajnc said in how to configure 2 Network Interfaces..One for Internet and Second for FOG Server..?:

This eth1 is for FOG SERVER (Static)
auto eth1
iface eth1 inet static
address 192.168.147.XXX
netmask 255.255.255.0
network 192.168.147.0
broadcast 192.168.147.255

The above thing is enough configuration of eth1 to make Fog Server Successful?

is it OK Sir OR need to do any extra Configurations over here ?

Heartily Thank you for kind Reply

Basavaraj From India.

@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```

@Towndrunk Please look at the chat bubble for additional information.

Ended up being a database related error on the server. I basically went through the install of the server software again, then activated the “new” database and all good.

@Wayne-Workman

Tried a totally different, but exactly the same, box and the master image worked for capturing and deploying. Very strange but whatever. I’ll take it.

Thanks!

@Wayne-Workman said in Fog tftp only works when I disable firewalld:

sestatus

Turns out this time around it was me not entering the correct info during the install. Wrong router address for the DHCP server and wrong address entered on the DHCP server for option 66. When I ran the installer again this morning I realized what I did wrong right away. So far so good right now…

I found a solution for my problem. I added “acpi=off” as Host Kernel Argument and now everything works fine.

@quazz Update… Updating cURL was the answer.
libcurl-7.19.7-52.el6.x86_64 already installed and latest version
Nothing to do

Upgraded to : [root@DO-FOG-02 yum.repos.d]# curl --version
curl 7.61.0 (x86_64-redhat-linux-gnu) libcurl/7.61.0 OpenSSL/1.0.1e zlib/1.2.3 c-ares/1.14.0 libssh2/1.8.0 nghttp2/1.6.0
Release-Date: 2018-07-11

You are correct, I tried it on fresh Ubuntu 16.04 and it worked.

I didn’t spend the time to pinpoint the exact error, but removing the old config (get rid of /opt/fog/.fogsettings) is letting the installer run, so this particular issue is fixed.

@jemerson93 The mbr/gpt issue needs to be resolved, period. The truth may be this slow creation process may be a ‘feature’ of 4.17.x kernel and not a bug. I can tell you this issue is still on the developers plate (which is getting overloaded at the moment). Please give them a bit to get back from holiday and back in business.

@sebastian-roth Can go ahead and mark this as solved. Thank you for the help.

@quazz said in Edit Image:

You could potentially use postdownloadscripts instead for something like this.

This is exactly how I go about updating the golden image between image captures. It uses a similar concept to dynamically installing drivers during image deployment. I do take this one step more by creating a file in the golden image that has a sequence number in it, that way I can reference that file in the post install script to only apply the fixes related to that specific sequence number.

Thanx.
The thread can be marked als solved. Can I do this somewhere or can just a board admin do that?

@Korvyr From the pictures yo posted I guess you have a different issue to what has been initially posted. Would you mind opening a new thread and posting your client hardware details there? I will move your posts to that as soon as you opened a new thread.

@Mike-Fahey Can you post the commands used to delete and how you see that there is still no free space? If we don’t see what you are, how can we help you?