Memory usage might be one culprit. Have you tried using
dumpcap instead of Wireshark?
Dumpcap works very well for long term capturing.
- Chris
From:
wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of John E Miles
Sent: Wednesday, May 05, 2010 1:47 PM
To: wireshark-dev@xxxxxxxxxxxxx
Cc: kris.chancery@xxxxxxxxxxxx
Subject: [Wireshark-dev] Wireshark Capture Program Shut Down Problem
=> Please Assist
Importance: High
Hello,
I am working
with a customer who is capturing Ethernet data off of their Managed Switch
using Wireshark and their program is shutting down unexpectedly and stopping
the capture of data.
They are
capturing data every (3) minutes using multiple files for a total of 480 files.
The goal is to have 480 (3) minute increments of data over the course of
24 hours.
The system
shuts down around the 48th file and stops capturing data.
The Data files
are ~20 MB of data so the Network is very very busy. It is being used for
Process Controls and Messaging, etc.
Can you assist
on common culprits which cause these unecessary shutdowns of Wireshark?
Please call
(402.321.5057) or email me (jemiles@xxxxxxxxxxxxxxx).
Thanks!
John E. Miles
Field Service Engineer (FSE)
Customer Support & Maintenance (CSM)
Rockwell Automation
5103 S. 111th St.
Omaha, NE
Office: 402.593.4185
Mobile: 402.321.5057
Email: jemiles@xxxxxxxxxxxxxxx
