Lenovo N22 PXE boot issues

[Wayne Workman]

@blue_steel said in Lenovo N22 PXE boot issues:

@george1421 Indeed, the linux user password here

vi /opt/fog/.fogsettings

Was not correct.

Well, that’s arguable. Anything set in the .fogsettings file is the ultimate definition of “correct” on your system. Everything is based around that file. All updates follow that file. It was correct as far as fog was concerned, it’s up to you to adjust that as you need.

[blue_steel]

Ok, so the fog server is up and running and everything is getting images again after the file fix. Except for the N22. Will try different kernels and see if that helps.

[george1421]

@blue_steel If you have the trunk version installed you have the latest kernels. So no need to work in that area.

Now that you are on a current build, can you refresh our memories what is failing with the N22?

[blue_steel]

@george1421

[george1421]

@blue_steel I know I’m asking for this again, but we have a different set of contexts to deal with (trunk version of fog). If you run a compatibility test does both the hard drive and network adapter pass?

[blue_steel]

@george1421

[george1421]

@Developers Any idea on how to debug this. It looks like its failing in the registration script (fog.man.reg) in the FOS Engine.

I’ve looked at the code between
echo " * Starting host registration"
and
[[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n

There is nothing that jumps out at me other than calls to urls like http://${web}service... where if $web doesn’t contain a trailing slash the call would fail.

@blue_steel cal you tail the apache error log and see if its throwing an error when you try to register. If it is an invalid path the apache error log should trap it.

[blue_steel]

@george1421 tried sudo tail -f /var/log/apache2/error.log and nada.

I do now get this

[Wayne Workman]

@george1421 said in Lenovo N22 PXE boot issues:

other than calls to urls like http://${web}service…

If ARP is screwed like ours is, it would fail on a web call to a remote network. Remote being a different broadcast domain where a router must be traversed.

[george1421]

@blue_steel For this specific model I want you to do this .

1. Manually register this host
2. Create a capture or deploy (depending on what your goal is). But when you create the capture/deploy task make sure you tick the check box to create a debug capture/deploy.
3. Then PXE boot the target computer it should drop you to a linux command prompt on the target computer after a few presses of the enter key. (this is the debug console)
4. From the linux command prompt see if you can ping the FOG server.

If you can then I have a few more commands to run. But I want to see of the FOS engine can connect to the fog server with a ping.

[blue_steel]

@george1421 pinging works

[Tom Elliott]

@blue_steel Are you using the fog server with web setup as a DNS Name? For example, the storage node is defined with an IP of say blue_steel.blue_steels_domain.com? If so can you actually ping a system using a hostname itself?

[blue_steel]

@Tom-Elliott Ok, so no dns errors. I can ping fog.myschool.state.us and am getting responses same as when I tried the ip itself

[george1421]

OK so dns and arp work as expected (nuts).

this one has be a bit baffled. How many network adapters are in this device?

If you run the following command in the FOS engine command window, can you post the output here?
. / usr/share/fog/lib/funcs.sh

You need that leading dot space then the full path to the script
Then get a screen grab of set This will let us see what kernel parameters FOG is sending to the FOS engine.

Just for your sanity there is an easier way to interact with the FOS engine. Please do the following.

1. On the fos linux console give root a password with passwd
2. Then pick up the IP address of the fos engine with ip addr show look for eth0 and note its IP address.
3. From a windows computer running putty, you should be able to ssh into the fos engine and copy and paste commands using putty.

[blue_steel]

@george1421 ok so after . / usr/share/fog/lib/funcs.sh, I see nothing. Tried it with output ( >output.txt) and it was blank as well. After typing set, this is what I see.

[Sebastian Roth]

@blue_steel I think there is a typo. Shouldn’t it be . /usr/share/fog/lib/funcs.sh or source /usr/share/fog/lib/funcs.sh? So no space between the first slash and ‘usr’ I’d say.

[george1421]

@Sebastian-Roth Ugh, you are right. Because it looks like the script didn’t run since there are no kernel parameters in the set output. When the script is run it won’t look like it does anything but it does update the environment variables with the current kernel parameters.

[Tom Elliott]

@george1421 it won’t do much even after that. All funcs does is give functions. And set variables. There is no output as far as a script goes

[blue_steel]

Any other scripts I an run or ideas to get some usable info towards troubleshooting?