Thore wrote: > I'm using Xen for vitualization and let 3 VPS run. All of them are > running Munin without problems. 'munin'? Or 'munin-node'? Where does the munin server process run? On *one* of the nodes? That would be fine. And then all of the others simply run the client munin-node process. > But the dom0 has problems. > After installing Munin the System is telling me something about > kernel errors (Oops). > I removed munin an started hardware checks/let the hoster start. > No hardware errors. > I reinstalled munin --> same error You mean munin-node here, right? If you have the munin server running on one of your VPS instances then you would run munin-node on the other nodes. > I removed munin and reinstalled it (this time I was watching syslog > and debug.log)-->same error How much memory are you giving to your dom0? If it doesn't have enough memory then the added resource needs of munin-node might be pushing it over the cliff into problems of memory starvation. > everytime I mus let restart the system, a reboot command doesn't work. > After I had restarted the system 5 minutes later the system told me > again that a kernel Oops happened. > I removed munin again. At the moment ist is not installed. If you install it are you able to connect to the node and query it for modules? For example (using 'connect', but you might have 'telnet' or 'nc' available instead): $ connect localhost 4949 # munin node at localhost list apache_accesses apache_processes apache_volume cpu cpuspeed df df_inode entropy forks fw_packets if_br0 if_err_br0 if_err_eth0 if_err_vnet0 if_eth0 if_vnet0 interrupts irqstats load memory mysql_bin_relay_log mysql_commands mysql_connections mysql_files_tables mysql_innodb_bpool mysql_innodb_bpool_act mysql_innodb_insert_buf mysql_innodb_io mysql_innodb_io_pend mysql_innodb_log mysql_innodb_rows mysql_innodb_semaphores mysql_innodb_tnx mysql_myisam_indexes mysql_network_traffic mysql_qcache mysql_qcache_mem mysql_replication mysql_select_types mysql_slow mysql_sorts mysql_table_locks mysql_tmp_tables nfs4_client nfs_client nfsd nfsd4 ntp_kernel_err ntp_kernel_pll_freq ntp_kernel_pll_off ntp_offset ntp_states open_files open_inodes postfix_mailqueue postfix_mailvolume proc_pri processes smart_sda smart_sdb swap threads uptime users vmstat Do you see that munin-node is installed and with lots of plugins? > Could hddtemp or lm-sensors (both was installed before the > installation of munin) be the reason? Unlikely. Especially if running those commands by themselves don't cause trouble. If you suspect a plugin then I would remove all of the plugins and then test. If that works okay then add plugins back one by one and test each time until you discover the problem. Bob
Attachment:
signature.asc
Description: Digital signature