Troubleshooting: Arculix RADIUS Configuration Change Not Applying

Follow
    Applies to:
  • Arculix
Deployment model:
  • Cloud
  • Version Affected: Arculix Radius
     
     

    Overview

    After making a configuration change to radius-agent-config.env, the new settings may not appear to apply, even after stopping and starting the radius-agent container in Docker.

     

    Cause

    Restarting the container is not enough to tell Docker to re-read the config file.

     

    Resolution:

    Instead of stopping and starting the radius-agent container, recreate it so the .env file is re-read:

    Navigate to the RADIUS Agent folder -- for example, /var/arculix/radius-agent -- so the Docker container loads properly using the YAML configuration file in that folder, then run:

    docker-compose down
    docker-compose up

    This forces the .env file to be re-read and the new setting to apply.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.