Opened 9 years ago

Closed 9 years ago

#777 closed incident (fixed)

HybridLeythenrode1 & 2 niet bereikbaar

Reported by: ed Owned by:
Keywords: Leiderdorp Cc:
Location: Generiek

Description

HybridLeythenrode1 & 2 niet bereikbaar via WL netwerk.

Change History (3)

comment:1 by ed, 9 years ago

Via buurnode in kunnen loggen en gezien dat Lvrouted door gebrek aan swap space is gestop.

ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
pid 1781 (named), uid 53, was killed: out of swap space
pid 1627 (lvrouted), uid 0, was killed: out of swap space
pid 5530 (python), uid 0, was killed: out of swap space
pid 5532 (python), uid 0, was killed: out of swap space
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)

HybridLeythenrode1# sh /usr/local/etc/rc.d/lvrouted status
lvrouted is not running.

HybridLeythenrode1# sh /usr/local/etc/rc.d/lvrouted start
WARNING: Flushing all existing DYNAMIC routes

HybridLeythenrode1# sh /usr/local/etc/rc.d/lvrouted status
lvrouted is running as pid 60263.

Toegevoegd in crontab zodat deze weer automatisch gestart wordt.

comment:2 by ed, 9 years ago

Functioneerd weer

comment:3 by ed, 9 years ago

Resolution: → fixed
Status: new → closed
Note: See TracTickets for help on using tickets.