The problem was the client version. (old version: 0.9.12)
I had to install the new one on each computer (0.11.9), then reboot each computer.
Then “reset encrypted data” on the group
Now it works fine.
I thought that once there was a new version on the server the client updated “alone”.
plegrand
@plegrand
Best posts made by plegrand
-
RE: Hostname Changer failed
-
RE: Upgrade to debian 9
@wayne-workman i used " your packages line" and it seems to work.
Then now i have to test pxe boot, capture and deploy !!THanks for your help
-
RE: fog with an existing pxe server
Hello,
in first thank a lot for your answer.
For my test i’m going to work with a virtual machine with only one interface, then forget the “3 networks”
I begin by installing fog like that :
(i use my own dhcp server)Type d’installation : N
IP du serveur FOG : 192.168.39.243
Would you like to setup a router address for the DHCP server? : n
Would you like to setup a DNS address for the DHCP server and client boot image? : n
Would you like to change the default network interface from eth0? : n
Would you like to use the FOG server for DHCP service? n
This version of FOG has internationalization support, would you like to install the additional language packs? nMy own dhcp server is configured like that (it has 192.168.39.247 for ip address):
subnet 192.168.39.0 netmask 255.255.255.0 {
range 192.168.39.40 192.168.39.230;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.39.255;
option routers 192.168.39.254;
next-server 192.168.39.247;
filename “pxelinux.0”;
}
then next server is the dhcp server itselfHere is a part of the PXE configuration (on my own dhcp server. (The dhcp server act as dhcp, tftp and pxe server)
DEFAULT vesamenu.c32
KBDMAP fr.kbd
MENU BACKGROUND splash.jpg
menu color title 1;37;40 #ffffffff #00000000 std
menu color timeout_msg 37;40 #80ffffff #00000000 std
menu color timeout 1;31;40 #ffff0000 #00000000 std
menu color border 30;44 #00000000 #00000000 noneTIMEOUT 300
ALLOWOPTIONS 0
PROMPT 0MENU TITLE MENU
LABEL BootNormal
MENU LABEL Boot local
MENU DEFAULT
COM32 chain.c32
APPEND hd0LABEL Drivers_Universels
MENU LABEL Drivers Universels
KERNEL memdisk
APPEND keeppxe floppy initrd=ghost/universels.imgLABEL hdt
MENU LABEL Hardware Detection Tool
COM32 hdt/hdt.c32
APPEND modules=hdt/modules.pcimap pciids=hdt/pci.idsLABEL memtest
MENU LABEL Memtest86+
LINUX hdt/memtest86±4.20.binMy question is how i could add entry for fog server using ipxe while i’m iusing pxe (pxelinux.0)
Thanks again for your help -
RE: Could Not Mount Image
Hello, i think i’ve got the same problem except i made modification on the web interface :
i didnt want the “images” directory be at the root (/images)
then i copy the images directory into /home/images.Then i modify the image path on the web interface, i thought it would modify the export file also but it seems not.
then i had to modify manualy the export file. Now it works fine.
Could it be the problem ? -
RE: Debian Jessie 8
@need2 now i agree with you : if you accept that mysql root has no password
and if you know that if installer told you to go to http://192.168.39.243/fog it means you have to go to http://192.168.39.243/html/fog.
I know it’s a ridiculous bug of the default installer (without parameters) but it disturbed meany way fog seems to be a great program, the forum is very reactif and it permit me to go on
Then thanks again for your help i appreciate
sorry for my poor english
@Tom Elliot : i will try with --docroot to tell you if it works.
But can you confirm me that the installer without parameters make a mistake between http://192.168.39.243/fog and http://192.168.39.243/html/fog to be sur we are agree ?Thanks again for your help everybody !!
-
RE: Some questions
@Wayne-Workman said:
@plegrand said:
It’s not our dns servers
You don’t have to use them. You can make your own and direct all hosts to use yours.
I install dynamique DNS with bind and it works fine. Thanks again
-
RE: MultiCast very slow
@Wayne-Workman
I just made the test unicast (deploy and not multicast)
It’s a room with 12 stations.
2 stations failed
10 works fine (1.6 GB/min)
i’ll tell you more tomorrow -
RE: samba domain integration
@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !! -
RE: FOG restore only one partition
@Sebastian-Roth May be i could give you access to this machine if it’s usefull ?
Latest posts made by plegrand
-
Snapin group
FOG 1.5.9
Hello, i’ve got a litle problem with group and snapins.
When i assign a snapin to a group if i look again on this group the snapin i just assigned before is not selected.
Am’i wrong with this way to do ?
Thanks for your help -
BAckup Database
Hello,
since an update, I don’t know which one, it is impossible for me to backup database with this command :/usr/bin/mysqldump --allow-keywords -x -v fog > /home/tmp/toto.sql
mysqldump: Got error: 1045: "Access denied for user 'root'@'localhost' (using password: NO)" when trying to connect
It worked before.
Now what is the user and the password to use mysqldump ?Thanks for your help
-
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth
There is always a problem during this operation:Testing internet connection.................................There was no interface with an active internet connection found.
As we are behind proxy, the ping command does not works.
May be it could be possible to test internet connection with curl or wget ?
https://github.com/FOGProject/fogproject/blob/master/lib/common/functions.sh#L386Thanks again
-
RE: Stuck on : "Ensuring node username and passwords match...."
With the good config file for curl
.curlrcproxy = http://blabla.fr:3128/ noproxy=localhost,127.0.0.0/8,192.168.39.243
It works fine.
Just for information, here is what i use :
.wgetrc
http_proxy = http://blabla.fr:3128/ https_proxy = http://blabla.fr:3128/ use_proxy = on no_proxy=localhost,127.0.0.0/8,192.168.39.243
.gitconfig
[http] proxy = http://blabla.fr:3128
.curlrc
proxy = http://blabla.fr:3128/ noproxy = localhost,127.0.0.0/8,192.168.39.243
There is always a problem during this operation:
* Testing internet connection.................................There was no interface with an active internet connection found.
As we are behind proxy, the ping command does not works.
May be it could be possible to test internet connection with curl or wget ?
https://github.com/FOGProject/fogproject/blob/master/lib/common/functions.sh#L386Thanks again
-
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth said in Stuck on : "Ensuring node username and passwords match....":
You can see it’s just a curl request to the FOG webserver to make sure the storage node settings (username/password/IP) in the database are correct.
$ipaddress in this line is the "real ip address of the server, not “localhost” or “127.0.0.1” ?
Thanks for your help
-
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth
Has it always been curl?
I’m behind a proxy and i made this configuration for wget :
http_proxy = http://cache.blabla.fr:3128/
https_proxy = http://cache.blabla.fr:3128/
use_proxy = on
no_proxy=localhost,127.0.0.0/8,192.168.39.243
May be i should make the same configuration for curl ?I just remember that i made an export comand for proxy, then installer use proxy for all actions.
I’ll test tomorrow whithout export command to see.
I’ll tell you -
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth
Is it safe t “re run” the installer to see exactly the good logs ?
Is there other logs to watch except /var/log/apache2/error.log ?Can you tell me what the installer try to do?
A wget request?
with wich url ? -
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth The FOG UI seems to work fine
-
RE: Stuck on : "Ensuring node username and passwords match...."
@Sebastian-Roth said in Stuck on : "Ensuring node username and passwords match....":
dpkg -l | grep php
[root@fog] ~ # dpkg -l | grep php ii libapache2-mod-php7.3 7.3.19-1~deb10u1 amd64 server-side, HTML-embedded scripting language (Apache 2 module) ii php 2:7.3+69 all server-side, HTML-embedded scripting language (default) ii php-cli 2:7.3+69 all command-line interpreter for the PHP scripting language (default) ii php-common 2:69 all Common files for PHP packages ii php-curl 2:7.3+69 all CURL module for PHP [default] ii php-fpm 2:7.3+69 all server-side, HTML-embedded scripting language (FPM-CGI binary) (default) ii php-gettext 1.0.12-0.1 all transitional dummy package for php-php-gettext ii php-mbstring 2:7.3+69 all MBSTRING module for PHP [default] ii php-mysql 2:7.3+69 all MySQL module for PHP [default] ii php-pear 1:1.10.6+submodules+notgz-1.1 all PEAR Base System ii php-php-gettext 1.0.12-0.1 all read gettext MO files directly, without requiring anything other than PHP ii php-xml 2:7.3+69 all DOM, SimpleXML, WDDX, XML, and XSL module for PHP [default] ii php7.3 7.3.19-1~deb10u1 all server-side, HTML-embedded scripting language (metapackage) ii php7.3-bcmath 7.3.19-1~deb10u1 amd64 Bcmath module for PHP ii php7.3-cli 7.3.19-1~deb10u1 amd64 command-line interpreter for the PHP scripting language ii php7.3-common 7.3.19-1~deb10u1 amd64 documentation, examples and common module for PHP ii php7.3-curl 7.3.19-1~deb10u1 amd64 CURL module for PHP ii php7.3-fpm 7.3.19-1~deb10u1 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ii php7.3-gd 7.3.19-1~deb10u1 amd64 GD module for PHP ii php7.3-json 7.3.19-1~deb10u1 amd64 JSON module for PHP ii php7.3-mbstring 7.3.19-1~deb10u1 amd64 MBSTRING module for PHP ii php7.3-mysql 7.3.19-1~deb10u1 amd64 MySQL module for PHP ii php7.3-opcache 7.3.19-1~deb10u1 amd64 Zend OpCache module for PHP ii php7.3-readline 7.3.19-1~deb10u1 amd64 readline module for PHP ii php7.3-xml 7.3.19-1~deb10u1 amd64 DOM, SimpleXML, WDDX, XML, and XSL module for PHP
-
RE: Stuck on : "Ensuring node username and passwords match...."
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