Nagios Support Forum

Support for Nagios products and services
https://support.nagios.com/forum/

KVM guest to guest 'No data received from host'

https://support.nagios.com/forum/viewtopic.php?t=30842

Page 2 of 3

Re: KVM guest to guest 'No data received from host'

Posted: Mon Jan 19, 2015 12:54 pm
by tgriep
What is the IP address of the Nagios server?

What is the IP address of the Windows server?

Can you post the allowed hosts line from the nsclient.ini file from the Windows server?

Have you tried to restart the Nsclient++ service on the Windows server?

Re: KVM guest to guest 'No data received from host'

Posted: Thu Feb 05, 2015 10:41 am
by scottthepotter
Sorry, didn't see the 'page 2' and I don't seem to be getting emails when responses are posted.

Nagios Server IP - 192.168.0.25
Windows Server IP - 192.168.0.21
allowed hosts = 192.168.0.25

I have restarted the NSClient service to no avail.

As I stated in a previous post I can ping each computer from the other, so I don't believe that it is a 'routing' problem.

Re: KVM guest to guest 'No data received from host'

Posted: Thu Feb 05, 2015 4:07 pm
by bdgoecke
How is your networking configured on you host(s) for the guests ?

Do you have a bridge configured that the guests are using or are they using the default NAT'd network connections ?

On your host system could you do a

Code: Select all

ifconfig -a
So we could get a peek at your networking config.

==>brian.

Re: KVM guest to guest 'No data received from host'

Posted: Thu Feb 05, 2015 7:47 pm
by Box293
Can you post your nsc.ini or nsclient.ini file here please.

Re: KVM guest to guest 'No data received from host'

