In your nodeX.log files, user message posts are logged like:
#TIME/DATE Posted #X #MESSAGE_AREA

X seems to count up, and sometimes skips around a bit.

I have one user who ALWAYS gets:
#TIME/DATE Posted #0 #MESSAGE_AREA

Always a #0, and their posts SAY Saving... Saved!, but are not being added to the BBS. They didn't realize this, and have lost like 30 messages!

My logs show its only this one user, and everyone else can post correctly.

Any ideas? What is that #X point to? Where I could hunt for issues?

Thanks kindly, rockstars... :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 11 May 2021 at 03:18p, paulie420 pondered and said...

In your nodeX.log files, user message posts are logged like:
#TIME/DATE Posted #X #MESSAGE_AREA
X seems to count up, and sometimes skips around a bit.
I have one user who ALWAYS gets:
#TIME/DATE Posted #0 #MESSAGE_AREA
Always a #0, and their posts SAY Saving... Saved!, but are not being
added to the BBS. They didn't realize this, and have lost like 30 messages!
My logs show its only this one user, and everyone else can post
correctly.
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)

[MY POSTED #0 MESSAGE ISSUE]

Those would be my first thoughts :)

All of your suggestions are great; and we'll do those suggestions. Jeez - I don't know what it is. Its not my BBS; is on a drive [SDCard] that we have been having corruption issues with [ding], but no other users are experiencing it - and the user is ME... I have acs s240, with no weird settings in the Security Level part - so... weird; when we figure the issue I'll let you know, but you posted some suggestions for us to TRY. Thanks super kindly!! :P

Ugh... its always somethin.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 11 May 2021 at 10:30p, paulie420 pondered and said...

are experiencing it - and the user is ME... I have acs s240, with no

Perhaps try s255 too?

TRY. Thanks super kindly!! :P

No probs :)

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