Was working prior to update, Image deployment
-
Boom!!
-
@EAHarvey Good catch!! This is weird, why does it say “line 641” when there is no call to pigz/partimage on line 641 (but line 658) in funcs.sh?!? Can you please run
ls -al /var/www/fog/service/ipxe/init*on your FOG server and post the (full) output here? How do you upgrade to the latest version? Updating from the repo and then re-running the installer??As well please show us the output of
file /images/COMMPC/d1p1.img* -
@EAHarvey Do you see the this on all of your EeePCs or just a single one? Possibly a faulty memory chip if you only have that issue on one machine.
-
@Sebastian-Roth All.
-
-
@EAHarvey Are you 100% sure this is a partimage image?
-
@Tom-Elliott As far as I know yes. It was made with partimage back when we were running .032. I swapped the setting to partclone and it said it was not a partclone image. Its is the same image we’ve been using and imaging with.
-
I was looking into the folder structure for the file—>>>>>/usr/share/fog/lib.
There is no such directory. hmm strange. So it’s trying to call a location that may not be there?
-
@EAHarvey Where are you looking for that structure?
-
@Tom-Elliott It was in the error pic that i uploaded.
-
@Tom-Elliott Do you have an idea why it would say line 641 in funcs.sh???
-
@EAHarvey Yes, but those scripts are included in the initrd image file that boots up your client when your upload or deploy an image. Those scripts don’t exist on your FOG server installation. Well they do exist in the repository path you checkout when you upgrade your FOG installation. Not sure if this explanation is of any help to you. More or less complicated when you start looking into the details of FOG. You should not need to worry about this. Was trying to get Tom’s thoughts on what is going on here. As I can see from the listings you posted the init files seam to be new (date March 1st). Still confuses me.
-
Looks like svn was updated to 4915. ok to give it a try?
-
@EAHarvey yes please
-
@Tom-Elliott testing now.
-
@Tom-Elliott Same error. segment fault changed to 3291 from 3290.
-
@Tom-Elliott heading out for the day. I will check back in the morning. Thanks for all the help.
-
@EAHarvey seeing as this worked then suddenly stopped I wonder if you have another old image available to test with?
-
@Tom-Elliott also, if possible I did update the kernel today so maybe something in it is causing this issue? Try using an older kernel maybe?
-
@Tom-Elliott I have that image and another called asusioncommpc. I pretty sure I already tried that but i will try again this morning.
The kernel issue, I can just go through the GUI and change it to an earlier version?
