ASL 4.0.2 - Invalid configuration values detected

Customer support forums for Atomic Protector (formerly Atomic Secured Linux). There is no such thing as a bad question here as long as it pertains to using Atomic Protector. Newbies feel free to get help getting started or asking questions that may be obvious. Regular users are asked to be gentle. :-)
imadsani
Forum Regular
Forum Regular
Posts: 112
Joined: Mon Sep 16, 2013 10:10 am
Location: Lahore

ASL 4.0.2 - Invalid configuration values detected

Unread post by imadsani »

Getting the following popup on two servers, one is freshly upgraded from 4.0.1 and the other is a clean install to 4.0.2, and btw typo with Invalid

Code: Select all

Invliad configuration values detected.
The following will be set to their defaults if configuration is saved from ASL Web:

UPDATE_TYPE
	current / default: off / all
	allowed: all | rules-only | exclude-kernel

CLAMAV_LogFileMaxSize
	current / default: 0 / 0
	allowed: 1m | 10m | 100m

CLAMAV_MaxFileSize
	current / default: 25m / 25M
	allowed: 0 | 10M | 25M | 50M | 100M | 250M | 500M
Second issue: some event issue windows are blank, same issue on both servers

http://i1196.photobucket.com/albums/aa4 ... 584a63.jpg
jgodwin
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 39
Joined: Mon Sep 14, 2009 12:15 pm

Re: ASL 4.0.2 - Invalid configuration values detected

Unread post by jgodwin »

UPDATE_TYPE needs to be set to one of the listed allowed values. Disabling should be done by setting AUTOMATIC_UPDATES to "none"

CLAMAV_LogFileMaxSize - fix for this erroring when set to its default value has been committed and will be in our next release

CLAMAV_MaxFileSize - case matters, set to "25M"

Invliad - fixed in next release

Event details - fixed in next release. This effects events where the source ip is currently blocked.
imadsani
Forum Regular
Forum Regular
Posts: 112
Joined: Mon Sep 16, 2013 10:10 am
Location: Lahore

Re: ASL 4.0.2 - Invalid configuration values detected

Unread post by imadsani »

jgodwin wrote:UPDATE_TYPE needs to be set to one of the listed allowed values. Disabling should be done by setting AUTOMATIC_UPDATES to "none"
Thank you for the reply, regarding Update_TYPE, I selected none during the install process.
Post Reply