Re: BBS Entry
By: Digital Man to Jeffrey Bodenstein on Fri Sep 25 2020 10:08 am

Do you have the SYNCDATA conference in your BBS configuration? Is there an SBL2SMB timed event configured and enabled on your systems (which runs "?sbbslist export")? The next step would
be
to double check that it's actually running and perhaps use 'smbutil r' command to read the syncdata sub-board and confirm that your BBS entry was in fact exported there.

digital man

I do have SYNCDATA and yes the times events are setup. I did a force to run them again and did not show up. I was able to find via the SYNCDATA the Orginal posting and two changes but nothing after that which does match up to why the data never changed.

As a test I deleted my BBS and forced an update which then in the logs I see the BBS complaining so I went back in and added my BBS back into the list with all the correct data. I now see the message in SYNCDATA ready to go out at the next call out for Dove-Net. So fingers crossed that all should be good going forward.

Thanks again for the reply and another page of notes on how this runs. That is awesome in my book.

JB

---
� Synchronet � Coffee House BBS - Lisle, IL (bbs.coffeehousebbs.me)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BBS Entry
By: Jeffrey Bodenstein to Digital Man on Fri Sep 25 2020 11:13 pm

Re: BBS Entry
By: Digital Man to Jeffrey Bodenstein on Fri Sep 25 2020 10:08 am

Do you have the SYNCDATA conference in your BBS configuration? Is there an SBL2SMB timed event configured and enabled on your systems (which runs "?sbbslist export")? The next step would be
to double check that it's actually running and perhaps use 'smbutil r' command to read the syncdata sub-board and confirm that your BBS entry was in fact exported there.

I do have SYNCDATA and yes the times events are setup. I did a force to run them again and did not show up. I was able to find via the SYNCDATA the Orginal posting and two changes but nothing after that which does match up to why the data never changed.

As a test I deleted my BBS and forced an update which then in the logs I see the BBS complaining so I went back in and added my BBS back into the list with all the correct data. I now see the message in SYNCDATA ready to go out at the next call out for Dove-Net. So fingers crossed that all should be good going forward.

Thanks again for the reply and another page of notes on how this runs. That is awesome in my book.

Yeah, I think you were being limited by the default export frequency. Adding the '-force' option to the sbbslist.js export command-line likely would have fixed that.

digital man

Rush quote #36:
Raging at unreachable glory, straining at invisible chains
Norco, CA WX: 64.6�F, 89.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BBS Entry
By: Digital Man to Jeffrey Bodenstein on Sat Sep 26 2020 12:45 am

Yeah, I think you were being limited by the default export frequency. Adding the '-force' option to the sbbslist.js export command-line likely would have fixed that.

digital man

gotcha - I will add that to my notes. Shouldn't really need that in the future but never know.

JB

---
� Synchronet � Coffee House BBS - Lisle, IL (bbs.coffeehousebbs.me)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)