Confirmed users
1,364
edits
CIDuty/Reconfigs: Difference between revisions
updated for location of cron driven update log files
(updated for location of cron driven update log files) |
|||
| Line 66: | Line 66: | ||
= Help, my reconfig failed! = | = Help, my reconfig failed! = | ||
Assuming you're using the end_to_end_reconfig.sh script, you can resume after fixing the error. Errors and exit state can be found in the manage_masters-##########.log which is created in /tmp/reconfig by default. | Assuming you're using the end_to_end_reconfig.sh script, you can resume after fixing the error. Errors and exit state can be found in the manage_masters-##########.log which is created in /tmp/reconfig by default. The hourly auto reconfig logs are in the bb dir as <tt>reconfig.{log,lock}</tt>. | ||
Running the script again will yield the following menu: | Running the script again will yield the following menu: | ||
| Line 80: | Line 80: | ||
Reconfigs can take as little as 30 minutes to run, but can take up to 2 hours depending on how busy the systems are. | Reconfigs can take as little as 30 minutes to run, but can take up to 2 hours depending on how busy the systems are. | ||
In general, linux test masters are the slowest to reconfig. You can tail the manage_masters-##########.log to keep up with progress. By default, this log is created in /tmp/reconfig. | In general, linux test masters are the slowest to reconfig. You can tail the manage_masters-##########.log to keep up with progress. By default, this log is created in /tmp/reconfig. The hourly auto reconfig logs are in the bb dir as <tt>reconfig.{log,lock}</tt>. | ||
If the reconfig gets stuck, see [[ReleaseEngineering/How_To/Unstick_a_Stuck_Slave_From_A_Master|How To/Unstick a Stuck Slave From A Master]]. | If the reconfig gets stuck, see [[ReleaseEngineering/How_To/Unstick_a_Stuck_Slave_From_A_Master|How To/Unstick a Stuck Slave From A Master]]. | ||