Warning: Undefined array key "DOKU_PREFS" in /usr/share/dokuwiki/inc/common.php on line 2082
cluster:194 [DokuWiki]

DokuWiki

User Tools

Site Tools

Trace:
cluster:194

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
cluster:194 [2020/06/17 10:10]
hmeij07 [Update] 		cluster:194 [2020/08/17 09:40]
hmeij07 [Update]
Line 352: Line 352:
 ==== Update ==== ==== Update ====
  
-Change the Train to 11.3, then you will apply the update first in the WebUI to the passive controller. +**Change the Train** to 11.3, then you will apply the update first in the WebUI to the passive controller. 
  
 After its reboots, you will failover to it by **rebooting** the Active controller (the **current** WebUI).  After its reboots, you will failover to it by **rebooting** the Active controller (the **current** WebUI). 
Line 364: Line 364:
 Enable HA, click icon Enable HA, click icon
  
-Apply Pending Updates+**Apply Pending Updates**
 Upgrades both controllers. Files are downloaded to the Active Controller and then transferred to the Standby Controller. The upgrade process starts concurrently on both TrueNAS Controllers. Upgrades both controllers. Files are downloaded to the Active Controller and then transferred to the Standby Controller. The upgrade process starts concurrently on both TrueNAS Controllers.
  
-Server responds while HA disabled.  Fail over just take 5 seconds. Update takes 15 mins. Log out and log back in once the passive standby is on new update.+Server responds while HA disabled.  You are instructed to Initiate Fail Over, do so, just take 5 seconds. The Continue with pending upgrade ... wait 5 mins or so, watch console activity.  **THEN** Log out and log back in once the passive standby is on new update. 
 + 
 +Update takes 15 mins in total. 
  
 ==== HDD ==== ==== HDD ====
Line 395: Line 397:
  
 </code> </code>
 +
 +==== Logs ====
 +
 +From support:
 +
 +That information is logged via syslog for the opposite controller. For example, to find the information I did here, I looked in the syslog output on the controller that was passive at the time these alerts occurred.
 +
 +You can look that information up yourself by opening an SSH session to the passive controller, navigating to the /root/syslog directory and examining the files. The "controller_{a,b}" file shows the output for today. Extract the controller_a.0.bz2 file and read the output of the resulting controller_a.0 file to see the output for yesterday. controller_a.1 would contain the output for the day before yesterday, and so on.
 +
  
  
cluster/194.txt · Last modified: 2024/01/03 13:50 by hmeij07

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki