Sun Sep 07 2014 05:04:42 EDT from Freakdog @ Dog Pound BBS II
Wed Sep 03 2014 09:23:26 AM EDT from dothebart @ Uncensored
Wed Sep 03 2014 07:51:50 EDT from Freakdog @ Dog Pound BBS II
Tue Sep 02 2014 05:20:32 PM EDT from dothebart @ UncensoredI don't have any troubles with spool files, probably due to the single coredness of my server.
If you have, you will have to provide more information so that we can fix thisWFM YMMV ;-)
Hmm...I'm running my Citadel in a VirtualBox VM which has been allocated a single core. The underlying server is running a quad core CPU.
I find that if I remove the offending spool file, the issue goes away...I can always identify the offending spool file, easily, as it's the largest spool file in the spoolout directory...continuing to grow but never sent/picked up.I haven't encountered it in quite a while, though.
so if you re-sync a room this may happen to you?
where does it break? in collectding? or sending?
or does it break while collecting the spoolfiles with large attachments to the spoolfile to transmit?
I haven't resync'd a room in quite a long time...and I was not resyncing any rooms at the times this happened.
It appears to break while sending...if I was reading the logs, correctly, while spooling out, not while actually transmitting the spoolfile. In fact, the spoolfile was growing, I believe, because my node could not connect to the remote, nor did the remote seem to be connecting to me.
I'm not aware of any attachments that may have been in the spoolfiles at the time.
Ok, we have some fixes for this now. I found one missing critical section, and some conditions which would introduce race conditions with the queueing mechanism.
I guess it would be worth while retrying it.
