Unable to find some network devices

[Tim C]

Hullo
I'm not sure if this is the correct group or not. And, annoyingly, I
may be missing some critical pieces of data at the moment, but in case
anyone's got any obvious answers...

I'm running the PerfMon agent on a debian VM with jmeter on my mac.
The VM has ~12 ip addresses. When I add network I/O to the metrics
that the agent is reporting, I'm getting lots of errors of this form
constinuously spewed out of the terminal running the agent:

ERROR 2012-04-20 16:10:32.712 [kg.apc.p] (): Failed to get interface
stat: eth0:90
org.hyperic.sigar.SigarException: No such device or address: eth0:90
at org.hyperic.sigar.SigarProxyCache.invoke(SigarProxyCache.java:220)
at $Proxy0.getNetInterfaceStat(Unknown Source)
at
kg.apc.perfmon.metrics.NetworkIOMetric.getValue(NetworkIOMetric.java:
88)
at
kg.apc.perfmon.PerfMonMetricGetter.getMetricsLine(PerfMonMetricGetter.java:
114)
at kg.apc.perfmon.PerfMonWorker.processSenders(PerfMonWorker.java:
273)
at kg.apc.perfmon.PerfMonWorker.run(PerfMonWorker.java:236)
at java.lang.Thread.run(Thread.java:636)

for the various network devices. I am getting I/O use for some network
device, although it's not obvious which one (could be a 'real' device
- at least as far as the O/S is concerned - or some aggregator. I do
not seem to get the error for eth0, so I'd guess that the issue is
either something to do with >1 network device, or something to do with
the mechanism for putting multiple IP addresses on one device (eg
ethX:Y). Either way, I'd expect the issue to be well known, but
Google's not finding it.

Any suggestions?

cheers
Tim

[Andrey Pohilko]

Please, start your serverAgent with --sysinfo parameter. It will show you available network interfaces.

AFAIK VMs have issues with disk io and network io measuring. You should collect those metrics at host machine.

суббота, 21 апреля 2012 г., 12:02:09 UTC+3 пользователь Tim C написал:

[Tim C]

Below is what I get from the --sysinfo flag, which implies to me that
the devices are there (eth0:90 in the error log). I appreciate that
there could well be issues with measuring the rate of anything on a vm
as their clocks aren't that reliable. However, I'd expect it to behave
with no errors, even if the data were rubbish. I can then migrate this
to some sort of physical machine when I've got the tests working (or
just move them to the containing machine).


+ java -jar /home/tim/JMeterPlugins/serverAgent/CMDRunner.jar --tool
PerfMonAgent --sysinfo
INFO 2012-04-23 11:25:08.902 [kg.apc.p] (): *** Logging available
processes ***
INFO 2012-04-23 11:25:09.707 [kg.apc.p] (): Process: pid=1335
name=bash args=bash
INFO 2012-04-23 11:25:09.707 [kg.apc.p] (): Process: pid=1517
name=bash#1 args=bash
INFO 2012-04-23 11:25:09.707 [kg.apc.p] (): Process: pid=1518
name=dash args=sh -x /home/tim/JMeterPlugins/serverAgent/startAgent.sh
--sysinfo
INFO 2012-04-23 11:25:09.708 [kg.apc.p] (): Process: pid=1520
name=java args=java -jar /home/tim/JMeterPlugins/serverAgent/
CMDRunner.jar --tool PerfMonAgent --sysinfo
INFO 2012-04-23 11:25:09.718 [kg.apc.p] (): *** Logging available
filesystems ***
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/sys
type=sysfs
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/etc/
alertme type=ext3
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/opt/
alertme type=ext3
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/dev
type=tmpfs
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/root
type=ext3
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/dev/shm
type=tmpfs
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/lib/
init/rw type=tmpfs
INFO 2012-04-23 11:25:09.720 [kg.apc.p] (): Filesystem: fs=/dev/pts
type=devpts
INFO 2012-04-23 11:25:09.721 [kg.apc.p] (): Filesystem: fs=/
type=ext3
INFO 2012-04-23 11:25:09.721 [kg.apc.p] (): Filesystem: fs=/proc
type=proc
INFO 2012-04-23 11:25:09.721 [kg.apc.p] (): *** Logging available
network interfaces ***
INFO 2012-04-23 11:25:09.722 [kg.apc.p] (): Network interface:
iface=lo addr=127.0.0.1 type=Local Loopback
INFO 2012-04-23 11:25:09.722 [kg.apc.p] (): Network interface:
iface=eth0 addr=10.221.119.1 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:2 addr=10.221.119.2 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:3 addr=10.221.119.3 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:4 addr=10.221.119.4 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:5 addr=10.221.119.5 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:6 addr=10.221.119.6 type=Ethernet
INFO 2012-04-23 11:25:09.723 [kg.apc.p] (): Network interface:
iface=eth0:7 addr=10.221.119.7 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:8 addr=10.221.119.8 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:9 addr=10.221.119.9 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:10 addr=10.221.119.10 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:20 addr=10.221.119.20 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:30 addr=10.221.119.30 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:40 addr=10.221.119.40 type=Ethernet
INFO 2012-04-23 11:25:09.724 [kg.apc.p] (): Network interface:
iface=eth0:50 addr=10.221.119.50 type=Ethernet
INFO 2012-04-23 11:25:09.731 [kg.apc.p] (): Network interface:
iface=eth0:60 addr=10.221.119.60 type=Ethernet
INFO 2012-04-23 11:25:09.731 [kg.apc.p] (): Network interface:
iface=eth0:70 addr=10.221.119.70 type=Ethernet
INFO 2012-04-23 11:25:09.732 [kg.apc.p] (): Network interface:
iface=eth0:80 addr=10.221.119.80 type=Ethernet
INFO 2012-04-23 11:25:09.732 [kg.apc.p] (): Network interface:
iface=eth0:120 addr=10.221.119.120 type=Ethernet
INFO 2012-04-23 11:25:09.732 [kg.apc.p] (): Network interface:
iface=eth0:90 addr=10.221.119.90 type=Ethernet
INFO 2012-04-23 11:25:09.732 [kg.apc.p] (): *** Done logging
sysinfo ***
INFO 2012-04-23 11:25:09.732 [kg.apc.p] (): Binding UDP to 4444
INFO 2012-04-23 11:25:10.827 [kg.apc.p] (): Binding TCP to 4444

