Help with SBG database - blank reports
/opt/Symantec/Brightmail/mysql/bin/mysqlcheck -h127.0.0.1 -ubrightmailuser -p`cat /data/etc/.brightmailuser` brightmail --auto-repair
The results were:
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.admin_password_history OK
brightmail.admin_user
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.alias OK
brightmail.compliance_message OK
brightmail.compliance_message_folder OK
brightmail.compliance_message_recipient OK
brightmail.custom_rule
warning : 3 clients are using or haven't closed the table properly
status : OK
brightmail.custom_rule_condition
warning : 3 clients are using or haven't closed the table properly
status : OK
brightmail.day_zero_message OK
brightmail.dlist OK
brightmail.dlist_member_rel OK
brightmail.file_class OK
brightmail.file_type OK
brightmail.host
warning : 6 clients are using or haven't closed the table properly
status : OK
brightmail.im_user OK
brightmail.im_user_registration_email
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.im_user_screenname OK
brightmail.incident_audit_log OK
brightmail.installation OK
brightmail.ldap_group OK
brightmail.ldap_group_member_rel OK
brightmail.ldap_source
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.ldap_sync_notification
warning : 17 clients are using or haven't closed the table properly
status : OK
brightmail.ldap_user OK
brightmail.log OK
brightmail.log_action OK
brightmail.log_component OK
brightmail.log_marker
warning : 18 clients are using or haven't closed the table properly
status : OK
brightmail.log_severity OK
brightmail.policy_annotation OK
brightmail.policy_archive OK
brightmail.policy_attachment OK
brightmail.policy_attachment_type OK
brightmail.policy_dictionary OK
brightmail.policy_dictionary_item OK
brightmail.policy_notification OK
brightmail.policy_pattern OK
brightmail.policy_record OK
brightmail.policy_record_field OK
brightmail.policy_record_view OK
brightmail.policy_record_view_field OK
brightmail.policy_threat_track
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.report_connection_classes OK
brightmail.report_executive OK
brightmail.report_favorite OK
brightmail.report_im_file_transfer OK
brightmail.report_im_overview OK
brightmail.report_im_recipient OK
brightmail.report_im_recipient_buffer
note : The storage engine for the table doesn't support check
brightmail.report_im_recipient_name OK
brightmail.report_im_sender OK
brightmail.report_im_sender_buffer
note : The storage engine for the table doesn't support check
brightmail.report_im_sender_name OK
brightmail.report_incident_history OK
brightmail.report_message OK
brightmail.report_policy OK
brightmail.report_policy_name OK
brightmail.report_policy_summary OK
brightmail.report_rcpt OK
brightmail.report_rcpt_alias OK
brightmail.report_rcpt_buffer
note : The storage engine for the table doesn't support check
brightmail.report_rcpt_domain OK
brightmail.report_reputation OK
brightmail.report_sender OK
brightmail.report_sender_alias OK
brightmail.report_sender_buffer
note : The storage engine for the table doesn't support check
brightmail.report_sender_domain OK
brightmail.report_sender_helo OK
brightmail.report_sender_ip_address OK
brightmail.report_smtp_connection OK
brightmail.report_smtp_connection_address OK
brightmail.report_spam_summary OK
brightmail.report_total OK
brightmail.report_total_host
warning : 10 clients are using or haven't closed the table properly
status : OK
brightmail.report_virus OK
brightmail.report_virus_name OK
brightmail.report_virus_summary OK
brightmail.sender_group
warning : 3 clients are using or haven't closed the table properly
status : OK
brightmail.settings_address_masquerading OK
brightmail.settings_alert
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.settings_alert_notification
warning : 23 clients are using or haven't closed the table properly
status : OK
brightmail.settings_alias OK
brightmail.settings_ca_certificate_detail
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.settings_certificate OK
brightmail.settings_certificate_detail OK
brightmail.settings_certificate_selection
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.settings_compliance OK
brightmail.settings_connection_class OK
brightmail.settings_container OK
brightmail.settings_domain
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.settings_ensure OK
brightmail.settings_host_access_control
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.settings_im OK
brightmail.settings_ldap
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.settings_ldap_sync_notification OK
brightmail.settings_log
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.settings_message_queue OK
brightmail.settings_notification_template OK
brightmail.settings_policy OK
brightmail.settings_quarantine
warning : 2 clients are using or haven't closed the table properly
status : OK
brightmail.settings_report OK
brightmail.settings_scanner_replication
warning : 14 clients are using or haven't closed the table properly
status : OK
brightmail.settings_scheduled_backups OK
brightmail.settings_smtp_filter_host OK
brightmail.settings_smtp_mgmt_host
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.settings_system
warning : 9 clients are using or haven't closed the table properly
status : OK
brightmail.settings_user_pref
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.site
warning : 8 clients are using or haven't closed the table properly
status : OK
brightmail.spam_message OK
brightmail.spam_message_release_audit OK
brightmail.spam_message_summary OK
brightmail.spam_message_summary_from_addr_head OK
brightmail.spam_message_summary_msg_id OK
brightmail.spam_message_summary_subject OK
brightmail.status
warning : 23 clients are using or haven't closed the table properly
status : OK
brightmail.status_component_crash OK
brightmail.status_im_relay OK
brightmail.status_jlu
warning : 23 clients are using or haven't closed the table properly
status : OK
brightmail.status_record OK
brightmail.status_record_replication OK
brightmail.status_rule
warning : 23 clients are using or haven't closed the table properly
status : OK
brightmail.status_scanner_replication
warning : 16 clients are using or haven't closed the table properly
status : OK
brightmail.status_version
warning : 1 client is using or hasn't closed the table properly
status : OK
brightmail.status_watchdog
warning : 22 clients are using or haven't closed the table properly
status : OK
brightmail.user OK
brightmail.user_spam_message OK
brightmail.user_spam_message_to_addr_env OK
brightmail.user_token
warning : 3 clients are using or haven't closed the table properly
status : OK
brightmail.virus_exclude OK
brightmail.virus_exclude_item OK
Question:
How can I fix the "x clients are using or haven't closed the table properly."?
We cannot generate any reports for the past month.
Comments
Hi, the reason for that is
Hi,
the reason for that is documented on the mysql website:
dev.mysql.com/doc/refman/5.0/en/myisam-table-close.html
Not having other details I'd suggest you open a support case with us.
Regards,
Federico
Thanks for the link,
Thanks for the link, fferaboli.
I have already opened a support case for this, apparently our server got filled up. I failed to mention in this post that we have setup the server-to our clients request- to never delete any logs and to track all incoming emails. I have already changed the settings to purge all old data and the restart was scheduled 3 days ago. I'm checking the server status today.
“Your most unhappy customers are your greatest source of learning.”
Would you like to reply?
Login or Register to post your comment.