@Tom-Elliott I will try to test it with the old machine again.
Latest posts made by Frank
-
RE: Fog Service does not start due to time-out
-
RE: Error "Undefined index: pass" in capture
@Frank said in Error "Undefined index: pass" in capture:
@Wayne-Workman I’ve followed the troubleshooting guide in case of “Update database…failed” and tftpd passwords are OK.
The error happens in fog.imgcomplete script, in “curl” line. If I do the curl at command prompt I get this:curl -ks --data ‘mac=98:90:96:d8:29:4d&type=up&osid=9’ http://<ip_of_main_fog_server>/fog/service/Post_Stage2.php
Type: 8, File: /var/www/html/fog/lib/fog/fogbase.class.php, Line: 837, Message: Undefined index: pass. Host: <storage_node_ip>, Username:fog
SOLVED!! So simple as a firewall rule! Shame on me.
Fog main server was unable to contact client to port 21.
What had made me crazy was log messages, which seemed to have no sense.
Thanks anyway. -
RE: Error "Undefined index: pass" in capture
@Wayne-Workman I’ve followed the troubleshooting guide in case of “Update database…failed” and tftpd passwords are OK.
The error happens in fog.imgcomplete script, in “curl” line. If I do the curl at command prompt I get this:curl -ks --data ‘mac=98:90:96:d8:29:4d&type=up&osid=9’ http://<ip_of_main_fog_server>/fog/service/Post_Stage2.php
Type: 8, File: /var/www/html/fog/lib/fog/fogbase.class.php, Line: 837, Message: Undefined index: pass. Host: <storage_node_ip>, Username:fog
-
RE: Error "Undefined index: pass" in capture
@Wayne-Workman
After rebooting all implied servers now its working !?!
Let’s left it as another IT mystery. Thanks to all for your help anyway.
Problem can be closed as well.
My God! I was on holiday and I have confused myself! sorry!
Its still failing at the same point -
RE: Error "Undefined index: pass" in capture
@Frank said in Error "Undefined index: pass" in capture:
@Tom-Elliott I’ve monitoring de “database updating” with wireshark and I see an http dialog between fog main server an the client. This seems to go OK, but after clients seems to wait something for half a minute until the error appears.
Does this tell something to you?I’m going to try to be more explicit:
First come a http dialog between fog main server and client.
Then clients waits on “Updating database…” half a minute.
“Failed” is shown.
Another http dialog happens between main server and client. -
RE: Error "Undefined index: pass" in capture
@Tom-Elliott I’ve monitoring de “database updating” with wireshark and I see an http dialog between fog main server an the client. This seems to go OK, but after clients seems to wait something for half a minute until the error appears.
Does this tell something to you? -
RE: Error "Undefined index: pass" in capture
@Tom-Elliott Thanks for your answer.
I guess you mean issues with ftp credentials, but the message points to code. I have not changed any storage settings but I am going to double-check it anyway. -
Error "Undefined index: pass" in capture
Server
- FOG Version: 1.3.5
- OS: Ubuntu 14.04
Client
- Service Version:
- OS: Windows
Description
I’m capturing an image and in one of the last steps, after uploading image, in “Updating database…” phase I get:
“Error returned: Type: 8. File: /var/www/html/lib/fog/fogbase.clas.php. Line: 837. Message: Undefined index: pass.Host: xx.xx.xx.xx. Username: fog” -
RE: Change multicast interface in storage node
Hi @Tom-Elliott, thanks for your answer,
you’re right, it could be a solution. The only thing is it forces to deal with routes to reach storage because it will be on a different network. -
Change multicast interface in storage node
Server
- FOG Version: 1.3.5
- OS: ubuntu 14.04
Client
- Service Version:
- OS: Windows
Description
Hi,
one of our storage nodes has two interfaces; one attached to same lan as main fog server on the other attached to a different private network where clients resides. It is supposed storage repository deploy multicast images to these clients, but I don’t know how to set up this to work.
I’ve tried changing storage node interface, using multicast route daemons as pimd, adding static routes, but nothing works.
Help please!