[Ace] [Controls_dept] Advise on rebooting all console servers

[Gary Croke]

We usually discover several console problems in the lead up to, or in the early stages of a run.  We either realize we can't connect to a console, or look for information in the logs that isn't there because the console stopped logging at some point.  I think anything that can be done to reduce instances of these problems is definitely worthwhile.  If it's not easy to monitor the console servers, the proactively rebooting periodically sounds like a good idea to me.

________________________________
From: Controls_dept <controls_dept-bounces at jlab.org> on behalf of Anthony Cuffe <cuffe at jlab.org>
Sent: Friday, July 1, 2022 2:29 PM
To: controls_dept at jlab.org <controls_dept at jlab.org>; ace at jlab.org <ace at jlab.org>
Subject: [Controls_dept] Advise on rebooting all console servers

I would like to setup a task to reboot all console servers on a regular schedule.  This would be to address things like port hang ups.  I propose doing this once a month on a Weds at around 5am.  This way, the chances of anyone using one would be minimal and if a console server does not reboot properly, one of us can address it when we arrive in the morning.

Any suggestions or comments?


--
=========================
  Anthony Cuffe
  voice  : 757 269-6213
  e-mail : cuffe at jlab.org
=========================
_______________________________________________
Controls_dept mailing list
Controls_dept at jlab.org
https://mailman.jlab.org/mailman/listinfo/controls_dept
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/ace/attachments/20220701/b3b141dc/attachment-0001.html>