@kibade

My memory I really bad but IIRC I ended up having to upgrade to Ubuntu I was on 20.04 at the time

@jmeyer You can find more details on this in GitHub as well: https://github.com/FOGProject/fogproject/issues/424

I have found the answer - hostname was changed after next deploy operation. We can close the topic.

Thanks a lot,
@Sebastian-Roth !

Can confirm. In 1.5.9.159 Snapin update is working as expected.

Peter

@george1421 Let me try if it will create a conflict by using Location instead of Sites

@sebastian-roth Hi , Resume works but for example i create new topic, i didn’t receive when have a reply

@sebastian-roth Hi, just tested, works like a charm 🙂

@sgennadi Should be fixed now. Sorry for the issue. A kernel testing build got in the way.

Finally I found where the problem came from !

We are using a NAS Synology to share the printers drivers. It’s a share accessible without password (guest account enable on the NAS). We’ve got no access problem to this share at anytime.
This NAS is joined to the domain… And here is the problem !

As soos as we unjoined the NAS from the domain, FOG printers are pushed without problem.

I don’t know why but if you execute printui command as local system account when the drivers files are shared on a NAS member of a domain, there is an access error. If you try the same command as local Administrator, it works…

So unjoining the NAS from the domain was the solution.

@tatanas Well done!

@gn_ro Not exactly sure why you run into this issue but looking through the code and searching the web for this error message I might have an idea what’s going on. After the deployment (through partclone.dd in this case) FOS looks for any NTFS partition, tries to mount it and see if it can modify registry files to change the hostname of the machine (pre Windows boot up!). This feature is called “early hostname change” and can be turned off. In the FOG web UI go to FOG Configuration -> FOG Settings -> section General Settings -> uncheck CHANGE HOSTNAME EARLY and save settings.

Unfortunately this can only be turned on and off globally. Most people want to keep that turned on and so might you for most of your machines. But I think it’s appropriate for you to quickly turn it off whenever you need to deploy that special machine.

@sebastian-roth Thank you! I hope will help others too.

@colej Which version of FOG do you use?

@Afernandes Just updated the FOG kernels to 5.10.34 and included the firmware as requested. You can keep using the kernel George provided or update to the latest as you like.

@altitudehack Thanks and sorry for the long time it took. Finally found time to fix the issue and push to dev-branch. Please update to the latest.

@greg-plamondon Should be fixed in latest.

Thank you,

@sebastian-roth said in Fog 1.5.9.62 Location problems.:

@Greg-Plamondon Just pushed the fixed 1.5.9.63.

Awsome!
Appreciate your work!

@sebastian-roth A fourth colleague had the same problem today so I restarted fog service, it takes a while but photocop_rgi printer has been connected after that :

------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 18/02/2021 15:37:55 Client-Info Client Version: 0.12.0 18/02/2021 15:37:55 Client-Info Client OS: Windows 18/02/2021 15:37:55 Client-Info Server Version: 1.5.9.60 18/02/2021 15:37:55 Middleware::Response Success 18/02/2021 15:37:55 PrinterManager Adding printers 18/02/2021 15:37:55 PrinterManager \\impression\Compta already exists 18/02/2021 15:37:55 Printer Adding: \\impression\Photocop_RGI 18/02/2021 15:37:55 PrinterManager PrintUI return code = 0 18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Compta for all users 18/02/2021 15:37:56 PrinterManager PrintUI return code = 0 18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Photocop_RGI for all users 18/02/2021 15:38:26 PrinterManager PrintUI has not finished in a timely fashion, abandoning process 18/02/2021 15:38:26 PrinterManager Restarting spooler ------------------------------------------------------------------------------

I’m just unable to explain this problem…

@george1421 I am looking for a way to easely clone (for backup) the data on several PIs

@jkozee @Tom-Elliott Sorry for bringing up such an old topic again. Working on moving towards the new 5.10.x kernel I was looking at the patches we still apply to our kernel. Most are part of the upstream kernel but not the fix discussed in this topic.

Though the kernel code has changed a bit and I am wondering if we’d still see the slowness without our fix? Would anyone of you be able to replicate the issue with a 5.10.x kernel (with and without fix)?

Searching the web a little more I stumbled upon this patch that made it into the official kernel not long ago: https://patchwork.kernel.org/project/linux-input/patch/20200910143455.109293-12-boqun.feng@gmail.com/

Not sure but could play a role in this case. Anyway it would be great to see if the issue can still be replicated with the newer kernel - without fix.