The Fog server doesn’t have much ressources and it comes hard when i have task to send to dozens of clients at the same time.
I think it could be nice to enable delayed tasks when it comes to group, and scheduled them on a 5min delay.
(i’m not sure to be clear - sorry for poor english : here is an example of what i mean)
[INDENT=1]I have my group called “Room3” of 15 computers. I want to use “Disk Surface Test” on all of them.[/INDENT]
[INDENT=1]I go in Group management / Room 3 and then select the task i want and ask for a 10mn delay and launch it immediately;[/INDENT]
[INDENT=1]Then, computer1 runs the task, and 10mn after the computer2 runs the task, 10mn later the computer3, etc etc[/INDENT]

I hope someone who might think it’s a good idea would re-write the idea to make it clear for everyone

Thanks you all

Hello
i’m posting here my problem & solution at the same time. I’ve been checking around this forum for threads on the problem, but I couldn’t find any.
(fog 0.32, running on Ubuntu Server 12.04 LTS)

So here is the message I got when I want to upload an image to the server (I didn’t test on the deploying side)

[CODE]>>Send method…NFS

Preparing to send image File to the server.

Mounting File System… mount : RPC: Remote system error - Connection refused

mounting 172.17.17.17:/images/dev/ on /images failed : Bad File Descriptor

Done

Checking Mounted File System…

---

*An error has been detected!

---

Fatal Error : Failed to mount NFS Volume.

---

• Computer will reboot in 1minute.

************************************[/CODE]

After some searches, i could resolve the issue by restarting the nfs service… The portmapper caused troubles for me as well, so i include it here :
[CODE]service portmap restart
service nfs-kernel-server restart
[/CODE]

I hope this is to be useful for somebody !

SOLVED !
Indeed, to reply to your message, I stayed connected to internet during the installation of Fog, and disconnected as soon as possible. I ran the installation twice in fact (once while connected, the other time disconnected).

Anyway, here’s the cause of the problem -which makes me feel dumb…
The person who worked before I came configured a 066 option in the extended field.
I didn’t knew anything about that ; I did my configuration in the main DHCP field.
His PXE came first and the PXE was done on a server (still in use) that no longer hosts a up to date PXE.
…
Thank you for your support. Now It’s (at least) time for fun !!

[Up]
As i’m trying to find out where the problem comes from, i’ve done several tests :

I’ve installed Ubu desktop 12.04 on a new server.
I downloaded the fog install, unplugged the server from network & ran the install
I used the options below ;
[LIST]
[]-[N] route for DHCP
[]-[N] DNS server
[*]-[Y] use fog’s DHCP
[/LIST]
I configured it out, and then i found a good old switch. I used it to plug the server and another computer for testing.
The PXE boot ran without problem.
I stopped the DHCP on the server ([CODE]#sudo service isc-dhcp-server stop[/CODE])
I plugged the Good’Old Switch on the network and tested on the server the network connection
I configured the 66 option on my WS2k3 to point to the server

and… Still the same message, my Good’Old “[SIZE=1]no DEFAULT or UI configuration directive found!”[/SIZE]

The problem seems to come from the network, rather than the FOG server.
Any idea how to find the source of the problem ?[SIZE=1][/SIZE]

Thank you for your reply !
here is the content of
[CODE]#vi /tftpboot/pxelinux.cfg/default[/CODE] (the smiley’s wrath does fear me ! )

[CODE]DISPLAY boot.txt
DEFAULT fog.local

LABEL fog.local
localboot 0

LABEL fog.memtest
kernel fog/memtest/memtest

LABEL fog.reg
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000
ip=dhcp dns=172.17.1.3 mode=autoreg keymap= web=172.17.1.10/fog/ loglevel=4 cons
oleblank=0

LABEL fog.reginput
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000
ip=dhcp dns=172.17.1.3 mode=manreg keymap= web=172.17.1.10/fog/ loglevel=4 conso
leblank=0

PROMPT 1
TIMEOUT 130 [/CODE]

Does it seems correct ?

Hello.
I have some problems with fog, and I want to back it up to a newly fresh installation.
I would like to know if there is a how-to or the procedure to do so.

thank you

Still the same problem. i’ve tried with “pxelinux.cfg/default” after the “boot:” prompt, and then I have the following message:

“Invalid or corrupt kernel image.”

I’ve tried other entries (like fog/memtest/memtest ) but it returns “could not find the kernel image : …”
I’ve done " # cp /tftpboot/fog/memtest/memtest /tftpboot/pxelinux.cfg/memtest"
and i have the same issue (could not find… ).
I’ve tried to make a file with only an entry and to save it to /tftpboot/pxelinux.cfg/test but still it is not found.

Any idea of where can I search to find out why “pxelinux.cfg/default” returns something and not the other test ?

Do you think the problem could come from the routers or the switches between the server and the client ?
–EDIT
I’ll give a try to use the 10.04 server on an isolated network. I’ll keep trace of my ( probably bad) process of debuging the issue.
I still can’t find any valuable instruction to put to the “boot:” prompt I got.

I’m coming to the idea that Tftp is not enabled on the school’s network. May the loading of the file pxelinux.cfg/default isn’t using that protocole ?
I hope I can sort it all out !

I wanted to change fog install from a hard drive to another one (bigger) and - as it was to be on the same PC hardware, i just used the DD command to copy one disk to the another, then expand the partition with fstab

I’ve installed fog .32 on an ubuntu 10.04 and tried to boot on it but the problem is still here. Anyone has an idea about that problem? I’m not familiar with PXE booting, and I can’t sort out where the problem could come from.

The web interface works but I can’t boot on PXE, neither to display Fog Menu nor to launch a scheduled task.
And still, i don’t know what can I write at the “boot:” to test or launch manually the menu.

-sorry for bad english