Posts made by JiC

Of course, I updated all nodes before reading the news This will learn me (maybe…) to read all the instructions before doing something.

Don’t apologize, Fog saves my life everyday : so, thank you again for this fantastic software, and thank you for the very fast help.

JC

Hi

I updated my Fog Server and all my storage nodes, and when I read again the news about the release, I saw that :

Please make sure you stop replication on the master first systemctl stop FOGImageReplicator; systemctl stop FOGSnapinReplicator, then update the storage node(s) and then update master node as a last step.

Oops, and then update master node as a last step ? Obviously, now, I have a problem with the replication between my server and the nodes, which saturates the bandwidth between servers.

I understood that hashing code needed to be changed, but where/how can I patch that now ?

Many thanks,

JC

@Wayne-Workman It’s a luck that upgrading and downgrading Fog is so easy

I confirm with running Version 1.3.0-RC-9 (SVN Revision: 5952), I can make capture. It works perfectly (but multicast is still broken ^_^).

@Tom-Elliott Thank you so much

I tried the “version 19” from branch “working-RC-10” (SVN Revision: 5953). The problem with the multicast is solved, you rule !!!

But when I tried to capture a new image, the upload doesn’t work anymore (I have an error like “Mounting file system : failed”). I think the problem is more general, because when I start capture in “debug mode”, I can see many settings are not defined :

(uploading was ok yesterday)

Hum, yes you’re right, I’m already in RC-9, I don’t know if the problem was in RC-8 too. I’ll wait for the next release, I hope for you this will not be too hard to patch

With my encouragement !

JC

Hi everybody

I’m installing a new fresh Fog Server on a Debian 8.x (the previous was perfect, but the system disk died 0:-) ). Your work on Fog 1.3 is incredible, you made a very great job !

Managing computers, groups, uploading images (…) : all is ok, but not multicast When I make a multicast task, I have errors like “invalid multicast session” or “attempting to check in”. Here are the logs from /opt/fog/log/multicast.log ; the “Array” PHP error just after “–interface” looks very suspect…

[09-05-16 4:37:36 pm] | Task (1) Multi-Cast Task is new!
[09-05-16 4:37:36 pm] | Task (1) Multi-Cast Task has been cleaned.
[09-05-16 4:37:36 pm] | Task (1) /images/imagelouvre2015 image file found.
[09-05-16 4:37:36 pm] | Task (1) 4 client(s) found or to receive.
[09-05-16 4:37:36 pm] | Task (1) Multi-Cast Task sending on base port: 56514
[09-05-16 4:37:36 pm] | CMD: cat /images/imagelouvre2015/d1p1.img | /usr/local/sbin/udp-sender --interface Array --min-receivers 4 --max-wait 600 --portbase 56514 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/imagelouvre2015/d1p2.img | /usr/local/sbin/udp-sender --interface Array --min-receivers 4 --max-wait 10 --portbase 56514 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/imagelouvre2015/d1p3.img | /usr/local/sbin/udp-sender --interface Array --min-receivers 4 --max-wait 10 --portbase 56514 --full-duplex --ttl 32 --nokbd --nopointopoint;
[09-05-16 4:37:36 pm] | Task (1) Multi-Cast Task has started.
[09-05-16 4:37:46 pm] | Task (1) Multi-Cast Task is no longer running.
[09-05-16 4:37:46 pm] | Task (1) Multi-Cast Task has been completed.

Do you know where is the problem ?

My Fog version is SVN Revision 5952 :

commit a84bdebfe1b1149829cf14e745ae1f086b34ef14
Author: Tom Elliott tommygunsster@gmail.com
Date: Mon Sep 5 07:08:53 2016 -0400
Fix issue of hosts not able to search. Maintain as 1.3.0-RC-9.

Thank you for your help !

Yours,

JC

[quote=“Tom Elliott, post: 24291, member: 7271”]
FOG_TFTP_PXE_CONFIG_DIR is no longer really required as we’ve moved the pxelinux.cfg directory to /var/www/fog/service/ipxe. The “config” is done dynamically from the boot.php/BootMenu.class.php files. Tasks aren’t “saved” anywhere anymore so we don’t need to ftp the 01-XX-XX-XX-XX-XX-XX files anymore.
FOG_TFTP_PXE_KERNEL_DIR should be set based on the variables during install time. If it’s not set, I don’t know why. However, this should be set to /var/www/fog/service/ipxe
FOG_TFTP_PXE_KERNEL should only contain “bzImage” as iPXE uses relative links. So when it chains to iPXE, it’s chaining to [url]http://{fogserverip}/service/ipxe/boot.php[/url]

The relative location in full form when loading bzImage and init.xz would then be:
[url]http://{fogserverip}/service/ipxe/{bzImage,init.xz}[/url]

The location of the init.xz and bzImage files is in: /var/www/fog/service/ipxe which is why you set the KERNEL_DIR parameter to that folder. If for some reason permissions weren’t setup properly, this folder should be chown -R fog.root /var/www/fog/service/ipxe
[/quote]

Thank you for all these explanations, you made many interesting changes since 0.32… I better understand how it all fits.

I only changed my DHCP server to use “undionly.kpxe” : when I started my test computer, it started with the fog kernel. It didn’t clone this computer (maybe because it’s an “Advanced Format Drive”), but cloning is ok with classic disks.

Many thanks

Hi to all,

I tried to install the latest 0.33b release (r1340) ; it’s a fresh install on a Debian 7 system.

