Backing up database.........................................failed
-
Hello
For information :
Debian Stable
Fog svn 5273
The server is behind a proxy but since the beginning and it worked fine
wget is well configured with http_proxy and https_proxy
it failed only to get the local mysql dump@Sebastian-Roth said:
Backing up the database is done via sending a HTTP request to the FOG server using wget. Usually people see this failing if their entire web interface is crooked. From what I seam to read between the lines in your post you are still able to access the web interface, right?
Yes.
Please try downloading the SQL export dump from a client PC within you network using this URL http://x.x.x.x/fog/management/export.php?type=sqldump (where x.x.x.x is the IP address of your FOG server)
It works fine i can get the mysql dump without problem
Strangely in /var/log/apache2/error.log, i’ve got this line "Enter password: "Do you see any errors in the browser or in the apache error log on your FOG server?
Or you can skip the database backup. See my post here on how to do this: https://forums.fogproject.org/topic/5993/rev-4201-blank-page-when-trying-to-install-update-database-schema/38
Thanks for your help
@Tom-Elliott said in Backing up database…failed:
@plegrand Do you have a mysql password?
No, during first installation the installer didnt “put” password
-
@plegrand Do you have a mysql password?
-
No, during first installation the installer didnt “put” password
-
@plegrand can you update and try again?
I just added a checker to only pass the password if the password field has any real viable data.
-
@george1421 I found a solution adding this line in my .wgetrc
no_proxy=localhost,127.0.0.0/8,192.168.39.243my .wgetrc become :
http_proxy = http://my.cache.fr:3128/
https_proxy = http://my.cache.fr:3128/
use_proxy = on
no_proxy=localhost,127.0.0.0/8,192.168.39.243But it stay very strange because i didn’t have this problem before
-
@Tom-Elliott i remove my wgetrc config ?
-
No, I didn’t know you had proxy.
Backing up database has only been in for the last 50 or 100 commits, so my guess is this was always a problem, but you didn’t know about it until i actually added backup code to the installer.
-
@Tom-Elliott Then i can confirm that it’s a proxy setting.
With your las commit without the wgetrc configuration it failed again.
I have to add this line to make it works :
no_proxy=localhost,127.0.0.0/8,192.168.39.243Then it works fine with this wget configuration :
.wgetrc
http_proxy = http://my.cache.fr:3128/
https_proxy = http://my.cache.fr:3128/
use_proxy = on
no_proxy=localhost,127.0.0.0/8,192.168.39.243 -
The reason why I asked about he proxy server is I ran into the same problem, documented here: https://forums.fogproject.org/topic/6062/svn-5221-failing-to-install-on-fog-server-using-proxy-server
The line you added to wgetrc may or may not work [no_proxy=localhost,127.0.0.0/8,192.168.39.243]. I ended up exporting those statements in bashrc. It may not matter where the command is put.
This is what I put at the end of the bashrc file.
export http_proxy=http://192.168.1.110:3128
export https_proxy=http://192.168.1.110:3128
export ftp_proxy=http://192.168.1.110:3128
export no_proxy=“192.168.1.88”The issue (not really a problem, just the way it works) is the install scripts uses wget to connect back to the IP address of the FOG server to dump the database data. wget gets a little confused and tries to contact the proxy server to contact the FOG server. At least in my environment this fails causing the backup to fail.
-
@george1421 Same problem here but now it works
thanks for your help -
Great that you worked it out. I think this is pretty normal and actually expected behavior. If you configure wget to use a proxy server it will do so whatever URL you are trying to request!! To exclude some URL (like local ones) is a pretty common configuration. That’s fine!
