Task error after IP address change

[martyassembly]

@martyassembly

Sorry I should note too that the old IP is 192.168.168.3

[Wayne Workman]

@martyassembly I’ve not seen this particular error before.

What’s in the Apache logs?
Web interface -> FOG Configuration -> Log Viewer -> Apache error logs

Try to create the error again, and then immediately look in the logs. Post relevant ones, look at the timestamps on the entries.

[martyassembly]

@Wayne-Workman

Thanks for the reply, that is the old IP address, the new one which I have configured is 10.10.10.20

Sorry that Apache logs function doesn’t appear to work for me.
I have however attempted to start a new deploy task (which fails) and can’t see anything logged in here;
/var/log/apache2/access.log (ubuntu)

[Tom Elliott]

@martyassembly may seem a bit odd but exactly what error are you getting?

[Tom Elliott]

@Tom-Elliott I see now the error but now what version of fog are you running?

[martyassembly]

@Tom-Elliott I am running Trunk via Git - Running Version: 7853

[Tom Elliott]

@martyassembly would you mind updating?

[martyassembly]

@Tom-Elliott Sure, Running Version: 7923 - same error

[Tom Elliott]

@martyassembly Likely you need to edit the node so it’s got the updated IP address for the node. I’d also confirm that the global settings web_host setting is correct as well.

[martyassembly]

@Tom-Elliott
Ok thanks for the info. Is it possible to clarify in the context of this, what do you mean by ‘node’ ?
I have queried the DB with;

'use fog; SELECT * FROM globalSettings;' | grep HOST

which returned;

1	FOG_TFTP_HOST	Hostname or IP address of the TFTP Server.	10.10.10.20	TFTP Server
19	FOG_WEB_HOST	This setting defines the hostname or ip address of the web server used with fog.	10.10.10.20	Web Server

I have also ensured that the server has been updated with the correct IP address (this is supplied via a DHCP reservation)

ifconfig
eth0      Link encap:Ethernet  HWaddr **:**:**:**:**:**  
          inet addr:10.10.10.20  Bcast:10.10.10.255  Mask:255.255.255.0

Is there somewhere else to check to ensure that I have updated every where I need to?

[Tom Elliott]

The node is under nfsGroupMembers table.

The node is where all the data is retained as far as images.

My guess, the original setup was using the 192 ip address, and this node never got updated.

[martyassembly]

@Tom-Elliott Ah great yes I can see that IP in the table, is there a way to edit that entry in the table via the web-gui or is that something I need to change via mysql? thanks for your help!

[Tom Elliott]

@martyassembly It will be under the GUI.

Go to Storage Management->All Storage Nodes->Your relevant storage node

It should be near the top of the page.

[martyassembly]

@Tom-Elliott
I updated that manually and away we go!

Not sure this will come in handy for anyone but in the interest of keeping all this together

After changing my fogserver IP from 192.168.168.3 to 10.10.10.20 I got this error when attempting to deploy an image to a host;

Failed to create deployment tasking for the following hosts
Type: 8, File: /var/www/html/fog/lib/fog/fogmanagercontroller.class.php, Line: 59, Message: Undefined variable: whereArray, Host: 192.168.168.3, Username: fog

I ran this in terminal of my fog server;

sudo mysql -u root -p
use fog
UPDATE nfsGroupMembers
SET ngmHostname = '10.10.10.20'
WHERE ngmID = 1;

And that has fixed it.

[Wayne Workman]

@martyassembly ngmHostname is just the address for the node. You can set this in the web interface.

[martyassembly]

@Wayne-Workman
Great, any chance you could direct me as to where that is just for future reference…

[Wayne Workman]

@martyassembly Yes.
Web interface -> Storage Management -> [click node name] -> IP Address

That’s it. That field is what is stored into nfsGroupMembers, along with all those other fields.

For normal FOG operations, you don’t need to access CLI or MySQL. Of course it’s great that you can with ease and know how, but you should use the web interface where possible.

[martyassembly]

@Wayne-Workman
Totally if I had worked out where it was then I would of changed it in the web interface as per your note here!

Anyway thanks for your help!