Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Spam notification schedule task failed, only some users received the notificaiton

Created: 17 Dec 2012 | 2 comments
patriot3w's picture

We just upgraded from v9.0.1 to v10.0.1, other settings all ok but this spam notification task failed.

Tried to change to every one hour, but some users received after 2 hours.

Below is the error from the brightmail.log, any idea?

Thank you.

Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - --- Status Code: 100
Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - --- Status Message: The operation was successful
Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - --- Request ID: 1355741999803
Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - 
com.symantec.smg.controlcenter.internal.dataaccess.DataAccessException: An unexpected database error has occurred. Please contact your system administrator. ; nested exception is:
  java.sql.SQLException: Field 'report_connection_classes_address_id' doesn't have a default value
 at com.symantec.smg.controlcenter.reporting.ReportDAOImpl.updateStatistics(ReportDAOImpl.java:1234)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticManager.updateConnectionClassStatistics(StatisticManager.java:1323)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticManager.updateEngineStatistics(StatisticManager.java:318)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticAgentHelper.retrieveStatistics(StatisticAgentHelper.java:243)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticAgentHelper.retrieveStatistics(StatisticAgentHelper.java:128)
 at com.symantec.smg.controlcenter.agent.AgentManager.retrieveStatistics(AgentManager.java:202)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticTask.executeTask(StatisticTask.java:105)
 at com.symantec.smg.controlcenter.internal.scheduledtask.ScheduledTask.execute(ScheduledTask.java:133)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
 at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: java.sql.SQLException: Field 'report_connection_classes_address_id' doesn't have a default value
 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
 at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
 at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
 at com.mysql.jdbc.Connection.execSQL(Connection.java:3283)
 at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1332)
 at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1604)
 at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1519)
 at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1504)
 at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
 at com.symantec.smg.controlcenter.reporting.ReportDAOImpl.updateStatistics(ReportDAOImpl.java:1229)
 ... 9 more
Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - An agent error has occurred in the following code path:
java.lang.Exception
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticAgentHelper.retrieveStatistics(StatisticAgentHelper.java:256)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticAgentHelper.retrieveStatistics(StatisticAgentHelper.java:128)
 at com.symantec.smg.controlcenter.agent.AgentManager.retrieveStatistics(AgentManager.java:202)
 at com.symantec.smg.controlcenter.reporting.statistic.StatisticTask.executeTask(StatisticTask.java:105)
 at com.symantec.smg.controlcenter.internal.scheduledtask.ScheduledTask.execute(ScheduledTask.java:133)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
 at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Dec 17 2012 18:59:59 [BrightmailScheduler_Worker-1] ERROR - Cannot obtain data blob.

Discussion Filed Under:

Comments 2 CommentsJump to latest comment

Art_P's picture

The error you are showing is quite likely not related to your issue. The usual cause of quarantine notification failures is data transfer interference. This happens most often when the Control Center is sending messages to Microsoft Exchange implementations that have "tarpitting" or "backpressure" enabled.

The spam notification process attempts to complete in a single connection to the downstream MTA, with each message separated by a "NOOP" keepalive command. Some traffic monitors, such as tarpitting, cause a delay in the traffic or responses.

I recommend checking your installation for anything that may be causing severe delays to the spam notification transmission. For more information on this sitation, please refer to the following KB:

Quarantine notification process appears to be failing. Logs show 421 4.4.1 Connection timed out

http://www.symantec.com/business/support/index?page=content&id=TECH161742

If the KB above does not resolve your issue, I would recommend opening a case with Symantec Technical Support so they can help you check the health of your database. Even if the KB does resolve the issue, you may want to contact support at some point to check on the error you posted (but it is possible that the error may dissipate over time when reporting data is expired).

Regards,

Art

If you find a useful post, please use the "thumbs up" feature to mark the post as helpful. If your question has been answered, please select the "Mark as solution" for the post that best answered your question. Thank you.

patriot3w's picture

thanks. alreayd opened support case, just repaired the databse, hope the issue will be resolved.