Getting hung up on mysql install on Fedora 23

[mageta52]

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.

[mageta52]

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

[Wayne Workman]

@mageta52 I wrote both of these articles, actually. The first one you posted was my first round with FOG, in February of 2015. I had a pretty rough time and was still pretty green to Linux.

I left a note at the top of the article suggesting to follow the newer tutorials.

[mageta52]

@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]#

[Sebastian Roth]

@mageta52 Probably your mysql DB is not properly started. service mysql status? Maybe your disk is full. df -h? Try starting the DB service mysql start

[mageta52]

@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

[Tom Elliott]

Yes, use whatever service it is that handles your database.

[mageta52]

@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?

[Wayne Workman]

@mageta52 SELinux. Also, on Fedora, firewall is ON by default. instructions for these are in those tutorials. -and they are not the same for 21 and 23.

[mageta52]

@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

[Wayne Workman]

@mageta52 if you go to where you put your FOG Trunk install files, go into bin/error_logs/ you will see some files in there, named fog_error_xxxx.log

The xxxx should be the revision number your on. Can you supply us with that file?

[Tom Elliott]

Remoted in. Found an error in the schema-page and fixed it. THen found that the DB connections weren’t operating properly and fixed that. All is updated in the codebase too.