LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Paul Russell <[log in to unmask]>
Tue, 18 May 2010 09:42:13 -0400
text/plain (55 lines)
 > show version
LISTSERV(R) High Performance for unix version 15.5, managed by:
   [log in to unmask]

Master nodes file version:   2009-06-02 17:32:59 (VERS9922)
NJE peers file version:      2009-06-02 17:32:59
Internet peers file version: 2010-02-04 19:46:41
Service file version:        2009-10-07 23:45:39 (VERS9922)
Alias file version:          2009-12-10 00:03:02
Running under:               Linux 2.6.9-89.0.16.ELsmp
Build date:                  27 Nov 2007

 > show license
License type:      Permanent
Expiration date:   None - perpetual license
Maintenance until: 30 Jun 2010, serial number MNT-NOTRED-8
Capacity:          Unlimited
Product options:   HPO
Version:           15.5
Serial number:     NOTRED-10
Build date:        27 Nov 2007

Comments:          1395

====================================================================
One of our LISTSERV servers has been issuing the following error messages every
hour on the hour for the past several days, perhaps longer.  It also issued
these error messages after a recent restart of the LISTSERV service.

--- begin ---
 >>> Error during virtual disk slot emulation:
Invalid virtual disk slot designation - "".
18 May 2010 08:20:45 >>> Error X'00000065' during virtual disk slot emulation
for "" <<<
18 May 2010 08:20:45  -> Severity: Severe error
18 May 2010 08:20:45  -> Facility: Generic error codes
18 May 2010 08:20:45  -> Abstract: Logic error detected
18 May 2010 08:20:45  -> Rejected: Invalid virtual disk slot designation -
18 May 2010 08:20:45               "".
 >>> Error from LSWDACCF - Invalid virtual disk slot designation - "".
--- end ---

The only reference I can find to this error is in a thread in this list from
April 1996.  A site running LISTSERV 1.8b reported recurring errors of this
nature.  Eric responded and advised the site to upgrade to the latest version of
LISTSERV.

What is the likely cause of this error, and what do I need to do to resolve the
issue?

--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame

ATOM RSS1 RSS2