cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

274
Views
15
Helpful
3
Replies
Highlighted
Beginner

CSCvr28018 - Emails to be quarantined, are delivered when DB is busy

Hi,

 

I'm facing the same issue with my CES SMA which is on 12.0.0-478.

Is there a solution? All mails will be delivered, so the whole quarantine process won't work!

 

Regards

Steffen

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Beginner

Re: CSCvr28018 - Emails to be quarantined, are delivered when DB is busy

Hi,

 

the error is fixed.

 

 

Here the solution from TAC:

 

 

Problem description:

SMA regularly got this error:

unable to quarantine MID 35 - quarantine system unavailable

 

Actions taken:

  • Checked the SMA logs and found every time that error was displayed, an AppFault was generated:

Critical: Quarantine:('egg/coro_postgres.py _quote_string|180', "<type 'exceptions.TypeError'>", 'expected string or buffer', '[egg/quarantine_hermes.py quarantine_message|3597] [egg/quarantine.py add_message|671] [egg/quarantine.py _get_quarantine_data|1939] [egg/quarantine.py _quote_list|2144] [egg/coro_postgres.py quote_string|171] [egg/coro_postgres.py _quote_string|180]')

 

Critical: unable to quarantine MID 35 - quarantine system unavailable

 

  • Checked the  mails logs on the  ESA, found when emails were flagged to be sent to the Outbreak Quarantine, the following entry was displayed:

11:50:31 2019 Info: MID 108 enqueued for transfer to centralized quarantine "None" (Outbreak rule Malware: Malware)

 

 

Findings:

Found this AppFault is caused because the ESA does not recognize the Outbreak quarantine as an existent quarantine.

In other words, this message is being sent to a quarantine that does not exist.

 

Actions taken:

Updated the internal backend configuration files to include the Outbreak quarantine.

 

Results:

AppFault disappeared, mail logs now show  the correct quarantine.

Info: MID 4649152 enqueued for transfer to centralized quarantine "Outbreak" (Outbreak rule Malware: Malware)

 

Why does this happen?

This problem is very rare, we have seen it when the migration of the quarantine was done, but  the feature key was not installed yet, or had expired.

 

 

 

 

Thanks TAC!

 

Regards

Steffen

View solution in original post

3 REPLIES 3
Beginner

Re: CSCvr28018 - Emails to be quarantined, are delivered when DB is busy

Hi,

 

the error still exists.

 

Fri Oct 11 16:19:38 2019 Critical: Quarantine: ('egg/coro_postgres.py _quote_string|180', "<type 'exceptions.TypeError'>", 'expected string or buffer', '[egg/quarantine_hermes.py quarantine_message|3597] [egg/quarantine.py add_message|671] [egg/quarantine.py _get_quarantine_data|1939] [egg/quarantine.py _quote_list|2144] [egg/coro_postgres.py quote_string|171] [egg/coro_postgres.py _quote_string|180]')


Fri Oct 11 16:19:38 2019 Critical: unable to quarantine MID 27 - quarantine system unavailable

 

 

Is there any news to solve the problem? Any workaround?

I got an other system with the exact same 12.0.0-478 version which is working.

 

 

Regards

Steffen

Beginner

Re: CSCvr28018 - Emails to be quarantined, are delivered when DB is busy

Hi all,

 

we upgraded the CES SMA to 12.5.0-648.

This version is also effected. Still no fixed version.

 

Regards

Steffen

Beginner

Re: CSCvr28018 - Emails to be quarantined, are delivered when DB is busy

Hi,

 

the error is fixed.

 

 

Here the solution from TAC:

 

 

Problem description:

SMA regularly got this error:

unable to quarantine MID 35 - quarantine system unavailable

 

Actions taken:

  • Checked the SMA logs and found every time that error was displayed, an AppFault was generated:

Critical: Quarantine:('egg/coro_postgres.py _quote_string|180', "<type 'exceptions.TypeError'>", 'expected string or buffer', '[egg/quarantine_hermes.py quarantine_message|3597] [egg/quarantine.py add_message|671] [egg/quarantine.py _get_quarantine_data|1939] [egg/quarantine.py _quote_list|2144] [egg/coro_postgres.py quote_string|171] [egg/coro_postgres.py _quote_string|180]')

 

Critical: unable to quarantine MID 35 - quarantine system unavailable

 

  • Checked the  mails logs on the  ESA, found when emails were flagged to be sent to the Outbreak Quarantine, the following entry was displayed:

11:50:31 2019 Info: MID 108 enqueued for transfer to centralized quarantine "None" (Outbreak rule Malware: Malware)

 

 

Findings:

Found this AppFault is caused because the ESA does not recognize the Outbreak quarantine as an existent quarantine.

In other words, this message is being sent to a quarantine that does not exist.

 

Actions taken:

Updated the internal backend configuration files to include the Outbreak quarantine.

 

Results:

AppFault disappeared, mail logs now show  the correct quarantine.

Info: MID 4649152 enqueued for transfer to centralized quarantine "Outbreak" (Outbreak rule Malware: Malware)

 

Why does this happen?

This problem is very rare, we have seen it when the migration of the quarantine was done, but  the feature key was not installed yet, or had expired.

 

 

 

 

Thanks TAC!

 

Regards

Steffen

View solution in original post

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here