Can you upload your fog install log? It is located here:
[CODE]/var/log/foginstall.log[/CODE]

I got the same issue - but unfortunately, creating a new image and pulling it from the client does not work either. It is just going through the check stuff and reboots the client.

System Ubuntu 12.04
FOG 1.2.0

Still the same error ;(
root@v1fog:/images# service nfs-kernel-server status
nfsd running
root@v1fog:/images# ufw status
Status: inactive
root@v1fog:/images#

Update: This is resolved.

There were 2 issues:

I had the wrong mysql username/password in Config.class.php on the nodes. During the node install, I had given it a generic root account but found out earlier today that I specifically needed the username/password for storage nodes, which I found under the storage node section in settings on the main server.

Second: I realized the nodes couldn’t even connect to the main database, and I was able to narrow that down to the my.cnf file on the main server. It had the bind address set to 127.0.0.1. I commented that line out, restarted mysql, and then they were able to connect.

After I verified everything was talking correctly, I restarted the FOGImageReplicator service and everything instantly started copying. The fogreplicator.log file on Node1 shows Group #2 as I expected it might.

This also fixed an issue that I never really cared about enough to fix… On the main fog dashboard page under disk information, It always told me “Failed to connect to” when I selected Node1 or Node2. that’s fixed now and I can see the disk usage for them.

Thanks for the help!

Turns out the problem is with the dc7900 and ipxe. It looks like according to [url]http://www.fogproject.org/wiki/index.php/WorkingDevices[/url] page that there is a known problem with the dc7900. We have a high percentage of those around here yet, so I’m just going to back rev to .32 until I can get the ipxe thing figured out on the dc7900. The other site had dc5800s and Optiplex980s which both worked fine with 1.2.0 I was able to get the 800 G1 to go fine with the 3.8.8 kernel.

Is there anything showing in your apache2 error log when this client tries to connect?

Stop the fog service on the client
[CODE]net stop “FOG Service”[/CODE]
Follow the apache2 error log via a terminal to the fog server:
[CODE]tail -f /var/log/apache2/error.log[/CODE]
Start the FOG service:
[CODE]net start “FOG Service”[/CODE]
Watch the error log, if any entries show up, please post them here.

Sorry, meant to get back to you sooner. The kkpxe didn’t change the situation. I just upgraded to 1.2.0 today and noticed it set the menu back to the original… so I had to go in and edit the file again. Glad I posted here, made it a lot easier to re-locate it. 🙂

Something with the video chip in these 320s just doesn’t like that bg.png file… I can add a video card to a 320 and it works fine. The built in video appears to be the problem.

Great, thanks again. I saw an older thread about automatically associating the pending MACs with a host, so you don’t have to open each host and click + to add the wireless MAC.

Is that actually possible and/or could you point me in the right direction? Because it seems like it would be a time-saver…

Thanks,
D.L.

It’s OK

[quote=“neilm, post: 37138, member: 24150”]has this been resolved? i checked all settings and can login to ftp with broswer and filezilla. but images stay in /images/dev until manually moved[/quote]

Tom Elliott’s post above fixed it for me. You have to edit /etc/vsftpd.conf and then restart the ftp services.

Separate those VLans and everything should be golden.

I already was. It looks like that worked. I will try to image a new machine now. Thank You!!

as always thanks for the help and quick responses

SVN version 2402,
I also check apache log on server and it is not good.[IMG]http://217.113.158.51/files/rzaczek/apachelog.png[/IMG]
Regards

the snapin problem is resolved on rev 2402.

best regards

[FONT=Tahoma][COLOR=#000000]Here are the rights of the directory :[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#000000][CODE]drwxrwxrwx 20 root root 4096 2014-03-17 17:26 images[/CODE][/COLOR][/FONT]
and the sub directories
[CODE]drwxr-xr-x 2 root root 4096 2014-03-17 08:25 7pro32
drwxrwxrwx 2 root root 4096 2011-04-11 15:03 7-pro-32-sysprep-vauban
drwxrwxrwx 2 root root 4096 2011-04-04 12:56 7-pro-64-sysprep-vauban
drwxrwxrwx 2 root root 4096 2012-06-11 15:56 acer-m480
drwxrwxrwx 2 root root 4096 2012-06-11 16:45 admin-lenovo-1577-7-64
drwxrwxrwx 2 root root 4096 2010-02-02 11:49 cdi-acer-veriton-m410
-rw-r–r-- 1 root root 4628810288 2012-04-02 16:08 cdi-dell-optiplex-210L
-rw-r–r-- 1 root root 9685721343 2014-03-17 17:25 dell210Liaca
drwxrwxrwx 2 root root 4096 2013-12-09 17:57 dellcdi
drwxr-xr-x 2 root root 4096 2012-09-17 15:17 dell-optiplex-390
drwxrwxrwx 2 fog root 4096 2014-03-17 17:26 dev
drwxrwxrwx 2 root root 4096 2012-06-25 14:00 h22-acer-m480-32bits
drwxrwxrwx 2 root root 4096 2012-07-02 11:41 h22-acer-veriton-m410
-rw-r–r-- 1 root root 3546020335 2012-06-25 13:57 h22-nec-ml7
drwxrwxrwx 2 root root 4096 2012-11-12 16:24 h27dell390
drwxrwxrwx 2 root root 4096 2013-12-03 19:09 h27dell39001
-rw-r–r-- 1 root root 5333007375 2012-04-16 10:10 h27-dell-gx620
drwxrwxrwx 2 root root 4096 2012-06-11 14:29 lenovo-1577-7-64
-rw-r–r-- 1 root root 2825225992 2011-11-07 17:33 master-h22
-rwxrwxrwx 1 root root 3176718665 2010-07-05 15:36 nec-h22
-rw-r–r-- 1 root root 2575353559 2012-06-25 12:17 nec-ml7
drwxrwxrwx 2 root root 4096 2013-01-28 08:54 opti39032bit
-rw-r–r-- 1 root root 2586100327 2012-06-11 13:10 profs-acer-m410
drwxrwxrwx 2 root root 4096 2012-07-02 16:27 profs-acer-m480
drwxrwxrwx 2 root root 4096 2010-05-03 15:19 salleh27
drwxr-xr-x 5 fog fog 4096 2014-03-13 17:48 systemes-vierges
-rw-r–r-- 1 root root 1744269556 2011-11-02 14:13 xp-corp-sysprep-2011-11-03 [/CODE]

Hi,

Thank’s for reply. Now it’s ok in the multicast.log, but parclone stay on Starting to restore image (-) to device (/dev/sda1).

I don’t understand why in multicast the machine contact the storage node.

In my EMC2 nas, I need to create a fog user with the same uid than the fog server ?

This is by far affecting more than FOG.

Java has been doing a lot of updates recently and whenever you get the ignore and reload it will continue to block java. You need to go under the control panel and set a security exception for your FOG server’s IP.

This feature was actually removed from the newer versions of FOG.