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
Siegfried Schmitt <[log in to unmask]>
Fri, 23 Apr 2004 20:00:41 +0200
text/plain (36 lines)
I am currently using LISTSERV 1.8d (2000b) on HP-UX 10.20. 

Today, shortly after midnight, LISTSERV crashed and I found the
following error in the log file:

>>> Error X'0028004B' writing file /usr/mailhost/lsv/home/signup.newf14 <<<

23 Apr 2004 00:00:45 SIGNUP files are being compressed...
23 Apr 2004 00:00:58 -> One entry removed.
23 Apr 2004 00:00:58 The time stamp of ALIASES NAMES has changed.
23 Apr 2004 00:00:58 -> Tables will be reindexed.
23 Apr 2004 00:00:58 Reloading host aliases...
23 Apr 2004 00:00:58 -> 50 entries, 111 hostnames, table size is 25k
23 Apr 2004 00:00:58 SIGNUP data is being re-hashed...
23 Apr 2004 00:01:08 >>> Error X'0028004B' writing file /usr/mailhost/lsv/home/signup.newf14 <<<
23 Apr 2004 00:01:08  -> Severity: Error
23 Apr 2004 00:01:08  -> Facility: LFxxx routines
23 Apr 2004 00:01:08  -> Abstract: Record length larger than 65535
23 Apr 2004 00:01:08  -> I/O mode: Block write

*** HALT statement encountered ***

A detailed analysis revealed that signup.file14 had been damaged. The file
contained an extremely long line (about 7000 characters, many "@" signs):

@N³Ô@@@AB@@@@@CK@NÙ@@@BB@@@@@CCM@N߬@...@@@@@C@@RLSRUHE.DE Wolf-Dieter Glaeser

After I had removed this long line from signup.file14, LISTSERV could be
restarted without any problems. Has anybody else encountered a similar
problem with a damaged signup file? I have no idea how this file could
have been damaged.

Kind regards,

Siegfried

ATOM RSS1 RSS2