WatchGuard Firebox III needs restart after flood

I have the Firebox III/700, WG version 6.2.B1292.

After a huge and rapid data transfer, it times out. By huge and rapid, I mean I am running a search crawler that crawls thousands of websites.

I found a similar issue with a similar product here:

formatting link
Any help is highly appreciated.

Here is my log:

Log:

18051838 01/27/06 01:29:04 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051868 01/27/06 01:29:10 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051878 01/27/06 01:29:15 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051908 01/27/06 01:29:20 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051928 01/27/06 01:29:25 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051958 01/27/06 01:29:35 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18051998 01/27/06 01:29:42 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18052028 01/27/06 01:29:49 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18052078 01/27/06 01:29:58 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18052088 01/27/06 01:30:04 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18052108 01/27/06 01:30:10 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

18052118 01/27/06 01:30:14 kernel eth0: Transmit timed out, status e4360000, CSR12 000050cc, resetting...

08 01/27/06 02:29:56 installd[52] Watchguard Installer Daemon 6.2.B1315 (C) 1996-2003 WGTI

18 01/27/06 02:29:56 installd[52] Performing loopback detect..

28 01/27/06 02:29:56 installd[52] Loopback: No loopbacks detected.
Reply to
nyclamusician
Loading thread data ...

Hi

imho, the log does not contain sufficient information for a debug. Have you any opportunity to watch the incoming and outgoing packets ? "Transmit timed out" looks like too many connections to track.

Berk

snipped-for-privacy@gmail.com schrieb:

Reply to
Berk Uysaler

[snip]

You need to be running 7.x and the 4 service updates.

I never experienced the problems you are with 6.3, but the big question is why are you running such old firmware on the III/700?

Reply to
Leythos

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.