From maiko at pcsinternet.ca Wed May 5 10:57:05 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Wed, 5 May 2021 09:57:05 -0500 Subject: [nos-bbs] heads up 'remote disc early' possibly corrupting area index ? Message-ID: I'm seeing an instance of say 5 bulletins I forward but the remote system is disconnecting before the 5th is done, and it would appear the (in this case) area 'ww' index is corrupted, so any subsequent forwards to the same partner or others forwarding that same area, result in JNOS just disconnecting after the FS +_=+@ whatever ... Example log entry : 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit Example log entry with major debugging : 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ 09:35:21? SUMCALL @ SUMCALL - about to validate FS line [FS +++++] msg cnt 5 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [0] 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [1] 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [2] 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [3] 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [4] 09:35:21? SUMCALL @ SUMCALL - FS is okay, now send '+' messages 09:35:21? SUMCALL @ SUMCALL - sline [$31941_SUMCALL] index [0] 09:35:21? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] 09:35:21? SUMCALL @ SUMCALL - fbbsendmsg: truncated ww msg 103 would result from err 2 09:35:21? SUMCALL @ SUMCALL - fbb send msg error, why ? 09:35:21? SUMCALL @ SUMCALL - not connected, why ? 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit Until I repair the index at the JNOS console using 'index www', then the forward behaves again. So if you have a gazillion forwarding partners, they will likely ALL behave like they're stuck and just doing nothing until you repair the index of the area that they are all working on. I'm not sure why this is happening, but after putting in some big debug code it's very clear what's going on here. Just thought this might be helpful information. Maiko / VE4KLM From maiko at pcsinternet.ca Wed May 5 11:00:29 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Wed, 5 May 2021 10:00:29 -0500 Subject: [nos-bbs] heads up 'remote disc early' possibly corrupting area index ? In-Reply-To: References: Message-ID: <560543c3-e17a-57fa-2222-e9f68e653649@pcsinternet.ca> As silly as it may sound, I wonder if perhaps an option to limit max messages for any particular remote systems in forward.bbs (?) is an idea ? comments ? On 05/05/2021 9:57 a.m., M Langelaar wrote: > I'm seeing an instance of say 5 bulletins I forward but the remote > system is > disconnecting before the 5th is done, and it would appear the (in this > case) > area 'ww' index is corrupted, so any subsequent forwards to the same > partner > or others forwarding that same area, result in JNOS just disconnecting > after > the FS +_=+@ whatever ... > > Example log entry : > > 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ > 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit > > Example log entry with major debugging : > > 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ > 09:35:21? SUMCALL @ SUMCALL - about to validate FS line [FS +++++] msg > cnt 5 > 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [0] > 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [1] > 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [2] > 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [3] > 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [4] > 09:35:21? SUMCALL @ SUMCALL - FS is okay, now send '+' messages > 09:35:21? SUMCALL @ SUMCALL - sline [$31941_SUMCALL] index [0] > 09:35:21? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] > 09:35:21? SUMCALL @ SUMCALL - fbbsendmsg: truncated ww msg 103 would > result from err 2 > 09:35:21? SUMCALL @ SUMCALL - fbb send msg error, why ? > 09:35:21? SUMCALL @ SUMCALL - not connected, why ? > 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit > > Until I repair the index at the JNOS console using 'index www', then > the forward > behaves again. So if you have a gazillion forwarding partners, they > will likely ALL > behave like they're stuck and just doing nothing until you repair the > index of the > area that they are all working on. > > I'm not sure why this is happening, but after putting in some big > debug code it's > very clear what's going on here. > > Just thought this might be helpful information. > > Maiko / VE4KLM > From maiko at pcsinternet.ca Wed May 5 11:07:22 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Wed, 5 May 2021 10:07:22 -0500 Subject: [nos-bbs] heads up 'remote disc early' possibly corrupting area index ? In-Reply-To: <560543c3-e17a-57fa-2222-e9f68e653649@pcsinternet.ca> References: <560543c3-e17a-57fa-2222-e9f68e653649@pcsinternet.ca> Message-ID: <5cb7d31e-ffc0-8eab-99cf-9e79d917b35e@pcsinternet.ca> last one, sorry ... AND I have still not been able to get the 'offset' feature to work, which is no doubt not helpful as far as keeping indexes clean, since JNOS just buggers up the flow whenever the 'offset' shows up - I need to get that working :( ??? about to validate FS line [FS ---!1500+] msg cnt 5 I've tried, but failed several times, hard to simulate this Anyways ... Maiko / VE4KLM On 05/05/2021 10:00 a.m., M Langelaar wrote: > As silly as it may sound, I wonder if perhaps an option to limit max > messages > for any particular remote systems in forward.bbs (?) is an idea ? > comments ? > > On 05/05/2021 9:57 a.m., M Langelaar wrote: >> I'm seeing an instance of say 5 bulletins I forward but the remote >> system is >> disconnecting before the 5th is done, and it would appear the (in >> this case) >> area 'ww' index is corrupted, so any subsequent forwards to the same >> partner >> or others forwarding that same area, result in JNOS just >> disconnecting after >> the FS +_=+@ whatever ... >> >> Example log entry : >> >> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >> >> Example log entry with major debugging : >> >> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >> 09:35:21? SUMCALL @ SUMCALL - about to validate FS line [FS +++++] >> msg cnt 5 >> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [0] >> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [1] >> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [2] >> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [3] >> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [4] >> 09:35:21? SUMCALL @ SUMCALL - FS is okay, now send '+' messages >> 09:35:21? SUMCALL @ SUMCALL - sline [$31941_SUMCALL] index [0] >> 09:35:21? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] >> 09:35:21? SUMCALL @ SUMCALL - fbbsendmsg: truncated ww msg 103 would >> result from err 2 >> 09:35:21? SUMCALL @ SUMCALL - fbb send msg error, why ? >> 09:35:21? SUMCALL @ SUMCALL - not connected, why ? >> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >> >> Until I repair the index at the JNOS console using 'index www', then >> the forward >> behaves again. So if you have a gazillion forwarding partners, they >> will likely ALL >> behave like they're stuck and just doing nothing until you repair the >> index of the >> area that they are all working on. >> >> I'm not sure why this is happening, but after putting in some big >> debug code it's >> very clear what's going on here. >> >> Just thought this might be helpful information. >> >> Maiko / VE4KLM >> From maiko at pcsinternet.ca Wed May 5 15:57:25 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Wed, 5 May 2021 14:57:25 -0500 Subject: [nos-bbs] heads up 'remote disc early' possibly corrupting area index ? In-Reply-To: <5cb7d31e-ffc0-8eab-99cf-9e79d917b35e@pcsinternet.ca> References: <560543c3-e17a-57fa-2222-e9f68e653649@pcsinternet.ca> <5cb7d31e-ffc0-8eab-99cf-9e79d917b35e@pcsinternet.ca> Message-ID: <71c6fb16-4139-e2bd-a469-c2de576058c2@pcsinternet.ca> Just on a roll ... some may construe this as rambling ... sorry (as they say in Canada) ... It would help if my 'mbox tdisc' was not set to 60 seconds, duh !!! Re: my early disconnect issues Yupppp .... M On 05/05/2021 10:07 a.m., M Langelaar wrote: > last one, sorry ... > > AND I have still not been able to get the 'offset' feature to work, > which is no > doubt not helpful as far as keeping indexes clean, since JNOS just > buggers > up the flow whenever the 'offset' shows up - I need to get that > working :( > > ??? about to validate FS line [FS ---!1500+] msg cnt 5 > > I've tried, but failed several times, hard to simulate this > > Anyways ... > > Maiko / VE4KLM > > On 05/05/2021 10:00 a.m., M Langelaar wrote: >> As silly as it may sound, I wonder if perhaps an option to limit max >> messages >> for any particular remote systems in forward.bbs (?) is an idea ? >> comments ? >> >> On 05/05/2021 9:57 a.m., M Langelaar wrote: >>> I'm seeing an instance of say 5 bulletins I forward but the remote >>> system is >>> disconnecting before the 5th is done, and it would appear the (in >>> this case) >>> area 'ww' index is corrupted, so any subsequent forwards to the same >>> partner >>> or others forwarding that same area, result in JNOS just >>> disconnecting after >>> the FS +_=+@ whatever ... >>> >>> Example log entry : >>> >>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >>> >>> Example log entry with major debugging : >>> >>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >>> 09:35:21? SUMCALL @ SUMCALL - about to validate FS line [FS +++++] >>> msg cnt 5 >>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [0] >>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [1] >>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [2] >>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [3] >>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [4] >>> 09:35:21? SUMCALL @ SUMCALL - FS is okay, now send '+' messages >>> 09:35:21? SUMCALL @ SUMCALL - sline [$31941_SUMCALL] index [0] >>> 09:35:21? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] >>> 09:35:21? SUMCALL @ SUMCALL - fbbsendmsg: truncated ww msg 103 would >>> result from err 2 >>> 09:35:21? SUMCALL @ SUMCALL - fbb send msg error, why ? >>> 09:35:21? SUMCALL @ SUMCALL - not connected, why ? >>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >>> >>> Until I repair the index at the JNOS console using 'index www', then >>> the forward >>> behaves again. So if you have a gazillion forwarding partners, they >>> will likely ALL >>> behave like they're stuck and just doing nothing until you repair >>> the index of the >>> area that they are all working on. >>> >>> I'm not sure why this is happening, but after putting in some big >>> debug code it's >>> very clear what's going on here. >>> >>> Just thought this might be helpful information. >>> >>> Maiko / VE4KLM >>> From maiko at pcsinternet.ca Wed May 5 16:03:29 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Wed, 5 May 2021 15:03:29 -0500 Subject: [nos-bbs] heads up 'remote disc early' possibly corrupting area index ? In-Reply-To: <71c6fb16-4139-e2bd-a469-c2de576058c2@pcsinternet.ca> References: <560543c3-e17a-57fa-2222-e9f68e653649@pcsinternet.ca> <5cb7d31e-ffc0-8eab-99cf-9e79d917b35e@pcsinternet.ca> <71c6fb16-4139-e2bd-a469-c2de576058c2@pcsinternet.ca> Message-ID: <26f54763-6a13-13af-2225-7b3bf466fa60@pcsinternet.ca> Interesting, that's not it actually .... good grief ... 14:59:03? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] 14:59:03? SUMCALL @ SUMCALL - MBOX (sumcall) lzhuf compress 1387/2703 = 48 percent 14:59:03? SUMCALL @ SUMCALL - FBBFWD: remote disconnected early. Maiko On 05/05/2021 2:57 p.m., M Langelaar wrote: > Just on a roll ... some may construe this as rambling ... sorry (as > they say in Canada) ... > > It would help if my 'mbox tdisc' was not set to 60 seconds, duh !!! > > Re: my early disconnect issues > > Yupppp .... > > M > > On 05/05/2021 10:07 a.m., M Langelaar wrote: >> last one, sorry ... >> >> AND I have still not been able to get the 'offset' feature to work, >> which is no >> doubt not helpful as far as keeping indexes clean, since JNOS just >> buggers >> up the flow whenever the 'offset' shows up - I need to get that >> working :( >> >> ??? about to validate FS line [FS ---!1500+] msg cnt 5 >> >> I've tried, but failed several times, hard to simulate this >> >> Anyways ... >> >> Maiko / VE4KLM >> >> On 05/05/2021 10:00 a.m., M Langelaar wrote: >>> As silly as it may sound, I wonder if perhaps an option to limit max >>> messages >>> for any particular remote systems in forward.bbs (?) is an idea ? >>> comments ? >>> >>> On 05/05/2021 9:57 a.m., M Langelaar wrote: >>>> I'm seeing an instance of say 5 bulletins I forward but the remote >>>> system is >>>> disconnecting before the 5th is done, and it would appear the (in >>>> this case) >>>> area 'ww' index is corrupted, so any subsequent forwards to the >>>> same partner >>>> or others forwarding that same area, result in JNOS just >>>> disconnecting after >>>> the FS +_=+@ whatever ... >>>> >>>> Example log entry : >>>> >>>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >>>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >>>> >>>> Example log entry with major debugging : >>>> >>>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) got response FS +++++ >>>> 09:35:21? SUMCALL @ SUMCALL - about to validate FS line [FS +++++] >>>> msg cnt 5 >>>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [0] >>>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [1] >>>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [2] >>>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [3] >>>> 09:35:21? SUMCALL @ SUMCALL - fsr [+] index [4] >>>> 09:35:21? SUMCALL @ SUMCALL - FS is okay, now send '+' messages >>>> 09:35:21? SUMCALL @ SUMCALL - sline [$31941_SUMCALL] index [0] >>>> 09:35:21? SUMCALL @ SUMCALL - mailbox file [./spool/mail/ww.txt] >>>> 09:35:21? SUMCALL @ SUMCALL - fbbsendmsg: truncated ww msg 103 >>>> would result from err 2 >>>> 09:35:21? SUMCALL @ SUMCALL - fbb send msg error, why ? >>>> 09:35:21? SUMCALL @ SUMCALL - not connected, why ? >>>> 09:35:21? SUMCALL @ SUMCALL - MBOX (sumcall) fwd exit >>>> >>>> Until I repair the index at the JNOS console using 'index www', >>>> then the forward >>>> behaves again. So if you have a gazillion forwarding partners, they >>>> will likely ALL >>>> behave like they're stuck and just doing nothing until you repair >>>> the index of the >>>> area that they are all working on. >>>> >>>> I'm not sure why this is happening, but after putting in some big >>>> debug code it's >>>> very clear what's going on here. >>>> >>>> Just thought this might be helpful information. >>>> >>>> Maiko / VE4KLM >>>> From maiko at pcsinternet.ca Fri May 14 10:16:43 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Fri, 14 May 2021 09:16:43 -0500 Subject: [nos-bbs] cases of B2F showing up in BPQ sid ... Message-ID: I have put in a small mod for people to `try` out if this applies to you. under rsync, just retrieve the one file, mboxmail_4GUS.c I was told BPQ is giving out B2F in recent versions when you connect to it, which to be honest JNOS has not been tested with. I only wrote the B2F support for Winlink CMS systems at the time. Forwarding with BPQ will get majorly messed up or something will simply go wrong if we say to BPQ that we support B2F. This `mod` will make sure JNOS only returns B2F for Winlink CMS systems and will downgrade the forwarding session to B1F for any other systems that are asking for B2F (for now anyways). In theory the mod should work. Maiko / VE4KLM From maiko at pcsinternet.ca Sat May 15 14:17:52 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Sat, 15 May 2021 13:17:52 -0500 Subject: [nos-bbs] cases of B2F showing up in BPQ sid ... In-Reply-To: References: Message-ID: Gus confirms this works, and my Winlink CMS forward still does too. Maiko On 14/05/2021 9:16 a.m., M Langelaar wrote: > I have put in a small mod for people to `try` out if this applies to you. > > under rsync, just retrieve the one file, mboxmail_4GUS.c > > I was told BPQ is giving out B2F in recent versions when you connect > to it, which to be honest JNOS has not been tested with. I only wrote > the B2F support for Winlink CMS systems at the time. > > Forwarding with BPQ will get majorly messed up or something will simply > go wrong if we say to BPQ that we support B2F. > > This `mod` will make sure JNOS only returns B2F for Winlink CMS systems > and will downgrade the forwarding session to B1F for any other systems > that > are asking for B2F (for now anyways). > > In theory the mod should work. > > Maiko / VE4KLM > > From stanzepa at gmail.com Sun May 16 19:47:18 2021 From: stanzepa at gmail.com (Stan Horzepa) Date: Sun, 16 May 2021 19:47:18 -0400 Subject: [nos-bbs] DCC Survey Results Message-ID: Dear DCC Survey Respondents: Thank you for taking the time to help us understand our potential DCC audience. Your responses were very helpful. We wanted to let you know the results of the survey. Roughly half of you were not planning on showing up at the DCC this year. Approximately 15% were definitely interested in coming and the remaining 35% were undecided. The overwhelming reason for not coming was concern over COVID and associated issues (traveling, ability to get on planes, ability for international travel, hotel limits). There is a very large interest in attending a Virtual DCC. Consequently, we've decided to have another Virtual DCC this year and work towards an in-person DCC next year. Thanks again for your help, 73 Bruce Raymond, ND8I nd8i at tapr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From maiko at pcsinternet.ca Sun May 23 12:21:35 2021 From: maiko at pcsinternet.ca (M Langelaar) Date: Sun, 23 May 2021 11:21:35 -0500 Subject: [nos-bbs] vara access mode status ... Message-ID: Well I think I am making some pretty good progress here, as a matter of fact I am able to pick off a message from a Winlink Express running in the VARA HF P2P mode. BUT there's just something not quite right yet, and I am stuck on the lzhuf (compression), but the traffic flow is remarkably good, anyways just thought I would mention that, hope to get it figured out 'soon'. It is quite a cool mode, and I hear it on 30 meters a fair amount, interesting in that you can hear the adaptive component to this mode on air during the back and forth between 2 stations. From slow tone sequences to pactor III+ type sounds and back again, over and over, it is truly very very cool :) Hope everyone is doing okay, the puttering around of this hobby has helped. ?* I would be lying if I said I was (for me it's been really mental) ... Maiko / VE4KLM