[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #RSN-549334]: LDM-6.3.11 *possible* issue with external firewalls going down

Hi Gilbert,

Wow! That's a puzzler.

Thanks for sending it in.

I'll have to think about it.

Is there anything relevant in the LDM log file? Do the times match?

> I've seen this happen rarely for 15 years, but maybe you can figure it out.
> 
> Per Victor Gensini at NIU, they replaced their campus firewall this past
> week. When they took the firewall down, and then brought the new one up,
> all was well with the campus network except his LDM 6.13.11 had crashed
> with a corrupt queue. In years past, they had significant issues with
> their firewall, and when it went down, occasionally, the LDM queue was
> instantly corrupted, and thus the LDM crashed.
> 
> Obviously, this is still going on. I was wondering if a product got
> chopped off right in the middle of being sent as the firewall went
> down? Obviously, we don't want to keep bringing the firewall down and
> up to try and diagnose this issue. :-)  Again, it only happens, and not
> consistently, when the *external* (ie, University) firewall the LDM is
> behind goes down.
> 
> Obviously, since this rarely happens, I'm not sure this is worth
> pursuing. I can tell you this happens to other software I use, which
> forces me to restart it (notably GRlevel3 and Analyst, which has to be
> restarted if the Internet is lost while storm chasing, or when NIU's
> firewall went down). But I thought you'd want to know that this is still
> happening. I don't know if there can be a fix for this or not. But if
> there is, you'd be the guy to know...


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RSN-549334
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.