SVN 3530 Download Issue (Partimage)
-
Quick question when anyone has time. I upgraded my fog unit to SVN 3530 from 1.2, and I noticed now after downloading an image, after it gets to about 5% the progress screen gets all wacked out and the imaging doesn’t finish. Below is a picture of the normal screen along with the screen it changes to at about 5%. I appreciate any help, Thanks!
-
The colors aren’t as strange but does this happen on every system or just that particular one.
-
Hi Tom,
Thanks for your quick response and sorry about the late reply. I will get back to you on the imaging issue here soon. I put the old .31 server back in place just for the time being because Apache keeps having issues. Computers in the network are unable to boot to PXE, so I just swapped the server for the time being. This has happened for a few days in a row now. I would get apache working, but it would eventually fail (I would come into work in the morning and computers would be having issues starting up because they were not able to PXE boot). I would get errors similar to the ones below.[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket '/var/run/mysq$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.69.85] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/fog/lib/db/MySQL.class$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.77.50] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket '/var/run/mysq$
[Mon Jun 08 10:37:42 2015] [error] [client 192.168.77.50] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 165Regarding the imaging issue, I just hooked up the SVN 3530 server in a separate network where I can troubleshoot apache and the imaging screen mentioned in the post. Apache seems to be working again. I will test a few different models to see if it’s just this one model that has that weird screen.
-
Just tested another model and got the same results.
-
@dustindizzle11 are they exactly the same?
-
@Tom-Elliott
It’s the same type of image. Some of the text looks different in spots.
-
So as some of you know, I’ve had some issues with FOG lately that I’ve mostly resolved by reformatting my Ubuntu FOG server and by reinstalling everything fresh. With that being said, I am now able to successfully upload and deploy new images to my FOG server.
BUT, I too, have this exact same issue reported on this thread on SVN 3537. It seems to ‘only’ occur with these legacy image settings:
Image Type: Single Disk - Resizable
Image Manager: PartImagePS: We still use the settings listed above for some legacy XP machines that were imaged that way. All other legacy “PartImage” images that are “Multi-partition - Single Disk” work just fine.
-
Is it at all possible to build a .32 fog server on some old desktop machine and quickly deploy these old images to the relevant hardware, and then upload those freshly imaged machines to a partclone image on the new FOG server???
-
Possible? Yes. Practical? Not really, since we have quite a few legacy models.
What I think I might do though is leave our old FOG 0.32 server running in case we need to use it for these specific legacy images.
Thanks again to everyone on the FOG team for all of the development and support you all do!
-
@crosser said:
Possible? Yes. Practical? Not really, since we have quite a few legacy models.
What I think I might do though is leave our old FOG 0.32 server running in case we need to use it for these specific legacy images.
Thanks again to everyone on the FOG team for all of the development and support you all do!
That’s a good choice. Sorry we couldn’t help more, but this issue is pretty bizarre.
