You are running version 5419 now, but this morning you were not.  5419 started getting pushed out to clients sometime after 11:30am today.  I, too, experienced two lockups this morning.  After my last reboot, my system fetched the 5419 update, and the lockups have stopped.  Note that NOD32 does not advertise to you that it is fetching updates, so you likely would not have noticed when the signature database changed.


On 9/2/2010 12:14 PM, Rama Kocherlakota wrote:
[log in to unmask]" type="cite">Well, I'm on 5419 and my system locked up several times this morning.


On 9/2/2010 11:55 AM, J. Greg Mackinnon wrote:
  The problematic database version was 5418... I have been able to
verify that this was the database version that was in use on at least
one locked-up system. (You can verify this to be the problem by
disconnecting ethernet cables and switching off wireless on a locked up
system /prior to /forcing a restart. Check the signature database
version before reconnecting to the network.)
J. Greg Mackinnon | ETS Systems Architecture and Administration | x68251

On 9/2/2010 11:51 AM, J. Greg Mackinnon wrote:
Currently we suspect that these problems are being caused by bad ESET
NOD32 antivirus signatures:

ESET already is distributing new signatures that should rectify the
problem. If your system is using virus signature database version 5419
or later, you should be okay (hover you mouse over the ESET green sys
i nthe system tray to determine the database version in use on you

J. Greg Mackinnon | ETS Systems Architecture and Administration | x68251

On 9/2/2010 9:27 AM, Zoey Trenkle wrote:
We are having connectivity issues in our department, 221 Waterman.
Staff are experiencing lag time or freezing up in web browsers and
other applications.

Anyone else?

J. Zoey Trenkle
Information Technology Professional
Student Financial Services
The University of Vermont
tel: 802-656-0365
fax: 802-656-4076
[log in to unmask]