[Andrey Pohilko]

You're right, if serverAgent can list that interface, it should be able to monitor it. 

Have you escaped a colon in interface name, as documentation requires?

понедельник, 23 апреля 2012 г., 14:36:16 UTC+3 пользователь Tim C написал:

[Tim C]

Nope. Cannot find this point in the documentation. The only reference
that I can see is here: http://bit.ly/IzsiaO and relates to Specifying
Metric Params, which I don't think I'm doing.

Sounds like the right issue. I'll try to dig harder into the
documentation.

Tim

[Andrey Pohilko]

This is exactly "Specifying Metric Params" that you doing. So you must to escape colons inside interface names, like eth0\:12

вторник, 24 апреля 2012 г., 14:21:51 UTC+3 пользователь Tim C написал:

[Tim C]

I'm sure that I'm specifying the parameters somehow and somewhere, but
I've not done anything explicit, so I'm lost as to where these
interface names have been specified. I can see what the syntax needs
to be, but I've no idea where it's being used

On Apr 24, 1:12 pm, Andrey Pohilko <a...@apc.kg> wrote:
> This is exactly "Specifying Metric Params" that you doing. So you must to
> escape colons inside interface names, like eth0\:12
>
> вторник, 24 апреля 2012 г., 14:21:51 UTC+3 пользователь Tim C написал:
>
>
>
>
>
>
>
>
>
> > Nope. Cannot find this point in the documentation. The only reference

> > that I can see is here:http://bit.ly/IzsiaOand relates to Specifying

[Andrey Pohilko]

So how do you set up your Metrics Collector? Using wizard or something?

вторник, 24 апреля 2012 г., 15:39:27 UTC+3 пользователь Tim C написал:

[Tim C]

I think that I've found where it goes on the gui page (I'd assumed
that nothing meant monitor all interfaces).

If I try:
iface=eth0
It works, (but that's the wrong interface). if I try:
iface=eth0\:40

I'm still getting the same sort of error:
ERROR 2012-04-24 13:28:06.547 [kg.apc.p] (): Failed to get interface
stat: eth0:40

On Apr 24, 1:39 pm, Tim C <timco...@gmail.com> wrote:
> I'm sure that I'm specifying the parameters somehow and somewhere, but
> I've not done anything explicit, so I'm lost as to where these
> interface names have been specified. I can see what the syntax needs
> to be, but I've no idea where it's being used
>
> On Apr 24, 1:12 pm, Andrey Pohilko <a...@apc.kg> wrote:
>
>
>
>
>
>
>
> > This is exactly "Specifying Metric Params" that you doing. So you must to
> > escape colons inside interface names, like eth0\:12
>
> > вторник, 24 апреля 2012 г., 14:21:51 UTC+3 пользователь Tim C написал:
>
> > > Nope. Cannot find this point in the documentation. The only reference

> > > that I can see is here:http://bit.ly/IzsiaOandrelates to Specifying