Posts made by jbsclm

From earlier testing as long as you use the same dmi field, you can associate 2 images. As an example, you set the dmi field to manufacturer, and then associate 2 different images with it. The capone server side code returns both of these to the client, and the capone client side code realises there are 2 and asks you which one you want. When I get chance I check out the latest svn and see if it is still this way.
As an alternative, you could set the dmi field to model, then associate 3 images, xp, w7, and w8.
when a client of that model images via capone it will ask which one you want.
unfortunately the dmi field is global for capone, ie you can’t have model for some and manufacturer for others.

Looks like tftpd on your fog server is working OK.
does [url]http://192.168.1.17/fog/service/ipxe/boot.php[/url]
work OK, it should return the ipxe menu source?
As Tom says, is your client on the same lan in virtual box as your fog server.
If so, please reinstall fog, this time letting fog be the dhcp server.
You will need to stop the dns-masq service.
Please be aware that you will have 2 x dhcp servers on your lan, so either switch off the main one, or ensure that the virtual box host cannot see it, you can’t just pull the cable, as the Virtual box network adapters will not work.
Hence my other suggestion to put both the fog server and client network adapters on the internal network.

Once you have a working basic fog server, with the fog server doing the dhcp, you can reinstall with fog dhcp set to No, and get your dnsmasq config correct.

I can’t offer any advice on dnsmasq as I don’t use it but there are a number of post on the forums about it.
Regards

It sounds like tftpd is not looking at the correct place. The above example was for ubuntu 14.04, you are running 13.10

I haven’t got either OS, but you need to get the following working on you fog server before you go any further, running as root on the fog server try the following.
tftp 192.168.1.17
//if the above fails the tftpd isn’t running, see other threads for this problem.
tftp> get /default.ipxe
tftp>
if you get an error, then the tftpd server cannot find default.ipxe, so it is probably pointing at the wrong root folder

you will need to do the following
check that default.ipxe is in /tftpboot
look at /etc/default/tftpd-hpa for the root folder for tftpd (TFTP_DIRECTORY)

cd <TFTP_DIRECTORY> //ie what you got from the config file.

root@p9:/var/lib/tftpboot# ln -s /tftpboot/default.ipxe default.ipxe

Hope this helps

also see my previous post

[url]http://fogproject.org/forum/threads/chain-booting-0-33-beta-from-0-32.10156/[/url]

Which of the two above problems do you have, can you give a screenshot?
If it is the first above, ie “cannot read from boot medium, system halted” I suggest you reinstall, with fog providing the dhcp, with your lan set to internal network only.
Once you have that working, you can reinstall with the LAN set to bridged, with fog not providing dhcp.
If that then does not work, it is your dhcp/ dhcp proxy settings that are the problem.

Is your client virtual box?

If so set the network card hardware to Intel, other types give this problem.
It also occurs on VMware I believe, real hardware is OK.

Assuming that the new card is working, ie ifconfig shows eth1 as the network interface, and you can ping successfully from the box, and ping it from others, there is no need to reinstall, from what I remember you need to go into fog settings, and change the instances of eth0 to eth1, and then go into the storage node settings, and again change eth0 to eth1.
Thia worked at 0.32 and I don’t think it will be any different at .33

Glad to know it worked, all I can think is that something was left hanging around from the previous install.

yes, see below.

The settings are also available in the fog settings->plugin capone section.
Just a thought, I assume you enabled the plugin system in the settings page,although I can’t see how you would have got as far as you did without it.

[ATTACH=full]765[/ATTACH]

[url=“/_imported_xf_attachments/0/765_Ubuntu Fog.png?:”]Ubuntu Fog.png[/url]

I’ve just installed the latest svn, r1683, from scratch on ubuntu 12.04, and can confirm that although I haven’t tried a deploy, the web pages come up OK.
r1683 is available at
[url]http://svn.code.sf.net/p/freeghost/code/trunk[/url]

rgds

I take it you are using 1.0.0, I’ll upgrade my test system to that and get back to you. Capone certainly worked at an earlier svn.

Tom, given the number of people that have tripped over this, is there any way that the init.gz could be modified to wipe the gpt at the start of deploying an mbr image?

Tim, for what it’s worth, my recommendation is as follows.
Don’t use Ubuntu 14.10, there area lot of documented issues with it. I use ubuntu 12.04 on virtual box.
There is a Wiki here
[url]http://fogproject.org/forum/threads/ubuntu-installation-for-fog-12-04.9338/[/url]
Set up your server on a Natted lan, so the server can see the outside world to download the packages and updates.
Set it up so that your Fog server not is the DHCP.
Change you Virtual lan to an internal network.
Rerun the install which will pick up the previous settings, let the Fog server provide the DHCP.

Set up your client NICs as an Intel card, others, realtek, in my case don’t play well with IPXE. This is a virtual problem, it is OK with real cards.
Set yourself up a virtual client, on the internal network LAN, build in with Windows 7 or even xp which is quicker, and you can just image and restore for a test, W7 needs a bit of sysprep/fogprep stuff, even just to image and restore successfully.

You now have Fog server and client setup on it’s own isolated network.
2 real PCs and a hub or switch would achieve the same, and takes VMware out of the mix.

Once you have this working you can rerun the install, this time without the fog server doing the DHCP.
Change the network back to bridged or whatever it is called on VMware.
Now you only have the Sophos UTM to configure.

Hope this helps

My init.gz fixes the problem for 0.32, if anyone else needs a copy send me a message.

It sounds like the name is wrong, but it looks right.
I’ll grab a copy of my working init.gz for you later today, and stick it on google drive for you.

Hi Chris
That rings a bell.

If you copied the file in you’ll need to chmod the file, as it probably got dos permissions, which don’t come across into unix ones.

If you go to the folder and do
ls -l
it will tell you what the others are

ls -l fog.capone will give something like
-rw-rw-r–
which is 664, ignore the initial “-”, it is the sticky bit.
it will tell you what the others are, fog.capone needs to be the same.
At a guess they will be either 755 or 777

to set them you do

chmod 755 fog.capone

also check the ownership, and change as necessary with

chown <username> fog.capone.

at the end it should look the same as the others.

Further to what Tom says, as you have noticed ipxe has a completely different menu structure to pxelinux which 0.32 used.
If you set anything in the fog settings->pxe boot menu->advanced configuration menu a new item (advanced) will appear at the bottom of the first level menu.
What you have to do is make sure that what you put in the advanced configuration menu is a valid ipxe menu.

The example from the above post is below, note that the code inserts #!ipxe as the first line.

:MENU
menu
item example1 Boot to disk
item example2 Iso Boot
item example3 Example Text 3
:example1
sanboot --no-describe --drive 0x80 || goto MENU
:example2
kernel memdisk iso raw
initrd win764.iso
boot || goto MENU
:example3
kernel memdisk iso raw
initrd win8-164.iso
boot || goto MENU
autoboot

It is useful to point you browser at the following urls, you can then see what is returned as the menu.
[url]http://<fog[/url] ip>/fog/service/ipxe/boot.php for the initial menu.
[url]http://<fog[/url] ip>/fog/service/ipxe/advanced.php for the advanced.

you need to make sure that the files you are trying to use, (initrd, win764 etc) , can be accessed via http,

The example below is an adaptation of one I have used at work, I’ve not tested it in this form, but you would need to copy memdisk and the diags files to a fog/dell folder in the apache folder.
Don’t forget to change the ip address below to that of your fog server.

set fog-server 192.168.1.11
set boot-url [url]http://${fog-server}/fog/[/url]

FONT=Courier Newmenu Imaging and Diagnostics[/FONT]

FONT=Courier Newitem dell1 Dell Diags - GX760 GX380 E5400 XT2 E4200[/FONT]
FONT=Courier Newitem dell2 Dell Diags - D4x0 D600-D630 GX240-GX755 P370-T3400[/FONT]
FONT=Courier Newitem dell3 Dell Diags - XT[/FONT]
FONT=Courier Newitem dell4 Dell Diags - T1500[/FONT]
FONT=Courier New#item foginfo FOG system info[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New [/FONT]
FONT=Courier Newitem shell shell[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New [/FONT]
FONT=Courier Newchoose fog-opt && goto ${fog-opt}[/FONT]
FONT=Courier New [/FONT]

FONT=Courier New [/FONT]
FONT=Courier New:dell1[/FONT]
FONT=Courier Newkernel ${boot-url}fog/dell/memdisk raw[/FONT]
FONT=Courier Newinitrd ${boot-url}fog/dell/diags1.img [/FONT]
FONT=Courier Newboot[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New:dell2[/FONT]
FONT=Courier Newkernel ${boot-url}fog/dell/memdisk raw[/FONT]
FONT=Courier Newinitrd ${boot-url}fog/dell/diags2.img [/FONT]
FONT=Courier Newboot[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New:dell3[/FONT]
FONT=Courier Newkernel ${boot-url}fog/dell/memdisk raw[/FONT]
FONT=Courier Newinitrd ${boot-url}fog/dell/diags3.img [/FONT]
FONT=Courier Newboot[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New:dell4[/FONT]
FONT=Courier Newkernel ${boot-url}fog/dell/memdisk raw[/FONT]
FONT=Courier Newinitrd ${boot-url}fog/dell/diags4.img [/FONT]
FONT=Courier Newboot[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New [/FONT]
FONT=Courier New:foginfo[/FONT]
FONT=Courier Newkernel ${boot-url}fog/kernel/bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=${fog-server}/fog/ loglevel=4 consoleblank=0 mode=sysinfo[/FONT]
FONT=Courier Newinitrd ${boot-url}fog/images/init.gz [/FONT]
FONT=Courier Newboot[/FONT]
FONT=Courier New [/FONT]
FONT=Courier New:shell[/FONT]
FONT=Courier Newshell[/FONT]

Hope this helps

It is a problem with the fog.capone script. It has been fixed in 0.33 however the 0.32 problem is documented here with a fix.
[url]http://fogproject.org/forum/threads/capone-and-fog-0-32-not-working-errors.192/#post-762[/url]

essentially.
copy init.gz (just in case it all goes wrong)
uncompress init.gz
mount it
edit /bin/fog.capone as per the instructions
unmount init.gz
compress init.gz

Hope this helps.

PS
the modified fog.capone is in the link above, which will save you editing it.

I’ve installed various revision of 0.33 on ubuntu 12.04 lts, but now just install the new revision over the top. All I did on the install was to su - and cd to the bin directory under the fog source, and then ./installfog.sh
I don’t remember having to change anything, other than to answer the questions. I certainly didn’t do anything with the mysql config, just accept the prompt from the installer to set the password to null.
I let the installer download all the required packages, rather than installing, and configuring them beforehand.
hope this helps

Have a look at my post here, it may be what you want
[url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/page-59#post-24274[/url]