#2333: osgeo7 /proc/uptime not working on containers
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2019-II
Component: Systems Admin | Keywords:
---------------------------+---------------------------------------
jef just noticed
{{{
cat /proc/uptime
}}}
doesn't work on containers
Gives error:
{{{
cat: /proc/uptime: Transport endpoint is not connected
}}}
I suspect this might be just a result of lxd autoupgrade to 3.15
The server is asking for a reboot. I'll reboot this weekend and retest
and if still an issue will investigate further. My test lxd host which is
running 3.15 is fine, but I recently rebooted it.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2333>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2333: osgeo7 /proc/uptime not working on containers
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2019-II
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+----------------------------------------
Comment (by robe):
I just noticed rebooting each container would probably work too.
I just rebooted the wordpress-dev container by logging into it and
triggering a reboot.
Before that it had the issue and after it was fine.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2333#comment:1>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2333: osgeo7 /proc/uptime not working on containers
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2019-II
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+----------------------------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
Comment:
This was resolved a couple weeks ago after rebooting osgeo7
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2333#comment:2>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.