Yes, please upgrade. There have been a lot of bugs and fixes lately…

Do you mean you deleted 70-persistent-net.rules on the client before uploading?? So what does this file look like after imaging to the other clients and booting them (it should be generated on every client I suppose)?

[quote=“Uncle Frank, post: 42859, member: 28116”]Maybe try capturing the DHCP traffic to see which options are really send to the clients. Possibly an intermediate switch might change the filename on the way?!?[/quote]

Good call Uncle Frank. It looks like the DHCP server is passing the right IP and filename (unidonly.kpxe) to the client. Then the client turns around and asks FOG for undionly.0?? I don’t have that file in my tftpboot directory, but I renamed undionly.kpxe to undionly.0 and my clients boot right up! Hooray! Thanks for your help!

If I remember correctly, Ubuntu by default will provided colorized output. If installfog.sh was executable, it would be highlighted a different color. Run:

[B]ls -l[/B]

This will show the permissions on the file. You should see [B]-rwxr-xr-x[/B] for permissions. If you don’t have any executable bits, you’ll get the response you got. How do you fix it? For a start, you could run:

[B]sudo chmod 755 installfog.sh[/B]

This will only make that first script executable. In the same directory, there’s a .install.sh file that probably won’t have executable rights either.

[B][U]If you really want to make sure it works[/U][/B]
It seems you must have extracted the files in a strange way because you should already have the correct permissions. When you get the tar.gz from the website, run tar to extract the files to preserve permissions:

[B]tar zxvf fog_1.2.0.tar.gz[/B]

This will extract everything out into your current directory. Then all the permissions should be correct.

Update we have a PRTG server running on the same network I’m working with its admin to get it to monitor via SNMP still troubleshooting that as for network from the server switch it connects direct to out 10ge backbone and from there to our fiber ring to the individual schools I have it set for 20 simultaneous connections depending on the results of the monitoring I may increase that significantly we image at 25 separate campuses so its used pretty much non stop.

[COLOR=#ff0000][B][SIZE=4]It´s undionly.kpxe any version 1.0.0 or higher:oops: sorry[/SIZE][/B][/COLOR]

Ubuntu Server to Fog 1.2.0
]#### add by racl

subnet 192.168.212.0 netmask
255.255.255.0{
option routers 192.168.212.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 80.58.61.250, 80.58.61.254;
range 192.168.212.8 192.168.212.254;

filename “undionly.kpxe”;
next-server 192.168.212.5;

[quote=“Joseph Hales, post: 41509, member: 18131”]Here is the mistake I made fog now has 2 kernels bzimage and bzimage32 both should be updated to the same version and the kernel update page will name them correctly for you just download the 32bit version and the 64/32 bit version both with the same version number. I was used to .32 in which you only had bzimage if your like me when you click on one and saw the bzimage32 file name presented you may have assumed it was wrong and renamed it which leads to kernel panics and other assorted weirdness. Take note I am by no means an expert but It did happen to me.[/quote]

The autonaming you see now is only in current SVN releases, not the 1.2 release.

The “Published Kernels/Old Published Kernels/Unofficial Kernels” dropdowns are also new to SVN where 1.2 only had Published Kernels and Unpublished.

That all said, the way the naming works for use as “defaults”

Kernels with ARCH type x86_64 are typically the bzImage
Kernels with ARCH type x86 are typically bzImage32.

I’ve had good luck with 12.04 ubuntu even got bonded NIC’s working.

Hello every body,
Sorry for my english, i come from Marseille (France)
I’ve got the same problem. After pushing the image to the corresponding host, the host is starting, boot on the pxe, i see all information about the computer and then, restart…

It do that on a dell latitude 5500. I would like to do unicast. I’m trying to download Windows 7 x86.

I’m using ubuntu 14.04 Fresh install 4 days, fog server 1.2.0

Any idea?

Thanks

You could use raw disk access instead of shared folders (which might be even faster I suppose). At first create a RAW VMDK file which actually is just kind of a link to your real raid array device file:

[CODE]VBoxManage internalcommands createrawvmdk -filename “/tmp/rawarray.vmdk” -rawdisk “/dev/md0”[/CODE]

Check it out if you want:
[CODE]$ cat /tmp/rawarray.vmdk

Disk DescriptorFile

version=1
CID=44799ca3
parentCID=ffffffff
createType=“fullDevice”

Extent description

RW 234441648 FLAT “/dev/md0” 0
…[/CODE]

Then add this VMDK to your VirtualBox and startup. It should be ‘/dev/sdb’ inside your VirtualBox host if I remember right. Check ‘dmesg’…

This is kind of known. FOG Services start “too early” (before mysql is fully up). See here how I got this “fixed” on my system.
[url]http://fogproject.org/forum/threads/fogscheduler-needs-started-manually-since-upgrading-to-svn-2912-from-1-2-0.12266/#post-41094[/url]
I didn’t have the time to have a look into the start scripts yet. You are more than welcome to look into this! 🙂

Guys, he solved his issue, this is an old topic. We are just playing Necromancy.

Thanks Tom! I’ll just stick with 6.5 then.

yes the exports files is ok.
now the task start but when display " … prepare device … " , waiting…
when i press “enter” , dispay " invalid partition data" and reboot

. i setting “other windows image not resizable” because if setting “windows 7 system” fog return when start-up , boot sector not found !

[quote=“Tom Elliott, post: 40087, member: 7271”]Try this:

[code]update-rc.d isc-dhcp-server disable[/code]

Then edit the file:

Add before the exit 0 line:

[code]sleep 30 && start isc-dhcp-server[/code]

Restart and hopefully all things will work.[/quote][/quote]

Thank you for your help. The syslog still reads the same interface error. I looked into previous syslog files, and at one point, it read out:
[CODE]Withdrawing address record for [IP address] on eth0
Leaving mDNS multicast group on interface eth0
Interface eht0 IPv4 no longer relevant for mDNS[/CODE]

Could any of this have to do with the error?

Yes, it is very true with Ubuntu . I am using Ubuntu and have faced the same problem while setup of internet connection,as this issue got resolved from the experts on [URL=‘http://www.libertybts.com’]site web[/URL] in my new office.

Hi [URL=‘http://fogproject.org/forum/members/junkhacker.21583/’]Junkhacker[/URL],

After creating a image with “Single disk” “Resizable” it’s allright.
The whole disk space is allocated.

Super!

Thanks for the tip!

Kr,

Joeri

Adding authorized_keys will do the job, but I’m not going to add it. Mostly because of the security involvements. If I create a copied authorized keys, it’d be done using methods that would be extremely insecure as it would always have to be the same key.

in what way is it not working?