Fog hangs while trying to upload

[Scootframer]

@lukebarone I thought I would try to upload again from a different computer. It hung on same spot but with different image name.

 total 8
drwxrwxrwx. 19 fogproject root 4096 Feb  6 08:13 .
dr-xr-xr-x. 20 root       root 4096 Feb 27 15:31 ..
drwxrwxrwx.  2 fogproject root  206 Oct 21 11:25 21H2GoldSophos
drwxrwxrwx.  2 fogproject root  206 Oct 21 11:06 21H2TemplateSophos
drwxrwxrwx.  2 fogproject root  206 Nov 16 07:54 22H2GoldSophos
drwxrwxrwx.  2 fogproject root  206 Feb  3 16:13 22H2TemplateSophos
drwxrwxrwx.  5 fogproject root  106 Mar  1 09:44 dev
drwxrwxrwx.  2 fogproject root  246 Jan 13 15:12 ImageforTestingalso
drwxrwxrwx.  2 fogproject root  206 Feb  6 08:13 ImageforTestingonly
-rwxrwxrwx.  1 fogproject root    0 Dec 21  2021 .mntcheck
drwxrwxrwx.  2 fogproject root   30 Dec 21  2021 postdownloadscripts
drwxrwxrwx.  2 fogproject root  246 Jan 13 15:34 TestImageONLY
drwxrwxrwx.  2 fogproject root  266 Oct 13 14:57 VanillaUEFI
drwxrwxrwx.  2 fogproject root  246 Sep 14 15:39 VanillaUPD
drwxrwxrwx.  2 fogproject root  206 Mar  9  2022 Win10-21H2-Vanilla
drwxrwxrwx.  2 fogproject root  222 Dec 23  2021 Windows10-EDU-20H2-UEFI-Template
drwxrwxrwx.  2 fogproject root  206 Oct 12 12:18 Windows10-EDU-21H2-UEFI
drwxrwxrwx.  2 fogproject root  206 Oct 12 12:05 Windows10-EDU-21H2-UEFI-Template
drwxrwxrwx.  2 fogproject root  206 Jan 13 13:53 Windows10-EDU-22H2-UEFI
drwxrwxrwx.  2 fogproject root  206 Jan 13 13:41 Windows10-EDU-22H2-UEFI-Template
[root@d9fogserver ~]#

[lukebarone]

@Scootframer Hmmm… I’m not sure off the top of my head. I know I’ve seen this issue before, but I do not recall what the fix was.

[Scootframer]

@lukebarone Thanks for the all the assistance Luke. I am still able to deploy my images which is the most important thing. If you think of the solution let me know.

Thanks,
Scott

[Sebastian Roth]

@Scootframer So capturing an image has worked before just fine as we see from the images directory. It’s on a local LVM storage, XFS format. Does not look like something causing trouble in general.

What happens at this stage is simply a chmod -R 777 /images/a4bb6d84ebf4, so setting access rights to allow full access for everyone on this directory. I really have no idea why it would hang here. In the step “Preparing backup location” just before this one the directory is being created, which obviously does not hang or error out.

You might wanna try a debug capture (go to where you would schedule a normal task but in the last step you can tell to run in debug mode). Boot up the PC and hit ENTER twice to get to the shell. Then start the process by running the command fog and start stepping through it. Then just before the “Setting permission location” step you wanna stop the run via ctrl+c. Then run chmod -R 777 /images/a4bb6d84ebf4 and see if that’s returning or not.

[Scootframer]

@Sebastian-Roth Hi Sebastian,
I ran through the steps that you recommended I try. After hitting ctrl-c after the “preparing backup location” and typing in your chmod command it just leaves me with a blinking cursor on the next line. I tried to upload a pic of it but I just get an error on upload.

[Sebastian Roth]

@Scootframer Do you get anything in the server logs?

dmesg | tail
tail /var/log/syslog /var/log/messages
journalctl -f

[Scootframer]

