Hello All!

I have noticed on my hub that one of my BBS's can not be polled, I havent made any changes at all to that setup here is whats showing in binkd.log

1:105/85
07:29 [33121] BEGIN, binkd/1.1a-115/Linux -p -P1:105/85 /etc/ftn/binkd.cfg
07:29 [33121] creating a poll for 1:105/85@fidonet (`d' flavour)
07:29 [33121] clientmgr started
$ -d 1:105/85@fidonet
+ 07:29 [33122] call to 1:105/85@fidonet
+ 07:29 [33122] getaddrinfo failed: No address associated with hostname (-5)
07:29 [33121] rc(33122)=0
07:29 [33121] the queue is empty, quitting...

I have verified all address's in binkd.cfg and the nodelist etc. I tried changing from fqdn to local ip in binkd.cfg it does not change the error. Any ideas?

Regards,

Rick

... BBSing is a Maalox Moment.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Rick wrote (2023-02-24):

Hello All!

I have noticed on my hub that one of my BBS's can not be polled, I havent made any changes at all to that setup here is whats showing in binkd.log

1:105/85
07:29 [33121] BEGIN, binkd/1.1a-115/Linux -p -P1:105/85 /etc/ftn/binkd.cfg 07:29 [33121] creating a poll for 1:105/85@fidonet
(`d' flavour) 07:29 [33121] clientmgr started
$ -d 1:105/85@fidonet
+ 07:29 [33122] call to 1:105/85@fidonet
+ 07:29 [33122] getaddrinfo failed: No address associated with hostname (-5) 07:29 [33121] rc(33122)=0
07:29 [33121] the queue is empty, quitting...

I have verified all address's in binkd.cfg and the nodelist etc. I tried changing from fqdn to local ip in binkd.cfg it does not change the error.
Any ideas?

Is it still a problem? I can poll 1:105/85. Maybe a (temporary) DNS problem?

---
* Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (2:280/464.47)

Hello Rick,

On Friday February 24 2023 07:30, you wrote to All:

I have noticed on my hub that one of my BBS's can not be polled, I
havent made any changes at all to that setup here is whats showing in binkd.log

No problem from here:

+ 10:44 [2956] call to 1:105/85@fidonet
10:44 [2956] trying os2.abon.us [65.102.14.166]:24557...
10:44 [2956] connected
+ 10:44 [2956] outgoing session with os2.abon.us:24557 [65.102.14.166]
- 10:44 [2956] OPT CRAM-MD5-318079fde9ec0cb84ab5f652d632d3ee
+ 10:44 [2956] Remote requests MD mode
- 10:44 [2956] SYS OS/2 Test System
- 10:44 [2956] ZYZ Rick Smith
- 10:44 [2956] LOC Portland, OR
- 10:44 [2956] NDL 115200,TCP,BINKP
- 10:44 [2956] TIME Sat, 25 Feb 2023 01:42:25 -0800
- 10:44 [2956] VER binkd/1.1a-115/OS2 binkp/1.1
+ 10:44 [2956] addr: 1:105/85@fidonet
- 10:44 [2956] OPT EXTCMD GZ BZ2
+ 10:44 [2956] Remote supports EXTCMD mode
+ 10:44 [2956] Remote supports GZ mode
+ 10:44 [2956] Remote supports BZ2 mode
+ 10:44 [2956] done (to 1:105/85@fidonet, OK, S/R: 0/0 (0/0 bytes))
10:44 [2956] session closed, quitting...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello Oli!

Saturday February 25 2023 09:51, you wrote to me:

* Forwarded from area 'BINKD'
Rick wrote (2023-02-24):

Hello All!

I have noticed on my hub that one of my BBS's can not be polled,
I havent made any changes at all to that setup here is whats
showing in binkd.log

1:105/85
07:29 [33121] BEGIN, binkd/1.1a-115/Linux -p -P1:105/85
/etc/ftn/binkd.cfg 07:29 [33121] creating a poll for
1:105/85@fidonet (`d' flavour) 07:29 [33121] clientmgr started $
-d 1:105/85@fidonet + 07:29 [33122] call to 1:105/85@fidonet +
07:29 [33122] getaddrinfo failed: No address associated with
hostname (-5) 07:29 [33121] rc(33122)=0
07:29 [33121] the queue is empty, quitting...

I have verified all address's in binkd.cfg and the nodelist etc.
I tried changing from fqdn to local ip in binkd.cfg it does not
change the error.
Any ideas?

Is it still a problem? I can poll 1:105/85. Maybe a (temporary) DNS problem?

oddly it just resolved. So I would say it was some sort of a DNS problem


Regards,

Rick

... To go where no man has gone before... BBSing!
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hello Michiel!

Saturday February 25 2023 10:44, you wrote to me:

* Forwarded from area 'BINKD'
Hello Rick,

On Friday February 24 2023 07:30, you wrote to All:

I have noticed on my hub that one of my BBS's can not be polled,
I havent made any changes at all to that setup here is whats
showing in binkd.log

No problem from here:

+ 10:44 [2956] call to 1:105/85@fidonet
10:44 [2956] trying os2.abon.us [65.102.14.166]:24557...
10:44 [2956] connected
+ 10:44 [2956] outgoing session with os2.abon.us:24557 [65.102.14.166]
- 10:44 [2956] OPT CRAM-MD5-318079fde9ec0cb84ab5f652d632d3ee
+ 10:44 [2956] Remote requests MD mode
- 10:44 [2956] SYS OS/2 Test System
- 10:44 [2956] ZYZ Rick Smith
- 10:44 [2956] LOC Portland, OR
- 10:44 [2956] NDL 115200,TCP,BINKP
- 10:44 [2956] TIME Sat, 25 Feb 2023 01:42:25 -0800
- 10:44 [2956] VER binkd/1.1a-115/OS2 binkp/1.1
+ 10:44 [2956] addr: 1:105/85@fidonet
- 10:44 [2956] OPT EXTCMD GZ BZ2
+ 10:44 [2956] Remote supports EXTCMD mode
+ 10:44 [2956] Remote supports GZ mode
+ 10:44 [2956] Remote supports BZ2 mode
+ 10:44 [2956] done (to 1:105/85@fidonet, OK, S/R: 0/0 (0/0 bytes))
10:44 [2956] session closed, quitting...

Thank you, yes it resolved on its own... haunted I guess


Regards,

Rick

... Sleep... The thing "some" SysOps go without, cuz BBSing is too fun;-)
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)