This is a known issue with FOG 0.32.

Open up the tasks.confirm.include.php file and replace all instances of &$tmp to $tmp.

The ISD services is started if that matters and I can force it to start from a command prompt.
Nothing pops up but I’ll take another look at it again today.

Thanks

EDIT: Not sure what the deal was before but I repackaged the snapin exactly like it was before and re-uploaded it with a different name and it’s working exactly like it’s supposed to now

I added correctly [CODE]date.timezone = “Europe/Athens”[/CODE], restarted apache and pc but nothing has changed:
Time here 11:00
in pc:
localtime: 11:00
bios time: 8:00
Log viewer/Schedulerer:
8:00…
I find strange:
time here 11:00
in pc:
localtime: 14:00 (which is wrong)
bios time: 11:00
Log viewer/Schedulerer: 8:00
I thought that Log viewer/Schedulerer: 8:00 was utc but in 2nd case it is not.
With or without [CODE]date.timezone = “Europe/Athens”[/CODE] the above are the same.
In the 1st case I can schedule correctly when I put scheduled tasks in bios time.
Why does this happen? I never had time problems…
Linux is debian 7.5 and fog 1.1.2. With xubuntu 14.04 happens exactly the same. With debian 7.5 with 1.1.1 I did not have any time problems.
Is it something related to fog 1.1.2 or some wrong setting in my pc?

[CODE]# cat /etc/timezone
Europe/Athens

hwclock from util-linux 2.20.1
Using /dev interface to clock.
Last drift adjustment done at 1404124210 seconds after 1969
Last calibration done at 1404124210 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick…
…got clock tick
Time read from Hardware Clock: 2014/06/30 08:42:35
Hw clock time : 2014/06/30 08:42:35 = 1404117755 seconds since 1969
Mon 30 Jun 2014 11:42:35 AM EEST -0.453762 seconds
[/CODE]

Axel12, thanks for pointing out the obvious to me. 🙂 I looked through the log and it turns out I had disabled the Auto Log Out module for the client service. (Evidently, that’s important…) I enabled all modules and, voila! Joined the domain. Thanks for the help.

you could try having a pfsense VM do your routing.

pfsense VM with 2 NICs, one NAT, one internal.
other VMs have internal NICs, pfsense can handle your DHCP easily enough.

I do this with bridged NIC instead of NAT… but might work.

if your serious, drop the wireless and get Ethernet.

On your storagenodes are all settings correct?

In their respective config.php/Config.class.php are they able to connect to the database properly? Are their paths correct on the server? Are the permissions for those paths correct?

Well Congratz lol!

Sorry… Found the problem. The /etc/network/interfaces file had the wrong dns-nameservers configuration so it was not resolving domain names.

Download the latest fog_1.1.2.tar.gz file from sourceforge. This should be fixed in the new one.

Not one you downloaded two day’s ago right when we released, redownload as I’ve updated it.

Edit your /opt/fog/.fogsettings setting the snmysqluser to root, snmysqlpass to the mysqlpass you set at install time (or just two double quotes if you left it blank) and snmysqlhost to localhost.

Just went into .install.sh and changed ignore htmldoc from 0 to 1
It ignored it this time but it did not upgrade fog to 1.1.2

Any idea to deploy a Windows 7 starting at sector 2048 without the system partition ?
I have tried “Other”, “Vista” and “XP” but none is working.

Well that’s weird… I don’t have a .fogsettings file, none the less I changed the fog account password and now my images are being replicated successfully. Thanks again for your help!

Give your VM more resources such as CPU and RAM and you should see an increase in speed.

Thanks, guys. I finally got it working. It was a mess…I must have just started changing things willy-nilly and stopped paying attention to what I was doing.
The export file, as ianabc stated was incorrect. I did:
nano /etc/exports
[SIZE=2]pointed the first line to [/SIZE]fog/images *(ro,sync,no_wdelay,insecure_locks,no_root_sq$
[SIZE=2]and my machines immediately started imaging.[/SIZE]

The funny thing is that yesterday I’m almost certain I had a line in that file pointing to that path. Maybe I didn’t comment out the other one.

Either way, it appears to be working. Hopefully I didn’t change something else somewhere that’s going to drive me nuts!

Thanks!!!

[quote=“Tom Elliott, post: 31568, member: 7271”]The images folder should be with permissions set as:
[code]chmod -R 777 /home/images[/code][/quote]
Thanks!

[quote=“Jaymes Driver, post: 31422, member: 3582”]That part is only required to server multiple subnets, for now focus on getting one of your networks working and look into the ip Helper later. I personally don’t use the ip Helpers. My other co workers set some up to help resolve to WDS and I want to use FOG, so I use DNSmasq to override their settings. I’ve never had an issue, but I realize it’s all about the network structure and the equipment.[/quote]

Thank you, this has worked 🙂

Another idea is to use the hostname… but this also dont work, cause i have to use the FQDN and our domain names are different in every office :/…

When i find any solution to do that with one image i will post it here

Thank you for your answers Tom.

Just remember, any changes you make to have “service” controlled files is just loading a cached version of the needed files at service start time. It has no clue about any changes until after a restart. I wish I could make it work without having to restart, but at least we know how to fix it when you edit these files.