Newbe Fog installation issue
-
OK, so I went with CentOS, got that installed and installed Fog, however, when I go to the URL to complete the database initialization, I get 'Database connection unavailable. Fog was reinstalled without error but same issue. I provided a password for all requests for one and they are all the same. Not sure how to proceed.
-
@mstumpo Do you happen to know which version you’re trying to install?
1.5.4 should be compatible with Ubuntu 18.04
-
The tests I have going use Ubuntu 18.04 Server, not desktop.
There’s another issue open on github about this very thing I believe: https://github.com/FOGProject/fogproject/issues/261
That guy’s answer was to add theuniverserepository. I guess Ubuntu desktop 18.04 doesn’t come with that repo enabled by default. -
@Wayne-Workman said in Newbe Fog installation issue:
I guess Ubuntu desktop 18.04 doesn’t come with that repo enabled by default.
When I did the testing with Ubuntu 18.04 server I ran into the missing
universesection issue. Not sure about desktop though.@mstumpo said:
OK, so I went with CentOS, got that installed and installed Fog, however, when I go to the URL to complete the database initialization, I get 'Database connection unavailable.
Are you able to connect to the database via console command? Open a terminal on your FOG server and run
mysql -u root -p. If your password is empty simply hit ENTER when it asks for a password.In case you cannot login make sure the database is actually running
sudo systemctl status mysqlIn case you want/need to reset the DB password, find instructions here: https://www.digitalocean.com/community/tutorials/how-to-reset-your-mysql-or-mariadb-root-password
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Sebastian-Roth said in Newbe Fog installation issue:
When I did the testing with Ubuntu 18.04 server I ran into the missing universe section issue. Not sure about desktop though.
That is very strange. I didn’t add any repositories to my 18.04 server. I made sure
vimandgitwere installed, and configured SSL the way my setup needs it, that was it. I do fully update the OS before very test run though. -
@Wayne-Workman said in Newbe Fog installation issue:
I didn’t add any repositories to my 18.04 server.
Maybe this has changed from 18.04 to 18.04.1??? Just a wild guess. Not sure if I am keen to try out. Not sure if there is anything in the setup causing that repository section to be added?!
@mstumpo Sorry we rumble on about such things in your topic. Stopping it now!
-
For UBuntu 18.4.01 LTS + fogproject-1.5.4
Try Run this:
sudo echo "deb http://cz.archive.ubuntu.com/ubuntu bionic main universe" >> /etc/apt/sources.list sudo apt-get update sudo apt-get upgrade sudo tar -xzvf fogproject-1.5.4.tar.gz sudo cd fogproject-1.5.4/bin sudo chmod 777 installfog,sh sudo ./installfog.shNow you are able to installation
-
OK, got Fog installed and can access the console on the local computer. However, when I attempt to PING or open the console from a remote station on the same subnet, I can’t do either. I am assuming it is a firewall issue on the local CentOS station. Not being familiar with Linux, I found the firewall dialog and enabled HTTP and TFTP, neither of which works. In addition, when booting a station to PXE, it gets an IP address, Subnet and gateway IP, but TFTP time out. Any thoughts please?
-
@mstumpo There are two prerequisites that you need to do before installing fog or you will have pains later.
- Disable the linux firewall. For centos the command are
systemctl disable firewalld
systemctl stop firewalld - Set selinux (akin to Windows UAC) to permissive. Edit the file /etc/selinux/config and change
SELINUX=enforcingtoSELINUX=permissive. Then reboot your fog server.
- Disable the linux firewall. For centos the command are
-
@george1421 OK, great. Thanks for the info. I’ll be there later today and will try this.
-
@george1421 OK, those worked and I can now open the Fog console from my laptop. I still can’t get a computer to PXE boot to Fog server. TFTP now does not show timeout, goes right to Intel Agent exiting and boots windows 7.
-
@mstumpo OK so what did you set dhcp options 66 and 67 to?
-
@george1421 66 - 10.0.0.164 (fogserver IP) and 67 (undionly.kpxe).
-
@mstumpo Do you see it download (or appear to load) undionly.kpxe? You should see the fog menu if it does. Understand by default the fog menu has a very short timeout defined. So if you miss the menu, it will attempt to boot from the first hard drive.
Also be aware that undionly.kpxe is for bios based systems, you need a uefi kernel ( ipxe.efi ) if your target computer is uefi based.
-
@george1421 No, I did not. The test station is Windows 7 so the undionly.kpxe should be OK. There is no menu at all. Stations grabs IP information via PXE, TFTP line option goes by quickly and then Intel agent indicates exiting and Windows 7 boots.
-
@mstumpo said in Newbe Fog installation issue:
Intel agent indicates exiting
OK this means that its still not grabbing the file. You should see the iPXE banner as it boots.
From a windows computer, install the tftp client feature. Then from a dos command prompt key in
tftp <fog_server_ip> GET undionly.kpxeI’m only interested in if it is downloading that file or not.Also is the target pxe computer on the same subnet as the FOG server and DHCP server?
-
@george1421 OK, I ran the command. Get Error on server : Permission denied. connect request failed.
Yes, all stations, fog server, DHCP/DNS servers, etc. are on the same subnet. -
@mstumpo Well this is an interesting one.
- Can you ping the fog server from the windows client?
- You may need to temporarily drop the windows firewall to make tftp work since it functions similarly to ftp with a command channel and a data channel back.
- On the fog server key in the following
netstat -an|grep 69. You should see a line that looks like this:
udp 0 0 0.0.0.0:69 0.0.0.0:* -
@george1421 1. Yes. 2. Already disabled and 3. Just as you indicated. Also, tried PXE booting from another station. Same issue, get IP information. TFTP line immediately goes to PXE-M0F: Existing Intel Boot Agent. Selected boot device failed.
-
@mstumpo Ok lets see if we can find the bad actor here. Please follow this process: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
Upload the pcap to the forum and let me review.
