Ad Widget

Collapse

zabbix server logging problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • micholus
    Junior Member
    • Mar 2009
    • 7

    #1

    zabbix server logging problem

    Hello.
    I have a zabbix server 1.6.2 on Debian Lenny running just fine, but I have some problems with logs.
    In my config file: /etc/zabbix/zabbix_server.conf I have defined a log file:
    LogFile=/var/log/zabbix-server/zabbix_server.log
    Still, all messages go to /var/log/syslog
    Additionally my syslog is now full of messages from zabbix kernel like this:

    Mar 16 10:49:27 zabbix syslogd 1.5.0#5: restart.
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] ------------[ cut here ]------------
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] WARNING: at arch/x86/kernel/hpet.c:299 hpet_legacy_next_event+0x2f/0x47()
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] Modules linked in: ipv6 loop psmouse snd_hda_intel tpm_infineon tpm tpm_bios snd_pcsp serio_raw snd_pcm snd_timer snd soundcore snd_page_alloc wmi button intel_agp agpgart evdev ext3 jbd mbcache sg sr_mod cdrom sd_mod 8139cp floppy ahci 8139too mii ehci_hcd ide_pci_generic ide_core uhci_hcd ata_generic libata scsi_mod dock usbcore thermal processor fan thermal_sys
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] Pid: 0, comm: swapper Tainted: G W 2.6.26-1-686 #1
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c012256f>] warn_on_slowpath+0x40/0x66
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0110037>] lapic_suspend+0xec/0x11a
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0252365>] sock_def_readable+0x2f/0x58
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c02518c0>] sock_queue_rcv_skb+0xaa/0xb1
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c028d02f>] __udp_queue_rcv_skb+0xf/0x7f
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c028db1b>] udp_queue_rcv_skb+0x19e/0x1f9
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c028dfe7>] __udp4_lib_rcv+0x471/0x6f5
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0272ec3>] ip_local_deliver_finish+0xe8/0x183
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0272dbe>] ip_rcv_finish+0x286/0x2a3
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01140da>] hpet_legacy_next_event+0x2f/0x47
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0138770>] clockevents_program_event+0xc4/0xd2
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0139472>] tick_dev_program_event+0x1e/0x82
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0138ef8>] tick_broadcast_set_event+0xf/0x11
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01390e1>] tick_handle_oneshot_broadcast+0xbe/0xd5
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0105f91>] timer_interrupt+0x41/0x47
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0151fd2>] handle_IRQ_event+0x23/0x51
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01531c3>] handle_edge_irq+0xbf/0xfa
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c0105f3a>] do_IRQ+0x4d/0x63
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01042a7>] common_interrupt+0x23/0x28
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01300d8>] param_set_charp+0x8/0x48
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<f883c29b>] acpi_idle_enter_simple+0x196/0x203 [processor]
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c024990d>] cpuidle_idle_call+0x5b/0x86
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c02498b2>] cpuidle_idle_call+0x0/0x86
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] [<c01025ce>] cpu_idle+0xab/0xcb
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] =======================
    Mar 16 10:49:27 zabbix kernel: [ 551.315645] ---[ end trace c2ce36cb871b74d4 ]---


    Can anyone help me with this?

    micholus
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    First thought - config change. Did you restart Zabbix server after you made that LogFile= change?

    But those are not messages you would normally see in zabbix_server.log. At least none that I have ever seen, even with tracing set to 4.
    Last edited by tchjts1; 01-04-2009, 23:52.

    Comment

    Working...