I had 3 problems :
[LIST]
[]During the installation process, when Fog installer asks “What is the IP address to be used by this FOG Server? [adr:111.222.111.222]” if I submit as is for default value, the installer rejects the IP Address. I must specify it manually if I want to continue.
[/LIST]
[LIST]
[]When I go on the page “Service configuration”, if I enable/disable the status of a service (check/uncheck “Service Status” box) and click on the “update” button, I only have a white page ([url]http://myserver/fog/management/index.php?node=service&sub=edit&tab=displaymanager[/url]) and the change I made is not applied. If I edit the same settings in “FOG Configuration”->“FOG Settings”, it works. Maybe it’s a known bug ?
[/LIST]
[LIST]
[]After installing Fog, everything seems Ok. But I think there is a problem with TFTP Server settings :
[/LIST]
[INDENT][LIST]
[]FOG_TFTP_PXE_CONFIG_DIR contains “TFTP_PXE_CONFIG_DIR” (which doesn’t seem set elsewhere)
[]FOG_TFTP_PXE_KERNEL_DIR contains nothing
[]FOG_TFTP_PXE_KERNEL only contains “bzImage”
[/LIST]
My /tftpboot folder contains this (there’s no file “bzImage”) :

[CODE]-rw-r–r-- 1 fog root 828 mars 18 12:17 boot.txt
-rw-r–r-- 1 root root 75 mars 18 12:17 default.ipxe
-rw-r–r-- 1 fog root 395760 mars 18 12:17 ipxe.krn
-rw-r–r-- 1 fog root 25340 mars 18 12:17 memdisk
-rw-r–r-- 1 fog root 16794 mars 18 12:17 pxelinux.0.old
-rw-r–r-- 1 fog root 169248 mars 18 12:17 snponly.efi
drwxr-xr-x 2 fog root 4096 mars 18 12:17 tftpboot
-rw-r–r-- 1 fog root 100430 mars 18 12:17 undionly.kpxe
-rw-r–r-- 1 fog root 147728 mars 18 12:17 vesamenu.c32[/CODE]

When I boot with a test computer, it can’t find any PXE Boot…
Do you know what I must change ?[/INDENT]

Well… I tested bzImageCORE today but it doesn’t work. I can imagine how it’s hard to debug without the right disks ! For my emergency, I’ll clone with my old Acrns DVD, this will be slower but it doesn’t matter

At work we use a lot Fog, it saves us lot of time ; so we seriously consider the possibility of donating. But it’s very hard for us (French Public Administration) to make a donation 1) with PayPal 2) to a non-organisation (but we’re working on it).

The first thing we could do is to buy equipment, for example 1 or 2 AF drives… Would it help you ?

I set my image with “Windows 7” OS and “multiple partition-single disk” ? (I have 2 partitions on my disk).

I checked : my disks are 4K / Advanced Format drives. Bloody hell

I saw that Fog 0.33b was able to manage AF drives, so I tried it today.

When I make a new task to upload my image, FOG only upload the MBR (d1.mbr) in the /images/myimage/ folder. But no partitions

When I try an image with debug mode, I’m stuck on an error :

“/bin/fog : line 7 OS_ID_WIN7 not found
/bin/fog : line 8 OS_ID_WIN8 not found”

I patched /bin/fog (spaces before and after the sign “=”), but if I retry launching fog, the task was completed before so nothing happens (“Unable to find a valid task ID…”). I don’t know how to patch it for good in my FOG server.

So I can’t check if Fog 0.33 will patch the AF Drives problem for me ?

Notes for later - relative topics :

[url]http://fogproject.org/forum/threads/advanced-format-drives.845/[/url]
[url]http://fogproject.org/forum/threads/another-advanced-format-drive-question.866/[/url]

Well, I’m lost ^_^

I can’t find any clue about “Advanced Format Drive”, it’s a basic Seagate Barracuda 250 GB, ST250DM000, Serial ATA III.

When you ask me setting a custom layer, where should I do this ?? In FOG, in the BIOS of my computer ? Elsewhere ? I reached my level of incompetence

I tried a new test ! Before installing Win 7 x64, I backuped up the hard drive : I kept the Win 7 x32 drive on a secure place, and I put in my computer a new and empty disk on which I installed Win 7 x64. Both disks are the same model (Seagate barracuda 250 GB).

When I put the Windows x32 version, I can upload an image.
When I put the Windows x64 version, I can’t upload an image. Only d1.mbr is written in the folder [COLOR=#333333][FONT=Arial]/images/dev/(mac address).[/FONT][/COLOR]

It looks like if FOG is not able to read some disks where Windows 7 x64 [COLOR=#333333][FONT=Arial]is installed. It happens only on one computer (HP Compaq 8200 Elite). This computer has an EFI BIOS but I disabled EFI Boot Sources before installing Windows.[/FONT][/COLOR]

Hi Tom & Kam,

I’ve almost the same problem.

In june, I uploaded an image of a Windowd 7 32 bits computer, and I had no problems. I change the OS on this computer (same Windows 7, but this time x64) and I can’t clone it anymore. I have the same problem as Kamz :

[I] unable to move /images/dev/(mac address) to /images/[/I]

I think it’s a permissions problem, because I can upload others images… Even x64 computers !!

The amazing thing is that on the FOG Server, in the “/images/dev/(mac address)” folder, the file “d1.mbr” is written. But no data from partitions. It’s like if FOG is not able to read Windows 7 x64 partitions ??