Loading ...
Sorry, an error occurred while loading the content.

Connection retries that seem to ignore retry parm?

Expand Messages
  • Jeff - WA4ZKO
    Was checking in on things this afternoon and noticed KB0WSA s connection (an AXUDP link) into my BBS was stuck in BPQMailChat. I also noticed an endless
    Message 1 of 4 , Apr 7 11:02 AM
    • 0 Attachment
      Was checking in on things this afternoon and noticed KB0WSA's connection (an AXUDP link) into my BBS was "stuck" in BPQMailChat. I also noticed an endless string of connect requests to the node (KB0WSA-6 MOBRA) showing in monitor that are ignoring the retry counter parm (7 in this case):

      [17:25:57T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:01T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:05T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:09T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:15T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:19T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:23T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:27T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:31T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:35T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:39T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:43T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:47T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:51T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:55T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:26:59T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:27:03T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:27:07T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:27:11T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>
      [17:27:14T WA4ZKO-5>KB0WSA-6 Port=8 <C C P>

      Looks like it's firing off every 4 seconds per FRack on that port, but not giving up after the 7 tries. This just goes on and on.

      Forcing a disconnect of KB0WSA in BPQBBS doesn't change things, the string of connect attempts continues. A few minutes ago KB0WSA apparently rebooted their node and things returned to normal after a few minutes.

      While I was watching things I also noticed another oddity, if I did a N MOBRA the 2nd number (obs counter ?) in that response was really high in the 150-160's and slowly dropping in value. Yeah, you read that right....in the high 100's. I cleared the screen so I can't cut-n-paste it here, but it was way above the 5 or less that it should of been.

      All other links to other nodes/BBS were working fine.

      Maybe Billie or K.O. can chime in on what was happening on their end this afternoon, but it was clear that my node didn't handle the dropout of that connection properly.

      Been a few other reports of folks seeing similar on RF. Did we ever find out what happened on this one:

      http://groups.yahoo.com/group/BPQ32/message/2870?l=1

      Looks to be pretty much what I saw.

      73
      Jeff
      WA4ZKO
      http://twitter.com/wa4zko
    • K.O. Higgs
      Shortly before noon I shut down MOBRA and all of its children to do some cleanup in the computer. About half past noon I re-started MOBRA (BPQ32,
      Message 2 of 4 , Apr 7 11:26 AM
      • 0 Attachment
        Shortly before noon I shut down MOBRA and all of its "children" to do some "cleanup" in the computer. About half past noon I re-started MOBRA (BPQ32, BPQTelNetServer, BPQMail, RMS Packet), Then I ate lunch.. after lunch I checked the operation of MOBRA and it seemed (and still seems) to be working properly. Are there special (or additional) checks that you would like for me to do?

        73,  K.O.

        On 4/7/2010 1:02 PM, Jeff - WA4ZKO wrote:
         

        Was checking in on things this afternoon and noticed KB0WSA's connection (an AXUDP link) into my BBS was "stuck" in BPQMailChat. I also noticed an endless string of connect requests to the node (KB0WSA-6 MOBRA) showing in monitor that are ignoring the retry counter parm (7 in this case):

        [17:25:57T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:01T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:05T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:09T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:15T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:19T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:23T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:27T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:31T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:35T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:39T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:43T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:47T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:51T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:55T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:26:59T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:27:03T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:27:07T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:27:11T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>
        [17:27:14T WA4ZKO-5>KB0WSA- 6 Port=8 <C C P>

        Looks like it's firing off every 4 seconds per FRack on that port, but not giving up after the 7 tries. This just goes on and on.

        Forcing a disconnect of KB0WSA in BPQBBS doesn't change things, the string of connect attempts continues. A few minutes ago KB0WSA apparently rebooted their node and things returned to normal after a few minutes.

        While I was watching things I also noticed another oddity, if I did a N MOBRA the 2nd number (obs counter ?) in that response was really high in the 150-160's and slowly dropping in value. Yeah, you read that right....in the high 100's. I cleared the screen so I can't cut-n-paste it here, but it was way above the 5 or less that it should of been.

        All other links to other nodes/BBS were working fine.

        Maybe Billie or K.O. can chime in on what was happening on their end this afternoon, but it was clear that my node didn't handle the dropout of that connection properly.

        Been a few other reports of folks seeing similar on RF. Did we ever find out what happened on this one:

        http://groups. yahoo.com/ group/BPQ32/ message/2870? l=1

        Looks to be pretty much what I saw.

        73
        Jeff
        WA4ZKO
        http://twitter. com/wa4zko


        -- 
        
        K.O. Higgs 
        n0kfq@...
        
        
      • Jeff - WA4ZKO
        Thanks K.O., that s all I was curious about unless you noticed an issue around that time. I could tell by your stats when your node was restarted and after
        Message 3 of 4 , Apr 7 3:01 PM
        • 0 Attachment
          Thanks K.O., that's all I was curious about unless you noticed an issue around that time. I could tell by your stats when your node was restarted and after that things cleared up.

          My guess is one (yours or mine) of the BBSes tried a scheduled connect right about the time you took yours down. Then somehow that connection got stuck on my end and BPQ didn't handle the link failure very gracefully for some reason.

          Also note that I shut BPQMailChat down and it didn't help either, so I suspect the bug is in the node portion not the BBS code.

          I was kind of busy multi-tasking during lunch, so I wasn't able to be overly thorough in my troubleshooting.


          73
          Jeff
          WA4ZKO
          http://twitter.com/wa4zko
        • K.O. Higgs
          I think you are probably right.. all was running normal with packet before I took the bbs down. It was not because of packet, but another program that I had to
          Message 4 of 4 , Apr 7 3:45 PM
          • 0 Attachment
            I think you are probably right.. all was running normal with packet before I took the bbs down. It was
            not because of packet, but another program that I had to re-start the computer.

            If you need me, just holler..  K.O.

            On 4/7/2010 5:01 PM, Jeff - WA4ZKO wrote:
             

            Thanks K.O., that's all I was curious about unless you noticed an issue around that time. I could tell by your stats when your node was restarted and after that things cleared up.

            My guess is one (yours or mine) of the BBSes tried a scheduled connect right about the time you took yours down. Then somehow that connection got stuck on my end and BPQ didn't handle the link failure very gracefully for some reason.

            Also note that I shut BPQMailChat down and it didn't help either, so I suspect the bug is in the node portion not the BBS code.

            I was kind of busy multi-tasking during lunch, so I wasn't able to be overly thorough in my troubleshooting.

            73
            Jeff
            WA4ZKO
            http://twitter. com/wa4zko


            -- 
            
            K.O. Higgs 
            n0kfq@...
            
            
          Your message has been successfully submitted and would be delivered to recipients shortly.