BLOG     |     FORUM
Welcome, Guest
Username: Password: Remember me
Issues related to installation, running, bugs, and features.

TOPIC: Installer Package

Re:Installer Package 10 years 6 months ago #454

vivek [unleash] wrote:
Okay, this is probably due to listening on eth0 by default.

Sefault started occurring after I switched from the default eth0 to the Dag stream.
If it continues to segfault, can you send me the log file by email to info @ unleashnetworks ?

What log are you looking for? The syslog only has the single line entry for the segfault and there's no reference to the crash in any of the Trisul log files.
The administrator has disabled public write access.

Re:Installer Package 10 years 6 months ago #455

I am looking for INFO messages in the /usr/local/var/log/trisul/ns-001.log file. Specifically I want the lines that say :

Libpcap mode is now : x

and

listening on dagX


From the dmesg it seems like something tripped in libpcap 1.1.1 that might have been caused by the way Trisul called into it. Perhaps I can send you a build dynamically linked with libpcap 1.1.1.

Thanks,
Vivek R
Unleash Networks
Support : www.unleashnetworks.com/forums
The administrator has disabled public write access.

Re:Installer Package 10 years 6 months ago #456

vivek [unleash] wrote:
I am looking for INFO messages in the /usr/local/var/log/trisul/ns-001.log file. Specifically I want the lines that say :

Libpcap mode is now : x

ns-001.log:Wed May 4 11:51:18 2011.654410 DEBUG Opening and registering adapter 0 dag0:62
ns-001.log:Wed May 4 11:51:20 2011.858590 INFO Found adapter [2] dag0:12 : (No description available)
ns-001.log:Wed May 4 11:51:20 2011.858600 INFO Found adapter [3] dag0:14 : (No description available)
ns-001.log:Wed May 4 11:51:20 2011.858703 ERROR Requested adapter 0 [dag0:62] not found on this machine
ns-001.log:Wed May 4 11:51:20 2011.858725 ERROR Error initializing adapter dag0:62, check TRISUL_CAPTURE_PROFILES table

What's interesting to me here is I haven't defined dag0:12 and dag0:14 in Trisul(they're assigned to some other software). I have dag0:62 defined as the listening interface in Trisul.
listening on dagX

ns-001.log:Wed May 4 11:51:18 2011.613957 INFO Libpcap run mode is set to 0
The administrator has disabled public write access.

Re:Installer Package 10 years 6 months ago #457

Hi,

For some reason Trisul is not picking up the dag62:0 interface that you created. The other interfaces in the log are just Trisul enumerating the available interfaces.

Back to the log:
ns-001.log:Wed May 4 11:51:18 2011.613957 INFO Libpcap run mode is set to 0

I was expecting to find "mode is set to 1"
ns-001.log:Wed May 4 11:51:18 2011.654410 DEBUG Opening and registering adapter 0 dag0:62
ns-001.log:Wed May 4 11:51:20 2011.858590 INFO Found adapter [2] dag0:12 : (No description available)
ns-001.log:Wed May 4 11:51:20 2011.858600 INFO Found adapter [3] dag0:14 : (No description available)

I also expected to see adapter [1].



I made some changes to the trisul build that might fix this.

Can you download from
www.unleashnetworks.com/lib/private/trisul_1.2.708_amd64.deb

Remove old package (dpkg -r) and install the new one.

Once done - run this command to list all interfaces seen by trisul

trisul --listdev

You should see all your dag interfaces, including the dag62:0. This is just a call to pcap_findalldevs() so the DAG API must recognize the interface.

If you can see dag62 then, just start Trisul. It should work. If you are on a very high bandwidth environment you can try to disable the packet store for now and add it in later.

I hope this does the trick. Please let me know how it goes.

Thanks,

Vivek
Vivek R
Unleash Networks
Support : www.unleashnetworks.com/forums
The administrator has disabled public write access.

Re:Installer Package 10 years 6 months ago #458

See the docs here for listing interfaces unleashnetworks.com/trisulwiki/docs/doku...available_interfaces
Vivek R
Unleash Networks
Support : www.unleashnetworks.com/forums
The administrator has disabled public write access.

Re:Installer Package 10 years 6 months ago #459

root@:~# dpkg -r trisul
(Reading database ... 79778 files and directories currently installed.)
Removing trisul ...
Stopping trisul daemon:
Terminated
invoke-rc.d: initscript trisul, action "stop" failed.
Processing triggers for ureadahead ...

root@:~# dpkg -i --ignore-depends=libpcap0.8 trisul_1.2.708_amd64.deb
Selecting previously deselected package trisul.
(Reading database ... 79722 files and directories currently installed.)
Unpacking trisul (from trisul_1.2.708_amd64.deb) ...
Setting up trisul (1.2.708) ...
Processing triggers for ureadahead ...

root@:~# trisul --listdev
---------------------------------------------------------------------------
Num     Name            Description 
---------------------------------------------------------------------------
1       eth0            not available
2       dag0:12         not available
3       dag0:14         not available
4       eth1            not available
5       usbmon1         USB bus number 1
6       usbmon2         USB bus number 2
7       usbmon3         USB bus number 3
8       usbmon4         USB bus number 4
9       usbmon5         USB bus number 5
10      usbmon6         USB bus number 6
11      usbmon7         USB bus number 7
12      usbmon8         USB bus number 8
13      any             Pseudo-device that captures on all interfaces
14      lo              not available
---------------------------------------------------------------------------

root@:~# trisul --version
1.2.708

Still not finding the other interfaces. Not sure why it's only picking out 12 and 14. Everything below 20 has something listening on it, nothing special about those 2.
The administrator has disabled public write access.
Moderators: vivek [unleash]
Time to create page: 0.033 seconds