Hi I have just provisioned a brand new server, all yum updated and vanilla fresh.

Upon putting on ASL, I have noticed that all the options I selected in configuration are not replicated within the ASL screen.

I have rebooted the server just to be sure that everything that needs to clicks and assumes position but

I have installed ASL a good number of time but have seen this twice.

Is their anything that could cause this to happen - Im finding my experience with ASL becoming a little bit frustrating and expensive

Any help on this is appreciated.

Its all the same config file, /etc/asl/config

I have the same or similar problem with a fresh installation of ASL in a VZ-Container.

Configuration-Changes are not saved, regardless whether via asl -c or the web-gui.

I entered PHP_CHECKS="yes" manually, ran asl -f -s and then to verify asl -c again.
But several entries for php-Functions are not mentioned in the file. asl -c just lists them with empty default.

Any tips on how to solve this?

kind regards -Stephan

Great - so I am not going mad !!

Scott, I edited the config file but the ASL GUI still shows incorrectly + I am not sure if it is even reading correctly or if ASL is even doing its just and protecting my systems.

Its a little bit worrying as I purchased ASL for peace of mind but Im a little bit rattled

New problem in addition is the below :

asl --force-update
Checking for updates..
Updating ASL: successful [OK]
Updating APPINV to 201201041122: updated [OK]
Updating CLAMAV to 201205151137: updated [OK]
Updating GEOMAP to 201205161104: updated [OK]
Updating MODSEC to 201205161106: updated [OK]
Updating Anti-Spam Protection: updated [OK]
Updating Attack Protection: updated [OK]
Updating Dataloss Protection: updated [OK]
Updating Malware Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
Updating Shell Protection: updated [OK]
tortixd: Could not reliably determine the server's fully qualified domain name, using xxx.xx.xxx.xxx for ServerName
Updating OSSEC to 201205091009: updated [OK]
Updating Self Healing modules: updated [OK]
Updating Brute Force Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
: command not foundne 11:
: command not foundne 12:
: command not foundne 17:
: command not foundne 33:
: command not foundne 46:
: command not foundne 52:
: command not foundne 98:
: command not foundne 99:
: command not foundne 100:
: command not foundne 110:
: command not foundne 111:
: command not foundne 117:
: command not foundne 137:
: command not foundne 138:
: command not foundne 186:
: command not foundne 187:
: command not foundne 222:
: command not foundne 234:
: command not foundne 238:
: command not foundne 239:
: command not foundne 248:
: command not foundne 251:
: command not foundne 255:
: command not foundne 258:
touch: cannot touch `/var/asl\r/data/updates-data': No such file or directory
/data/security-modules: No such file or directory
/data/updates-data: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/updates-data: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/updates-data: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/updates-data: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/security-modules: No such file or directory
/data/test*db: No such file or directory
/data/test*db: No such file or directory
/data/test*db: No such file or directory
/data/test*db: No such file or directory
/data/vulnerability-data: No such file or directory
/data/vulnerability-data: No such file or directory
/data/vulnerability-data: No such file or directory
/data/vulnerability-data: No such file or directory
/data/vulnerability-report.html: No such file or directory
/data/test*db: No such file or directory

Not sure whats going on with my install of ASL.

I did ask in a support ticket if support could have a look and install as something is amiss with this as it used to install smoothly all the time

Does anyone have an idea what is going on ?

Yeah, you must have edited the file in something that linux doesnt like, see this?

"/var/asl\r" <- that \r isnt valid

Thats the thing the file was edited through plesk - but the path sections were not touched.

Do you have any ideas on why config does not stick / reflect in the GUI ie ?

Not really, I can tell you that \r isnt a valid character and linux wouldnt normally let you create one.

If you manually edited the /etc/asl/config file, or used some tool to do that then you need to reinstall ASL. We do not support manually editing of that file.

Hi Mike,

I was just following on from the below.



What is the recommended way to edit the file, taking into account my configuration was not syncing with the parameters set whilst installing initially, in the same fashion as stephan-zrh.

If there is a point of reference in relation to editing the config file would appreciate any pointers.

The weird thing with this all is I have had ASL working on multiple servers with no problems so these new niggles are frustrating to say the least

Thanks for the follow up question, use the ASL gui to change those settings - but since the file is corrupt somehow thats not going to work for you. Any sorts of typos, weird meta characters, etc. from an editor or another tool will definitely cause all sorts of havoc with the file. Its got to be clean to parse correctly.

If this only happened on one host, then I think its safe to say something corrupted the file. The easiest way to fix this is to run the installer again.

Hi Mike,

I appreciate you taking the time to respond.

Does the uninstall function /var/asl/lib/uninstall 100% remove all traces of a previous ASL installation or are their some extra steps one can take to completely remove all traces of ASL and then reinstall again ?

It should, but because the config file is munged its possible it might miss something. So after you run the uninstaller, delete your entire /etc/asl directory as thats really what you need to wipe out and ensure the installer replaces.

rm -rf /etc/asl

You can run the installer over and over again safely, but in your case because of the weirdness with your config file I'd start with a clean slate.

Mike thanks for that I will try that route and see fi that helps.

Will keep you posted

OK- I uninstalled - > REBOOTED SERVER -> INSTALLED - > Configured through the installer and still the options I select in the installer do not reflect in the GUI.

Apart form the asl folder, is it possible shrapnel is left over in the database for ASL.

If so what the easiest ( read layman's ) method of completely removing ASL from the system / database so its as if it had never been installed ?

Do you happen to have the output from the installer handy? And would it be possible to log onto your system and see whats going on? If we can log in, please follow this process to provide us with access:

https://www.atomicorp.com/wiki/index.ph ... _system.3F