Subj : mis poll get 'stuck'
To   : Biite
From : Zip
Date : Wed Sep 15 2021 11:21 pm

Hello Biite!

I got this first now -- or my Mystic's message pointers are acting up. =)

Anyway...

On 26 Jul 2021, Biite said the following...
 Bi> Same here, haven't checked here with strace (not really familiar on how
 Bi> to do that ;) )

To run mis poll manually from the command line and trace what it's doing, you could use something like:

strace -f -s32768 -vvv ./mis poll 2>&1 | tee /tmp/trace.txt

....and then break with Ctrl+C and look at /tmp/trace.txt.

But it's not a good "solution" for intermittent errors.

As for logrotate and stopping/starting Mystic, I use the "copytruncate" logrotate option instead, so that the "rotated" files are copies of the current logs and the current logs are truncated (and Mystic continues to write to them, so no need for stopping/starting Mystic).

Something like:

/mystic/logs/*.log {
        daily
        notifempty
        missingok
        rotate 7
        compress
        delaycompress
        copytruncate
        su bbsuser bbsgroup
}

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.