Posts made by plegrand

plegrand

I think these errors are consistent with when I was updating :

[Tue Oct 13 15:19:45.400239 2020] [proxy_fcgi:error] [pid 18237] [client 192.168.39.202:59804] AH01067: Failed to read FastCGI header
[Tue Oct 13 15:19:45.400269 2020] [proxy_fcgi:error] [pid 18237] (104)Connection reset by peer: [client 192.168.39.202:59804] AH01075: Error dispatching request to :
[Tue Oct 13 15:19:45.424226 2020] [proxy:error] [pid 23571] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:19:45.424272 2020] [proxy_fcgi:error] [pid 23571] [client 192.168.39.202:59805] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:19:45.426384 2020] [proxy:error] [pid 18238] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:19:45.426412 2020] [proxy_fcgi:error] [pid 18238] [client 192.168.39.202:59806] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:19:45.447120 2020] [mpm_prefork:notice] [pid 707] AH00169: caught SIGTERM, shutting down
[Tue Oct 13 15:20:27.916679 2020] [mpm_prefork:notice] [pid 13584] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1d configured -- resuming normal operations
[Tue Oct 13 15:20:27.916729 2020] [core:notice] [pid 13584] AH00094: Command line: '/usr/sbin/apache2'
[Tue Oct 13 15:20:27.993053 2020] [proxy:error] [pid 13585] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:27.993095 2020] [proxy_fcgi:error] [pid 13585] [client 192.168.39.201:59662] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.043766 2020] [proxy:error] [pid 13586] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.043797 2020] [proxy_fcgi:error] [pid 13586] [client 192.168.39.144:49574] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.092625 2020] [proxy:error] [pid 13587] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.092655 2020] [proxy_fcgi:error] [pid 13587] [client 192.168.39.144:49575] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.095287 2020] [proxy:error] [pid 13588] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.095315 2020] [proxy_fcgi:error] [pid 13588] [client 192.168.39.144:49576] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.097553 2020] [proxy:error] [pid 13589] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.097580 2020] [proxy_fcgi:error] [pid 13589] [client 192.168.39.201:59663] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.100708 2020] [proxy:error] [pid 13585] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.100727 2020] [proxy_fcgi:error] [pid 13585] [client 192.168.39.201:59664] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.119168 2020] [proxy:error] [pid 13586] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.119194 2020] [proxy_fcgi:error] [pid 13586] [client 192.168.39.83:50776] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.152719 2020] [proxy:error] [pid 13587] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.152734 2020] [proxy_fcgi:error] [pid 13587] [client 192.168.39.51:51557] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.167072 2020] [proxy:error] [pid 13588] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.167087 2020] [proxy_fcgi:error] [pid 13588] [client 192.168.39.83:50777] AH01079: failed to make connection to backend: 127.0.0.1
[Tue Oct 13 15:20:28.170549 2020] [proxy:error] [pid 13589] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed
[Tue Oct 13 15:20:28.170563 2020] [proxy_fcgi:error] [pid 13589] [client 192.168.39.83:50778] AH01079: failed to make connection to backend: 127.0.0.1

plegrand

Hello,
i just updated my fog server with 1.5.9 version on debian .
Everything seems to works fine . Just an error message at the end during “Ensuring node username and passwords match…”

The following error was encountered while trying to retrieve the URL: http://192.168.39.243/fog/maintenance/create_update_node.php

    Connection to 192.168.39.243 failed.

The system returned: (110) Connection timed out

The remote host or network may be down. Please try the request again.

Is there a way to know what the installer try to do during this step ?

When i do a “wget http://192.168.39.243/fog/maintenance/create_update_node.php” on the server it works fine

Thanks for your help
Pascal

plegrand

May be a bug fixed here :
https://github.com/FOGProject/fogproject/commit/468bdde623620774407f73763602023bd877ee12

plegrand

@Sebastian-Roth
I made the test with a fresh install of the latest client with same problems.

plegrand

I’m using FOG 1.5.8 on Debian stable.
I can see on log a lot of this kind of error message :

