@Tom-Elliott I will try to test it with the old machine again.

@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.

@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

@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

@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.

@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?

@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.

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”

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.

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!

@Tom-Elliott Hi again.
I’ve tested another (smaller) image and all the tests (capture, deploy, fog agent boot start) went ok. So I think it’s strongly related to client computer capabilities. I’m testing with an old HP dc5700 Core2 Duo 2 GB RAM. I guess there won’t be issues on a little newer computer.

@Tom-Elliott Sorry for the delay. Nom client does not have any AV client but windows defender, that I have taken off the scheduler. I’m wondering if it’s something related to any driver. I’m going to apply latest patches and see what happens.

@Joe-Schmitt After a second boot, agent started. I guess it is a difficult issue to track.

@Joe-Schmitt The image is not syspreped. I have optimized disk, and after that agent have started again on boot. But after capturing image once again, problem have risen again, and agent does not start on boot.

@Tom-Elliott I’ve optimized disk and agent have started at boot. So it seems strongly related to system performance. I’m goig to make another capture just to check.

@Tom-Elliott There is no task currently. The task indicated in log file was a capture, which finished ok. After that, fog agent has not started at boot time.

@Tom-Elliott Yes, it was an image capture, and it went ok, but agent has not started at boot time since that.

0_1489580840910_fog.log
Here goes fog.log file. Now its 13:27 here and you will see last time log is about 8:40. I’ve restarted the computer several times since and fog agent has not started due same timeout error.

Server

• FOG Version: 1.3.5-RC14
• OS: Ubuntu 14.05

Client

• Service Version: 0.11.10
• OS: Windows 10

Description

Sometimes Fog Service does not start, and in Events Viewer appears an error with code 7009 about time-out (30000 ms)while connecting with FOGService.
I don’t know if it is actually a bug because perhaps is related to busy slow system.
It could be useful if other people reports the same issue.

@Tom-Elliott Thanks!