Subj : Re: Posted #X errors?
To   : paulie420
From : Avon
Date : Wed May 12 2021 02:51 pm

On 11 May 2021 at 03:18p, paulie420 pondered and said...
 
 pa> In your nodeX.log files, user message posts are logged like:
 pa> #TIME/DATE Posted #X #MESSAGE_AREA
 pa> X seems to count up, and sometimes skips around a bit.
 pa> I have one user who ALWAYS gets:
 pa> #TIME/DATE Posted #0 #MESSAGE_AREA
 pa> Always a #0, and their posts SAY Saving... Saved!, but are not being
 pa> added to the BBS. They didn't realize this, and have lost like 30
 pa> messages!
 pa> My logs show its only this one user, and everyone else can post
 pa> correctly.
 pa> Any ideas? What is that #X point to? Where I could hunt for issues?

It's pointing to the next available message number the user can post in the
message base. So if there were 50 messages in the message base, their post
would count as message 51 etc.

I'm wondering if it's an ACS permissions thing for your user? That they don't
have post privs set?

Another angle may be the message base itself being corrupt in which case
other users would have probs as well.

I guess it could be related to the user account in which case you might offer
to set them up with a new login and delete their old account from your user
database. This may fix it.

Perhaps check that message base pack and purge works ok across your bases too.

Those would be my first thoughts :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.