Was working prior to update, Image deployment

[Tom Elliott]

@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?

[EAHarvey]

@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?

[Tom Elliott]

@EAHarvey Yes.

[EAHarvey]

@Tom-Elliott Moved the kernal back to 4.4.2 and same result. Going to double check a different image real quick.

[EAHarvey]

@Tom-Elliott Tried a different older image with same result.

[Sebastian Roth]

@EAHarvey I am still wondering if there is something wrong with the inits. Can you please run a debug deploy for this client (normal deploy but tick “Schedule task as a debug task” just before you hit the button “CREATE DEPLOY TASK FOR …”). When you get to the shell run head -n 642 /usr/share/fog/lib/funcs.sh | tail -n 3 Please take a picture of what you see on the screen and post it here.

Then you can run the debug deploy job using the command fog. Now you need top step through hitting ENTER. When things go wrong you might fall back to the shell (or try getting back to the shell with Ctrl+c). Take a look at the logfile by cat /tmp/status.fog

This is not going to solve anything. I am just trying to gather more information on what could be causing the broken pipe… my understanding is that the pigz (parallel gzip) is crashing and therefore not delivering data to the pipe anymore. Just a guess though.

[EAHarvey]

@Sebastian-Roth

When I try and cat that /tmp/status it says no directory.

[Sebastian Roth]

@EAHarvey Thanks for the picture. Seams like your inits are fine. Not sure why it says line 641 (maybe the beginning of that function although this does not make sense to me…)?!

When I try and cat that /tmp/status it says no directory.

Tried after partimage crashed?

[EAHarvey]

@Sebastian-Roth yes. right after i got the error I ctrl-c and ran the command. So is there a way to svn back down to the previous version or is it just step forward?

[EAHarvey]

After working with @Sebastian-Roth we discovered it was the latest init files that were causing my problem. I was able to copy the init files from a backup folder and all is working correctly. I am going to test the other backup builds to see where the error starts. I will post back here with what I find.

[EAHarvey]

Just wanted to update. I have been busy here at work so I have not been able to do anymore testing on the init files. So sorry for the delay.