@Tom-Elliott
So no problem to upgrade from 1.5.9.111 (dev-branch) to 1.5.9.235(dev-branch) ?
Thanks
Posts made by plegrand
-
RE: changelog
-
changelog
Hello,
I am currently using FOG version 1.5.9.111 (dev-branch).
It seems that the last version of “dev-branch” is 1.5.9.235.On github I don’t see the changelog concerning this version.
Can I upgrade from 1.5.9.111 to 1.5.9.235 without any problem?
They are minor corrections?
Thanks for your help.
Pascal -
RE: reset encryption data
When I click this button, if I leave FOG and go back to the same host, the button is displayed again.
But it seemed to me that once I had clicked on this button, it was not supposed to be displayed again for the same host -
reset encryption data
Hello,
I have a little problem on the web interface.
I have to regularly click on the “reset encryption data” button of some hosts and it seems that this action is not remembered.
What could be the problem?
Thanks for your help
Pascal -
RE: Migrate Fog on a new server
@sebastian-roth
I think i 've got the solution :
in fogsettings,storageLocation was ='/images',
then
/etc/exports was :/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
After correcting fogsettings (storageLocation =‘/home/images’,
/etc/exports :/home/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /home/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
and it seems to works
-
RE: Migrate Fog on a new server
@sebastian-roth Hello
The migration is done and I think I followed the documentation.
During a test I encounter the following problem:Could not mount images folder (/bin/fog.download)
Reason: mount: mounting 192.168.39.243:/home/images/ on /images failed: Permission deniedMy images directory is in /home/images.
Do i miss something ? -
Migrate Fog on a new server
Hello,
I’m planning to migrate our fog server to a new machine.
The new machine will be configured in the same way.I had some questions about this migration:
- Is the documentation available at this address still up to date?
[https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG](link url) - The old machine is in version 1.5.9, the new machine, due to installation problems is in version 1.5.9.111.
Is this a problem? Or do I have to upgrade the old machine to 1.5.9.111?
During tests, I noticed some bugs during the installation of the master branch on a stable debian (bullseye):
The installer tries to install the “php-gettext” package, but this package doesn’t exist anymore and you have to install the “php-php-gettext” package
The installer proposes the installation of certificate, if to the first question it is answered no, to the second question, it is not possible to say no to give a server name for the certificate.
So the installation fails with the stable versionWhen switching to the dev-branch version, the problems are the same but the installation finishes normally.
Thanks for your help.
- Is the documentation available at this address still up to date?
-
RE: FOG installation ERROR: "E: Unable to locate package php-gettext"
@utpalgiriarc
You should install these packages:
php-gettext
php-php-gettext
This is what is installed on my server
Use aptitude or apt to install them. -
RE: Upgrade Debian to bullseye
@sebastian-roth
I completed the upgrade without any major problems.
I had to reinstall some php packages that had been removed during the upgrade
(the comparison between the packages installed on the old version and the new one allowed me to reinstall them easily)I also had to re-run installfog.sh because I had the same problem as here:
https://forums.fogproject.org/topic/15254/503-service-unavailable-after-debian-upgrade.Also, unrelated to fog, I had to review the configuration of mariadb and more particularly the authentication mode of the “root@localhost” user.
Indeed the user “root@localhost” was still using authentication with a password, but the new method is to use auth_socket :+-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | mysql_native_password | XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX |
+-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | unix_socket |
this is all I can say
-
Upgrade Debian to bullseye
Hello,
i plan to upgrade my server fog to the latest debian stable “bullseye”.
Can there be compatibility problems ?i see that php go from 7.3 to 7.4.
Do i have to run “installfog.sh” once debian upgraded?
Do i have to modify /opt/fog/.fogsettings :php_ver='7.3' php_verAdds='-7.3'
to
php_ver='7.4' php_verAdds='-7.4'
In .fogsettings, does this line is always usefull :
packages='apache2 bc build-essential cpp curl g++ gawk gcc gzip htmldoc lftp libapache2-mod-php7.3 libc6 libcurl4 m4 mariadb-client mariadb-server net-tools nfs-kernel-server openssh-server php7.3 php7.3-bcmath php7.3-cli php7.3-curl php7.3-fpm php7.3-gd php7.3-json php7.3-mbstring php7.3-mysql php-gettext sysv-rc-conf tar tftpd-hpa tftp-hpa unzip vsftpd wget xinetd zlib1g'
thanks for your help
-
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