With dhcp-boot=undionly.kkpxe,192.168.1.6 the result was the same.

Posts made by hariskar
-
RE: Boot from SAN device failed
-
RE: Boot from SAN device failed
Yes, I use in Tomato DHCP / DNS Server (LAN) settings: dhcp-boot=undionly.kpxe,192.168.1.6
-
RE: Boot from SAN device failed
Here are some details. I hope they help.
Microsoft Windows 8.1
6.3.9600 Δομή 9600Microsoft Corporation
Manufactor Gigabyte Technology Co., Ltd.
Model Z97P-D3
System type x64-based PC
CPU IntelCore
i5-4590 CPU @ 3.30GHz, 3301 Mhz, 4 cores, 4 λογικοί επεξεργαστές
Έκδοση BIOS/Ημερομηνία American Megatrends Inc. F7, 22/4/2015
Έκδοση SMBIOS 2.7
Λειτουργία BIOS UEFI
BaseBoard Gigabyte Technology Co., Ltd.
RAM 8,00 GB -
RE: Boot from SAN device failed
No the other are older PCs with Win XP. I just mentioned them for you to know that I have done this procedure again.
Thank you Ch3i.
-
Boot from SAN device failed
I added a PC and try to make it boot with fog, but I get this message:
Boot from SAN device 0X80 failed: Operation cancelled (http://ipxe.org/0b8080a0)I use latest fog 1.2.0 and have no problems with the other 2 PCs.
What could I do?
Thank you! -
RE: Can we distinguish Download from Upload scheduled tasks in Scheduled tasks list?
I think it would be good. Of course people know what tasks they are creating but sometimes mistakes happen, so it would be good if we could double check.
Thank you!
-
RE: Can we distinguish Download from Upload scheduled tasks in Scheduled tasks list?
Thank you, I have 1.1.2.
Wouldn’t it be better if in Task Management[COLOR=#000000]/[/COLOR][COLOR=#000000][COLOR=#000000][URL=‘http://192.168.1.5/fog/management/index.php?node=tasks&sub=scheduled’][COLOR=#000000]Scheduled Tasks[/COLOR][/URL] was a column with the scheduled task type (Upload or Download)? Active tasks don’t help, eg they are empty for me now.[/COLOR][/COLOR] -
Can we distinguish Download from Upload scheduled tasks in Scheduled tasks list?
Is there any way to see if a scheduled task in the list is Upload or Download?
Thank you -
RE: 1.1.2 time bug
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? -
RE: 1.1.2 time bug
Thank you, but 1.1.1 works perfectly with not altering any file from default. Now I have 1.1.1 and it works perfectly. If I upgrade to 1.1.2, then comes the problem. Is it a 1.1.2 bug?
-
RE: 1.1.2 time bug
No one else has this problem with 1.1.2? I can not upgrade because of this…
-
1.1.2 time bug
I installed 1.1.1 on debian 7.5 and I had not the time problems I mention here [url]http://fogproject.org/forum/threads/time-problem.10961/[/url] (I have to schedule in utc (3hours earlier) to start a task the time I want).
Then I upgraded to 1.1.2 and immediately the problem begun. I removed 1.1.2 and re-installed 1.1.1 on the same system and it is OK. Any solution?
Thank you
-
RE: Time problem
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/Athenshwclock --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] -
RE: Fog upgrade 1.1.1 --> 1.1.2 database error
I had the same issue because during installation in the last message I pressed Enter without reading it. But the message was first to update database and then press enter. So I uninstalled fog and reinstalled correctly.
-
RE: Time problem
Thank you.
I don’t mind times being reported correctly but I want to schedule in localtime and not utc.I edited [SIZE=3][FONT=arial][COLOR=#333333]/etc/php5/apache2/php.ini[/COLOR][/FONT][/SIZE]
[SIZE=3][FONT=arial][COLOR=#333333]and put Europe/Athens with and without “” in [/COLOR][/FONT][/SIZE][SIZE=3][FONT=arial][COLOR=#003300][CODE]date.timezone =[/CODE]. I restarted, but time in Log viewer/Scheduler still is UTC. I changed the HW clock from localtime to UTC, but the problem remains.[/COLOR][/FONT][/SIZE] -
Time problem
Since today I have a problem with time:
HW clock and system clock are both set to localtime. But in Logviewer/Scheduler the time shown in the list is UTC.
The same happens if I set HW clock to UTC.
So I have to schedule to UTC time to run tasks at the desired time (UTC time is -3 hours from localtime).
Has it something to do with 1.1.2 update I did today, or I messed something up?
Any solution?
Thank you -
RE: 1st daily scheduled task starts but 2nd never
Thank you for instant solution Tom!