/Default.ipxe.....Operation not supported
-
Package php-5.3.3-48.el6_8.x86_64 already installed and latest version
Nothing to do
[root@fog-server commons]# php -v
PHP 5.3.3 (cli) (built: Aug 11 2016 20:33:53)
Copyright
1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright 1998-2010 Zend Technologies -
Then something else is afoot.
How, exactly, are you install 1.3.0?
-
@Tom-Elliott My production FOG server running Centos 7 v1511 has php at 5.6.28. (just be aware I didn’t do anything crazy with my production server, this is straight out of the box).
-
Should have clarified, just realized this is centos 6.8
-
Doesn’t matter.
How are you installing FOG 1.3.0? I need exact details, such as what you’re using to get the latest and greatest.
See, fog installs a specific repository and uses that repository to install php packages. The fact that you are only ever getting php 5.3 is really off.
You might need to run:
yum -y remove --erase php* -
Was told this was a centos 7 server, in fact this is centos 6.8
-
Yum is only giving me 5.3.3
-
yum install git -y
cd ~
mkdir git
cd git
git clone --depth 1 https://github.com/FOGProject/fogproject.git
cd fogproject/bin
./installfog.sh -
@finvader if you run:
yum -y update php* --enablerepo=remi,remi-php56 -
@Tom-Elliott i now have php 5.5 the command you posted did not work correctly, i wget the the remi repo and it gave me remi-php55. Is that good enough?
-
It should be sure.
-
OK, so the installation using php5.5 worked succesfully, rebooted and tried to download image to a machine and encountered a chain load error and could not boot.
http://172.16.61.17/fog/service/ipxe/boot.php …Input/output errorCould not boot: Input/output error
Chainloading failed, hit ‘s’ for the ipxe shell; reboot in 10 seconds -
This is why I’m not a fan of isolated fog servers. I’m not saying they shouldn’t be around, but there’s too much 'tis for 'tat kind of stuff going on.
Please check your /etc/httpd/conf.d/fog.conf file.
Where it says
ServerName 127.0.0.1change to read asServerName 172.16.61.17and restart httpd with:service httpd restart, Then pxe booting should work properly (hopefully). -
@Tom-Elliott said in /Default.ipxe.....Operation not supported:
isolated fog servers
Now I am here.
Mounting file system fail.
An error has been detectedcould not mount images folder (/bin/fog.download)
args passed:
Reason: mount: mounting 172.16.61.17 ://home/images/ on /images failde: Permissions denied -
@finvader Try restarting nfs service?
service nfs restart -
As of now, I am scraping the fix on this one. some of the files are owned fog.apache, some are root.root, permissions are wrong all over the place.
Going to attempt to put a clean fog install on a new centos 7 machine.
-
Thanks to all of you for your time. I know this is a rough one, at least for me.
So is reinstalled on a fresh centos 7.2 machine and I am getting tftp timeout issues. I installed using my corporate network of 10.x.x.x and I then went in attempted to change over to 172.x.x.x but there seems to be alot of places the IP gets stored. Think I will build a centos 6.8 and just use 1.2.0 as its all contained and doesnt need to talk back to the net. I can at least control the IPs etc, as I am not an expert in linux, php, apache, fog, etc.
I just need a server running asap, then I can go back and build the updated trunk as I do wish to have the new features, but right now we are down hard in our lab.
-
@finvader You are so close I hate to see you back track now. @Wayne-Workman has a script for a portable fog server that will fix all of the bits with the IP address once 1.3.0 is at the right IP address.
But that elusive /tftpboot/default.ipxe contains one of the places where the IP address is hardcoded. There is also in the storage node and then in the FOG configuration setting in the web gui
-
@george1421
Would love to have that script. I am not giving up on this one. Will be at this first thing in the morning. Gotta go home and feed the kids.Let me know how I can get that script you mentioned. I did check the default.ipxe and it was good to go.
V/R