messaging server problem
HI, I have strange problems on messaging server its version is:
Sun Java(tm) System Messaging Server 6.1 HotFix 0.11 (built Feb, 2005)
libimta.so 6.1 HotFix 0.11 (built 16:16:35, Jan 28 2005)
SunOS host name 5.9 Generic_117171-12 sun4u sparc SUNW,Sun-Fire-V440
It was working fine but this day, it makes users read messages as unread frequently, user抯 mailboxes reports false quota, deleted messages
Are not expunged .mboxlist dir contains more files, even I have delete the contain to rebuild it by following the procedure and run reconstruct -m
Many times but this couldn抰 help. Any one could experience such problem or got an idea.
[677 byte] By [
ethiois] at [2007-11-26 6:49:29]
# 1
sounds like you need a
reconstruct -r
not a reconstruct -m
these commands are quite different, and do very different things. . . .
It also sounds like you may have some disk problems. When was the last time you restarted your Messagng Server?
Have any of the process crashed recently? Do you experience a buildup of "transaction logs"? (files with the name starting with "log" in the mboxlist directory)
You're also using some pretty old bits.You might want to upgrade to current version. What you're running is over a year old.
# 2
> sounds like you need a
>
> reconstruct -r
>
> not a reconstruct -m
>
> these commands are quite different, and do very
> different things. . . .
>
> It also sounds like you may have some disk problems.
> When was the last time you restarted your Messagng
> Server?
>
> Have any of the process crashed recently? Do you
> experience a buildup of "transaction logs"? (files
> with the name starting with "log" in the mboxlist
> directory)
>
> You're also using some pretty old bits.You might
> want to upgrade to current version. What you're
> running is over a year old.
Hi,tanks for your help
Befor a week it freezs and i have to take it up on the DR site.about the logs in the mbox list dir there are four fils that start with "log" .i have run reconstructr -r
but it dosn't resolve ,it loks fine for the time being but the problem exists.
the storge has no errors it looks fine.what do you think that makes read flag
to unread .
# 3
you say you have 4 transaction logs.
That's a problem. It likely means that one of more of your processes crashed, and left the database locked.
You need to recover from that FIRST
stop-msg
use ps to locate any processes that haven't stopped, and stop them.
Now, you can re-start. This is the ONLY way to unlock the database. What you're describing is a symptom of what we call an "orphan database lock". I've spoken about this many times in this forum. You can search for a more thorough treatment.
Once you're unlocked the database, you can then run reconstruct.
reconstruct -r user/userid
You MUST run reconstruct this way, for a single user. Here's what I say over the phone:
"reconstruct dash r 'the word user' slash 'the user id'
if you run it this way,
reconstruct -r userid
it will do nothing. It'll run, but since the syntax is not correct, nothing useful gets done.
