Results 1 to 2 of 2

Thread: Ubuntu 8.04 LTS (32 and 64 bit) /var/log/syslog question

  1. #1
    mmichalik is offline Member
    Join Date
    Sep 2008
    Posts
    14
    Rep Power
    6

    Exclamation Ubuntu 8.04 LTS (32 and 64 bit) /var/log/syslog question

    Hi everyone,

    I just installed the following Zimbra server, Version 6.0.5_GA_2213.UBUNTU8_64.FOSS onto a Ubuntu 8.04 LTS 64-bit machine (I also installed a 32-bit version on a Ubuntu 8.04 LTS 32-bit machine and had the same thing happen there) and now my syslog is filling up with the following messages:

    Mar 3 12:42:47 (IP Removed) zimbramon[19430]: 19430:info: zmstat vm.csv: timestamp, r, b, swpd, free, buff, cache, si, so, bi, bo, in, cs, us, sy, id, wa, MemTotal, MemFree, Buffers, Cached, SwapCached, Active, Inactive, SwapTotal, SwapFree, Dirty, Writeback, AnonPages, Mapped, Slab, SReclaimable, SUnreclaim, PageTables, NFS_Unstable, Bounce, CommitLimit, Committed_AS, VmallocTotal, VmallocUsed, VmallocChunk, loadavg:: 03/03/2010 12:42:47, 4, 0, 0, 205008, 134892, 4362632, 0, 0, 0, 1033, 384, 665, 71, 12, 2, 0, 7864540, 205008, 134892, 4362632, 0, 5298976, 2025948, 0, 0, 6780, 0, 2616728, 66664, 141704, 109596, 32108, 19456, 0, 0, 3932268, 8656308, 34359738367, 392, 34359737975, 4.15

    Mar 3 12:42:47 (IP Removed) zimbramon[19434]: 19434:info: zmstat io-x.csv: timestamp, sda1:rrqm/s, sda1:wrqm/s, sda1:r/s, sda1:w/s, sda1:rkB/s, sda1:wkB/s, sda1:avgrq-sz, sda1:avgqu-sz, sda1:await, sda1:svctm, sda1:%util, sdb:rrqm/s, sdb:wrqm/s, sdb:r/s, sdb:w/s, sdb:rkB/s, sdb:wkB/s, sdb:avgrq-sz, sdb:avgqu-sz, sdb:await, sdb:svctm, sdb:%util, sdc:rrqm/s, sdc:wrqm/s, sdc:r/s, sdc:w/s, sdc:rkB/s, sdc:wkB/s, sdc:avgrq-sz, sdc:avgqu-sz, sdc:await, sdc:svctm, sdc:%util, sdi:rrqm/s, sdi:wrqm/s, sdi:r/s, sdi:w/s, sdi:rkB/s, sdi:wkB/s, sdi:avgrq-sz, sdi:avgqu-sz, sdi:await, sdi:svctm, sdi:%util:: 03/03/2010 12:42:47, 0.00, 80.90, 0.00, 142.86, 0.00, 895.04, 12.53, 1.21, 8.48, 0.12, 1.68, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.10, 0.03, 6.82, 0.13, 50.00:::2E88E04C-26EC-11DF-A462-BBC42543729E:::

    Mar 3 12:42:47 (IP Removed) zimbramon[19434]: :::2E88E04C-26EC-11DF-A462-BBC42543729E:::, 14.63, 0.46, 66.87, 4.35, 2.98
    Mar 3 12:43:00 domU-12-31-39-00-44-82 zimbramon[19415]: 19415:info: zmstat proc.csv: timestamp, system, user, sys, idle, iowait, mailbox, mailbox-total-cpu, mailbox-utime, mailbox-stime, mailbox-totalMB, mailbox-rssMB, mailbox-sharedMB, mailbox-process-count, mysql, mysql-total-cpu, mysql-utime, mysql-stime, mysql-totalMB, mysql-rssMB, mysql-sharedMB, mysql-process-count, convertd, convertd-total-cpu, convertd-utime, convertd-stime, convertd-totalMB, convertd-rssMB, convertd-sharedMB, convertd-process-count, ldap, ldap-total-cpu, ldap-utime, ldap-stime, ldap-totalMB, ldap-rssMB, ldap-sharedMB, ldap-process-count, postfix, postfix-total-cpu, postfix-utime, postfix-stime, postfix-totalMB, postfix-rssMB, postfix-sharedMB, postfix-process-count, amavis, amavis-total-cpu, amavis-utime, amavis-stime, amavis-totalMB, amavis-rssMB, amavis-sharedMB, amavis-process-:::35CA0520-26EC-11DF-ACA4-A8C42543729E:::

    Mar 3 12:43:00 (IP Removed) zimbramon[19415]: :::35CA0520-26EC-11DF-ACA4-A8C42543729E:::count, clam, clam-total-cpu, clam-utime, clam-stime, clam-totalMB, clam-rssMB, clam-sharedMB, clam-process-count:: 03/03/2010 12:43:00, system, 84.2, 13.5, 2.3, 0.0, mailbox, 0.3, 0.3, 0.0, 3700.1, 1083.0, 12.7, 1, mysql, 0.2, 0.2, 0.0, 2721.3, 318.4, 4.9, 1, convertd, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0, ldap, 0.0, 0.0, 0.0, 323.6, 56.8, 4.8, 1, postfix, 0.0, 0.0, 0.0, 46.4, 2.3, 1.7, 4, amavis, 0.0, 0.0, 0.0, 200.2, 85.7, 3.7, 11, clam, 0.0, 0.0, 0.0, 167.9, 127.7, 0.9, 2

    Mar 3 12:43:00 (IP Removed) zimbramon[19502]: 19502:info: zmstat mysql.csv: timestamp, Aborted_clients, Aborted_connects, Binlog_cache_disk_use, Binlog_cache_use, Bytes_received, Bytes_sent, Com_admin_commands, Com_alter_db, Com_alter_table, Com_analyze, Com_backup_table, Com_begin, Com_call_procedure, Com_change_db, Com_change_master, Com_check, Com_checksum, Com_commit, Com_create_db, Com_create_function, Com_create_index, Com_create_table, Com_create_user, Com_dealloc_sql, Com_delete, Com_delete_multi, Com_do, Com_drop_db, Com_drop_function, Com_drop_index, Com_drop_table, Com_drop_user, Com_execute_sql, Com_flush, Com_grant, Com_ha_close, Com_ha_open, Com_ha_read, Com_help, Com_insert, Com_insert_select, Com_kill, Com_load, Com_load_master_data, Com_load_master_table, Com_lock_tables, Com_optimize, Com_preload_keys, Com_prepare_sql, Com_purge:::35E791E4-26EC-11DF-BCDE-FFC42543729E:::

    Mar 3 12:43:00 (IP Removed) zimbramon[19502]: 19502:info: :::35E791E4-26EC-11DF-BCDE-FFC42543729E:::, 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:::35E7AC2E-26EC-11DF-BCDE-FFC42543729E:::


    Is this expected behavior in Version 6? I have several clients on version 5 and this isn't happening to them and I'm reluctant to do an upgrade until until I find out how to control this.

    This has happens all day long and you can see how quickly the posts are occurring. (within seconds of each other)

    It's making it very difficult to get any usable information from my syslog or messages log because i have to filter through all of this.

    Any thoughts from anyone? Can I put these entries into a different log file? Can I suppress them entirely? What are they there for? (I'm assuming they are there for the STATS stuff but, it's beyond crazy)

    Thanks in advance.

    Mike

  2. #2
    ArcaneMagus's Avatar
    ArcaneMagus is offline Moderator
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    It's not the "expected" behavior, and was actually fixed for all(?) OS's... besides the one in the bug report. You can follow the progress of fixing it on Ubuntu here:
    Bug 43541 - rsyslog: exclude local1 and local0 from logging to /var/log/messages

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •