Messenger Pro (version 5.13 approx) on Nixiyo, my Iyonix, freezes
Nixiyo when I run it. As soon as I run it, the Messenger status panel
says that it is "debatching Lakeview/incoming mail: 13364" but nothing
gets debatched and Nixiyo immediately freezes.
!SysLog.Logs.MsgServe has the line "Index inconsistency detected in
group 'lakeview/Incoming mail' - reason 5" which is, presumably,
relevant.
I can't get into Messenger Pro to do an expiry or do anything as running
it causes the freeze immediately. I am posting this from Riscy, my Risc
PC.
Any ideas?
Cheers,
David Lane
--
RISC OS 'til the bitter ends.
> Messenger Pro (version 5.13 approx) on Nixiyo, my Iyonix, freezes
> Nixiyo when I run it. As soon as I run it, the Messenger status panel
> says that it is "debatching Lakeview/incoming mail: 13364" but nothing
> gets debatched and Nixiyo immediately freezes.
>
> !SysLog.Logs.MsgServe has the line "Index inconsistency detected in
> group 'lakeview/Incoming mail' - reason 5" which is, presumably,
> relevant.
>
> I can't get into Messenger Pro to do an expiry or do anything as
> running it causes the freeze immediately. I am posting this from
> Riscy, my Risc PC.
If using Hermes, the corrupt file may be in !Hermes.MailDir.mailin.spool
Try moving the contents of that directory elsewhre, so that it is empty.
If that allows MPro to start, investigate the removed files.
Tony
!Hermes.MailDir.mailin.spool was empty. However, there is another
directory in !Hermes.MailDir.mailin called uid which had 5 text files,
0001, 0002, 0003, 0004 and 0005, with dates of the last time (today)
that I did a fetch. Each file starts #UID List V2 and, for some
files that is all there is and for others there are entries like
Uid:1My47x-1O6000-01-BMY
Stamp:1257681307
Action:1
Reason:0
From:
Subject:
Head:
Size:97274
I removed the contents of this uid directory, ran Messenger Pro again
with the same result, a freeze, necessitating a shut down and restart.
:-(
David Lane
--
Dr D.R. Lane Address: 11, Coniston Way,
Tel: +44-(0)1737 767210 Reigate,
Fax: 0870 056 1781 (24 hours) Surrey RH2 0LN
Email: D_L...@Lakeview.demon.co.uk U.K.
What about
!Newsdir.MsgServe.Queue.Mail
and
!Newsdir.MsgServe.Transports.Hermes
Tony
> I removed the contents of this uid directory, ran Messenger Pro again with
> the same result, a freeze, necessitating a shut down and restart. :-(
I'm not familiar with Hermes, so I'll leave purging the mail queue to
someone else.
However: is the disc OK? What do DiscKnight and Verify think?
Second, is this /really/ a Messenger problem, or could it be the "elderly
Iyonix doesn't like heavy disc accesses after switch-on" problem? Do you
ever get other disc errors reported during heavy use (which clear after a
re-boot)? Does leaving the machine on for a few hours and /then/ starting
Messenger make any difference?
--
Steve Fryatt - Leeds, England
A DiscKnight check showed that there were errors in the disc map, some
files in the Msgserve Spool directory being not found in the map.
A DiscKnight repair was successful. The Overview file of
lakeview/incoming mail was corrupt.
The cause of all this was due to Nixiyo not starting well, possibly
due to Nixiyo being cold. Nixiyo froze while debatching. I have
noticed before that, if one attempts to get Nixiyo to do more than
one thing after starting, Nixiyo might freeze. I have to be more
patient!
Messenger Pro now works.
I had also thought of doing a DiscKnight check because Nixiyo was
writing to the disc when it froze.
Thanks for help, you encouraged me to do the disc check.
David Lane
--
RISC OS peace protesters say: ROMs not Bombs.
> I had also thought of doing a DiscKnight check because Nixiyo was
> writing to the disc when it froze.
Some time ago I had similar 'freezing' problems, often just after my
Iyonix startup, when debatching mail into Pluto. It happened more when it
had been colder overnight, but over many weeks slowly got worse and worse.
After much investigation, I realized it was happening whenever large
files were being written. This may be the case with Messenger as well.
I proved this by writing a simple little program called DiscTest to
stress the disc by writing large temporary files, which is now available
from my web site http://www.avisoft.f9.co.uk if you want to try it.
It was also true that RMkill DMAManager made the problem reduce of even
disappear, because it slowed it down so the disc (and PSU) was not being
stressed so much.
I checked the PSU voltages - they looked fine, BUT a replacement PSU
solved the problem immediately. Bad voltages mean bad PSU: good voltages
do not necessarily mean good PSU!
Martin
--
Martin Avison
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received.