Conversation

Notices

1. moved_sdf_NYbill (movedsdfnybill@sn.gunmonkeynet.net)'s status on Friday, 01-Apr-2016 19:03:16 UTC moved_sdf_NYbill

   • @mcscx@quitter.se
   • kaligule
   @mcscx @kaligule Yes, Linode moved our rack to a new hardware. Since then, Mediagobin has been crashing. I'll have time to look into things this weekend.
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Friday, 01-Apr-2016 19:18:26 UTC @mcscx@quitter.se

     in reply to
     @nybill new hardware leading to crashes of just Mediagoblin but leaving alone the rest sounds interesting
   • moved_sdf_NYbill (movedsdfnybill@sn.gunmonkeynet.net)'s status on Friday, 01-Apr-2016 19:45:56 UTC moved_sdf_NYbill

     in reply to

     • @mcscx@quitter.se
     @mcscx Mediagoblin is the last thing running on that Linode. The rest is migrated to a Digital Ocean instance. MG is going to be a bear to move! Maybe I should just take this time to do it. The logs say MongoDB was shutdown unclean. Then exits.
   • moved_sdf_NYbill (movedsdfnybill@sn.gunmonkeynet.net)'s status on Friday, 01-Apr-2016 20:39:43 UTC moved_sdf_NYbill

     • @mcscx@quitter.se
     @mcscx I'm sure during the migration there was an unclean reboot.
   • moved_sdf_NYbill (movedsdfnybill@sn.gunmonkeynet.net)'s status on Saturday, 02-Apr-2016 12:28:10 UTC moved_sdf_NYbill

     • Wolfgang Romey
     @hier oof, don't ask. A early version. This is why I'll be having so much trouble migrating it. I missed the MongoDB DB conversion script along the way somewhere. I'm going to have to back up the DB, install an early version on the new server, restore the DB, then slowly upgrade to current.