MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Report bugs and workarounds
Post Reply
anti-spam
Posts: 34
Joined: 06 Oct 2015 14:32
Contact:

MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by anti-spam » 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
:arrow: always fighting spams ... :hand:

User avatar
shawniverson
Posts: 2080
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by shawniverson » 26 Mar 2017 09:19

Try this:

Code: Select all

wget https://raw.githubusercontent.com/mailwatch/1.2.0/develop/upgrade.php
sudo /usr/bin/php ./upgrade.php
Version 3.0.2.1 released! Update now to keep your eFa secure!

anti-spam
Posts: 34
Joined: 06 Oct 2015 14:32
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by anti-spam » 26 Mar 2017 09:44

hi,

thanks a lot for your fast answer.
Here is the result of your script :

Checking conf.php configuration entry:

- All mandatory entries are present.................................. OK
- All obsolete entries are already removed........................... OK
- optional RPC_PORT ................................................. WARNING
- optional RPC_SSL .................................................. WARNING
- optional RPC_REMOTE_SERVER ........................................ WARNING
- optional LDAP_BIND_PREFIX ......................................... WARNING
- optional LDAP_BIND_SUFFIX ......................................... WARNING
- optional EXIM_QUEUE_IN ............................................ WARNING
- optional EXIM_QUEUE_OUT ........................................... WARNING
- optional PWD_RESET_FROM_NAME ...................................... WARNING
- optional PWD_RESET_FROM_ADDRESS ................................... WARNING
- optional MAIL_SENDER .............................................. WARNING

*** ERROR/WARNING SUMMARY ***
Table Index: MySQL version unsupported for index `subject_idx` on table `maillog`, upgrade to version >= 50604 (you have version 50505)
conf.php: optional configuration entry "RPC_PORT" is missing, needed if RPC_ONLY mode is enabled
conf.php: optional configuration entry "RPC_SSL" is missing, needed if RPC_ONLY mode is enabled
conf.php: optional configuration entry "RPC_REMOTE_SERVER" is missing, needed to show number of mails in postfix queues on remote server (RPC)
conf.php: optional configuration entry "LDAP_BIND_PREFIX" is missing, needed when using LDAP authentication
conf.php: optional configuration entry "LDAP_BIND_SUFFIX" is missing, needed when using LDAP authentication
conf.php: optional configuration entry "EXIM_QUEUE_IN" is missing, needed only if using Exim as MTA
conf.php: optional configuration entry "EXIM_QUEUE_OUT" is missing, needed only if using Exim as MTA
conf.php: optional configuration entry "PWD_RESET_FROM_NAME" is missing, needed if Password Reset feature is enabled
conf.php: optional configuration entry "PWD_RESET_FROM_ADDRESS" is missing, needed if Password Reset feature is enabled
conf.php: optional configuration entry "MAIL_SENDER" is missing, needed if you use Exim or Sendmail Queue


The strange thing is that now i see the last messages, but since some minutes it's not refreshed ...
Do i have to fix something else ?
Best regards
:arrow: always fighting spams ... :hand:

User avatar
shawniverson
Posts: 2080
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by shawniverson » 26 Mar 2017 09:45

Might need to reboot at this point, just to make sure custom perl modules load properly.
Version 3.0.2.1 released! Update now to keep your eFa secure!

anti-spam
Posts: 34
Joined: 06 Oct 2015 14:32
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by anti-spam » 26 Mar 2017 09:51

thanks again for your answer.
How can i check if the perl modules loads ?
:arrow: always fighting spams ... :hand:

User avatar
shawniverson
Posts: 2080
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by shawniverson » 26 Mar 2017 09:55

You won't see those errors when you restart MailScanner.
Version 3.0.2.1 released! Update now to keep your eFa secure!

anti-spam
Posts: 34
Joined: 06 Oct 2015 14:32
Contact:

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by anti-spam » 26 Mar 2017 16:15

hi,

a quick reply to let you know that you resolved our problem :)
Thanks a lot.
Best regards
:arrow: always fighting spams ... :hand:

