Can't send inventory.. PLS HLP
-
I am very new to Fog, but understand this a fantastic product with a little tweeking.
I am trying to do an initial inventory and upload of an HP Z210 with Win 7 Pro.Steps I have done to this point:
- Installed the Fog Client and win7 cleint on the machine.
- I have setup the image directory in the image management section of the webgui.
- I have rebooted the target machine and IT boots to PXE, gives me the options of what I want to do. I select “Perform Full Host Registration and Inventory”
- It starts the inventory process but displays some errors but passes on to the next step of doing the inventory.
- It displays the computer information and then just keeps scrolling at the trying to upload inventory section with no progress bar or notification that it is doing anything.
Here are a few of the errors that I was able to catch during the process.
- Unable to register the host for the following reason: Inappropriate hparm ioct 0x304.
- unknown bios version Hewelett-Packard/HP-Z210. v01,35, please report, aborting.
I have tried using different kernel’s but haven’t had success…
Any help would be gratefully appreciated!
Pls keep in mind… I am only 2 days in as a FOG user!
-
The Unable to register the host for the following reason: Inappropriate hdparm ioctl 0x304 is not what’s causing the issue.
Also, the unknown bios version Hewlett-Packard/HP-Z210. v01,35 please report, aborting error is not what’s causing the issue.
First, what version of FOG are you using? FOG 0.32 or FOG 0.33b?
In either case all should work if you’re using the latest revision.
The only thing that comes to mind is the kernel doesn’t recognize your network card on the system. Do me a favor and do a compatibility check. If that returns as pass pass for both hard drive and network then it’s probably a configuration issue in the /tftpboot/pxelinux.cfg/default file.
-
I am using Fog_0.32 downloaded it this morning.
How do I do a compatibility check?
I will give another follow up tomorrow. I am currently at another client site.
Thanks for your rapid response!
-
From the fog PXE boot menu, you will see:
Boot from hard disk
Run memtest86
Quick host registration and Inventroy
Perform full host registration and Inventory
Quick Image
Client system information
Debug ModeA. Choose Client System Information
B. Your computer will load another menu and it will look like this:
1.) Reboot
2.) IP Information
3.) Partition Information
4.) Check FOG compatability
5.) Ping a Host
6.) Display MAC Address
7.) Show DMI InformationC. Type 4 and press Enter
-
Fantastic… I will try this tomorrow, once I am back on-site!
-
Just as an FYI the fog client is NOT required to boot the fog PXE menu.
The FOG client is an add on for your image and will allow FOG to register the freshly imaged machine with your AD network, and a few other nifty things.
Some of the options that the client allows you control of are as follows:
Auto Log Out - The Auto Log Out service module will log a user out of a workstation after x minutes of inactivity.
Client Updater - Client updater will keeps your FOG client up to date. (a.k.a. updates configurations when you change it on the GUI.)
Directory Cleaner - The Directory Cleaner module will clean out all files and directories within a parent directory during log off. This module can be useful if you have an application that uses cache that you don’t want to persist between users.
Display Manager - The Display Manager service module will reset a computers display to a fixed setting such as 1024 x 768 on user log in.
Green FOG - Green FOG is a service module that will shutdown / restart the client computers at a set time.
Hostname Changer - The hostname changer is a service module that rename the client’s hostname after imaging. This service also handles Microsoft Active Directory integration.
Host Registration - Host registration is a service module that will register unknown fog clients with the fog server.
Printer Manager - Printer Manager is a service module that will install, remove, and set the default printer on clients.
Snapin Client - The Snapin Service module is used to install snapin files to the client computers.
Task Reboot - The task reboot service will periodically query the fog service to determine is a the client has a task associated with it. If it does and no user is logged in, the host will restart.
User Cleanup - The User Cleanup module will clean out “stale” user account left over from services such as dynamic local user.
User Tracker - The user tracker module will watch for local login/logoff and log them to the fog database.I usually leave all of these options enabled on the client side and then disable those that I don’t need on the GUI.
When you log into your fog management site, the fifth icon from the end is the Fog Configuration page, this is where you can enable, disable, or change the settings your Fog client will use.
and of course, Welcome to FOG!!!
-
Tom the system did reply with a Pass, Pass on the system compatibility test. What would you suggest next?
-
I would recommend taking a look at your /tftpboot/pxelinux.cfg/default file. Make sure that the web= Parts are locating your system properly.
Meaning,
If your file shows the web lines as:
[code]XXX.XXX.XXX.XXX/fog[/code]
Add a trailing slash so it looks like:
[code]XXX.XXX.XXX.XXX/fog/[/code] -
I opened the prelinux.cfg/default file and found web=xxx.xxx.xxx.xxx/fog/ in three locations. Any other suggestions?
-
Here is an image of the file.
[IMG]https://dl.dropboxusercontent.com/u/40787797/IMG_4112.jpg[/IMG] -
Are the HP-Z210 the only machines you have tried to boot? Do you have other machines?
I had some Tangent computers that flat out REFUSED to boot via pxe menu from FOG but always displayed my WDS server.
I had to contact Tangent for a BIOS update that allowed me to properly connect to my fog server.Do you have other units you can test with? It looks like your file is okay. At least it looks like mine does, the ip addresses are different of course, but the contents are the same.
I’d be interested to see if the pxe menu fails on any other make/model.
-
Is this an upgraded system, or brand new install for 0.32?
-
Brand new install… Ubuntu 12.4 lts with 0.32
-
And you’re sure the database is accessible?
-
Jaymes… No I do not have any machines currently I can test. I have 40 z210’s that need imaged and I am hoping to get this solution working. I have heard great things about FOG so I figured I would give it a try.
-
Tom… How can I test that?
-
I checked the /opt/fog/service/etc/config.php and noticed that the SQL username was blank… Should Root be added here?
[IMG]https://dl.dropboxusercontent.com/u/40787797/IMG_2740.jpg[/IMG] -
Yes, but your main file dealing with that needs to match:
/var/www/fog/commons/config.php
-
Your host should be the FOG SERVER IP (not Localhost or 127.0.0.1)
The database should, typically, be called fog
The Username is usually root. If you have a different username, then use that, but typically it’s fog.
Did you set a password for the database? If you did, make sure that is correct as well.
-
Tom
I found in the /var/www/fog/commons/config.php the MYSQL_Host was set to “localhost”. I changed the “localhost” to the IP address of the server and rebooting. I just want to confirm that is the correct change for the MYSQL_Host variable.Thanks