@sebastian-roth Thank you very much for the response. Sorry for the delay, I was on a time crunch for delivering this image and I did not have enough time to continue troubleshooting. I ended up just deleting the image and recapturing and it replicated afterwards. Hopefully it was just a fluke. But i know how to check the replication log file now!

Thanks again for taking the time to respond.

@sebastian-roth Thank you very much for the response. Sorry for the delay, I was on a time crunch for delivering this image and I did not have enough time to continue troubleshooting. I ended up just deleting the image and recapturing and it replicated afterwards. Hopefully it was just a fluke. But i know how to check the replication log file now!

Thanks again for taking the time to respond.

@sebastian-roth

The image is Q1 2021 - Connect Academy TX HP and Q1 2021 Connect Academy TX - Len

[03-15-21 1:10:18 pm]  * All files synced for this item.
[03-15-21 1:10:19 pm]  * Found Image to transfer to 12 nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm] | Replication already running with PID: 22051
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - HP
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Found Image to transfer to 12 nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm] | Replication already running with PID: 28711
[03-15-21 1:10:19 pm] | Replication already running with PID: 22078
[03-15-21 1:10:19 pm] | Replication already running with PID: 28714
[03-15-21 1:10:19 pm] | Replication already running with PID: 28718
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm] | Replication already running with PID: 28748
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm]  * Not syncing Image between nodes
[03-15-21 1:10:19 pm]  | Image Name: Q1 2021 - Connect Academy TX - Len
[03-15-21 1:10:19 pm]  | File or path cannot be reached.
[03-15-21 1:10:19 pm] | Replication already running with PID: 28758
[03-15-21 1:10:19 pm] | Replication already running with PID: 28769
[03-15-21 1:10:19 pm]  * Found Image to transfer to 12 nodes

It looks like it seems to be saying the file or path cannot be reached. I can ping the nodes and the Master. I don’t undersatand what could possibly be going on. It was just with these images and it just happened this morning for the first time.

@sebastian-roth Thank you for your reply!

Please excuse my ignorance on this one. Would it be tail -f opt/fog/log/fogreplicator.log to get the full log? It seems like I can only get the head or the tail. Is there a command that would help me do this?

and yes, each node has about 70%-80% free space!

FOS: 1.5.8
OS: Debian 10

I captured three new images on Friday evening and none of them replicated to any of my 10 storage nodes. I have had issues in the past where I’ve had to compare checksums and delete the d1p1.img files to re-propogate them, but in this case, the entire image directory did not transfer to any of the nodes

The images were all set to “replicate” and there is only one storage group. I have rebooted all the machines and Master can ping all of the nodes and vice versa.

Is there any other info I can post to this topic to help everyone understand this problem?
Has anyone run into this issue before?

Thanks very much, y’all are great!

@george1421 said in Automate Snapins to run after deployment?:

@danieln FOG has a plug-in module called persistent groups. This plugin allows you to create one or more template hosts. You can assign setting, snapins, printers, etc to this template host. Then when you assign a target computer to the template group, the settings assigned to the template host are copied to the target compute.

That sounds like it’s exactly what I’m looking for. are these persistent groups something you’d configure in the Groups tab on the FOG dashboard? If so, I can’t seem to find it.

Right now there is a bug with the persistent group where it makes the connection to the snapin and printer, but the tasks are not created to actually deploy the snapin and printer. I have a workaround for that until we can find the timing issue in the code.

I’d be curious what the workaround is, if you don’t mind sharing. This feature is not something of extreme importance, but it is something that would may my workflow much, much easier.

If I have a group of hosts that I want to always deploy a specific set of drivers and software regardless of what it is imaged with, is there a way to have those hosts always start a Snapin pack after they’re imaged or do I have task them every time?

@george1421 said

FOG (FOS) kernels can be downloaded from here https://fogproject.org/kernels/ download both the x64 and x32 bit kernels. Save the x64 as bzImage and the x32 ad bzImage32 (case is important). Then you can just move the files to /var/www/html/fog/service/ipxe directory on the FOG server. It probably wouldn’t hurt to rename the existing ones before you move the new kernels in. You can confirm the version of the bzImage files with file /var/www/html/fog/service/ipxe/bzImage It should print out the version of the kernel.

