I have an issue since switching to BinkIT. I was able to binkd without issues.
Massacre wrote to All <=-
I have an issue since switching to BinkIT. I was able to binkd
without issues.
When a netmail message is created, it creates a .cut file in the
outbound folder and sits... When echomail is created, it
creates a packet with the ??# extention like it should but just
sits there.
I then disable the BinkIT service then fire up a poll with binkd.
IT then sends out the files without an issue.
Is it a semaphore issue? Configuration issue?
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Dmxrob to Massacre on Thu Mar 14 2019 11:18 am
Which timed events? The FIDOUT/FIDOIN ones? Like the lesr, etc. flags?
Massacre wrote to Dan Clough <=-
Re: BinkIT/SBBSEcho issues -
By: Dan Clough to Massacre on Thu Mar 14 2019 02:26 pm
They are and have been enabled. I wonder if there is a switch or
some kind of path, etc. that needs to change??
Massacre wrote to Dan Clough <=-
Re: BinkIT/SBBSEcho issues -
By: Dan Clough to Massacre on Thu Mar 14 2019 02:26 pm
They are and have been enabled. I wonder if there is a switch or
some kind of path, etc. that needs to change??
It would help if you would quote what you're replying to...
I forgot to mention in my first reply, you also need the FIDOOUT
and FIDOIN events enabled...
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Are you reading the log output when binkit runs?
digital man
Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992.
Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
Re: BinkIT/SBBSEcho issues - .cut files not sendingNotice how this address -------------------------------^^^^^^^^^^^^^^^^^
By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Are you reading the log output when binkit runs?
digital man
Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992.
Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:
3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
3/14 08:00:29p Running native timed event: FIDOOUT
3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
3/14 08:00:32p Timed event: FIDOOUT returned 0
3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
3/14 08:00:34p Running timed event: BINKOUT
Then BINKOUT is executed for outbound then callout:
3/14 08:00:34p BINKOUT Executing external: ?binkit
3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
3/14 08:00:34p BINKOUT Running outbound
3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
3/14 08:00:34p BINKOUT Lock successful.
3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.orgIs different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Are you reading the log output when binkit runs?
digital man
Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992.
Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:
3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
3/14 08:00:29p Running native timed event: FIDOOUT
3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
3/14 08:00:32p Timed event: FIDOOUT returned 0
3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
3/14 08:00:34p Running timed event: BINKOUT
Then BINKOUT is executed for outbound then callout:
3/14 08:00:34p BINKOUT Executing external: ?binkitNotice how this address -------------------------------^^^^^^^^^^^^^^^^^
3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
3/14 08:00:34p BINKOUT Running outbound
3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
3/14 08:00:34p BINKOUT Lock successful.
3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.orgIs different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^
FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.
digital man
This Is Spinal Tap quote #8:
Derek Smalls: Making a big thing out of it would have been a good idea. Norco, CA WX: 67.3øF, 24.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Digital Man to Massacre on Fri Mar 15 2019 12:56 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Are you reading the log output when binkit runs?
digital man
Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992. Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:
3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
3/14 08:00:29p Running native timed event: FIDOOUT
3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
3/14 08:00:32p Timed event: FIDOOUT returned 0
3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
3/14 08:00:34p Running timed event: BINKOUT
Then BINKOUT is executed for outbound then callout:
3/14 08:00:34p BINKOUT Executing external: ?binkitNotice how this address -------------------------------^^^^^^^^^^^^^^^^^
3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
3/14 08:00:34p BINKOUT Running outbound
3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
3/14 08:00:34p BINKOUT Lock successful.
3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.orgIs different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^
FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.
Thank you for your response. Is there a work around for this?
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Digital Man on Fri Mar 15 2019 10:41 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Digital Man to Massacre on Fri Mar 15 2019 12:56 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm
Re: BinkIT/SBBSEcho issues - .cut files not sending
By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm
I looked at the document again and went through the settings and the events were configured correctly.
I originally used binkd and that works fine. Something feels like a config issue.
Are you reading the log output when binkit runs?
digital man
Synchronet "Real Fact" #81:
Vertrauen has had the FidoNet node number 1:103/705 since 1992. Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:
3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
3/14 08:00:29p Running native timed event: FIDOOUT
3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
3/14 08:00:32p Timed event: FIDOOUT returned 0
3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
3/14 08:00:34p Running timed event: BINKOUT
Then BINKOUT is executed for outbound then callout:
3/14 08:00:34p BINKOUT Executing external: ?binkitNotice how this address -------------------------------^^^^^^^^^^^^^^^^^
3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
3/14 08:00:34p BINKOUT Running outbound
3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
3/14 08:00:34p BINKOUT Lock successful.
3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.orgIs different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^
FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.
Thank you for your response. Is there a work around for this?
If you remove the "@fidonet" from your configuration (just 4D addressing) - that might do it.
digital man
This Is Spinal Tap quote #43:
I feel my role in the band is ... kind of like lukewarm water.
Norco, CA WX: 63.3øF, 21.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs
On 03-15-19 20:07, Digital Man wrote to Massacre <=-
3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonetNotice how this address -------------------------------^^^^^^^^^^^^^^^^^
3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.orgIs different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^
FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.
Thank you for your response. Is there a work around for this?
If you remove the "@fidonet" from your configuration (just 4D
addressing) - that might do it.
FidoNet domains are supposed to be limited to 8 characters, so
"fidonet" is a valid FTN domain while "fidonet.org" is not. And it
doesn't match the system you're trying to connect to. The problem is on
the uplink's side.
Thank you for your response. Is there a work around for this?
On 2019 Mar 15 22:41:36, you wrote to Digital Man:Very true.
FidoNet domains are supposed to be limited to 8 characters, so
"fidonet" is a valid FTN domain while "fidonet.org" is not. And it
doesn't match the system you're trying to connect to. The problem is on
the uplink's side.
Thank you for your response. Is there a work around for this?
no, not really... that link needs to FixTheirShite<tm> instead of everyone else
having to work around their flawed configuration ;)
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Baked potatoes - Better with steak than barbecue.
If you remove the "@fidonet" from your configuration (just 4D addressing) - that might do it.
Is there a way to add the 'alias-for' in the binkit system?
You also mentioned removing the @fidonet domain from my configuration. I removed the domain from the config and it didn't work. Is there a specific way I need to do it?
Sysop: | Ruben Figueroa |
---|---|
Location: | Mesquite, Tx |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 254:48:11 |
Calls: | 79 |
Files: | 53 |
Messages: | 75,377 |