Still am not receiving anything from this side, though.
dothebart: Is that fix in 8.01?
It's definitely in 8.02, and I just posted tarballs of that release tonight.
All of the traffic bound for dogpound2 is no longer sitting in uncnsrd's spoolout directory, but rather in dogpound2's spoolin directory. Furthermore, dogpound2's spoolin directory contains a message that I sent to myself from dogpound2 to uncnsrd (which is where it's supposed to go first; the networker then sweeps it up and routes it).
It seems that the problem is that dogpound2's networking events are not firing.
Where are your citadel logs?
*whalks away whistling*
Thu Oct 13 2011 15:25:36 EDT from Freakdog @ Dog Pound BBS II Subject: Re:Do we have lock files for networking sessions?
we keep a list of nodes that we are currently talking to / are talking to us.
so, its sort of a lock.
Do Mai 05 2011 09:42:28 EDT von Freakdog @ Dog Pound BBS IIJust need to know...from where would I obtain the RPMs? (I think I missed that somewhere, and didn't notice it on the citadel.org download page yet)
Срд Апр 20 2011 06:55:51 EDT от dothebart @ Uncensored Тема: Re: Citadel @ RH-based distros
can you please provide the URLs from the OBS-Rpms for those distributions?
Now I'm repackaging it using 7.85 sources
*< kermit flails >*
Time to test networking.
hm, I probably broke networking for master
fixed with 2506fdb3c8df79cd2055bb3ca8306494d6d61e94
messages woludn't be netqueued...
Thu Nov 25 2010 09:54:01 AM EST from IGnatius T Foobar @ UncensoredAt the moment I'm trying to figure out why networking is all jammed up.
I'm seeing this in my logs:
2010/12/08 11:20:27.511984 [LWP:1125] [:4] network: processing inbound queue 2010/12/08 11:20:27.512041 [LWP:1125] [:4] network: processing 14434 bytes from /usr/local/citadel/network/spoolin//uncnsrd.4cfecf435e61fc87 2010/12/08 11:20:27.512528 [LWP:1125] [:4] network_process_buffer() processing 1 bytes 2010/12/08 11:20:27.512538 [LWP:1125] [:4] Corrupt message ignored. Length=1, firstbyte = 255, lastbyte = 255 2010/12/08 11:20:27.512550 [LWP:1125] [:4] network_process_buffer() processing 1 bytes 2010/12/08 11:20:27.512558 [LWP:1125] [:4] Corrupt message ignored. Length=1, firstbyte = 255, lastbyte = 255 2010/12/08 11:20:27.512569 [LWP:1125] [:4] network_process_buffer() processing 1 bytes 2010/12/08 11:20:27.512577 [LWP:1125] [:4] Corrupt message ignored. Length=1, firstbyte = 255, lastbyte = 255 2010/12/08 11:20:27.513198 [LWP:1125] [:4] network_process_buffer() processing 8175 bytes 2010/12/08 11:20:27.514751 [LWP:1125] [:4] CtdlSubmitMsg() called 2010/12/08 11:20:27.514764 [LWP:1125] [:4] ERROR: attempt to save message with NULL body 2010/12/08 11:20:27.514829 [LWP:1125] [:4] network: queue run completed
so, the new networker code is up and running.
for some reasons there were some contact attempts where the networker bailed out with 'dp2: so the : is to much.
imho it just can have been added by the server... maybe a connection overload?
Sun Oct 16 2011 09:53:53 EDT from Freakdog @ Dog Pound BBS II Subject: Re:Where is that list kept, how is it kept, and why is it that when I erased what appeared to be a spool file from the spoolout directory, networking with the node in question started working?
the list is kept in memory; its set by either the network queuing service itself, an inbound or an outbound networking connection.
once that connection is closed, the lock should be released.
However, I found a possible race very recently which I fixed by removing global vars.
unless you enable coring, and kill a stuck citserver with SIG11 and share some delights with us, we probably won't shed more light on why removing the file unfucked it.