[SAC] [OSGeo] #2318: dronie.osgeo.org is down (502 Bad Gateway)

[OSGeo]

#2318: dronie.osgeo.org is down (502 Bad Gateway)
---------------------------+---------------------------------------
 Reporter:  strk           |       Owner:  sac@…
     Type:  task           |      Status:  new
 Priority:  blocker        |   Milestone:  Sysadmin Contract 2019-I
Component:  Systems Admin  |  Resolution:
 Keywords:                 |
---------------------------+---------------------------------------

Comment (by robe):

 I was able to stop the dronie-server container by killing the process
 attached to it.


 {{{
 ps -faux | grep dronie-server
 }}}

 There still seems to be something clinging to the name though because when
 I tried to do


 {{{
 lxc mv dronie-server dronie-server-bad #went fine

 #get into the container
 lxc exec dronie-server-2 bash
 #in dronie-server-2 force graceful shutdown
 shutdown -P -H now

 #now back in osgeo7
 lxc mv dronie-server-2 dronie-server # went fine

 #but this failed
 lxc start dronie-server

 #so I had to rename it back to
 lxc mv dronie-server dronie-server-2
 }}}

 As far as data the data asof the 6/9 snapshot is fine.  I suspect if I
 went with the 6-11 snapshot I would see the data there too.


 I feel like the server needs to be rebooted (since it does say system
 restart required).

 So there could be an underlying funkiness with the network causing this
 that rebooting will resolve.

 Now is not a good time to bring everything down for this though as other
 things are working fine.

 Once we get osgeo4 reformatted, we'll be in much better condition as we
 can replicate containers between the two and this server really should be
 moved to the new osgeo4.

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2318#comment:15>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.