Posts made by mageta52

The setup is five hosts hooked up to a switch, and the FOG server hooked up to this switch as well. No other devices, this is on an isolated network.

All hosts are powered off, and I’m powering them on one at a time for registration. First host was able to connect and register with the server. Second host stalled out receiving a DHCP address. I thought it might be a physical connection issue, so I took the cable from the first host, who had connected successfully, and tried with that, still failed. These are all identical systems, I’m not sure why some of them fail to connect while others have no issues?

@Wayne-Workman
Both are disabled. I know it’s not as secure, but I just wanted to take that possibility out of the equation during the testing and setup.

[root@localhost httpd]# service firewalld status
Redirecting to /bin/systemctl status  firewalld.service
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

[root@localhost httpd]# sestatus
SELinux status:                 disabled

@Tom-Elliott

So from the above output, it looks like the Mariadb service is running, and disk space seems to be okay. Where else could the problem be?

@Sebastian-Roth

[root@localhost httpd]# service mysql start
Redirecting to /bin/systemctl start  mysql.service
Failed to start mysql.service: Unit mysql.service failed to load: No such file or directory.

However, on Fedora 23, didn’t Mariadb replace Mysql?

[root@localhost httpd]# service mariadb status -l
Redirecting to /bin/systemctl status  -l mariadb.service
● mariadb.service - MariaDB 10.0 database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2016-04-21 15:22:40 CDT; 17h ago
 Main PID: 9012 (mysqld_safe)
   CGroup: /system.slice/mariadb.service
           ├─9012 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
           └─9126 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock

Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        991M     0  991M   0% /dev
tmpfs          1000M  572K 1000M   1% /dev/shm
tmpfs          1000M  1.8M  998M   1% /run
tmpfs          1000M     0 1000M   0% /sys/fs/cgroup
/dev/sda2        20G  5.5G   13G  31% /
tmpfs          1000M   56K 1000M   1% /tmp
/dev/sda3       9.5G   53M  9.0G   1% /home
/dev/sda1       976M  131M  778M  15% /boot
/dev/sda6       239G   60M  227G   1% /images
tmpfs           200M   16K  200M   1% /run/user/42
tmpfs           200M   24K  200M   1% /run/user/1000
tmpfs           200M   36K  200M   1% /run/user/0

@Wayne-Workman So now there’s a new problem. The initial management page, where you go to update is just blank. Below are the Apache logs

URL reads 192.168.235.52/fog/management/?node=schemaupdater

[Thu Apr 21 15:26:00.631141 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 48
[Thu Apr 21 15:26:00.631544 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 36
[Thu Apr 21 15:26:00.631566 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 48
[Thu Apr 21 15:26:00.631958 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 36
[Thu Apr 21 15:26:00.631979 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 48
[Thu Apr 21 15:26:00.704199 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 36
[Thu Apr 21 15:26:00.704252 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 48
[Thu Apr 21 15:26:00.776411 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::select_db(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 36
[Thu Apr 21 15:26:00.776460 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /var/www/html/fog/lib/db/mysql.class.php on line 48
[Thu Apr 21 15:26:00.776631 2016] [:error] [pid 10057] [client 192.168.235.52:34464] PHP Fatal error:  Call to a member function get() on null in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 8
[root@localhost httpd]#

@Wayne-Workman You’re right, I wasn’t thinking the whole scenario through. I get it now.

After updates are finished I’ll move on with the install and report any issues I run into.

@george1421 Why is it important to set the static IP before installing FOG? I’m still confused about this.

• Internet access is needed to get the FOG files to install, so initially I must be on a subnet that has a gateway to the internet, in my case it’s 192.168.1.0.
• The isolated network I’ll use is going to be 10.0.1.0 /24. If I set my interface to something like 10.0.1.1 I won’t have internet access and cannot even begin to install FOG
• It sounds like what Quazz is saying, is that I can be on the local subnet ( 192.168.1.0 ) get the install done, then statically set the interface to 10.0.1.1 or something else on that isolated subnet, and then FOG will be able to adjust to it accordingly. Is this correct?

@Quazz Excellent, I’ll try this. Using Fedora workstation 23 by the way.

https://wiki.fogproject.org/wiki/index.php/FOG_on_an_Isolated_Network

What is the IP address to be used by this FOG Server? [current address]192.168.1.1
Your server’s current Internet address is displayed. When FOG is installed we will be disconnecting from the Internet and defining our own private IP address. Enter your future static IP private address: 192.168.1.1

So 192.168.1.1 is on a network with internet access? At what point is the address changed to be on the isolated subnet? What config file is edited to do this? With this setup, the management page will be on 192.168.1.1/fog/management, this is not good. It must be on the isolated subnet and I don’t know where to change this after it’s already been set up.

Would you like to use the FOG server for dhcp service? [Y/n] Y
Yes. This allows clients to get IP addresses on our private network and connect to the FOG server.

Where is this set up? Will the FOG installer do it automatically? Or do I have to set up DHCP independently?

Basically, due to requirements in the workplace, the imaging solution cannot touch the production network. FOG will be on 10.0.1.0 /24 with a switch and the clients to be imaged. There will be no DHCP server, or anything else, so the Linux box must do everything.

I found these instructions instead

https://wiki.fogproject.org/wiki/index.php?title=Fedora_23_Server

While I’m not using the server version, it did seem to work. I was able to get to the web GUI and update. I will continue on with the setup and hope that things go smoothly

Following this guide

https://wiki.fogproject.org/wiki/index.php/Configuration_on_Fedora_Workstation

At the part where it says

When it asks, the installer directory should be /images (we pre-made this during the Fedora install)

I get the error error reading information on service mysqld no such file or directory, Failed!

I looked it up and read that Mariadb has replaced mysql. I’m not sure how to progress past this part if mysql won’t work, how do I use Mariadb instead?

systemctl status mariadb.service - says it’s running, it’s installed, but I don’t know what I’m supposed to do to get it to work with FOG.