systemctl status FOGSnapinReplicator.service 
● FOGSnapinReplicator.service - FOGSnapinReplicator
   Loaded: loaded (/lib/systemd/system/FOGSnapinReplicator.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2020-09-28 08:06:54 CEST; 764ms ago
  Process: 3609 ExecStart=/usr/bin/php env /opt/fog/service/FOGSnapinReplicator/FOGSnapinReplicator (code=exited, status=1/FAILURE)
 Main PID: 3609 (code=exited, status=1/FAILURE)

Does someone could explain me what happen ?

Thanks for your help

plegrand

@Sebastian-Roth There is nothing in error.log

plegrand

@Sebastian-Roth
I saw that the client load the following url :
http://192.168.39.243/fog/status/getservertime.php
It get the following time : Sep 24, 2020 14:37 pm
In fact the time is 16:37 pm
But on the server :
[root@fog] ~ # date
jeudi 24 septembre 2020, 16:38:44 (UTC+0200)

Is it the problem ?

plegrand

@Sebastian-Roth
My fog server has this ip addresse: 192.168.39.243
The fog client is configured with this ip addresse
I can ping it from the client with adresse ip, short dns name, long dns name.
I can get the file http://192.168.39.243/fog/management/other/ssl/srvpublic.crt from the client and Firefox, edge and curl.

But i see these errors in fog.log

24/09/2020 10:20:52 Client-Info Version: 0.11.19
 24/09/2020 10:20:52 Client-Info OS:      Windows
 24/09/2020 10:20:52 Middleware::Authentication Waiting for authentication timeout to pass
 24/09/2020 10:21:49 Middleware::Communication Download: http://192.168.39.243/fog/management/other/ssl/srvpublic.crt
 24/09/2020 10:22:52 Middleware::Communication ERROR: Could not download file
 24/09/2020 10:22:52 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.

24/09/2020 10:24:52 Client-Info Version: 0.11.19
24/09/2020 10:24:52 Client-Info OS:      Windows
24/09/2020 10:24:52 Middleware::Authentication Waiting for authentication timeout to pass
24/09/2020 10:25:49 Middleware::Communication Download: http://192.168.39.243/fog/management/other/ssl/srvpublic.crt
24/09/2020 10:26:52 Middleware::Communication ERROR: Could not download file
24/09/2020 10:26:52 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.

24/09/2020 10:26:52 Middleware::Communication URL: http://192.168.39.243/fog/management/index.php?sub=requestClientInfo&configure&newService&json
24/09/2020 10:27:55 Middleware::Communication ERROR: Could not contact FOG server
24/09/2020 10:27:55 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.
24/09/2020 10:27:55 Middleware::Response Success
24/09/2020 10:27:55 Service ERROR: Invalid promptTime, using default
24/09/2020 10:27:55 Middleware::Communication URL: http://192.168.39.243/fog/management/index.php?sub=requestClientInfo&mac=60:F2:62:1A:2B:84|62:F2:62:1A:2B:83|60:F2:62:1A:2B:83|34:48:ED:02:2F:CF|60:F2:62:1A:2B:87&newService&json
24/09/2020 10:28:58 Middleware::Communication ERROR: Could not contact FOG server
24/09/2020 10:28:58 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.
24/09/2020 10:28:58 Middleware::Response Success
24/09/2020 10:28:58 Middleware::Communication URL: http://192.168.39.243/fog/service/getversion.php?clientver&newService&json
24/09/2020 10:30:01 Service ERROR: Unable to get cycle data
24/09/2020 10:30:01 Service ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.
24/09/2020 10:30:01 Middleware::Response Success
24/09/2020 10:30:01 Service Initializing modules

The time/date are corrects on client and server

I’m lost !!

plegrand

@Sebastian-Roth No it’s on http only

plegrand

Hello,
I’ve got a problem during client installation.
My server FOG has this address IP : 192.168.39.243
From the client i can ping the server from IP address
During installation, it stucks on “pinning server” then fail with “cannot install certificate”.

This problem occurs only when i try to use IP address, it works fine if i use the short dns name.

I’m using Fog server 1.5.8
Fog client 0.11.19
Windows 10 1909

Have you got an explanation ?
Thanks for your help.

Pascal

plegrand

Thanks for your help!!
it works !!

plegrand

Hello,
i’m using FOG 1.5.8

Kernel:
bzImage Version: 4.19.101
bzImage32 Version: 4.19.101

On a DELL Precision 3541 with windows 10 already installed.

If i try different task (inventory, deploy, capture) i’ve got this error message:

cannot find disk on system (getHardDisk)

Here is information from the bios:

SATA operation: RAID ON
M.2 PCIe SSD-0 : 512 GB BTHP938501NK512C

After a debug task, the lsblk command return nothing

Does someone could help me to solve this problem ?
Thank you

plegrand

@Sebastian-Roth
Yes absolutely, with the php updates that went with it. I guess the problem came from there?

plegrand

@Sebastian-Roth

Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
4.19.0-8-amd64

Lors de la mise à jour de Fog 1.5.7 vers 1.5.8 j’ai eu dans un premier temps ce message :

To improve the overall security the installer will create an
unpriviledged database user account for FOG's database access.
Please provide the database *root* user password. Be asured
that this password will only be used while the FOG installer
is running and won't be stored anywhere:

J’ai donc renseigné le mot de passe root
Suite à ça j’ai eu ce message :

The current fogstorage database password does not meet high
 security standards. We will generate a new password and update
 all the settings on this FOG server for you. Please take note
 of the following credentials that you need to manually update
 on all your storage nodes' /opt/fog/.fogsettings configuration
 files and re-run (!) the FOG installer:
 snmysqluser='fogstorage'
 snmysqlpass='Qsz+9uL1GcKZrL3ef8D1'

 Press [Enter] to proceed after you noted down the credentials.

J’ai donc appuyé sur enter et à ce moment j’ai eu un message d’erreur du type :

stopping web services................Failed!

A vrai dire je ne suis pas tout à fait sur du “stopping”
J’ai tout de même suivi la procédure (modifier /opt/fog/.fogsettings puis relancer l’installer)
Lorsque j’ai relancé l’installer j’ai eu de nouveau les mêmes messages (mot de passe root puis modification de /opt/fog/.fogsettings)
C’est ici que je parle de boucle dans la mesure ou à chaque fois que je lancais l’installer je devais tout recommencer.

A la lecture de ce post :
https://forums.fogproject.org/topic/14279/upgrade-debian-9-to-debian-10-fog-1-5-7-and-fog-1-5-8
Le problème ressemblait au miens, j’ai donc suivi les conseils de ce post et depuis tout fonctionne correctement.

plegrand

@Sebastian-Roth Bonjour,
je crois que tu parles français. Est-ce possible de t’expliquer ça en français ?

plegrand

Everything seems to works now. The problem was the same than this :
https://forums.fogproject.org/topic/14279/upgrade-debian-9-to-debian-10-fog-1-5-7-and-fog-1-5-8

plegrand

Hello,
i’ve got some problem to upgrade fog to 1.5.8 i’ve got a kind of loop :

To improve the overall security the installer will create an
unpriviledged database user account for FOG's database access.
Please provide the database *root* user password. Be asured
that this password will only be used while the FOG installer
is running and won't be stored anywhere:

I enter a password for this root user
then :

The current fogstorage database password does not meet high
 security standards. We will generate a new password and update
 all the settings on this FOG server for you. Please take note
 of the following credentials that you need to manually update
 on all your storage nodes' /opt/fog/.fogsettings configuration
 files and re-run (!) the FOG installer:
 snmysqluser='fogstorage'
 snmysqlpass='Qsz+9uL1GcKZrL3ef8D1'

 Press [Enter] to proceed after you noted down the credentials.

And again the same, endless
Could you help me ?

plegrand

@george1421
It seems yes

plegrand

@plegrand
Everything seems work fine and i’ve no more error in log files.