Menu
▾
▴
Re: [como-devel] Como on x86_64
|
From: Iannaccone, G. <gia...@in...> - 2009-08-10 20:08:23
|
I don't think Como on 64bit OS has ever been tested. I'm not surprised of seeing weird behaviors... -gianluca From: Oana Goga [mailto:oan...@en...] Sent: Monday, August 10, 2009 12:07 PM To: com...@li... Subject: [como-devel] Como on x86_64 Hello, I am trying to run CoMo v1.5 on a system with a: - 64bits processor : Dual-Core AMD Opteron 2222 and - kernel: Linux 2.6.26-2-amd64 #1 SMP Thu May 28 21:28:49 UTC 2009 x86_64 GNU/Linux. The installation works without problems, but, when I am trying to analyze a pcap trace file (example-trace.pcap) it doesn't read any packet, and I can't see any error in the log: $ /usr/local/bin/como -c como.conf ---------------------------------------------------- CoMo v1.0 (built Aug 10 2009 20:34:04) Copyright (c) 2004-2007, Intel Corporation All rights reserved. ---------------------------------------------------- ... log level: UI WARN STORAGE CAPTURE EXPORT QUERY SNIFFER TIMER ... sniffer [pcap] /usr/local/etc/como/example-trace.pcap [67813.091157 su] allocated 2048 MB of mapped memory [67813.091311 su] new_mem need 15184 have 4096 [67813.091384 su] create_socket SERVER [/tmp/comot5xAHw/SUPERVISOR.sock] 3 [67813.091405 su] create_socket SERVER [/tmp/comot5xAHw/STORAGE.sock] 4 [67813.091427 su] create_socket SERVER [/tmp/comot5xAHw/CAPTURE.sock] 5 [67813.108745 su] create_socket SERVER [http://localhost:44444/] 6 [67813.108880 su] new_mem need 208 have 512 [67813.108903 su] new_mem need 263304 have 16384 [67813.109823 su] new_mem need 8 have 8 [67813.109832 su] new_mem need 12 have 2 [67813.109843 su] new_mem need 4 have 4 [67813.109852 su] new_mem need 56 have 8 [67813.109861 su] new_mem need 80 have 4 [67813.109867 su] new_mem need 20 have 2 [67813.109873 su] new_mem need 100 have 16 [67813.109878 su] new_mem need 20 have 8 [67813.109885 su] new_mem need 88 have 4 [67813.109889 su] new_mem need 20 have 2 [67813.109894 su] new_mem need 56 have 16 [67813.109899 su] new_mem need 100 have 8 [67813.109905 su] new_mem need 19 have 4 [67813.109956 su] new_mem need 208 have 32 [67813.109966 su] new_mem need 11552 have 512 [67813.109992 su] new_mem need 56 have 8 [67813.109998 su] new_mem need 100 have 16 [67813.110003 su] new_mem need 19 have 2 [67813.110054 su] new_mem need 208 have 8 [67813.110063 su] new_mem need 20 have 4 [67813.110072 su] new_mem need 56 have 32 [67813.110079 su] new_mem need 100 have 8 [67813.110084 su] new_mem need 19 have 2 [67813.110132 su] new_mem need 208 have 16 [67813.110142 su] new_mem need 1048592 have 65536 [67813.113404 su] new_mem need 56 have 4 [67813.113414 su] new_mem need 100 have 8 [67813.113421 su] new_mem need 20 have 64 [67813.113428 su] new_mem need 88 have 4 [67813.113433 su] new_mem need 20 have 2 [67813.113477 su] new_mem need 208 have 8 [67813.113487 su] new_mem need 8 have 16 [67813.113494 su] new_mem need 56 have 4 [67813.113501 su] new_mem need 80 have 8 [67813.113506 su] new_mem need 20 have 2 [67813.113555 su] new_mem need 208 have 32 [67813.113565 su] new_mem need 16 have 4 [67813.113573 su] new_mem need 56 have 8 [67813.113579 su] new_mem need 100 have 16 [67813.113584 su] new_mem need 19 have 2 [67813.113590 su] new_mem need 120 have 8 [67813.113595 su] new_mem need 19 have 4 [67813.113600 su] new_mem need 108 have 64 [67813.113606 su] new_mem need 19 have 2 [67813.113614 su] new_mem need 56 have 8 [67813.113619 su] new_mem need 132 have 16 [67813.113626 su] new_mem need 18 have 4 [67813.113631 su] new_mem need 152 have 8 [67813.113637 su] new_mem need 18 have 2 [67813.113643 su] new_mem need 140 have 32 [67813.113649 su] new_mem need 18 have 8 [67813.113709 su] new connection from peer STORAGE on fd 7 [67813.091846 st] new connection from peer EXPORT on fd 7 [67813.113768 su] new connection from peer EXPORT on fd 8 [67813.091816 ex] create_socket CLIENT [/tmp/comot5xAHw/STORAGE.sock] 7 [67813.113808 su] new connection from peer CAPTURE on fd 9 [67813.091826 ex] create_socket CLIENT [/tmp/comot5xAHw/CAPTURE.sock] 8 [67813.092114 ca] sniffer-pcap: opening file /usr/local/etc/como/example-trace.pcap [67813.092152 ca] datalink Ethernet (1) [67813.092198 ca] new connection from peer EXPORT on fd 8 [67813.114020 ca] module apps activated with filter ip [67813.114112 ca] module protocol activated with filter ( ip ) and (ip) [67813.114181 ca] module topaddr activated with filter ( ip ) and (ip) [67813.114239 ca] module topports activated with filter ( udp or tcp ) and (tcp or udp) [67813.114301 ca] module traffic activated with filter all [67813.114358 ca] module tuple activated with filter ( ip ) and (ip) [67813.139904 st] new client for [/capture/analyse_oana/data/apps], id 0 [67813.140460 ca] sniffers enabled [67813.140040 st] new client for [/capture/analyse_oana/data/protocol], id 1 [67813.140467 ca] new_mem need 65536 have 32768 [67813.140146 st] new client for [/capture/analyse_oana/data/topaddr], id 2 [67813.140244 st] new client for [/capture/analyse_oana/data/topports], id 3 [67813.140332 st] new client for [/capture/analyse_oana/data/traffic], id 4 [67813.140438 st] new client for [/capture/analyse_oana/data/tuple], id 5 - up 0d00h04m15s; mem 2/1/2/2048MB (0); pkts 0 drops 0; mdl 6/6 I observed that soon after the launching como, one processor arrives at 100% and stays blocked there. Anyway, when I am trying to capture packets from eth0 with the libpcap sniffer it works perfectly fine. Do you have any idea why I am getting this behavior? Thanks, Oana |
