FOG Compatibility Test Failed

[Tom Elliott]

@Sebastian-Roth I must add that I do include Raid drivers already.

[techlover28]

@george1421 said:

@techlover28 OK then, If you navigate to your web servers base directory (usually /var/www/html or /var/html) and then go to <www_base_dir>/fog/service/ipxe/ and rename bzImage and bzImage32 to bzImage.old and bzImage32.old

Then run the following commands to download the latest kernels
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32

From there reboot your target device to load in the newest kernels. If something breaks with this target or any other ones, just roll back the changes you made to load the old kernels.

I have tried it (newer version of kernel) today. It says “Network - Fail” along with “Disk - Fail”. Older version of bzImage works with Network therefore as you mentioned, I did the rollback.

[techlover28]

@Sebastian-Roth said:

@techlover28 Sure you can try building your own kernel. This is a great way of diving into the details and learning how things work. I’d recommend the second article (https://wiki.fogproject.org/wiki/index.php/Build_TomElliott_Kernel) because you need to download firmware stuff!

I am not exactly sure from which end you might better start off. Either take Tom’s kernel config (see in the wiki article) and start adding RAID drivers or start with your own custom kernel config and try to add the right things to make it work with our init.xz (this might take a lot of trail and error till you get this booted I guess).

As per Tom, Trunk supports the new RAID controllers as well. Working with kernel compilation seems like a right thing to do but may take some time to get accomplished and it could also end up with restarting from scratch, considering my limited knowledge.

I am thinking of upgrading to Trunk as I have better chances with that.

[techlover28]

@Tom-Elliott Thank you for your response!

I will upgrade to Trunk today.

[techlover28]

@techlover28 said:

@Tom-Elliott Thank you for your response!

I will upgrade to Trunk today.

I am still trying to upgrade to Trunk. Have been facing few issues. Some of them have been resolved (which were related to repository). Now I am getting stuck at a place where it says " Backing up database…Failed! ".

After upgrade attempt (and getting above failure on screen), I loose the GUI access to FOG management and get the error mentioned below:

Before upgrade-

==================================================
wget http://192.168.1.1/fog/management/export.php?type=sqldump

–2016-01-29 14:05:51-- http://192.168.1.1/fog/management/export.php?type=sqldump
Connecting to 192.168.1.1:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 0 [text/html]
Saving to: “export.php?type=sqldump.1”

[ <=> ] 0 --.-K/s in 0s
2016-01-29 14:05:51 (0.00 B/s) - “export.php?type=sqldump.1” saved [0/0]

After upgrade attempt-

==================================================
wget http://192.168.1.1/fog/management/export.php?type=sqldump

–2016-01-29 14:01:36-- http://192.168.1.1/fog/management/export.php?type=sqldump
Connecting to 192.168.1.1:80… connected.
HTTP request sent, awaiting response… 500 Internal Server Error
2016-01-29 14:01:36 ERROR 500: Internal Server Error.

I have found few existing threads having the same issue. I am trying to resolve this problem as soon as I can.

https://forums.fogproject.org/topic/6097/backing-up-database-failed/
https://forums.fogproject.org/topic/5993/rev-4201-blank-page-when-trying-to-install-update-database-schema/
https://forums.fogproject.org/topic/5972/rev-5020-upgrade-error

[Sebastian Roth]

See what you have in your apache error log when wget fails. Try google to find out where the apache error log is on your system (by the way, is it Debian/CentOS/Fedora/Arch??). Post the error message here if you can’t find a solution yourself.

[techlover28]

@Sebastian-Roth said:

See what you have in your apache error log when wget fails. Try google to find out where the apache error log is on your system (by the way, is it Debian/CentOS/Fedora/Arch??). Post the error message here if you can’t find a solution yourself.

I am re-upgrading the server. I was not able to find any logs anywhere in the system when upgrade failed last time. I will check the apache logs (after running the wget command) once upgrade is finished (till error).

I am installing FOG on Cent OS 6.7.

[techlover28]

Not sure what happened but now it is not even reaching to the point where it reached earlier.

It stucks here-

Downloading inits, kernels, and the fog client…Failed!

I found the logs in “error_logs” directory, which shows below:

Stopping FOGMulticastManager: [FAILED]
Stopping FOGImageReplicator: [FAILED]
…/lib/common/functions.sh: line 717: /etc/rc.d/init.d/FOGSnapinReplicator: No such file or directory
Stopping FOGTaskScheduler: [FAILED]
…/lib/common/functions.sh: line 717: /etc/rc.d/init.d/FOGPingHosts: No such file or directory
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
mysqld (pid 6886) is running…
Stopping httpd: [ OK ]
Stopping php-fpm: [ OK ]

[techlover28]

I have re-installed and re-setup the FOG 1.2.0 again. I have the GUI and mysql working.

I have been trying to find out if I have all necessary RPMs, configurations etc. before I upgrade to Trunk.

I have followed the installation.txt file and updated my server. I did it last time as well. Should there be something else which I should take care before re-attempting the upgrade to Trunk?

[Sebastian Roth]

@techlover28 said:

Downloading inits, kernels, and the fog client…Failed!

Are you behind a proxy server or connected directly to the internet?

[techlover28]

@Sebastian-Roth said:

Are you behind a proxy server or connected directly to the internet?

As per feedback from network team, I am connected directly to the internet.

I passed the below section in my first attempt and did not get this error.

Downloading inits, kernels, and the fog client…Failed!

In the first attempt I got below error:

Backing up database…Failed!
https://forums.fogproject.org/topic/6551/fog-compatibility-test-failed/14

[george1421]

I agree here, if your fog server is behind a proxy server (i.e. you require to use a proxy server for internet access) there are some changes you need to make to allow this.

[techlover28]

@george1421 said:

I agree here, if your fog server is behind a proxy server (i.e. you require to use a proxy server for internet access) there are some changes you need to make to allow this.

I am connected to the internet directly.

[george1421]

@techlover28 Sorry I should have refreshed before I posted. It almost appears that your fog server can’t resolve IP addresses according to the error. Did your network team just directly connect you or has it alway been this way? It appears that dns resolution is not setup??

[Sebastian Roth]

Well then try (test-)downloading the kernel by hand and see what happens: curl -ko "/tmp/bzImage" https://fogproject.org/kernels/bzImage

[george1421]

@Sebastian-Roth said:

Well then try (test-)downloading the kernel by hand and see what happens: curl -ko "/tmp/bzImage" https://fogproject.org/kernels/bzImage

Actually this is what I was going to have the OP do to update the kernel without having to upgrade to the trunk (even though the trunk is a good choice)

[techlover28]

@george1421 said:

@techlover28 Sorry I should have refreshed before I posted. It almost appears that your fog server can’t resolve IP addresses according to the error. Did your network team just directly connect you or has it alway been this way? It appears that dns resolution is not setup??

No worries. I have an internal IP assigned to the server with a default gateway IP. It has always been this way. I can directly download/install the RPMs from atomic yum repositories. I am able to get the IP when I try to ping google or fogproject.org.

ping google.com
PING google.com (216.58.197.78) 56(84) bytes of data.
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=1 ttl=57 time=42.3 ms
^C
— google.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 976ms
rtt min/avg/max/mdev = 42.327/42.327/42.327/0.000 ms

ping forums.fogproject.org
PING fogproject.org (162.213.199.177) 56(84) bytes of data.
^C
— fogproject.org ping statistics —
7 packets transmitted, 0 received, 100% packet loss, time 6051ms

[george1421]

@techlover28 from the command prompt on the fog server can you successfully execute the curl command Sebastian posted below? That will test the innerworkings of the download processes. Its possible that pings are allowed but not downloads in your company firewall. The curl command will test how well the downloads work.

BTW: The target of that curl download command IS the latest 64 bit kernel. All you need to do is rename your current kernel and then move this one into place to upgrade to the latest kernel without upgrading FOG.

[techlover28]

@george1421 said:

Actually this is what I was going to have the OP do to update the kernel without having to upgrade to the trunk (even though the trunk is a good choice)

@Sebastian-Roth said:

Well then try (test-)downloading the kernel by hand and see what happens: curl -ko "/tmp/bzImage" https://fogproject.org/kernels/bzImage

Does above mean similar to below post?

@george1421 said:

@techlover28 OK then, If you navigate to your web servers base directory (usually /var/www/html or /var/html) and then go to <www_base_dir>/fog/service/ipxe/ and rename bzImage and bzImage32 to bzImage.old and bzImage32.old

Then run the following commands to download the latest kernels
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32

From there reboot your target device to load in the newest kernels. If something breaks with this target or any other ones, just roll back the changes you made to load the old kernels.

If yes, then it didn’t work last time when I tried. I can try again though.

@techlover28 said:

I have tried it (newer version of kernel) today. It says “Network - Fail” along with “Disk - Fail”. Older version of bzImage works with Network therefore as you mentioned, I did the rollback.

[george1421]

@techlover28 Yes that is the same. That is sad the newer kernels work not good. Maybe if you make a nice donation to the @Developers they would add your network driver and raid card to the FOG boot kernels

It looks like you may have to build your own kernel to get these specific drivers to work