Latest FOG 0.33b
-
That’s just a warning so it shouldn’t be affecting the operation.
Is the service started and still running?
Does the log have any information?
[code]cat /opt/fog/log/fogreplicator.log[/code] -
[quote=“Tom Elliott, post: 24302, member: 7271”]That’s just a warning so it shouldn’t be affecting the operation.
Is the service started and still running?
Does the log have any information?
[code]cat /opt/fog/log/fogreplicator.log[/code][/quote]
it’s ok for me, thank Tom -
When i give a “Storage Group” to a Image, the Image Path do not change…
example for the “Storage Group = NAS” the path do not modify to “/volume1/images/”[url=“/_imported_xf_attachments/0/594_img1.png?:”]img1.png[/url][url=“/_imported_xf_attachments/0/595_img2.png?:”]img2.png[/url][url=“/_imported_xf_attachments/0/596_img3.JPG?:”]img3.JPG[/url]
-
I’m going to guess that you have more than one node per group?
-
[quote=“Tom Elliott, post: 24307, member: 7271”]I’m going to guess that you have more than one node per group?[/quote]
I’ve one group and one node in this group. -
The way the path get’s specified is by the isMaster AND isEnabled node. So if your NAS is simply a storage node, but is not labeled as Master, (there can only be on master node within a group) it will display whichever node is the master which my guess is currently your FOG Server. The FOG Server’s storage path is /images/
-
[B]Storage Node Storage Group IP Address Image Path[/B]
DefaultMember default 172.16.8.43 /images
Storage_NAS NAS 172.16.8.44 /volume1/images -
In the picture, the Storage_NAS does NOT have the Master Node checkbox checked!
-
[quote=“Tom Elliott, post: 24309, member: 7271”]The way the path get’s specified is by the isMaster AND isEnabled node. So if your NAS is simply a storage node, but is not labeled as Master, (there can only be on master node within a group) it will display whichever node is the master which my guess is currently your FOG Server. The FOG Server’s storage path is /images/[/quote]
If i specify my NAS is the Master the scheduler say “I don’t appear to be the group manager, I will check back later.” and do not work -
r1343 released.
Fixes path display on Image Management Page, if you have multiple master nodes. It would only display the first node it found which would typically be the first ID in the sequence. It now pulls the master node based on the Group ID.
-
[quote=“Tom Elliott, post: 24314, member: 7271”]r1343 released.
Fixes path display on Image Management Page, if you have multiple master nodes. It would only display the first node it found which would typically be the first ID in the sequence. It now pulls the master node based on the Group ID.[/quote]
And so the “scheduler” will work ?
-
r1344
When i put my Storage NAS in master :
1°) The Scheduler service in log message say : “I don’t appear to be the group manager, I will check back later”
2°) If I change the Storage Group for NAS to default and i Update, the upate fail ! -
Which scheduler service says “I don’t appear to be the group manager, I will check back later”?
When you’re changing the Storage Group for nas, to default, make sure it isn’t set to default node!
-
And, I’m assuming your changing the Storage_NAS group to default and not trying to change the Group Name NAS to default?
-
[quote=“Tom Elliott, post: 24323, member: 7271”]And, I’m assuming your changing the Storage_NAS group to default and not trying to change the Group Name NAS to default?[/quote]
This conf is ok ? If i want use a NAS for the Storage ?[url=“/_imported_xf_attachments/0/597_Capture.JPG?:”]Capture.JPG[/url]
-
If you want NAS as the master storage node for the default group, it’s perfectly fine to set it, just remember to uncheck the defaultMember’s master status.
-
[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
-
I do not know if I speak well, this is what I want:
[U]Here’s what I have:[/U]
- Storage Group = default,
in this Group -> Storage Node = DefaultMember
image path = /images
IP = 172.16.8.44
(This group does me nothing)
- Storage Group = NAS
in this Group -> Storage Node = Storage_NAS
image path = /volume1/images
IP = 172.16.8.43
(this is where I want to save, it’s NAS Synology)
How to make:
- The Scheduler works (because it does not work when it is Storage_NAS in master)
- If I do not put in the master Storage_NAS but DefaultMember the Scheduler works, but I is not the path / volume1/images in the configuration file.
- Storage Group = default,
-
[quote=“Tom Elliott, post: 24314, member: 7271”]r1343 released.
Fixes path display on Image Management Page, if you have multiple master nodes. It would only display the first node it found which would typically be the first ID in the sequence. It now pulls the master node based on the Group ID.[/quote]
If i ave multiple master nodes the service sheduler log : I don’t appear to be the group manager, I will check back later. -
It’s not multiple master nodes. It multiple groups.
If you move the Storage_NAS into the Default group (as you’re using the server off of the default group) and make the Storage_NAS as master, all should work.
