Check this out on the wiki

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#You_must_first_upload_an_image_to_create_a_download_task

Had the same issue myself a while back and this resolved it.

Actually,

I added checks to know when you need the seccomp_sandbox=NO settings. It will not add this item for versions of VSFTPD that do not allow this setting. This is only viable for dev/trunk versions though as I was not aware of this requirement when we first released 1.2.0.

So I got this working in a round about way. I tried to create a new snap in and it gave me an FTP credential error, so I went in and changed my fog user password to match what the configuration showed it should be and now it works. The log viewer also works.

Not sure but maybe the install script is changing the fog password in one place and not another. But I am able to edit snap ins and view my event logs again.

@Wayne-Workman I will keep that in mind and share anything I find.

OK thanks for the info. Doesn’t sound like anything major.

@Lee-Rowlett Thanks. I’ll give it a try!

I restarted the installer several times - the only file, which could not be downloaded was the “FOGService.msi” maybe because I’m downloading behind a proxy. But because I’m cloning ubuntu machines I think I don’t need this file. Otherwise the installer said I can download it with:
wget -O /var/www/html/fog/client/FOGService.msi https://github.com/FOGProject/fog-client/releases/download/0.9.4/FOGService.msi.

The other files like “bzimage,bzimage_32,init.xz,init_32.xz” were downloaded properly.
Still the same Problem. I’m not sure but i think the problem is in the upgraded php5 packeges - if they are upgraded then some of the dependencies to the packages like libonig2 break. I’m not really good in linux and can’t manage it to repair the dependencies.
Did someone have the same problems? Ubuntu 14.04.2 LTS --> apt-get update, upgrade and dist-upgrade.
Thanks

thanks for all the mysql pointers, and that last line worked like a charm.

Spoke to soon.
Wrong data in the columns. Note image ID and image Name. Then it just gets worse.
Capture.JPG

@Tom Elliott: Yes, selinux was disabled and removed via:

sed -i 's/SELINUX=enforcing/SELINUX=disabled/' /etc/sysconfig/selinux sed -i 's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config systemctl stop firewalld systemctl disable firewalld

Thanks for the reply, the process isn’t being interrupted at this point. I’m not relying on WOL at the moment for my needs.

@Jason-Sauders Hi, have you solved your problem ?

Just following up…

The CentOS7 install (from link on previous) seemed pretty straight-forward.
Only change was that I couldn’t rename eth0 from it’s preset ens32, but it’s working anyway.

It’s up and I’m pushing my Win7 image now.

@Wayne-Workman

Er… during your post I was trying to find a better way to describe why was 2 different post, and tried to state better what I wanted. Sorry again for being a bit confusing. Pls read what I wrote now. Anyway, p4p1 thing you suggested is a bit more dangerous than you may wanted 😄 It is like killing a moskito with gunship, full power. It will kill, but… well, a bit more damage than wanted. 🙂

My problem maybe originated that some things can be configured on the web ui, but sometimes config information is kept in different location which is ok if I dont want to reconfigure “all things” after setup. It is hard to be done if I dont know where to make changes (ip addresses are located in many places, but in config files duplicated, cannot be modified from webui. This makes things harder for debugging.

There have been major improvements made in the area of your problem on FOG Trunk. Also, 1.2.0 has known instabilities on Ubuntu 14.04 and newer. These instabilities are also fixed in FOG Trunk.

Here is how you would upgrade to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

If you don’t wish to use FOG Trunk, you’ll have to wait for help from someone more experienced than myself.

@Lasticko http://prntscr.com/7s6p7c see where it says “filename”, change it from undionly.kpxe to undionly.kkpxe

I’m gonna shelve this for a bit we break for vacation today when i get back I will hit this again and get all the logs posted.

Welp, SF is working enough again that I was able to pull down 3.18.5 . 3.0.1 is weirding out though.

@netman86 said:

Running through debug it said something about the partition table in the image being no good.

What’s the exact error? Can you get a screen shot?