View Single Post
Old 02-14-2015, 08:37 AM   #79
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@ssholloway: That's... strange. If you got MRPI's UI restart with the visual feedback, there should definitely be something in the logs, and, moreover, the other .bin should definitely have been processed (it really does 'move on', on a package failure, not completely abort everything ). That, and the staging directory would also have been removed.

My best guess is either the Kernel's OOM killer and/or the watchdog took over, and somewhere along the line a hard-reboot was triggered. That you saw the "Package script failed (1), moving on . . . " doesn't really track with that though... :/

Anyway, I'd highly recommend that you reinstall Python from the snapshots, because there's a very good chance your Python install is inconsistent .

Last edited by NiLuJe; 02-14-2015 at 08:41 AM.
NiLuJe is offline   Reply With Quote