Posted: Fri Feb 06, 2015 10:32 am
by scottthepotter
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.20 netmask 255.255.255.0 broadcast 192.168.0.255
ether 54:9f:35:02:d0:ee txqueuelen 1000 (Ethernet)
RX packets 212993554 bytes 280160138733 (260.9 GiB)
RX errors 0 dropped 1639358 overruns 0 frame 0
TX packets 123356812 bytes 28276384224 (26.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 54:9f:35:02:d0:f0 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 1281549 bytes 89068360 (84.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1281549 bytes 89068360 (84.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

macvtap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5054:ff:fe94:9289 prefixlen 64 scopeid 0x20<link>
ether 52:54:00:94:92:89 txqueuelen 500 (Ethernet)
RX packets 13954518 bytes 1757352838 (1.6 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1385025 bytes 1014164223 (967.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

macvtap1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5054:ff:fe05:94b prefixlen 64 scopeid 0x20<link>
ether 52:54:00:05:09:4b txqueuelen 500 (Ethernet)
RX packets 33516859 bytes 9695433504 (9.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11268581 bytes 5668003352 (5.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

macvtap2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5054:ff:fe8d:16d9 prefixlen 64 scopeid 0x20<link>
ether 52:54:00:8d:16:d9 txqueuelen 500 (Ethernet)
RX packets 21321824 bytes 3649924294 (3.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8941317 bytes 7867533830 (7.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

macvtap3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5054:ff:fe53:b7d3 prefixlen 64 scopeid 0x20<link>
ether 52:54:00:53:b7:d3 txqueuelen 500 (Ethernet)
RX packets 11992534 bytes 1317837640 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 57556 bytes 4805241 (4.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

macvtap4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a00:27ff:fed3:8f36 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:d3:8f:36 txqueuelen 500 (Ethernet)
RX packets 14931098 bytes 2708320810 (2.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2179407 bytes 322420623 (307.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
inet6 fe80::fc00:27ff:fed3:8f36 prefixlen 64 scopeid 0x20<link>
ether 00:00:00:00:00:00 txqueuelen 0 (Ethernet)
RX packets 33 bytes 3245 (3.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 42 bytes 4618 (4.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.254.1 netmask 255.255.255.0 broadcast 192.168.254.255
ether 52:54:00:5b:a4:de txqueuelen 0 (Ethernet)
RX packets 190752866 bytes 266135716541 (247.8 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 104479366 bytes 9125097663 (8.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr1-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:5b:a4:de txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fec7:5fdb prefixlen 64 scopeid 0x20<link>
ether fe:54:00:c7:5f:db txqueuelen 500 (Ethernet)
RX packets 190752866 bytes 268806256665 (250.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 105773621 bytes 9192399115 (8.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Re: KVM guest to guest 'No data received from host'

Posted: Fri Feb 06, 2015 10:48 am
by scottthepotter
# If you want to fill this file with all avalible options run the following command:
# nscp settings --generate --add-defaults --load-all
# If you want to activate a module and bring in all its options use:
# nscp settings --activate-module <MODULE NAME> --add-defaults
# For details run: nscp settings --help


; Undocumented section
[/modules]

; CheckDisk - CheckDisk can check various file and disk related things. The current version has commands to check Size of hard drives and directories.
CheckDisk = 1

; Event log Checker. - Check for errors and warnings in the event log. This is only supported through NRPE so if you plan to use only NSClient this wont help you at all.
CheckEventLog = 1

; Check External Scripts - A simple wrapper to run external scripts and batch files.
CheckExternalScripts = 1

; Helper function - Various helper function to extend other checks. This is also only supported through NRPE.
CheckHelpers = 1

; Check NSCP - Checkes the state of the agent
CheckNSCP = 1

; CheckSystem - Various system related checks, such as CPU load, process state, service state memory usage and PDH counters.
CheckSystem = 1

; CheckWMI - CheckWMI can check various file and disk related things. The current version has commands to check Size of hard drives and directories.
CheckWMI = 1

; NRPE server - A simple server that listens for incoming NRPE connection and handles them.
NRPEServer = 1

; NSClient server - A simple server that listens for incoming NSClient (check_nt) connection and handles them. Although NRPE is the preferred method NSClient is fully supported and can be used for simplicity or for compatibility.
NSClientServer = 1


; Undocumented section
[/settings/default]

; ALLOWED HOSTS - A comaseparated list of allowed hosts. You can use netmasks (/ syntax) or * to create ranges.
allowed hosts = 192.168.0.25

; PASSWORD - Password used to authenticate againast server
password = XXXXXXXXXXX


; A list of aliases available. An alias is an internal command that has been "wrapped" (to add arguments). Be careful so you don't create loops (ie check_loop=check_a, check_a=check_loop)
[/settings/external scripts/alias]

; alias_cpu - Alias for alias_cpu. To configure this item add a section called: /settings/external scripts/alias/alias_cpu
alias_cpu = checkCPU warn=80 crit=90 time=5m time=1m time=30s

; alias_cpu_ex - Alias for alias_cpu_ex. To configure this item add a section called: /settings/external scripts/alias/alias_cpu_ex
alias_cpu_ex = checkCPU warn=$ARG1$ crit=$ARG2$ time=5m time=1m time=30s

; alias_disk - Alias for alias_disk. To configure this item add a section called: /settings/external scripts/alias/alias_disk
alias_disk = CheckDriveSize MinWarn=10% MinCrit=5% CheckAll FilterType=FIXED

; alias_disk_loose - Alias for alias_disk_loose. To configure this item add a section called: /settings/external scripts/alias/alias_disk_loose
alias_disk_loose = CheckDriveSize MinWarn=10% MinCrit=5% CheckAll FilterType=FIXED ignore-unreadable

; alias_event_log - Alias for alias_event_log. To configure this item add a section called: /settings/external scripts/alias/alias_event_log
alias_event_log = CheckEventLog file=application file=system MaxWarn=1 MaxCrit=1 "filter=generated gt -2d AND severity NOT IN ('success', 'informational') AND source != 'SideBySide'" truncate=800 unique descriptions "syntax=%severity%: %source%: %message% (%count%)"

; alias_file_age - Alias for alias_file_age. To configure this item add a section called: /settings/external scripts/alias/alias_file_age
alias_file_age = checkFile2 filter=out "file=$ARG1$" filter-written=>1d MaxWarn=1 MaxCrit=1 "syntax=%filename% %write%"

; alias_file_size - Alias for alias_file_size. To configure this item add a section called: /settings/external scripts/alias/alias_file_size
alias_file_size = CheckFiles "filter=size > $ARG2$" "path=$ARG1$" MaxWarn=1 MaxCrit=1 "syntax=%filename% %size%" max-dir-depth=10

; alias_mem - Alias for alias_mem. To configure this item add a section called: /settings/external scripts/alias/alias_mem
alias_mem = checkMem MaxWarn=80% MaxCrit=90% ShowAll=long type=physical type=virtual type=paged type=page

; alias_process - Alias for alias_process. To configure this item add a section called: /settings/external scripts/alias/alias_process
alias_process = checkProcState "$ARG1$=started"

; alias_process_count - Alias for alias_process_count. To configure this item add a section called: /settings/external scripts/alias/alias_process_count
alias_process_count = checkProcState MaxWarnCount=$ARG2$ MaxCritCount=$ARG3$ "$ARG1$=started"

; alias_process_hung - Alias for alias_process_hung. To configure this item add a section called: /settings/external scripts/alias/alias_process_hung
alias_process_hung = checkProcState MaxWarnCount=1 MaxCritCount=1 "$ARG1$=hung"

; alias_process_stopped - Alias for alias_process_stopped. To configure this item add a section called: /settings/external scripts/alias/alias_process_stopped
alias_process_stopped = checkProcState "$ARG1$=stopped"

; alias_sched_all - Alias for alias_sched_all. To configure this item add a section called: /settings/external scripts/alias/alias_sched_all
alias_sched_all = CheckTaskSched "filter=exit_code ne 0" "syntax=%title%: %exit_code%" warn=>0

; alias_sched_long - Alias for alias_sched_long. To configure this item add a section called: /settings/external scripts/alias/alias_sched_long
alias_sched_long = CheckTaskSched "filter=status = 'running' AND most_recent_run_time < -$ARG1$" "syntax=%title% (%most_recent_run_time%)" warn=>0

; alias_sched_task - Alias for alias_sched_task. To configure this item add a section called: /settings/external scripts/alias/alias_sched_task
alias_sched_task = CheckTaskSched "filter=title eq '$ARG1$' AND exit_code ne 0" "syntax=%title% (%most_recent_run_time%)" warn=>0

; alias_service - Alias for alias_service. To configure this item add a section called: /settings/external scripts/alias/alias_service
alias_service = checkServiceState CheckAll

; alias_service_ex - Alias for alias_service_ex. To configure this item add a section called: /settings/external scripts/alias/alias_service_ex
alias_service_ex = checkServiceState CheckAll "exclude=Net Driver HPZ12" "exclude=Pml Driver HPZ12" exclude=stisvc

; alias_up - Alias for alias_up. To configure this item add a section called: /settings/external scripts/alias/alias_up
alias_up = checkUpTime MinWarn=1d MinWarn=1h

; alias_updates - Alias for alias_updates. To configure this item add a section called: /settings/external scripts/alias/alias_updates
alias_updates = check_updates -warning 0 -critical 0

; alias_volumes - Alias for alias_volumes. To configure this item add a section called: /settings/external scripts/alias/alias_volumes
alias_volumes = CheckDriveSize MinWarn=10% MinCrit=5% CheckAll=volumes FilterType=FIXED

; alias_volumes_loose - Alias for alias_volumes_loose. To configure this item add a section called: /settings/external scripts/alias/alias_volumes_loose
alias_volumes_loose = CheckDriveSize MinWarn=10% MinCrit=5% CheckAll=volumes FilterType=FIXED ignore-unreadable

; default - Alias for default. To configure this item add a section called: /settings/external scripts/alias/default
default =

Re: KVM guest to guest 'No data received from host'

Posted: Fri Feb 06, 2015 3:34 pm
by bdgoecke
What are they setting for how the guest VMs were created in KVM ?

Often the default configuration for a guest VM is a NAT'd network interface, or another type of network interface that has "limited" access. The guest VM will be able to access the network, but other machines will not be able to access the guest VM. And in addition there can be more limited access for guest VM residing on the same host (this could be a "hairpin" issue).

Info regarding how the network interface was for the guest VM from the host would be great.

You can get this from the definition in virsh with the dumpxml info,

Code: Select all

virsh dumpxml {VMNAME}
Here is an example of the network definition on a KVM VM of mine.

Code: Select all

    <interface type='bridge'>
      <mac address='52:54:00:xx:xx:xx'/>
      <source bridge='br0'/>
      <target dev='vnet1'/>
      <model type='rtl8139'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <interface type='bridge'>
      <mac address='52:54:00:xx:xx:xx'/>
      <source bridge='br1'/>
      <target dev='vnet2'/>
      <model type='rtl8139'/>
      <alias name='net1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </interface>
This VM Guest has two network interfaces connected to two different bridges. I used bridges to connect as if the guest VMs were full machines on the network, and all the machines on the network (including other guest VMs on the same host) will have full access to the machines.

==>brian.

Re: KVM guest to guest 'No data received from host'

Posted: Mon Feb 09, 2015 4:53 pm
by scottthepotter
Well, I am pretty sure that that is not the problem as it is a Windows server 2008 guest that has 'shares' to another Windows server 2008 guest on the same host. But here is the relevant info ....


<interface type='direct'>
<mac address='52:54:00:05:09:4b'/>
<source dev='br0' mode='bridge'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<interface type='network'>
<mac address='52:54:00:c7:5f:db'/>
<source network='isolated'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</interface>

Re: KVM guest to guest 'No data received from host'

Posted: Tue Feb 10, 2015 5:05 pm
by abrist
As the newer versions of nsclient have been known to have issues, can you try running the old 0.3.9 version of nsclient on this host? The error message you posted on the previous page looks like an issue with that version of nsclient itself.

Re: KVM guest to guest 'No data received from host'

Posted: Wed Feb 11, 2015 6:32 pm
by scottthepotter
Installed 0.3.9. No joy :-(
Same results: Warning: No data was received from host.
So Nagios 'knows' the server exists, it just isn't getting the data.
????
Might have to give up and just install a stand alone Nagios server.
All times are UTC-05:00
Page 2 of 3

Powered by phpBB® Forum Software © phpBB Limited