ConfigServer Community Forum

That means that it didn't get a response from the clamd socket that you pointed cxs at. Did you install ClamAV and get clamd running? Is clamd running? Does the socket exist at that location?

Changes:

• Modified licensing to allow for NAT'd IP addresses
• Improved messaging for invalid licenses
• Fixed problem with UI --options default not being saved correctly
• Fixed problem with --background being applied to all functions, not purely scans

Try it again and it should be OK now.

Could you log a ticket with access details for one of the affected servers and I'll have a look?

Changes: Sort user list in UI Modified UI upgrade code to detect completion instead of using a timeout to help prevent incomplete upgrades Additional regex tests added Added multiple delete code in Quarantine View Fixed duplicate/incorrect entries showing in "Other Files" Sort "Other ...

What do you see from shell with:

cxs -V

What is the output from:

cxs -U

Do these pure-ftpd problems seem to have cleared up now?

Changes: Terminate cxs with the options display if there are options errors Added timout to UI cxs upgrade - this will only apply to upgrades made after this release Continue scanning file content if script file and --noscript Added UI option "Other Files" to view/edit files cxs.ignore, cx...

I'll put a timeout in the upgrade option. It seems to be related to the new restart of pure-ftpd

Just follow the installation procedure again. No need to uninstall first.