Hello Diethmar,

so far i have not yet noticed something llike that, but if this is an issue, we have problem. 

During the last update, we updated the Bitdefender API.

It should now be bumped to version: 

BitDefender bdavserver version 3.3.2

If you execute this command on your SMG Server, you should be able to verify, which version your SMG service is using.

/opt/microfocus/smg/services/av-as/app/bdamserver -version

Besides checking the actual In-Use version, for troubleshooting purposes monitoring the API scans and results we get back from Bitdefender might be an option to check if the results are now 'worse' than with the older API.

Therefor you could enable a more verbose logging on the SMG-level. 

In the file bdasserver.conf, which you can find  below /opt/microfocus/smg/services/av-as/app directory there are logging options.

#PathLog=/opt/microfocus/smg/services/logs/bdas.log
PathLog=/vastorage/smg/services/logs/bdas.log
#PathLog=

# Enables debugging log. Grows up very fast, do not use for production!
#
LogDebug=1

# Enables scan request logging.
#
LogScanRequests=1

# Enables opening the log file in APPEND mode. Do not enable on NFS!
#
LogAppend=0

If you enable these 3 options, or 4 if you like appending on log-files, after a SMG-service restart via '$ service smg restart' you should get more information on what actually is communicated between SMG and the Bitdefender API and are able to see if there are communication-problems appearing.

Thank you,

Georg

Hello Diethmar,

so far i have not yet noticed something llike that, but if this is an issue, we have problem. 

During the last update, we updated the Bitdefender API.

It should now be bumped to version: 

BitDefender bdavserver version 3.3.2

If you execute this command on your SMG Server, you should be able to verify, which version your SMG service is using.

/opt/microfocus/smg/services/av-as/app/bdamserver -version

Besides checking the actual In-Use version, for troubleshooting purposes monitoring the API scans and results we get back from Bitdefender might be an option to check if the results are now 'worse' than with the older API.

Therefor you could enable a more verbose logging on the SMG-level. 

In the file bdasserver.conf, which you can find  below /opt/microfocus/smg/services/av-as/app directory there are logging options.

#PathLog=/opt/microfocus/smg/services/logs/bdas.log
PathLog=/vastorage/smg/services/logs/bdas.log
#PathLog=

# Enables debugging log. Grows up very fast, do not use for production!
#
LogDebug=1

# Enables scan request logging.
#
LogScanRequests=1

# Enables opening the log file in APPEND mode. Do not enable on NFS!
#
LogAppend=0

If you enable these 3 options, or 4 if you like appending on log-files, after a SMG-service restart via '$ service smg restart' you should get more information on what actually is communicated between SMG and the Bitdefender API and are able to see if there are communication-problems appearing.

Thank you,

Georg

Well, my server seems to be on current version. I will enable logging ...