OpenVZ Forum


Home » General » Support » running dnstop in vm doesn't work -> unsupported data link type 113
icon5.gif  running dnstop in vm doesn't work -> unsupported data link type 113 [message #8124] Wed, 08 November 2006 17:38 Go to next message
rema is currently offline  rema
Messages: 17
Registered: November 2006
Junior Member
Hello,

I installed a debian based openvz machine.
Into a VM i tried to run dnstop for monitoring dns-request.

I even get this errormessage:

root:mirror-12:/# dnstop venet0:0
unsupported data link type 113

any ideas ?

Best Rene
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8225 is a reply to message #8124] Fri, 10 November 2006 16:47 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member

# strace -f -o out dnstop venet0:0
and attach out file then.


http://static.openvz.org/userbars/openvz-developer.png
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8233 is a reply to message #8225] Fri, 10 November 2006 18:41 Go to previous messageGo to next message
rema is currently offline  rema
Messages: 17
Registered: November 2006
Junior Member
tnx fpr your anwser.

15608 execve("/usr/sbin/dnstop", ["dnstop", "venet0:0"], [/* 11 vars */]) = 0
15608 uname({sys="Linux", node="dexxxxxxx", ...}) = 0
15608 brk(0)                            = 0x80ce000
15608 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
15608 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
15608 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)
15608 open("/etc/ld.so.cache", O_RDONLY) = 3
15608 fstat64(3, {st_mode=S_IFREG|0644, st_size=9241, ...}) = 0
15608 old_mmap(NULL, 9241, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
15608 close(3)                          = 0
15608 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
15608 open("/usr/lib/libpcap.so.0.8", O_RDONLY) = 3
15608 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P6\0\000"..., 512) = 512
15608 fstat64(3, {st_mode=S_IFREG|0644, st_size=150544, ...}) = 0
15608 old_mmap(NULL, 151548, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001b000
15608 old_mmap(0x4003f000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x24000) = 0x4003f000
15608 close(3)                          = 0
15608 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
15608 open("/lib/libncurses.so.5", O_RDONLY) = 3
15608 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\342"..., 512) = 512
15608 fstat64(3, {st_mode=S_IFREG|0644, st_size=252592, ...}) = 0
15608 old_mmap(NULL, 257868, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40040000
15608 old_mmap(0x40076000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x35000) = 0x40076000
15608 close(3)                          = 0
15608 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
15608 open("/lib/tls/libc.so.6", O_RDONLY) = 3
15608 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"..., 512) = 512
15608 fstat64(3, {st_mode=S_IFREG|0755, st_size=1254660, ...}) = 0
15608 old_mmap(NULL, 1264972, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4007f000
15608 old_mmap(0x401a9000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x129000) = 0x401a9000
15608 old_mmap(0x401b2000, 7500, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x401b2000
15608 close(3)                          = 0
15608 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x401b4000
15608 set_thread_area({entry_number:-1 -> 6, base_addr:0x401b4580, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
15608 munmap(0x40018000, 9241)          = 0
15608 brk(0)                            = 0x80ce000
15608 brk(0x80ef000)                    = 0x80ef000
15608 brk(0)                            = 0x80ef000
15608 time(NULL)                        = 1163183883
15608 stat64("venet0:0", 0xbffff944)    = -1 ENOENT (No such file or directory)
15608 socket(PF_PACKET, SOCK_RAW, 768)  = 3
15608 ioctl(3, SIOCGIFINDEX, {1, "lo"}) = 0
15608 ioctl(3, SIOCGIFHWADDR, 0xbffff730) = 0
15608 close(3)                          = 0
15608 socket(PF_PACKET, SOCK_DGRAM, 768) = 3
15608 ioctl(3, SIOCGIFINDEX, {3, "venet0:0"}) = 0
15608 bind(3, {sa_family=AF_PACKET, proto=0x03, if3, pkttype=PACKET_HOST, addr(0)={0, }, 20) = 0
15608 getsockopt(3, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
15608 setsockopt(3, SOL_PACKET, PACKET_ADD_MEMBERSHIP, "\3\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
15608 ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
15608 setsockopt(3, SOL_SOCKET, SO_ATTACH_FILTER, "\1\0\0\0\10\360\3@", 8) = 0
15608 fcntl64(3, F_GETFL)               = 0x2 (flags O_RDWR)
15608 fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
15608 recv(3, 0xbffff96b, 1, MSG_TRUNC) = -1 EAGAIN (Resource temporarily unavailable)
15608 fcntl64(3, F_SETFL, O_RDWR)       = 0
15608 setsockopt(3, SOL_SOCKET, SO_ATTACH_FILTER, "\16\0\1@\260\350\f\10", 8) = 0
15608 write(2, "unsupported data link type 113\n", 31) = 31
15608 exit_group(1)                     = ?



-----------
Maybe this lines ?
15608 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
15608 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)


[Updated on: Mon, 13 November 2006 14:41] by Moderator

Report message to a moderator

Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8235 is a reply to message #8233] Fri, 10 November 2006 19:58 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member

can you also strace it on working node plz?


http://static.openvz.org/userbars/openvz-developer.png
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8280 is a reply to message #8235] Mon, 13 November 2006 14:25 Go to previous messageGo to next message
Alexandr Andreev is currently offline  Alexandr Andreev
Messages: 35
Registered: October 2006
Member
Generally you can't use dnstop with venet0, because venet0 is a special interface and dnstop knows nothing about it.

You can use virtual ethernet device (veth) instead (http://wiki.openvz.org/Veth)

But if it's critical for you to use venet, we can make a patch for dnstop (or maybe for libpcap) and you will be able to use dnstop with venet.
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8282 is a reply to message #8124] Mon, 13 November 2006 15:50 Go to previous messageGo to next message
Alexandr Andreev is currently offline  Alexandr Andreev
Messages: 35
Registered: October 2006
Member
Here is a quick patch for dnstool.c

http://bugzilla.openvz.org/show_bug.cgi?id=345
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #8292 is a reply to message #8282] Mon, 13 November 2006 20:43 Go to previous messageGo to next message
rema is currently offline  rema
Messages: 17
Registered: November 2006
Junior Member
tnx for the patch, i'll try it out and post the result.

best rema
Re: running dnstop in vm doesn't work -> unsupported data link type 113 [message #35813 is a reply to message #8124] Fri, 24 April 2009 08:33 Go to previous message
aseques is currently offline  aseques
Messages: 12
Registered: December 2006
Junior Member
Just for the record, the version from the official site works fine with venet interfaces without patching.

You can get it here: http://dns.measurement-factory.com/tools/dnstop/src/dnstop-2 0090128.tar.gz
Previous Topic: ** SOLVED ** e1000e device eth0 does not seem to be found
Next Topic: ssh prblem with virtual
Goto Forum:
  


Current Time: Thu May 09 09:17:38 GMT 2024

Total time taken to generate the page: 0.01679 seconds