Project:
| View Revisions: Issue #38506 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0038506: Do not transition to offline if there are sync errors, then stay in special state which does limited whitelisting | ||
| Revision | 2018-06-12 12:33 by mtaal | ||
| Description | When the ss is online and cs has sync errors there are specific conditions: - some non-white listed services are still forwarded to cs, these are the ones which can not run in offline mode. - do not transition to offline eventhough it is requested by the code When the SS starts and there exist sync errors from the start then do not start in offline mode, but start in online mode. When starting and seeing that there are version differences and also sync errors, even then do not go offline |
||
| Revision | 2018-05-10 15:36 by mtaal | ||
| Description | When the ss is online and cs has sync errors there are specific conditions: - some white listed services are still forwarded to cs, these are the ones which can not run in offline mode. - do not transition to offline eventhough it is requested by the code When the SS starts and there exist sync errors from the start then do not start in offline mode, but start in online mode. When starting and seeing that there are version differences and also sync errors, even then do not go offline |
||
| Revision | 2018-05-08 22:55 by mtaal | ||
| Description | When the ss is online and cs has sync errors there are specific conditions: - some white listed services are still forwarded to cs, these are the ones which can not run in offline mode. - do not transition to offline eventhough it is requested by When the SS starts and there exist sync errors from the start then do not start in offline mode, but start in online mode |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |