@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.
Posts made by LJedi
-
RE: Fog Client Authentication Issue
-
RE: Fog Client Authentication Issue
@Sebastian-Roth said in Fog Client Authentication Issue:
SELECT * FROM hosts WHERE hostID=640;
After running that command, It did show a host, the host that I created the image from. I clicked on that host, and it was showing two MAC addresses (Its own MAC and the MAC of the PC that I deployed the image to). I went in and deleted that HOST and the correct PC showed up in the “Pending Host”. Really weird.
Update: The second MAC is the MAC from a VPN software that I installed. I think that is causing issues. I’ll continue to troubleshoot.
-
RE: Fog Client Authentication Issue
@Daniel-Miller Thank you!
MariaDB [fog]> SELECT * FROM hostMAC WHERE hmMAC IN ('00:ff:d4:ce:09:d6','b0:83: fe:83:73:4c'); +------+----------+-------------------+--------+-----------+-----------+-------- --------+-----------------+ | hmID | hmHostID | hmMAC | hmDesc | hmPrimary | hmPending | hmIgnor eClient | hmIgnoreImaging | +------+----------+-------------------+--------+-----------+-----------+-------- --------+-----------------+ | 664 | 640 | 00:ff:d4:ce:09:d6 | | 1 | | 0 | 0 | | 705 | 640 | b0:83:fe:83:73:4c | | 0 | 1 | 0 | 0 | +------+----------+-------------------+--------+-----------+-----------+-------- --------+-----------------+ 2 rows in set (0.001 sec)
-
RE: Fog Client Authentication Issue
@Sebastian-Roth Sure looks empty to me.
MariaDB [fog]> SELECT * FROM hostMAC WHERE hmMAC IN ('00:ff:d4:ce:09:d6','b0:83:fe:83:73:4c') ->
-
RE: Fog Client Authentication Issue
@Sebastian-Roth I looked over the forums that you linked and cleaned up the database and verified on the Fog server that I am not filtering anything when it comes to the hosts. I deleted the host that was having issues on the Fog server and hoping that it will show up under “Pending Hosts” and it never did. The fog log on the PC did change. Any ideas?
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 1/3/2020 10:29 AM Client-Info Version: 0.11.16 1/3/2020 10:29 AM Client-Info OS: Windows 1/3/2020 10:29 AM Middleware::Authentication Waiting for authentication timeout to pass 1/3/2020 10:31 AM Middleware::Communication Download: http://172.25.48.10/fog/management/other/ssl/srvpublic.crt 1/3/2020 10:31 AM Data::RSA FOG Server CA cert found 1/3/2020 10:31 AM Middleware::Authentication Cert OK 1/3/2020 10:31 AM Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before 1/3/2020 10:31 AM Middleware::Authentication ERROR: Could not get security token 1/3/2020 10:31 AM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'. 1/3/2020 10:31 AM Middleware::Communication POST URL: http://172.25.48.10/fog/management/index.php?sub=requestClientInfo&authorize&newService 1/3/2020 10:31 AM Middleware::Response Invalid security token 1/3/2020 10:31 AM Middleware::Communication URL: http://172.25.48.10/fog/management/index.php?sub=requestClientInfo&configure&newService&json 1/3/2020 10:31 AM Middleware::Response Success 1/3/2020 10:31 AM Middleware::Communication URL: http://172.25.48.10/fog/management/index.php?sub=requestClientInfo&mac=00:FF:D4:CE:09:D6|B0:83:FE:83:73:4C&newService&json 1/3/2020 10:31 AM Middleware::Authentication Waiting for authentication timeout to pass 1/3/2020 10:33 AM Middleware::Communication Download: http://172.25.48.10/fog/management/other/ssl/srvpublic.crt 1/3/2020 10:33 AM Data::RSA FOG Server CA cert found 1/3/2020 10:33 AM Middleware::Authentication Cert OK 1/3/2020 10:33 AM Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before 1/3/2020 10:33 AM Middleware::Authentication ERROR: Could not get security token 1/3/2020 10:33 AM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'. 1/3/2020 10:33 AM Middleware::Communication POST URL: http://172.25.48.10/fog/management/index.php?sub=requestClientInfo&authorize&newService 1/3/2020 10:33 AM Middleware::Response Invalid security token 1/3/2020 10:33 AM Middleware::Response Success 1/3/2020 10:33 AM Middleware::Communication URL: http://172.25.48.10/fog/service/getversion.php?clientver&newService&json 1/3/2020 10:33 AM Middleware::Communication URL: http://172.25.48.10/fog/service/getversion.php?newService&json 1/3/2020 10:33 AM Service Creating user agent cache 1/3/2020 10:33 AM Middleware::Response ERROR: Unable to get subsection 1/3/2020 10:33 AM Middleware::Response ERROR: Object reference not set to an instance of an object. 1/3/2020 10:33 AM Middleware::Response ERROR: Unable to get subsection 1/3/2020 10:33 AM Middleware::Response ERROR: Object reference not set to an instance of an object. 1/3/2020 10:33 AM Middleware::Response ERROR: Unable to get subsection 1/3/2020 10:33 AM Middleware::Response ERROR: Object reference not set to an instance of an object. 1/3/2020 10:33 AM Service Initializing modules
-
RE: Fog Client Authentication Issue
@Sebastian-Roth Thank you for the information! I’ll look into the database issue and report back what I find.
-
Fog Client Authentication Issue
Hello,
Running 1.5.7 on Debian 10. This is a new server and I had to follow the instructions here (https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG#If_old_server_was_FOG_1.3.0.2B) since I wanted to keep my current Fog client hosts to still communicate after the new server was up. Those clients (around 200) are communicating great after following those instructions.But, when I download the Fog client from the new server to be used on a new image and when that image is deployed, the authentication is broken. Looking at the fog log on the PC it looks like it wants to download a security token but can’t find where that is at. Any help would be great. Thanks again
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 1/2/2020 3:50 PM Client-Info Version: 0.11.16 1/2/2020 3:50 PM Client-Info OS: Windows 1/2/2020 3:50 PM Middleware::Authentication Waiting for authentication timeout to pass 1/2/2020 3:52 PM Middleware::Communication Download: http://172.25.48.10/fog/management/other/ssl/srvpublic.crt 1/2/2020 3:52 PM Data::RSA FOG Server CA cert found 1/2/2020 3:52 PM Middleware::Authentication Cert OK 1/2/2020 3:52 PM Middleware::Authentication ERROR: Could not get security token 1/2/2020 3:52 PM Middleware::Authentication ERROR: The system cannot find the path specified. 1/2/2020 3:52 PM Middleware::Communication POST URL: http://172.25.48.10/fog/management/index.php?sub=requestClientInfo&authorize&newService 1/2/2020 3:52 PM Middleware::Response Error multiple hosts returned for list of mac addresses
-
AD Default Password Not Encrypted 1.5.7-Debian 10
Hello,
I have done a clean install of Fog 1.5.7 on Debian 10 and under “Active Directory Defaults”. When I put in the password for “AD Default Password” and hit update. The password in not encrypted. On the Host side, under “Domain Password” when I selected to view the password, it too is not encrypted. -
RE: Cant create User - Setting up fogproject user..................................Failed!
@Sebastian-Roth : I fixed it. I needed to do run
su -
and that fixed the Path variable that is not set properly. Fog is now installed correctly and theuseradd
worked great. This is the page that I found that lead me to the fix.
https://linuxconfig.org/command-not-found-missing-path-to-sbin-on-debian-gnu-linuxThanks again for your help.
-
RE: Cant create User - Setting up fogproject user..................................Failed!
@Sebastian-Roth : I log in as my normal user then use the
su
to switch over to the root user.Here is the results:
echo $PATH /sbin/useradd /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games /sbin/useradd
echo $PATH /usr/sbin/useradd /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games /usr/sbin/useradd
-
RE: Cant create User - Setting up fogproject user..................................Failed!
root@testbebian10:/# useradd bash: useradd: command not found root@testbebian10:/#
-
RE: Cant create User - Setting up fogproject user..................................Failed!
@Sebastian-Roth Thank you Sebastian. Anything I can do to help please let me know. For background, this was a clean install of Debian 10.2 that I did today. Tomorrow, I will be doing another install of Debian 10.2 on a different box. I will let you know what the results are.
-
RE: Cant create User - Setting up fogproject user..................................Failed!
@Sebastian-Roth I run it just under the root user.
./installfog.sh
-
RE: Cant create User - Setting up fogproject user..................................Failed!
@Sebastian-Roth : I too am seeing this issue with Debian 10.2.0 running 1.5.7. Here are my log files for you to take a look at. Let me know what I can do to help troubleshoot. I have also tested the dev-branch with the same result.
/fogproject/bin# tail -20 /fogproject/bin/error_logs/fog_error _1.5.7.log ii php7.3 7.3.11-1~deb10u1 all server-side, HTML-embedded scri pting language (metapackage) ii php7.3-bcmath 7.3.11-1~deb10u1 amd64 Bcmath module for PHP ii php7.3-cli 7.3.11-1~deb10u1 amd64 command-line interpreter for th e PHP scripting language ii php7.3-curl 7.3.11-1~deb10u1 amd64 CURL module for PHP ii php7.3-fpm 7.3.11-1~deb10u1 amd64 server-side, HTML-embedded scri pting language (FPM-CGI binary) ii php7.3-gd 7.3.11-1~deb10u1 amd64 GD module for PHP ii php7.3-json 7.3.11-1~deb10u1 amd64 JSON module for PHP ii php7.3-mbstring 7.3.11-1~deb10u1 amd64 MBSTRING module for PHP ii php7.3-mysql 7.3.11-1~deb10u1 amd64 MySQL module for PHP ii php-gettext 1.0.12-0.1 all transitional dummy package for php- php-gettext ii sysv-rc-conf 0.99-7 all SysV init runlevel configuration to ol for the terminal ii tar 1.30+dfsg-6 amd64 GNU version of the tar archiving ut ility ii tftpd-hpa 5.2+20150808-1+b1 amd64 HPA's tftp server ii tftp-hpa 5.2+20150808-1+b1 amd64 HPA's tftp client ii unzip 6.0-23+deb10u1 amd64 De-archiver for .zip files ii vsftpd 3.0.3-12 amd64 lightweight, efficient FTP server w ritten for security ii wget 1.20.1-1.1 amd64 retrieves files from the web ii xinetd 1:2.3.15.3-1 amd64 replacement for inetd with many enh ancements ii zlib1g:amd64 1:1.2.11.dfsg-1 amd64 compression library - runtime ../lib/common/functions.sh: line 1194: useradd: command not found
tail -20 /fogproject/bin/error_logs/foginstal l.log * Checking package: php7.3-fpm................................OK * Checking package: php7.3-gd.................................OK * Checking package: php7.3-json...............................OK * Checking package: php7.3-ldap...............................OK * Checking package: php7.3-mbstring...........................OK * Checking package: php7.3-mysql..............................OK * Checking package: php-gettext...............................OK * Checking package: sysv-rc-conf..............................OK * Checking package: tar.......................................OK * Checking package: tftpd-hpa.................................OK * Checking package: tftp-hpa..................................OK * Checking package: unzip.....................................OK * Checking package: vsftpd....................................OK * Checking package: wget......................................OK * Checking package: xinetd....................................OK * Checking package: zlib1g....................................OK * Configuring services * Setting up fogproject user..................................Failed!
-
RE: Export Host File- Plain Text Password
@Tom-Elliott Thanks for the information.
-
Export Host File- Plain Text Password
Version 1.5.5
I have notice that when I export the host to a CSV file, the password that is used to join them to the domain is in plain text and not encrypted (possible bug?). I know that in previous version of Fog, the password was encrypted in the CSV file and not in plain text.
-
RE: 503 Service Unavailable
@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```
-
RE: 503 Service Unavailable
@george1421 Thanks for your feedback. I did verify that I did have 256M and not 256. I did run the top command and sorted by process and I do have php-fpm7.0 running in the top 4 services. I will also look to downgrading the linux kernels to resolve the 3-5 minute create disk structure issue.
-
503 Service Unavailable
Fog Version: 1.5.4.8
OS: Debian 9I am having an issue where my Fog server will get 503 service unavailable. I first saw this issue when I was booting 64 computers to my Fog server (1.5.2 at the time) to multicast. TFTP worked but was timing out at HTTP.
Updated to 1.5.4 but still had the issue so I switched to the working branch of 1.5.4.8 which resolved that issue. After the multicast was completed, the PCs were stuck at updating database. The web portal of Fog became unresponsive with 503 Service Unavailable. Eventually the PCs timed out and booted to the OS and the Fog web portal returned to normal.
I have reviewed other posts and I have verified that my www.conf file had the recommend settings where users reported 504 gateway timeout issues when they had updating database failures.
pm.max_children = 35 pm.max_requests = 2000 php_admin_value[memory_limit] = 256
I have not seen this before with older versions of Fog (1.5.0) which I was successfully able to multicast 130 computers at once without any issues (same hardware).
Any suggestions would be awesome!
Thanks!
-
RE: Debian 9- Creating SSL Certificate Failed
I got it to work. I had to use both the -C and -K command lines when running ./installfog.sh
./installfog.sh -C -K