Issues during installation on Debian 9.6 stretch
-
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
Unfortunately due to the location, this machine has to go through a proxy to access the internet, is it possible to skip this step in the installation?
Sure you can manipulate the scripts but you could also just run the installer like this:
./installfog.sh --exitFail(actually means “don’t exit on failure”)Strange that “no_proxy” wouldn’t properly work. Have you tested to set to
no_proxy="localhost,127.0.0.1,x.x.x.x"where x.x.x.x is the FOG server IP? -
@thegiantcat can you get an exact screen shot of your /etc/wgetrc file?
If you literally have:
"no_proxy="localhost""This may be a part of the problem.
I’d imagine you should have:
no_proxy=127.0.0.1,localhost,localhost.localdomain,X.X.X.XChange X.X.X.X to whatever your fog IP actually is.
Also, I believe the installer uses curl for binaries and database backups, so I imagine editing the /etc/wgetrc is the wrong approach.
I believe you would edit the file for whom you’re installing at:
~/.curlrcYou could set the same information up in /etc/skel/curlrc too I suppose.
however you’d want lines like:
proxy = <proxyInfoHere> noproxy = localhost,127.0.0.1,localhost.localdomain,127.0.1.1,X.X.X.XYou could also edit your
~/.bashrcTo contain lines like:export http_proxy=<http://proxyInfoHere> export https_proxy=$http_proxy export ftp_proxy=$http_proxy export rsync_proxy=$http_proxy export no_proxy="localhost,127.0.0.1,localhost.localdomain,127.0.1.1,X.X.X.X"If you do add to the .bashrc file, however, you’ll need to close the terminal/logout of the console, and log back in for the changes to take effect.
Hopefully this helps.
In the case you use the bashrc method, please change the X.X.X.X to that of your fog server’s actual IP address, and of course change your http_proxy line to be appropriate. It should include the schema (http{,s}://…) information as well.
-
@Tom-Elliott
My wgetrc file containshttp_proxy = http://172.22.0.102:3128 use_proxy = on no_proxy="localhost",127.0.0.0/8,172.22.0.102I’m not showing a hidden file for curl under ~/ or a config file for curl under /etc/curlrc
I edited my .bashrc to contain the following
export http_proxy=<http://172.22.0.102> export rsync_proxy=$http_proxy export https_proxy=$http_proxy export ftp_proxy=$http_proxy export no_proxy="localhost,127.0.0.1,localhost.localadmin,127.0.0.1,172.22.0.102"Is the syntax for that correct, I re-booted the machine after making the change. However its still looking like no dice. (at this point it actually failed at getting binaries
I made the following changes and it was able to get the binaries but it still failed at backing up the database
export http_proxy="http://172.22.0.102:3128" export rsync_proxy=$http_proxy export https_proxy=$http_proxy export ftp_proxy=$http_proxy export no_proxy="localhost,127.0.0.1,localhost.localadmin,127.0.0.1,172.22.0.102" -
@thegiantcat What’s the installer’s error log look like?
It should show us more information as to why backing up is failing.
I am a little confused too. Is your FOG Server also your PROXY machine?
-
@Tom-Elliott
No,The fog server is seperate from the proxy.
-
@thegiantcat Then why do you have:
export no_proxy="localhost,127.0.0.1,localhost.localadmin,127.0.0.1,172.22.0.102"The 172.22.0.102 (which shows as your proxy), should be your FOG Server’s IP address.
-
@Tom-Elliott
Also here is the error part from the log about when it gets to “Backing up databases”Dec 06 12:23:00 zstsvreefog systemd[1]: Starting The PHP 7.0 FastCGI Process Manager... Dec 06 12:23:00 zstsvreefog systemd[1]: Started The PHP 7.0 FastCGI Process Manager. --2018-12-06 12:23:02-- http://172.24.28.71//fog//maintenance/backup_db.php Connecting to 172.22.0.102:3128... connected. Proxy request sent, awaiting response... 302 Found Could not parse String-Transport-Security header Location: ?node=schema [following] --2018-12-06 12:23:03-- http://172.24.28.71//fog//maintenance/backup_db.php?node=schema Connecting to 172.22.0.102:3128... connected. Proxy request sent, awaiting response... 500 Internal Server Error 2018-12-06 12:23:04 ERROR 500: Internal Server Error.This is before making the requested change after the requested change i get
Dec 06 13:31:46 zstsvreefog systemd[1]: Starting The PHP 7.0 FastCGI Process Manager... Dec 06 13:31:46 zstsvreefog systemd[1]: Started The PHP 7.0 FastCGI Process Manager. --2018-12-06 13:31:48-- http://172.24.28.71//fog//maintenance/backup_db.php Connecting to 172.24.28.71:80... connected. HTTP request sent, awaiting response... 302 Found Could not parse String-Transport-Security header Location: ?node=schema [following] --2018-12-06 13:31:48-- http://172.24.28.71//fog//maintenance/backup_db.php?node=schema Connecting to 172.24.28.71:80... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2018-12-06 13:31:48 ERROR 500: Internal Server Error.The cert on the proxy server is self signed, i assume that its failing because of that, is there a way to start the installation and ignore this? Or a way to add it as a trusted site?
-
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
500 Internal Server Error
Please check your
/var/log/php-fpm/www-error.log! -
@Sebastian-Roth
I do not have the requested directory(php-fpm) under/var/log,
/var/log also doesn’t have an www-error.log
I also checked just to be through and there isn’t a log under
/etc/php/7.0/fpm -
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
is there a way to start the installation and ignore this?
As mentioned earlier, you can simply run the installer like this:
./installfog.sh --exitFail(actually means “don’t exit on failure”) -
@Sebastian-Roth
Thank you so much, I missed it when you originally said that, running it with --exitFail didn’t work, however running it with -X did work. After this I was able to update/install the schema and actually log into the server via the web interface.Additionally I tested booting to the server via PXE and was able too!
