MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9
Posted: 26 Mar 2017 07:45
Hello,
i updated 3 of our EFA this night, but i did not make a snapshot and 1 of them did a error
Right after the update, here is the error message i received :
Installed:
mod_evasive.x86_64 0:1.10.1-10.el6
mod_security.x86_64 0:2.7.3-3.el6
mod_security_crs.noarch 0:2.2.6-3.el6
mod_security_crs-extras.noarch 0:2.2.6-3.el6
Complete!
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
3.0.1.9 update is complete
All done
Please restart your system as soon as possible.
If your system does not return to a command prompt
you can now safely press ctrl-c to abort logsave
Thank you for using E.F.A.
Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 28.
) at /usr/share/MailScanner/perl/MailScanner/Config.pm line 1053
Press [Enter] key to continue...
So i thinked that the update can't be that bad, i rebooted the EFA.
But i notice now that this error message comes back again this night :
/var/log/maillog:Mar 26 05:34:45 mx3 MailScanner[15866]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 73.
/var/log/maillog:Mar 26 06:50:01 mx3 MailScanner[27397]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 67.
/var/log/maillog:Mar 26 07:52:33 mx3 MailScanner[6022]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 48.
/var/log/maillog:Mar 26 09:06:12 mx3 MailScanner[18676]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 82.
I did a (fast) compare of the MySQL tables, can't find a 'rblspamreport' ...
Is there a way to fix this ?
Also i noticed that the Recent Messages are not updated with the last emails. The new emails seems to come in, filtered and sended to the servers, it seems that it's only the MailScanner display that is not updated by the new emails.
Is this related to the MySQL error ?
Thanks for any help
Best regards
i updated 3 of our EFA this night, but i did not make a snapshot and 1 of them did a error
Right after the update, here is the error message i received :
Installed:
mod_evasive.x86_64 0:1.10.1-10.el6
mod_security.x86_64 0:2.7.3-3.el6
mod_security_crs.noarch 0:2.2.6-3.el6
mod_security_crs-extras.noarch 0:2.2.6-3.el6
Complete!
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
3.0.1.9 update is complete
All done
Please restart your system as soon as possible.
If your system does not return to a command prompt
you can now safely press ctrl-c to abort logsave
Thank you for using E.F.A.
Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 28.
) at /usr/share/MailScanner/perl/MailScanner/Config.pm line 1053
Press [Enter] key to continue...
So i thinked that the update can't be that bad, i rebooted the EFA.
But i notice now that this error message comes back again this night :
/var/log/maillog:Mar 26 05:34:45 mx3 MailScanner[15866]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 73.
/var/log/maillog:Mar 26 06:50:01 mx3 MailScanner[27397]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 67.
/var/log/maillog:Mar 26 07:52:33 mx3 MailScanner[6022]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 48.
/var/log/maillog:Mar 26 09:06:12 mx3 MailScanner[18676]: Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBD::mysql::st execute failed: Unknown column 'rblspamreport' in 'field list' at /usr/share/MailScanner/perl/custom/MailWatch.pm line 189, <CLIENT> line 82.
I did a (fast) compare of the MySQL tables, can't find a 'rblspamreport' ...
Is there a way to fix this ?
Also i noticed that the Recent Messages are not updated with the last emails. The new emails seems to come in, filtered and sended to the servers, it seems that it's only the MailScanner display that is not updated by the new emails.
Is this related to the MySQL error ?
Thanks for any help
Best regards