Version Affected: Arculix Radius
Description:
After making a configuration change to radius-agent-config.env the settings don't appear to apply despite stopping and starting the radius-agent in docker
Cause:
Restarting is not enough to tell docker to read the config file
Resolution:
Instead of stopping and starting the Radius-Agent in Docker, run the following commands to recreate the Docker Container.
Navigate to the directory where
docker-compose down
docker-compose up
This will force the .env to be read and the new setting to apply.
Note: Make sure you are in the RADIUS Agent folder when running the docker-compose commands so that the Docker Container loads properly using the YAML configuration file in said folder.
Eg. /var/arculix/radius-agent
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.
Comments
Please sign in to leave a comment.