Thank you for this info! I downloaded those files, renamed them, and moved them to /var/www/html/fog/service/ipxe . I ended up keeping the old files and renaming them bzImageOLD and bzImage32OLD respectively. The new output of file /var/www/html/fog/service/ipxe/bzImage is this:

/var/www/html/fog/service/ipxe/bzImage:     Linux kernel x86 boox executable bzImage, version 4.19.123 (jenkins-agent@Tollana) #1 SMP Sun May 17 01:04:09 CDT 2020, R0-rootFS, swap_dev 0x8, Normal VGA

/var/www/html/fog/service/ipxe/bzImage32:     Linux kernel x86 boox executable bzImage, version 4.19.123 (jenkins-agent@Tollana) #1 SMP Sat May 16 23:59:01 CDT 2020, R0-rootFS, swap_dev 0x7, Normal VGA

/var/www/html/fog/service/ipxe/bxImage32OLD: Linux kernel x86 boot executable bzImage, version 4.19.145 (sebastian@Tollana) #1 SMP Sun Sep 13 05:43:10 CDT 2020, R0-rootFS, swap_dev 0x7, Normal VGA

/var/www/html/fog/service/ipxe/bxImageOLD: Linux kernel x86 boot executable bzImage, version 4.19.145 (sebastian@Tollana) #1 SMP Sun Sep 13 05:35:01 CDT 2020, R0-rootFS, swap_dev 0x8, Normal VGA

Version 4.19.123 is what is on the master as well as all the other nodes. I trust that it will look at these since they’re named properly even though the other files are in the same directory but they’re renamed. I will run a recapture/deploy test and report back with findings.

Thank you both again!

@sebastian-roth said

Sure, taking a quick look doesn’t hurt. The 1.5.9-RC2 was a release candidate not long before 1.5.9 was released. Possibly that uses a different kernel - depends on when it was installed.

You should be able to get the kernel version by running the following command on all your nodes: file /var/www/html/fog/service/ipxe/bzImage* (the * will include the 64 bit and 32 bit kernel - the output should show kernel version 4.19.x or possibly 5.6.x.)

Well I’ll be damned. The kernel on the master and all of the working nodes is version 4.19.123 and the problematic node’s kernel is version 4.19.145. You think that may be what’s causing the issue? But why would some of the other images be working fine then?

At any rate, is there an easy way to update this kernel without having to do a full reinstall?

@sebastian-roth said

you’re thinking its more along the lines of hardware issues with the laptop and not with FOS or the Node itself? I feel like it only throws those ATA errors when connecting to that one node, but I could be wrong. Maybe that’s the next thing i’ll test.

Yes I would say it’s very unlikely to be caused by FOS or the node unless you have different FOG/kernel versions installed.

I’d like to circle back around to this to get some more clarifcation. My master node has version 1.5.9-RC2 and this particular node (as well as all the other nodes) have version 1.5.9. I’m unsure as to what the differences between RC2 and the 1.5.9 version are, but do you think this is something worth investigating?

@sebastian-roth

@danieln said in Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors:

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the Master node was:
e929a14a17c60b2b9a7dfdf18f526232 /images/DellE5450-80-Non-Office/d1p1.img

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the problematic node was:
1d4bf4ac2bcef83013fe4589149b0e30 /images/DellE5450-80-Non-Office/d1p1.img

That’s very interesting. I did not expect the checksums to be different but good that I asked. To me that means that the file was not replicated from the master to the storage properly. So please delete /images/DellE5450-80-Non-Office/d1p1.img on the storage node and wait till it’s being replicated from the master. Then check md5sums again. The FOG replication services checks filesize and checksums (this check only happens for smaller files because it puts too much load on the server if checksums for large files are calculated on every run) but seems like this is a seldom case where filesize matches but checksum doesn’t.

I cannot exagerrate how useful this information is for me to know for the future. So thanks a million! I will try that and report back. However, just for my own clarification, those two checksum outputs should be the same if it replicated correctly?

I am using Zstd for compression. Do you recommend Gzip? What are the pros/cons of both?

Both are fine. I tend to use Zstd more and more.

Good to know.