I’m prepping an update through git for the first time, I’ve always done it through svn before. I type in the commands: sudo -i
git clone https://github.com/FOGProject/fogproject.git /root/fogproject
This is the error I get: fatal: unable to access ‘https://github.com/FOGProject/fogproject.git/’: gnutls_handshake() failed: A TLS packet with unexpected length was received.
I did a search for some of these error’s but I didn’t find anybody referencing these error’s.
This was weird but I think it’s solved now. It didn’t matter which method I chose it would always give me the SAN error. I decided to reboot the server after current images finished. Then the error messages started to change. This now works with the REFINED_EFI method. I’m not sure why it didn’t want to update the method I chose but updating the server seemed to have kick what was stuck in it’s settings.
I have tried some yes. I’ve tried GRUB, EXIT, and REFINED_EFI. All of them, except REFINED_EFI give me the same error. REFINED_EFI tells takes me to it’s own menu where it basically says please press enter to reboot the machine.
I’ve seen many chainloading topics with UEFI but none of the solutions in those topics have helped resolve my situation that I’ve seen. Here is the situation. If I have an image prepped to either upload or download then the pc will see it and upload or download with no issues. If there is no image prepped to send then the chainloading error will occur. I error I get is “Boot from SAN device 0x80 failed: Error 0x3f142083”
“Could not boot: Error 0x3f142083”
“Could not boot: Error 0x3f142083”
Chainloading failed, hit ‘s’ for iPXE shell; reboot in 10 seconds.
That line does repeat twice on my screen. I don’t know what error logs to look at as to why this is happening. I just need some guidance on how I can resolve this issue.
The thing is though that the patch cable works on all the other machines. Could the NIC be bad? The DHCP part works, it’s just the TFTP that is timing out.
Just tried this. Unfortunately it still didn’t work. I even put a stick of ram in from another e5470 that imaged correctly.
BIOS looks to be correct on everything. Booth the NIC first and make sure pxe boot is enabled. I’ve had the same model of laptop (Latitude E5470) image with no issues. However some 5470’s are giving me this issue.
I have a weird issue that I’m wondering if anybody else has seen. On 99% of the machines I image I have no issues. However on the 1% of other machines get the PXE-E32 tftp timeout error. I can have the machine plugged into the same port as another machine that imaged without any issues, but the machine will still give me the PXE-E32 error. Has anybody else had this issue. My DHCP server already has option 66 and 67 loaded on it.
Here is the latest in my error logs:
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:04:35.841463 2016] [:error] [pid 26076] [client 172.52.8.7:58657] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 105, referer: http://172.28.2.21/fog/management/index.php?node=report&sub=host-list
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:03:19.508898 2016] [:error] [pid 22082] [client 172.52.8.7:58558] PHP Strict Standards: Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://172.28.2.21/fog/management/index.php?node=schema
[Fri May 27 12:03:19.218924 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.218895 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.133697 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.133666 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.030185 2016] [:error] [pid 22084] [client 172.24.8.30:50749] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in
I already rebooted the client. It just says:
Attempting to check in …failed
In line for 3:40
The in line for keeps increasing by 5.
@Tom-Elliott
I updated successfully, thank goodness, but I’m still failing to check in.
Fog says I’m currently on 5931. I rarely update FOG because every time I try to update it I need to have you hop on to my server for a couple hours to fix everything that broke with it. So I’m a little fearful to update it. I’m wondering why this suddenly happened when I made no changes to any files.
I have a really weird issue. Today after imaging perfectly fine all day my images are suddenly failing to start because the check in is suddenly failing. The error I get is:
Attempting to check in…failed
/bin/fog.checkin: line 66: sec2string: command not found
This just suddenly happened. I changed no files on the fog server for months so I don’t know why this happened. I did a search on my fog server for the file and found no trace of it. Any help would be appreciated.
I ran a new image after the update and the image log is still only showing the engineer as the one who is currently logged in. It didn’t properly reflect the user who created the image. This was after I updated to the latest version of FOG.
The latest version of FOG, SVN 4632 seems to have broken this again. It only displays the current logged on user and not the one who initiated the image.
I just updated fog to the latest svn, it has been a long while since I updated it since it was stable before. Now after the update when I try to log into fog I get this error. Fatal error: Class ‘System’ not found in /var/www/fog/commons/init.php on line 85
Any help would be greatly appreciated on this.
I found out what the issue was. Somebody on my team removed option 66 and 67 from our dhcp servers. So the network boot didn’t know where to look for any files.
I went through the entire wiki and I still have the issue. If I’m in windows I have no problem using the command prompt to tftp the undionly.kkpxe file. However when it tries to grab the file from boot up I get the “No boot filename recieved” error/
The tftp service is running. I’m not noticing any issues on that part. I have noticed as I have looked over my FOG config that I’m not finding the undionly.kkpxe file referenced anywhere. There used to be a dropdown setting that would allow me to pick it. It looks like that drop down doesn’t exist anymore. I’m wondering if that is the issue since we have our systems look for that file to pull.