Steve9R
Posts: 10
Joined: 27 Aug 2015 00:04

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by Steve9R » 19 Apr 2017 02:54

exact same issue for me as well..

i did an EFA-Update -update today from 3.0.1.8 -> 3.0.2.1
once rebooted i ran the EFA-Update -update again, and it said no updates required.

but on completion got same error as above.. ran the script provided and got :

Code: Select all


MailWatch for MailScanner Database Upgrade to 1.2.3-dev

Have you done a full backup of your database? Type 'yes' to continue: yes

Testing connectivity to the database ................................. OK

Updating database schema: 

 - Convert database to utf8........................................... OK

 - Drop `geoip_country` table......................................... ALREADY DROPPED
 - Drop `spamscores` table............................................ ALREADY DROPPED
 - Add autorelease table to `mailscanner` database.................... ALREADY EXIST
 - Add resetid, resetexpire and lastreset fields in `users` table..... ALREADY EXIST

 - Fix schema for username field in `audit_log` table................. OK
 - Fix schema for id field in `blacklist` table....................... OK
 - Fix schema for username field in `users` table..................... OK
 - Fix schema for spamscore field in `users` table.................... OK
 - Fix schema for highspamscore field in `users` table................ OK
 - Fix schema for username field in `user_filters` table.............. OK
 - Fix schema for username field in `whitelist` table................. OK
 - Fix schema for username field in `audit_log` table................. OK
 - Fix schema for password field in `users` table..................... OK
 - Fix schema for fullname field in `users` table..................... OK
 - Fix schema for rule_desc field in `mcp_rules` table................ OK

 - Cleanup orphaned user_filters...................................... OK
 - Add id field and primary key to `audit_log` table.................. OK
 - Add inq_id field and primary key to `inq` table.................... OK
 - Add maillog_id field and primary key to `maillog` table............ OK
 - Add rblspamreport field to `maillog` table......................... OK
 - Add token field to `maillog` table................................. OK
 - Check for missing tokens in `maillog` table........................ DONE
   13472 token generated
 - Add mtalog_id field and primary key to `mtalog` table.............. OK
 - Add mtalog_id field and primary key to `outq` table................ OK
 - Add id field and primary key to `saved_filters` table.............. OK
 - Add mtalog_id field and primary key to `user_filters` table........ OK

 - Dropping too big index `maillog_from_idx` on table `maillog`....... OK
 - Dropping too big index `maillog_to_idx` on table `maillog`......... OK

 - Convert database to utf8mb4........................................ OK

 - Convert table `audit_log` to utf8mb4............................... OK
 - Convert table `autorelease` to utf8mb4............................. OK
 - Convert table `blacklist` to utf8mb4............................... ALREADY CONVERTED
 - Convert table `inq` to utf8mb4..................................... OK
 - Convert table `maillog` to utf8mb4................................. OK
 - Convert table `mcp_rules` to utf8mb4............................... OK
 - Convert table `mtalog` to utf8mb4.................................. OK
 - Convert table `mtalog_ids` to utf8mb4.............................. OK
 - Convert table `outq` to utf8mb4.................................... OK
 - Convert table `saved_filters` to utf8mb4........................... OK
 - Convert table `sa_rules` to utf8mb4................................ OK
 - Convert table `users` to utf8mb4................................... ALREADY CONVERTED
 - Convert table `user_filters` to utf8mb4............................ OK
 - Convert table `whitelist` to utf8mb4............................... ALREADY CONVERTED

 - Convert table `audit_log` to InnoDB................................ OK
 - Convert table `autorelease` to InnoDB.............................. OK
 - Convert table `blacklist` to InnoDB................................ ALREADY CONVERTED
 - Convert table `inq` to InnoDB...................................... OK
 - Convert table `maillog` to InnoDB.................................. OK
 - Convert table `mcp_rules` to InnoDB................................ OK
 - Convert table `mtalog` to InnoDB................................... OK
 - Convert table `mtalog_ids` to InnoDB............................... OK
 - Convert table `outq` to InnoDB..................................... OK
 - Convert table `saved_filters` to InnoDB............................ OK
 - Convert table `sa_rules` to InnoDB................................. OK
 - Convert table `users` to InnoDB.................................... ALREADY CONVERTED
 - Convert table `user_filters` to InnoDB............................. OK
 - Convert table `whitelist` to InnoDB................................ ALREADY CONVERTED

 - Search for missing indexes on table `maillog`...................... DONE
 - Adding missing index `maillog_from_idx` on table `maillog`......... OK
 - Adding missing index `maillog_to_idx` on table `maillog`........... OK
 - Adding missing index `timestamp_idx` on table `maillog`............ OK
 - Adding missing index `subject_idx` on table `maillog`.............. WARNING

