FOG Compatibility Test Failed
-
@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
-
[[modules:composer.user_said_in, @george1421, FOG Compatibility Test Failed]]
@techlover28 Yes that is the same. That is sad the newer kernels work not good.
Ah! yes, that is sad.
Maybe if you make a nice donation to the @Developers they would add your network driver and raid card to the FOG boot kernels
I earn $12000 (minus income tax) an year, not ashamed to tell it
. Giving the fact that developers are so much helping and friendly, I was already thinking about giving a donation (not a nice amount but good percentage of my monthly income). Not that I am generous, but thankful for the help and support I have been getting instantly.It looks like you may have to build your own kernel to get these specific drivers to work
I will try it and hope it goes well. If it doesn’t work, I may have to move to some other solution as I am under pressure to finish this task soon.
-
@techlover28 Right now unless the @Developers are willing to add them to the official build, then yes building your own kernel version is the only option. Its not that hard it just take some time to setup the environment. You can get the drivers right from the intel site and then just build them in.
-
Well wget and curl do kind of the same thing but they are still different tools. Have you tried using the command I posted? Because curl is used in the installer script. And I thought it would be a good idea to test exactly what is going on when you run the installer (which failed when downloading kernel/init/fog client).
Adding RAID drivers which are not included in the official kernel source is kind of a huge effort. We would need to keep those updated and tested. How are we going to do this not having that hardware at home.
On the other hand you can just try following the kernel compile wiki articles to build your own custom kernel. We are more than happy to help if you run into a problem with this.The NIC is a bit of a mystery to me. Should be I350-AM4 (quad port) if I got this correct from the mainboard manual. Those should be supported by driver ‘igb’ in old and new kernels! http://cateee.net/lkddb/web-lkddb/IGB.html
-
@Sebastian-Roth said:
Well wget and curl do kind of the same thing but they are still different tools. Have you tried using the command I posted? Because curl is used in the installer script. And I thought it would be a good idea to test exactly what is going on when you run the installer (which failed when downloading kernel/init/fog client).
Yes, I tried the command. It successfully downloaded a bzImage file under /tmp directory with size 6883968 bytes.
The download kernel part failed on the 2nd attempt, first attempt was successful which later got stuck at “Backing up database”.Adding RAID drivers which are not included in the official kernel source is kind of a huge effort. We would need to keep those updated and tested. How are we going to do this not having that hardware at home.
On the other hand you can just try following the kernel compile wiki articles to build your own custom kernel. We are more than happy to help if you run into a problem with this.I will surely give it a try, starting Monday.
The NIC is a bit of a mystery to me. Should be I350-AM4 (quad port) if I got this correct from the mainboard manual. Those should be supported by driver ‘igb’ in old and new kernels! http://cateee.net/lkddb/web-lkddb/IGB.html
Yes, you are correct. Please find more information below:
– ethtool -i eth0
driver: igb
version: 3.2.10-k
firmware-version: 1.4-8
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes -
I had a problem with an older raid controller not being recognized by the centos/RHEL 7 kernel just yesterday. Would this happen to be an older hp smart array controller? Like 2008 or older?
You could try adding these host kernel arguments (in the gui for the host, register it manually if you haven’t already)hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1That might do the trick. These older array controllers are no longer supported by the RHEL kernels, this is where I got that info…
http://serverfault.com/questions/611182/centos-7-x64-and-hp-proliant-dl360-g5-scsi-controller-compatibility -
hi,
I rebuild the FOG server today and was able to move further on upgrade. This time it got stuck here:
====================================================================================
Downloading inits, kernels, and the fog client…OK
Comparing checksums of kernels and inits…Done
Enabling apache and fpm services on boot…OK
Creating SSL CA…OK
Creating SSL Private Key…OK
Creating SSL Certificate…OK
Creating auth pub key and cert…OK
Resetting SSL Permissions…OK
Setting up SSL FOG Server…OK
Restarting Apache2 for fog vhost…OK
Changing permissions on apache log files…OK
Backing up database…OKYou still need to install/update your database schema.
This can be done by opening a web browser and going to:http://192.168.1.1/fog/management
Press [Enter] key when database is updated/installed.
Setting up storage…OK
Setting up and starting DHCP Server…Failed!So I reconfigured the DHCP server and restarted its service manually with success.
Then I commented entire “installfog.sh” script for Trunk except last few lines where it executes all the functions like “configureDHCP” etc.
I executed “installfog.sh” again and it shows me below (everytime below is shown now with the commented “installfog.sh” script):
====================================================================================
- Setting up storage…OK
- Setting up and starting DHCP Server…Skipped
- Setting up and starting TFTP and PXE Servers…/lib/common/functions.sh: line 432: : No such file or directory
OK - Setting up and starting VSFTP Server…/lib/common/functions.sh: line 373: : No such file or directory
OK - Setting up FOG Snapins…OK
- Setting up UDPCast…OK
- Configuring UDPCast…OK
- Building UDPCast…OK
- Installing UDPCast…OK
- Installing FOG System Scripts…Failed!
====================================================================================
-
@techlover28 you commented the lines in installfog.sh that sources the config.sh files as well.
-
@Tom-Elliott said:
@techlover28 you commented the lines in installfog.sh that sources the config.sh files as well.
No, sorry forgot to tell. I started commenting the file after two source files (config.sh and functions.sh) lines.
-
@techlover28 please use the file provided as is. I don’t know what is or isn’t included in all the comments and what not. The only guess I have is from the before commenting part in which I’m guessing you want fog to be the dhcp server?
-
@Tom-Elliott said:
@techlover28 please use the file provided as is. I don’t know what is or isn’t included in all the comments and what not. The only guess I have is from the before commenting part in which I’m guessing you want fog to be the dhcp server?
Yes, I want fog to be dhcp.
I have attached the commented installfog.sh file (trunk). As the upgrade failed at the point where it was setting up DHCP, so just thought if commenting some part of script could avoid complete re-installation.
-
@Tom-Elliott I re-tried installing Trunk from scratch after removing-reinstalling DHCP and VSFTPD RPMs.
It got stuck at same place again (Setting up and starting DHCP Server…Failed!).
Attaching logs for reference. 1_1454387019861_foginstall.log 0_1454387019861_fog_error_6134.log
It is not able to start the DHCP service, therefore I manually configured it and re-executed the installfog.sh script. Script overwrites the configuration and fails.
My manual configuration which let DHCP service to start:
subnet 192.168.1.0 netmask 255.255.255.0 { # option subnet-mask ; range dynamic-bootp 192.168.1.10 192.168.1.100; default-lease-time 21600; max-lease-time 43200; # option domain-name-servers x.x.x.x; # option routers x.x.x.x; filename "undionly.kpxe"; }Script configuration which does NOT let DHCP service to start:
subnet 0.0.0.0 netmask { option subnet-mask ; range dynamic-bootp 0.0.0.253 192.168.1.254; default-lease-time 21600; max-lease-time 43200; # option domain-name-servers x.x.x.x; # option routers x.x.x.x; filename "undionly.kpxe"; } -
@techlover28 I don’t think you have the latest version of trunk. The very, very latest has a more robust dhcp configuration.
And, in the script you posted, I think it fails to start because your interface IP address is not being detected correctly. The address and mask detected are what’s used to calculate the subnet address and start range, exactly the things that are not configured correctly here. Also the subnet-mask option is blank, which would be blank if the netmask couldn’t be calculated.
If you can post the output of
ip addrI will try to come up with a more robust IP detection method that will hopefully solve your problem. -
@Wayne-Workman Thank you for your response.
I am using version 6134 (as written on a cloud on FOG management page). Please let me know where I can download latest Trunk.
Please find the output of said command below (I am using interface em2 for FOG/DHCP management):
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether f8:bc:12:3b:48:3c brd ff:ff:ff:ff:ff:ff inet 10.201.6.176/16 brd 10.201.255.255 scope global em1 inet6 2001:ac9:101:3e9:fabc:12ff:fe3b:483c/64 scope global dynamic valid_lft 2591952sec preferred_lft 604752sec inet6 fe80::fabc:12ff:fe3b:483c/64 scope link valid_lft forever preferred_lft forever 3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether f8:bc:12:3b:48:3d brd ff:ff:ff:ff:ff:ff ** inet 192.168.1.1/24 brd 192.168.1.255 scope global em2** inet6 fe80::fabc:12ff:fe3b:483d/64 scope link valid_lft forever preferred_lft forever 4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether f8:bc:12:3b:48:3e brd ff:ff:ff:ff:ff:ff 5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether f8:bc:12:3b:48:3f brd ff:ff:ff:ff:ff:ff -
@techlover28 we we ask you to upgrade we need you to update the sources as well. If you’re running svn trunk you cd to the trunk directory, for example /opt/svn/trunk then run
svn up cd bin ./installfog.sh -yIf running git for example stored in /opt/fogproject you cd there and run
git pull cd bin ./installfog.sh -y -
@Tom-Elliott I have done the “svn up”, below is the output:
# svn up A .gitignore U lib/common/functions.sh . . U packages/web/lib/fog/group.class.php Updated to revision 4752.But the install.sh script failed again at the same place (Setting up and starting DHCP Server…Failed!).
-
@techlover28 Ok so, you have many interfaces.
What network do you want FOG to serve DHCP to? The 192.168.1.0 network or the 10.201.0.0 network?
-
@Wayne-Workman I am using interface em2 (192.168.1.0) for FOG/DHCP management.
-
@techlover28 So are you specifying the correct interface during the FOG installation? the
em2interface? -
@Wayne-Workman Yes, I am.
* Here are the settings FOG will use: * Base Linux: Redhat * Detected Linux Distribution: CentOS * Server IP Address: 192.168.1.1 * Interface: em2 * Installation Type: Normal Server * Donate: 0 * Internationalization: 0 * Image Storage Location: /images * Using FOG DHCP: Yes * DHCP router Address: * DHCP DNS Address:
