Posts made by Joe Gill

@Tom-Elliott

Where are they located?

@Tom-Elliott

Ok. So I did the update. I still get the same error. It has the // still there.

Am I missing something?

Thanks!

Joe Gill

@Tom-Elliott

I’ll update and check. Thanks!!!

#!ipxe
set fog-ip 172.16.1.17
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://172.16.1.17/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0x00567a 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is registered as AE-21!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.keyreg Update Product Key
item fog.quickimage Quick Image
item fog.multijoin Join Multicast Session
item fog.quickdel Quick Host Deletion
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 5000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.keyreg
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param keyreg 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.quickimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.quickdel
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param delhost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.16.1.17/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://172.16.1.17/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

Also, I have nothing listed in my active tasks at all on the GUI.

So prior to this error things were working fine. I was able to image an entire labs worth of machines. What happened was I had imaged those machines and had gone to a new lab, used the image from the old lab to make a new machine to clone. When I got new machine done, I went to capture it again for the new image and forgot to rename said new image. That is when the problem showed up.

What I tried to do to resolve this…

I deleted all images from FOG GUI. Re-added them with the right names. Deleted host from the FOG server. Re-registered host with the FOG server. Rebooted into PXE and PXE failed.

The only other thing that changed was our DNS. We updated a DNS server so I had to make those updates in resolv.conf on the server. But DNS works on the server just fine. I can resolve names no problem.

Any ideas would be helpful.

Re: Could not boot: Input/Output error(http://ipxe.org/1d0c6539)

I am having this same issue. One of my hosts will not pxe boot. I can pxe boot other clients just fine but the one I want to make an image capture from is not

The current version of FOG I’m running is Trunk – Running Version: 8140 SVN Revision: 5698.

Any ideas? All of the hardware I’ve PXE booted so far have been identical. I defaulted this hosts bios settings and reset the pxe boot stuff as I normally do with no luck. Any ideas would be helpful.

Thanks!

Cheers!

Joe Gill

Hi guys,

Tom, thanks again for all the help! Everything is happy. The multi-cast we setup finished just fine. I’m making a new image today and imaging another lab. I doubt they’ll be any more issues with multicasting.

I’ll re-post if more issues arise.

Thanks!!

Cheers,

Joe Gill

@Tom-Elliott
I’m here still

@Tom-Elliott

Hi Tom,

65.x.x.x is our Public IP address on our router.
172.16.1.17 is the address for our FOG Server.
172.16.1.22 is the address for our FOG Storage Node.

Thanks!

Joe

Also, I did add back my Freenas storage node as an additional storage node but it is not master. I can’t seem to wrap my head around this. I did try uploading a new image with the new version of partclone. I’m going to try re-pushing a multicast on Monday. But I don’t think it’s going to matter much.

The one thing that is strange in this install is that when I initially set up the server I had my Freenas storage as the only node until I had problems. Then I demoted the Freenas down to slave and installed the FOG storage node. My main image was originally stored on the Freenas server when it was the master. But I’ve since reimaged that machine several times onto the new FOG storage.

I checked the /var/log/fog/multicast.log, and it still says:

[06-16-16 8:37:57 pm] Interface Ready with IP Address: 65.XXX.XX.194
[06-16-16 8:37:57 pm] Interface Ready with IP Address: 172.16.1.17
[06-16-16 8:37:57 pm] Interface Ready with IP Address: Fog
[06-16-16 8:37:57 pm] * Starting MulticastManager Service
[06-16-16 8:37:57 pm] * Checking for new items every 10 seconds
[06-16-16 8:37:57 pm] * Starting service loop
[06-16-16 8:37:57 pm] | This is not the master node

How do I get rid of the 65.xxx.xx.194 address? This is our outside address for our public ip address.

And yes this is the master node. I removed my secondary storage node just to be sure. I’ll go check the logs since I did that.

Restarted a Multicast with 2 machines and it’s stuck at the Partclone screen.

@Tom-Elliott

ps -ef | grep ‘FOGMulti’ | grep -v grep

Revealed nothing running.

Should I try re-running the multicast?

This was after I listened to you and ran the first command…

root@Fog:/# service FOGMulticastManager stop; sleep 10

• Stopping FOG Computer Imaging Solution: FOGMulticastManager [ OK ]
  root@Fog:/# ps -ef | grep ‘FOGMulti’ | grep -v grep

As you can see nothing is running now.

Hi Tom,

Here is the result…

root@Fog:/# ps -ef | grep ‘FOGMulti’ | grep -v grep
root 25118 1 0 12:43 ? 00:00:00 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager
root 25121 25118 0 12:43 ? 00:00:01 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager

Joe

Here is the results from the ps command… It appears the service is running.

root@Fog:/# ps aux | grep FOGMulti
root 25118 0.0 0.2 203568 24940 ? S 12:43 0:00 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager
root 25121 0.0 0.1 283860 19628 ? S 12:43 0:00 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager
root 26380 0.0 0.0 15948 2244 pts/7 S+ 14:08 0:00 grep --color=auto FOGMulti

Thanks for the responses!

I was able to download the latest trunk version. Yay! So now I’m up to date on my install.

I was also able to run the debug on multicast. I can successfully run a multicast with two clients in debug mode. So it must be a setting in FOG.

As for Clonezilla… I used it to image one of our labs. Basically I put the server edition on a USB flash drive, booted to it and pushed my images from their off of our NAS. This worked well. However, it does not provide all of the functionality of FOG.

Also, I did check the /var/log/fog/multicast.log file out. The majority of the errors there say:

This is not the master node.

I checked to make sure I have our primary node set correctly in the GUI and it is correct. I have the FOG storage as Master Node.

The only thing else that’s strange is that it says:

Interface Ready with IP Address: 65.XXX.XX.194 address listed which is our public IP.

Any ideas are appreciated!

Thanks!!

Cheers,

Joe Gill

@Joe-Gill

I did mange to download the latest trunk version using svn. I got it downloaded and am going to install it and see what happens. In the meantime help is appreciated. Thanks!!

Cheers,

Joe Gill