Checking MailScanner.conf settings: 

 - QuarantineWholeMessage ............................................ OK
 - QuarantineWholeMessagesAsQueueFiles ............................... OK
 - DetailedSpamReport ................................................ OK
 - IncludeScoresInSpamAssassinReport ................................. OK
 - SpamActions ....................................................... OK
 - HighScoringSpamActions ............................................ OK
 - AlwaysLookedUpLast ................................................ OK

Checking conf.php configuration entry: 

 - All mandatory entries are present.................................. OK
 - All obsolete entries are already removed........................... OK
 - optional RPC_PORT ................................................. WARNING
 - optional RPC_SSL .................................................. WARNING
 - optional RPC_REMOTE_SERVER ........................................ WARNING
 - optional LDAP_BIND_PREFIX ......................................... WARNING
 - optional LDAP_BIND_SUFFIX ......................................... WARNING
 - optional EXIM_QUEUE_IN ............................................ WARNING
 - optional EXIM_QUEUE_OUT ........................................... WARNING
 - optional PWD_RESET_FROM_NAME ...................................... WARNING
 - optional PWD_RESET_FROM_ADDRESS ................................... WARNING
 - optional MAIL_SENDER .............................................. WARNING
 - optional SESSION_NAME ............................................. WARNING

*** ERROR/WARNING SUMMARY ***
Table Index: MySQL version unsupported for index `subject_idx` on table `maillog`, upgrade to version >= 50604 (you have version 50505)
conf.php: optional configuration entry "RPC_PORT" is missing, needed if RPC_ONLY mode is enabled
conf.php: optional configuration entry "RPC_SSL" is missing, needed if RPC_ONLY mode is enabled
conf.php: optional configuration entry "RPC_REMOTE_SERVER" is missing, needed to show number of mails in postfix queues on remote server (RPC)
conf.php: optional configuration entry "LDAP_BIND_PREFIX" is missing, needed when using LDAP authentication
conf.php: optional configuration entry "LDAP_BIND_SUFFIX" is missing, needed when using LDAP authentication
conf.php: optional configuration entry "EXIM_QUEUE_IN" is missing, needed only if using Exim as MTA
conf.php: optional configuration entry "EXIM_QUEUE_OUT" is missing, needed only if using Exim as MTA
conf.php: optional configuration entry "PWD_RESET_FROM_NAME" is missing, needed if Password Reset feature is enabled
conf.php: optional configuration entry "PWD_RESET_FROM_ADDRESS" is missing, needed if Password Reset feature is enabled
conf.php: optional configuration entry "MAIL_SENDER" is missing, needed if you use Exim or Sendmail Queue
conf.php: optional configuration entry "SESSION_NAME" is missing, needed if experiencing session conflicts
the ones above that say 'already converted' are because i manually cron them over to replicate from a master EFA server (which upgraded fine)..

a reboot after this script has fixed the issue though.

jsegarra
Posts: 2
Joined: 19 Aug 2016 07:51

Re: MySQL error messsage and recent messages not updating the display - EFA 3.0.1.9

Post by jsegarra » 21 Apr 2017 09:49

Hi!

Thanks for your post, the problem that we had is that dumped the database from ESVA and loaded in EFA, from 3.0.1.9 the new messages don't appeared.

After running your script and rebooted all is going smoothly.

Thanks for the support!

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests