How to reduce level loging (file /var/log/messages)

[Alex_Saf]

Hi !

After server updating zimbra to version 6.0.6 GA in a file/var/log/messages the information large quantity began to appear:
Apr 26 08:06:30 proxy1 zimbramon[12816]: 12816:info: :::1808B1B8-50E9-11DF-8DCE-01330D04E66F:::, Com_purge_before_date, Com_rename_table, Com_repair, Com_replace, Com_replace_select, Com_reset, Com_restore_table, Com_revoke, Com_revoke_all, Com_rollback, Com_savepoint, Com_select, Com_set_option, Com_show_binlog_events, Com_show_binlogs, Com_show_charsets, Com_show_collations, Com_show_column_types, Com_show_create_db, Com_show_create_table, Com_show_databases, Com_show_errors, Com_show_fields, Com_show_grants, Com_show_innodb_status, Com_show_keys, Com_show_logs, Com_show_master_status, Com_show_ndb_status, Com_show_new_master, Com_show_open_tables, Com_show_privileges, Com_show_processlist, Com_show_slave_hosts, Com_show_slave_status, Com_show_status, Com_show_storage_engines, Com_show_tables, Com_show_triggers, Com_show_variables, Com_show_warnings, Com_slave_start, Com_slave_sto:::1808DBF2-50E9-11DF-8DCE-01330D04E66F:::

Apr 26 08:06:30 proxy1 zimbramon[12816]: 12816:info: :::1808DBF2-50E9-11DF-8DCE-01330D04E66F::, Com_stmt_close, Com_stmt_execute, Com_stmt_fetch, Com_stmt_prepare, Com_stmt_reset, Com_stmt_send_long_data, Com_truncate, Com_unlock_tables, Com_update, Com_update_multi, Com_xa_commit, Com_xa_end, Com_xa_prepare, Com_xa_recover, Com_xa_rollback, Com_xa_start, Compression, Connections, Created_tmp_disk_tables, Created_tmp_files, Created_tmp_tables, Delayed_errors, Delayed_insert_threads, Delayed_writes, Flush_commands, Handler_commit, Handler_delete, Handler_discover, Handler_prepare, Handler_read_first, Handler_read_key, Handler_read_next, Handler_read_prev, Handler_read_rnd, Handler_read_rnd_next, Handler_rollback, Handler_savepoint, Handler_savepoint_rollback, Handler_update, Handler_write, Innodb_buffer_pool_pages_data, Innodb_buffer_pool_pages_dirty, Innodb_buffer_pool_pages_flush:::1808E64C-50E9-11DF-8DCE-01330D04E66F:::


This information strongly disturbs to work with a system log-file. Whether it is possible to reduce somehow in zimbra of the information for logging?

[phoenix]

Please update your forum profile with the output of the following command (do not post it here):

zmcontrol -v

Did you search the forums before posting, this question has been answered before.

[Alex_Saf]

YOU can specify a post in which there would be a similar problem?

[phoenix]

Please update your forum profile as I've already asked.

[Alex_Saf]

I do not know where in a profile it is necessary to specify the value necessary to you.
Write the exact instruction as it to make.

[maxxer]

strange, these issues were solved in 605 and 606.

If I got it right you are on Fedora. What logger does it uses? (syslog-ng, ksyslog...)

[Alex_Saf]

I have some installations zimbra.
I will result examples:

1) kernel - 2.6.22.9-91.fc7 (NO PROBLEM!)
zimbra - Release 6.0.4_GA_2038.F7_20091214174343 F7 FOSS edition
logger - syslogd-1.4.2-8.fc7

2) kernel - 2.6.23.17-88.fc7 (NO PROBLEM!)
zimbra - Release 6.0.6_GA_2324.F7_20100406131557 F7 FOSS edition
logger - syslogd-1.4.2-9.fc7

3) kernel - 2.6.26.8-57.fc8PAE
zimbra - Release 6.0.6_GA_2324.F7_20100406131557 UNKNOWN FOSS edition.
logger - rsyslog-2.0.2-3.fc8

4) kernel - 2.6.32.11-99.fc12.i686.PAE
zimbra - Release 6.0.6_GA_2324.F11_20100406144520 UNKNOWN FOSS edition.
logger - rsyslog-4.4.2-1.fc12.i686

By first two cars OS Fedora 7 is established and there are no problems with not big records in/var/log/messages.

By the subsequent computers there are OS Fedora 8 and Fedora 12. They have problems with a considerable quantity of records in/var/log/messages.
The problem has arisen at updating zimbra with 6.0.4 to version 6.0.6. In versions to 6.0.4 (inclusive) such problems were not.

I ask to help

[maxxer]

it should be solved, in rsyslog
Bug 43541 – rsyslog: exclude local1 and local0 from logging to /var/log/messages

in case, comment on that bug