Latest FOG 0.33b
-
what do you mean in the snapin part choosing instead of browsing your local computer I like the option.
-
Well, you can still chose your local computer, but it also gives the choice to use already created files.
-
I have to test it again because i think I had issues editing it the other day and had to delete and re-add it but let me make sure that is the case but let me make sure it was not user error lol, but I like the setup.
-
So I just tested it, and while the task failed, I’m guess because of the XXXX’s in the key sent info (which is fine) I got:
FOG::SnapinClient Attempting to connect to fog server…
FOG::SnapinClient Module is active…
FOG::SnapinClient A snapin task was found but, not all the meta data was sent. Meta data length: 10 Required: 7. -
I Found a few errors and I’m sorry I missed them. It was never making it to snapins.file.php so the progress wouldn’t work. Remember the task doesn’t clear until all the snapinTasks are completed. I’m testing and man 5 minutes sucks!
-
Ok thought it was just me but just in case I am imaging another machine to test on I am using hyper-V by the way on a 2012 r2 server machine. Also can we change the 5 min option it does seem forever at times
-
how would I force delete a client from the database?
-
Went to add a new workstation to try to image and test and started to get this errors
FOG DEBUG: Host: Database Load Failed: ID: 0, Error: Row not found
-
Changing the checkin time is done per client in the file config.ini found in “C:\Program Files (x86)\FOG\etc”
I’ve got mine, now, set to 20 seconds just for testing, still trying to work out kink in it.
I don’t know why You’re seeing the issue with that, did it create the host and did you set an Image with the host?
-
[quote=“Tom Elliott, post: 21813, member: 7271”]Changing the checkin time is done per client in the file config.ini found in “C:\Program Files (x86)\FOG\etc”
I’ve got mine, now, set to 20 seconds just for testing, still trying to work out kink in it.
I don’t know why You’re seeing the issue with that, did it create the host and did you set an Image with the host?[/quote]
it created the host but when I click on it it shows no data like it is corrupted. I am not sure why it happened I just did a full host inventory from PXE menu.
-
That sounds like, to me at any rate, that the isValid() function is actually checking if the MAC is valid AND if it’s associated with a host. I don’t know yet, still working on snapins.
-
ok i will wait for you let me know when I can play again lol
-
So I think I fixed the issue, however I think the FOG Client is bugged.
Originally the files would be sent with #!ok\n and then the options information.
I found if I I send the commands as originally in 0.32, they say the meta issue. If I remove the \n on the ok line, it starts to work, but errors out saying it can’t find valid task id, which as far as I can tell is because it’s sending the JOBTASKID= variable as: #!okJOBTASKID=
Trying 0.32 service.
-
r1130 released. Should fix snapin tasks. Changes title for Pending Macs. More service fixups.
-
Snapin tasks now works.
r1131 released.
-
i suggest also to modify fog to do this:
GRUB2 stage1 location:
[LIST]
[][B]Stage 1[/B]: boot.img is stored in the master boot record (MBR), or optionally in any of the [URL=‘http://en.wikipedia.org/wiki/Volume_boot_record’]volume boot records[/URL] (VBRs), and addresses the next stage by an [URL=‘http://en.wikipedia.org/wiki/LBA48’]LBA48[/URL] address (the 1024 cylinder boundary of GRUB legacy is omitted); at installation time it is configured to load the first sector of core.img.
[][B]Stage 1.5[/B]: core.img is by default written to the sectors between the MBR and the first partition, when these sectors are free and available. For legacy reasons, the first partition of a hard drive does not begin at sector 1 (counting begins with 0) but at sector 63, leaving a gap of 63 sectors of empty space. That space is not part of any partition or file system, and therefore not prone to any problems related with it. Once executed, core.img will load its configuration file and any other modules needed, particularly [URL=‘http://en.wikipedia.org/wiki/File_system’]file system[/URL] drivers; at installation time, it is generated from diskboot.img and configured to load the [I]stage 2[/I] by its [URL=‘http://en.wikipedia.org/wiki/Path_(computing)’]file path[/URL].
[/LIST]
so copying only the MBR is not correct! we must copy also all data before sda1 starts -
Hi, I created (very) simple UML diagram of FOG 0.33. Just classes (that I found in /var/www/fog/lib/fog/) and their associations (no functions and variables of classes) and for now, doesn’t look nice, but it’s start. It’s been created in UMLet. I was not able to upload source (it has .uxf extension), so just .pdf. Is it possible to allow .uxf?
[url=“/_imported_xf_attachments/0/512_fog_0.33_v01.pdf?:”]fog_0.33_v01.pdf[/url]
-
Good morning all. Tom I am downloading new version as we speak will let you know if I have any problems.
-
[quote=“Tom Elliott, post: 21774, member: 7271”]It’s all good. You can decompress the init.gz with xz -d -c init.gz > init
Then mount the init file created to another directory. I Usually create a tmp folder inside /tftpboot/fog/images/
[code]
mkdir tmp
xz -d -c init.gz > init
mount -o loop init tmp
[/code][/quote]
i tryed to modify fog script.
simply modified the line:
partclone.${fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
with:
part_fs_type=
blkid $part | awk 'BEGIN {FS="\""} { print $4 }'### row patch to use correct partclone.fstype
partclone.${part_fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fogin upload section. I think that must work, but to test i recreated init.gz with:
umount ./init
xz -z -c init > init.gz
and overwrited original init.gz into tftp/fog dir : don’t boots
what i must do to recreate a working init.gz?
-
xz -C crc32 -z -c init > init.gz (I think)
That said, I don’t think that command will work.
extfs, ntfs, hfsp, btrfs, xfs are the partclone binary names. so if i read your script right, if it comes up as ext4, it’s going to try partclone.ext4 which is wrong.
