User Tools

Site Tools


cluster:226

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cluster:226 [2025/10/02 18:05] – [CAs & Certs] hmeij07cluster:226 [2026/05/07 16:14] (current) hmeij07
Line 213: Line 213:
     * don't click http -> https s0 you don't get locked out     * don't click http -> https s0 you don't get locked out
     * Save and in popup box click "Restart Web Service"     * Save and in popup box click "Restart Web Service"
 +
 +==== Power Outage ====
 +
 +Cables are all on UPS for both controllers and storage yet this happened ...
 +
 +<code>
 +
 +New alerts:
 +* Backup Controller (A) - hpcm40eth0c1.wesleyan.edu had an unscheduled system reboot. The operating
 +system successfully came back online at Fri Dec 19 11:07:24 2025.
 +
 +</code>
 +
 +What's weirder is that both M40 controllers have the almost identical uptime but I only got an email about controller A reboot and B is now active ... maybe that is normal, but my other TrueNAS appliance, the X20, plugged into same UPS pdus remained up and uptime is 135 days.
 +
 +**Next prolonged outage look at power leds !!!**
 +
 +==== middlewared ====
 +
 +As the next step, we would recommend restarting the middleware service on the active controller to refresh the UI/reporting communication state.
 +
 +This can be performed through SSH using:
 +
 +service middlewared restart
 +
 +Please note that restarting middleware will temporarily interrupt access to the TrueNAS web interface while the service restarts. Replication tasks and middleware-managed services may also briefly interrupt during this process, however they should resume automatically once middleware finishes restarting. The controller itself will not reboot and storage services should remain online.
 +
  
 ==== Update 13 ==== ==== Update 13 ====
cluster/226.1759428315.txt.gz · Last modified: by hmeij07