| Bug ID |
10763
|
| Summary |
ring buffer fails to create new file occasionally
|
| Product |
Wireshark
|
| Version |
1.10.6
|
| Hardware |
x86
|
| OS |
Debian
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
root@T3400:~# tshark -v
tshark: Lua: Error during loading:
[string "/usr/share/wireshark/init.lua"]:46: dofile has been disabled due to
running Wireshark as superuser. See
http://wiki.wireshark.org/CaptureSetup/CapturePrivileges for help in running
Wireshark as an unprivileged user.
TShark 1.10.6 (v1.10.6 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.39.91, with libpcap, with libz 1.2.8, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.10.0, with
Lua 5.2, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT
Kerberos, with GeoIP.
Running on Linux 3.13.0-39-generic, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8.
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Built using gcc 4.8.2.
root@T3400:~#
--
Attempting to run tshark with a 15 minute 96 file ring buffer.
command: tshark -i <interface> -b duration:900 -b files:96 -w /folder/file.pcap
Application runs fine for days but occassionally fails to start a new trace for
some time. Failure ranges from hours to almost a day.
cap_00077_20141204133122.pcap
cap_00078_20141204134622.pcap
cap_00079_20141204150647.pcap
cap_00080_20141204152147.pcap
You can see from file 77 to 78 the time frame was 15 minutes. However from 78
to 79 it was over an hour. From 79 to 80 the duration returned to 15 minutes.
In the following instance the duration of the failure was roughly 6 hours.
cap_00314_20141208043140.pcap
cap_00315_20141208044640.pcap
cap_00316_20141208105839.pcap
cap_00317_20141208111339.pcap
The problem doesn't seem to be related to TOD as one day it occurs at 3 PM and
the next day it occurs at 4 AM.
You are receiving this mail because:
- You are watching all bug changes.