cluster:226
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cluster:226 [2025/12/22 14:28] – [Update 13] hmeij07 | cluster:226 [2026/05/07 16:14] (current) – hmeij07 | ||
|---|---|---|---|
| Line 225: | Line 225: | ||
| </ | </ | ||
| + | |||
| + | 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/ | ||
| + | |||
| + | 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.1766413738.txt.gz · Last modified: by hmeij07