@Sebastian-Roth
[root@d9fogserver ~]# dmesg | tail
[262168.127909] nfsd: peername failed (err 107)!
[262263.362858] nfsd: peername failed (err 107)!
[262524.491146] nfsd: peername failed (err 107)!
[262585.932952] nfsd: peername failed (err 107)!
[262592.077249] nfsd: recvfrom returned errno 104
[263814.772339] nfsd: peername failed (err 107)!
[264045.179522] nfsd: recvfrom returned errno 104
[264840.851890] nfsd: peername failed (err 107)!
[264957.591855] nfsd: peername failed (err 107)!
[265277.089716] nfsd: recvfrom returned errno 104
[root@d9fogserver ~]# tail /var/log/syslog /var/log/messages
tail: cannot open ‘/var/log/syslog’ for reading: No such file or directory
==> /var/log/messages <==
Mar 2 11:35:21 d9fogserver kernel: nfsd: peername failed (err 107)!
Mar 2 11:35:28 d9fogserver xinetd[24281]: START: tftp pid=10997 from=10.39.210.89
Mar 2 11:35:28 d9fogserver in.tftpd[10998]: Error code 8: User aborted the transfer
Mar 2 11:35:28 d9fogserver in.tftpd[10999]: Client 10.39.210.89 finished ipxe.efi
Mar 2 11:35:35 d9fogserver in.tftpd[11171]: Client 10.39.210.89 finished default.ipxe
Mar 2 11:36:00 d9fogserver rpc.mountd[27250]: authenticated mount request from 10.39.210.89:986 for /images (/images)
Mar 2 11:40:39 d9fogserver systemd: Created slice User Slice of root.
Mar 2 11:40:39 d9fogserver systemd-logind: New session 81 of user root.
Mar 2 11:40:39 d9fogserver systemd: Started Session 81 of user root.
Mar 2 11:40:41 d9fogserver kernel: nfsd: recvfrom returned errno 104
[root@d9fogserver ~]# journalctl -f
– Logs begin at Mon 2023-02-27 09:59:41 PST. –
Mar 02 11:35:28 d9fogserver.### in.tftpd[10998]: Error code 8: User aborted the transfer
Mar 02 11:35:28 d9fogserver.### in.tftpd[10999]: Client 10.39.210.89 finished ipxe.efi
Mar 02 11:35:35 d9fogserver.### in.tftpd[11171]: Client 10.39.210.89 finished default.ipxe
Mar 02 11:36:00 d9fogserver.### rpc.mountd[27250]: authenticated mount request from 10.39.210.89:986 for /images (/images)
Mar 02 11:40:39 d9fogserver.### sshd[16750]: Accepted password for root from 10.39.210.79 port 59689 ssh2
Mar 02 11:40:39 d9fogserver.### systemd[1]: Created slice User Slice of root.
Mar 02 11:40:39 d9fogserver.### systemd-logind[907]: New session 81 of user root.
Mar 02 11:40:39 d9fogserver.### systemd[1]: Started Session 81 of user root.
Mar 02 11:40:39 d9fogserver.### sshd[16750]: pam_unix(sshd:session): session opened for user root by (uid=0)
Mar 02 11:40:41 d9fogserver.### kernel: nfsd: recvfrom returned errno 104

[JJ Fullmer]

@Scootframer
I found some things on some of these errors that suggest stopping or restarting the nfs service on the server, that doesn’t seem like the best workaround, but could be something.
What pxe boot file are you using? Have you tried reverting to an older kernel or init? You can download the bzImage with a different name in the kernel downloader within the fog gui and then set the host you’re capturing to use the alternate test kernel (so you’re not changing the kernel that you know is working for deploying images). i.e. go download the previous kernel from what you last updated and name it bzImage-test and then on the host your capturing put bzImage-test in the hosts kernel field in the fog gui and redo the debug capture steps and see what happens.

Also, are you able to run the chmod command on the server (instead of from the client in the debug session)?

[Sebastian Roth]

@Scootframer said in Fog hangs while trying to upload:

[262168.127909] nfsd: peername failed (err 107)!
[262263.362858] nfsd: peername failed (err 107)!
[262524.491146] nfsd: peername failed (err 107)!
[262585.932952] nfsd: peername failed (err 107)!
[262592.077249] nfsd: recvfrom returned errno 104
[263814.772339] nfsd: peername failed (err 107)!
[264045.179522] nfsd: recvfrom returned errno 104
[264840.851890] nfsd: peername failed (err 107)!
[264957.591855] nfsd: peername failed (err 107)!
[265277.089716] nfsd: recvfrom returned errno 104

Yeah definitely restart your whole FOG server as suggested by @JJ-Fullmer as well.

[Scootframer]

@JJ-Fullmer I appreciate everyone’s assistance on this issue. We are due for a Server upgrade next month so we are going to put this issue on hold, wait till April and create a new Fog server.
I did download an older Kernel from Sept of last year and renamed as you recommended and had Fog use the alternate kernal for that client. Same issue happened. After doing the Upload Debug steps, ctrl+C and tried the chmod (tried on client and server) it said directory not found? What the heck?
Thanks again for all the great advice. I will keep you guys on speed-dial and hope not to need you when I create our new Fog server next month.

[Sebastian Roth]

@Scootframer Have you done a server reboot yet? From what I read this would fix the current issue you see.

[Scootframer]

@Sebastian-Roth Yes, first thing this am after reading my notifications I rebooted the server.

[Sebastian Roth]

@Scootframer Do I get this right? The issue persists even after the server reboot?

[Scootframer]

@Sebastian-Roth Indeed it does, gets stuck in the same spot. When I ran the chmod it said the directory didn’t exist.

[Sebastian Roth]

@Scootframer Maybe the server’s disk is failing? Have you checked the disk’s SMART bearings yet?