Hi Avon, g00r00, All,

I have a replicable problem and have had to disable message packing from all maintenance jobs.

When running the message packing, mutil seems to think that all has done
well, it will pack what it needs to and logs as if everything is normal and
it hasn't done anything wacky.

However, when the job completes, all message bases have 0 messages in them
and the data files have gone back to completely empty - all the .j* files are gone, just .lnk and .xlr files remain in the message base folder. I've just done another test run and the end of the mutil log file for packing the bases looks like this:

+ May 30 16:03:05 Results: Removed 4 msgs in 10 bases in 7.02s
+ May 30 16:03:05 Shutdown Normal (0)

I presume there must be something funky going on with this routine where it's nuking files instead of writing them out.

For now, I won't be doing any message packing.

Thanks,
Adam

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Family Fun BBS (21:2/124)

On 05/30/17, Kinetix said the following...

When running the message packing, mutil seems to think that all has done well, it will pack what it needs to and logs as if everything is normal and it hasn't done anything wacky.

Just out of curiosity, in your message base editor in mystic -cfg, what do
you have set for your Max Msgs and Max Msg Age?


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Well, that would depend on the base... Only the Email message base has 0 & 0 for msgs and age. The rest of the bases have at least 500 msgs and 365 days.

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Family Fun BBS (21:2/124)

+ May 30 16:03:05 Results: Removed 4 msgs in 10 bases in 7.02s
+ May 30 16:03:05 Shutdown Normal (0)

I presume there must be something funky going on with this routine where it's nuking files instead of writing them out.

Ive been running it for a number of years and I've never encountered this problem. I don't think anyone else has ever reported this either.

This is indeed strange.

When are you running it and what version are you using? Have you tried to
turn on loglevel=3 and look in the log after running the packer? If this is something you can easily replicate then we can certainly pinpoint the issue
and get it resolved!

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 05/30/17, Kinetix pondered and said...

However, when the job completes, all message bases have 0 messages in
them and the data files have gone back to completely empty - all the .j* files are gone, just .lnk and .xlr files remain in the message base folder. I've just done another test run and the end of the mutil log
file for packing the bases looks like this:

+ May 30 16:03:05 Results: Removed 4 msgs in 10 bases in 7.02s
+ May 30 16:03:05 Shutdown Normal (0)

I presume there must be something funky going on with this routine where it's nuking files instead of writing them out.

Adam just check ownership permissions for all files in /mystic and it's
child dirs. I suspect something may be amiss there.

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

When are you running it and what version are you using? Have you tried
to turn on loglevel=3 and look in the log after running the packer? If this is something you can easily replicate then we can certainly
pinpoint the issue and get it resolved!

You bet - all my mutil ini files have loglevel=3 set in them so I can get as much info on what's going on as possible. That's the part that's really strange with this issue, is that it doesn't error out, it believes everything has packed appropriately as per the tail end of the logs I posted in the
first message.

The mutil version is: MUTIL v1.12 A33 Tue, May 30 2017 (loglevel 3)

Hope we can track it down!

Thanks,
Adam

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Family Fun BBS (21:2/124)

Adam just check ownership permissions for all files in /mystic and it's child dirs. I suspect something may be amiss there.

They're all set appropriately everywhere I look, the same user that mystic and mis are running under. The PurgeMessageBases function doesn't have any
issue, nor do importing and exporting echomail.

Thanks,
Adam

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Family Fun BBS (21:2/124)

On 05/30/17, Kinetix pondered and said...

Adam just check ownership permissions for all files in /mystic and it child dirs. I suspect something may be amiss there.

They're all set appropriately everywhere I look, the same user that
mystic and mis are running under. The PurgeMessageBases function
doesn't have any issue, nor do importing and exporting echomail.

OK so all have the same group:user membership and the same read/write/execute privs? I just thought that perhaps there may be something amiss in the JAM
data files in this regards but if not, all good.

Best, Paul

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

OK so all have the same group:user membership and the same read/write/execute privs? I just thought that perhaps there may be something amiss in the JAM data files in this regards but if not, all good.

The permissions & ownerships are all good - files are 644, the one message subdir is 755, all owned by the mystic user & group.

Here's a thought I'd have back to you, though - I could see permission or ownership issues causing problems for the utilities, mystic itself, etc., but I'm not sure how that would cause files to get deleted - a lack of ownership
or permission would generally prevent that from occurring. But... I am definitely aware of the complications permissions can cause - everything but the top-level directories have been created & controlled by mystic and it's utilities itself, as I definitely don't want to be manually working on permissions the system wants.

Thanks!
Adam

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Family Fun BBS (21:2/124)