Here are those lines:
[CODE] if (ini_get(‘date.timezone’))
date_default_timezone_set(date_default_timezone_get());
else
date_default_timezone_set(‘UTC’);[/CODE]

Bios is set to UTC. Should I change something in the lines above?
[CODE]# hwclock --debug
hwclock from util-linux 2.20.1
Using /dev interface to clock.
Last drift adjustment done at 1404282060 seconds after 1969
Last calibration done at 1404282060 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/07/02 06:47:09
Hw clock time : 2014/07/02 06:47:09 = 1404283629 seconds since 1969
Wed 02 Jul 2014 09:47:09 AM EEST -0.688132 seconds
[/CODE]

PC time is 09:47 now.

I also have [CODE]date.timezone = “Europe/Athens”[/CODE]

Thank you!

Edit: With
[CODE] if (ini_get(‘date.timezone’))
date_default_timezone_set(date_default_timezone_get());
else
date_default_timezone_set(‘localtime’);[/CODE] times are correct (but why are times correct since my hardware clock is set to utc? ). Is this setting correct? Should I leave it like this?

[quote=“Tom Elliott, post: 31923, member: 7271”]svn 1983 should fix this for you.[/quote]
Indeed it does.

Just wanted to make sure that it was known.

Thanks.

[quote=“Jim Holcomb, post: 32006, member: 15162”]Buehler? Anyone? Guys, I have seen multiple posts on here about this issue. Do we have any idea what’s going on, or when a fix might be in order?[/quote]

There are two places you probably need to check.

When you install fog we set a random password for the linux side’s fog user.

This password is then the password that is supposed to be set for Storage Management and your relevant storage node. This can be changed on the linux side with a few commands:
[code]sudo passwd fog[/code]
Enter your password twice and remember it
Log into the FOG GUI and set this username and password in
Storage Management->All Storage Nodes-><YOUR STORAGENODE>->Management User and Management Password.

Then goto:
FOG Configuration (? Icon)->FOG Settings->TFTP Server->FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD and set the same username/password pair.

Then test.

To make absolutely sure it’s not a permissions issue run:
[code]chown -R fog:root /tftpboot
chown -R fog:root /images
chmod -R 777 /images[/code]

Ok, that would be useful. I am just trying to get a few diagnostic and system tools up and running from network boot so we won’t need to be able read/write, but that could definitely come in handy on another project. Thanks for all your help.

Thanks so much for the info! So helpful! Do I follow the same steps to change the domain of an already registered host without imaging it again?

Thanks to everyone for their help and suggestions. I finally found the issue was dealing with the password setting in TFTP_FTP_PASSWORD and Storage management not matching. That was causing the issue with Image not showing properly. I did however, freshly install Fog 1.1.2 on Ubuntu 13.10 and so far so good. Thanks again for all the help everyone.

The files is not moved out of the dev folder and into its own folder. This was not a problem before I moved the /images folder into the /home folder. I have to do some more research tomorrow.

[quote=“Junkhacker, post: 31972, member: 21583”]update to 1.1.2[/quote]

AH okay, planning to do that later this afternoon.
Thanks for answering so many of my questions Junkhacker, its been a lot of help.

Many Thanks Tom

I had this problem when first setting up my server and I recall reading somewhere that when syspreping a machine, getting it ready for an image upload, it cannot be joined to the domain.
It has to be in a workgroup before running sysprep and uploading the image.
Since I started doing that, and making sure I entered my password correctly into FogCrypt, I haven’t had any problems with computers joining the domain.

Is this still true?

That’s a bit of a shame because it was neat to have it at your fingertips, ready to go on any machine, without having to install anything. But I also understand the downside of having to support it, code it into the web UI, etc.

Thanks for the help and for the information,
D.L.

I took the info here

[url]http://www.fogproject.org/wiki/index.php?title=WOL_Forwarding[/url] # WoL_Forwarding

It probably is.

I just realized one of my storage nodes were removed. Problem solved! I would delete the thread but I don’t see the option.

I didn’t realize FOG provided an uninstall guide :O, thanks!

I had this issue when trying to use Ubuntu 14.04 and I used 12.04 instead and have not had any issues since.

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 --debug

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]