000034048 - Identity router status changed to distressed after reboot in RSA SecurID Access

Document created by RSA Customer Support Employee on Sep 22, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034048
Applies ToRSA Product Set: SecurID Access
RSA Product/Service Type: Identity Router
 
IssueThe Identity router status changed to distressed just after performing a reboot.
CauseAn invalid static route was added on the Identity router.
The below message can be seen in the symplified.log 
2016-09-19/13:42:29.183/UTC [ServiceMonitor] WARN  com.symplified.service.shared.manager.ServiceMonitor[178] - Failed to start bootstrapService since Mon Sep 19 13:36:35 UTC 2016 (353 seconds), retrying..., cause: com.symplified.service.shared.StateChangeException: Unable to start service: bootstrapService [at com.symplified.service.shared.AbstractStatefulService.start(AbstractStatefulService.java:72)], Caused by java.lang.RuntimeException: Failed to apply custom rules [at com.symplified.service.appliance.network.Routing.resetRouting(Routing.java:112)], Caused by java.lang.RuntimeException: Problem applying custom route [/sbin/ip route add 10.10.10.10/32 dev eth0 via 10.05.5.5 table custom]: Error: an inet address is expected rather than "10.05.5.5".

 
Resolution1. In the Administration Console, click Platform > Identity Routers.
2. Next to the identity router name, select Edit.
3. Click Next Step to access the Settings page.
4. In the Static Routes section, correct the invalid route
5.. Click Next Step.
7. Click Save and Finish.
8. Click Publish Changes.
 

Attachments

    Outcomes