Hello All,

So lately I've been seeing some odd logging when starting binkd or when it automatically restarts after a config change:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

These are repeated multiple times for each. Obviously I understand that I don't
have a zone 2, 3, or 4 address, but I do have links in those zones. And I understand this is not breaking anything. It's more of an annoyance than anything. Hundreds of these log entries every time upon config change or startup just seems like it could be avoided somehow.

Is there any way to specify that zones 1-4 all fall under the 'fidonet' domain so I don't get these errors in my logs?

Regards,
Nick

... "I don't suffer from insanity; I enjoy every minute of it."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hi Nicholas!

13 Oct 2016 09:14, from Nicholas Boel -> All:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

I think it is only to point out that you did not have a domain set for those zones, and that binkd will use fidonet as it is the default domain..

Should not be an issue at all.

CU, Ricsi

--- GoldED+/LNX
* Origin: All those who believe in psychokinesis raise my hand (2:310/31)

Hi,

On 2016-10-13 09:14:57, Nicholas Boel wrote to All:
about: "Logging issue":

So lately I've been seeing some odd logging when starting binkd or
when it automatically restarts after a config change:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

These are repeated multiple times for each. Obviously I understand that I don't have a zone 2, 3, or 4 address, but I do have links in those zones. And I understand this is not breaking anything. It's more of an annoyance than anything. Hundreds of these log entries every time upon config change or startup just seems like it could be avoided somehow.

Is there any way to specify that zones 1-4 all fall under the 'fidonet' domain so I don't get these errors in my logs?

Since you see hundreds, I think you are using a BINKD.TXT that has the nodes listed without the '@fidonet' part. So no 5D addresses. Which causes binkd to generate those warnings when it reads the file, and comes across nodes in different zones than your default.

Because you are a linux user it would be easy for you to generate your own, using the php script originally by Ulrich Schroeter, that I recently updated to
this effect.

You can download it here:

http://ambrosia60.dd-dns.de/53f8ee03/drv_q/div27/i-util/bnlphp13.zip


Bye, Wilfred.


--- FMail-W32 1.72.0.0
* Origin: Native IPv6 connectable node (2:280/464)

Hello Wilfred,

On 13 Oct 16 17:45, Wilfred van Velzen wrote to Nicholas Boel:

So lately I've been seeing some odd logging when starting binkd
or when it automatically restarts after a config change:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

These are repeated multiple times for each. Obviously I
understand that I don't have a zone 2, 3, or 4 address, but I do
have links in those zones. And I understand this is not breaking
anything. It's more of an annoyance than anything. Hundreds of
these log entries every time upon config change or startup just
seems like it could be avoided somehow.

Is there any way to specify that zones 1-4 all fall under the
'fidonet' domain so I don't get these errors in my logs?

Since you see hundreds, I think you are using a BINKD.TXT that has the nodes listed without the '@fidonet' part. So no 5D addresses. Which
causes binkd to generate those warnings when it reads the file, and
comes across nodes in different zones than your default.

Wow, you hit the nail on the head. The last BINKD.TXT that was released in the I-BINKD file echo doesn't contain any domains for any of the addresses listed in it.

Because you are a linux user it would be easy for you to generate your own, using the php script originally by Ulrich Schroeter, that I
recently updated to this effect.

You can download it here:

http://ambrosia60.dd-dns.de/53f8ee03/drv_q/div27/i-util/bnlphp13.zip

I've grabbed it and will definitely look into it. I've been having problems with the BINKD.TXT that has been hatched out in the filegate for quite some time now. If it was hatched at all.

Thanks for the help Wilfred. I didn't even think to look at BINKD.TXT, and that's exactly where the issue lies. I'll remove the file echo and start creating it myself for all the networks I carry here.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Wilfred,

On 13 Oct 16 17:45, Wilfred van Velzen wrote to Nicholas Boel:

You can download it here:

http://ambrosia60.dd-dns.de/53f8ee03/drv_q/div27/i-util/bnlphp13.zip

FYI, I had to manually change line 296 from "\\" to "/" to work on Linux, as it
kept trying to look for a directory ending in a backslash, but other than that it works great! Once binkd reloaded config and looked at the newly generated file, there were no more errors.

I've added it to my nodelist processing script and have unlinked from the file echo.

Thanks again!

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hi,

On 2016-10-13 11:50:31, Nicholas Boel wrote to Wilfred van Velzen:
about: "Re: Logging issue":

Since you see hundreds, I think you are using a BINKD.TXT that has
the nodes listed without the '@fidonet' part. So no 5D addresses.
Which causes binkd to generate those warnings when it reads the file,
and comes across nodes in different zones than your default.

Wow, you hit the nail on the head. The last BINKD.TXT that was released in the I-BINKD file echo doesn't contain any domains for any of the addresses listed in it.

I had the same issue, so it sounded familiar! ;)

Because you are a linux user it would be easy for you to generate
your
own, using the php script originally by Ulrich Schroeter, that I
recently updated to this effect.

You can download it here:

http://ambrosia60.dd-dns.de/53f8ee03/drv_q/div27/i-util/bnlphp13.zip

I've grabbed it and will definitely look into it. I've been having

problems

with the BINKD.TXT that has been hatched out in the filegate for quite

some

time now. If it was hatched at all.

I noticed RJ had some system problems...


Bye, Wilfred.


--- FMail-W32 1.72.0.0
* Origin: Native IPv6 connectable node (2:280/464)

Hi,

On 2016-10-13 12:37:51, Nicholas Boel wrote to Wilfred van Velzen:
about: "Re: Logging issue":

You can download it here:

http://ambrosia60.dd-dns.de/53f8ee03/drv_q/div27/i-util/bnlphp13.zip

FYI, I had to manually change line 296 from "\\" to "/" to work on Linux, as it kept trying to look for a directory ending in a backslash, but other than that it works great! Once binkd reloaded config and looked at the newly generated file, there were no more errors.

I'm using it on linux, but don't use the "search" function, so that code isn't used on my system. I directly call it from my tic processor when the the daily nodelist arrives, with the exact file name.

There must be some compatible way to add a directory seperator in php. I might have a look later...

I've added it to my nodelist processing script and have unlinked from
the file echo.

Thanks again!

Glad to help!

Bye, Wilfred.


--- FMail-W32 1.72.0.0
* Origin: Native IPv6 connectable node (2:280/464)

13 Oct 16 09:14, you wrote to All:

Hello All,

So lately I've been seeing some odd logging when starting binkd or when it automatically restarts after a config change:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

do all of your NODE lines for your links have the @domain part specified?? if not, they should...

node 1:154/10@fidonet binkp.pharcyde.org -


i note that the newly hatched binkp.txt does not have the domains listed like it used to do... i suspect that RJ hasn't completed his recovery of his setup yet...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Judgement of beauty can err, what with the wine & the dark.
---
* Origin: (1:3634/12.73)

Hello Wilfred,

On 13 Oct 16 20:13, Wilfred van Velzen wrote to Nicholas Boel:

FYI, I had to manually change line 296 from "\\" to "/" to work
on Linux, as it kept trying to look for a directory ending in a
backslash, but other than that it works great! Once binkd
reloaded config and looked at the newly generated file, there
were no more errors.

I'm using it on linux, but don't use the "search" function, so that
code isn't used on my system. I directly call it from my tic processor when the the daily nodelist arrives, with the exact file name.

I was thinking about going that route, but I already have a script that runs when a nodelist comes in to automatically compile it for Golded. So instead, I just added the commands to that script since it all happens in the same directory. That said, I just run "./binkp_nodelister.php" with no extra parameters, and manually move the binkd.txt to the directory binkd already looks in via the include option.

There must be some compatible way to add a directory seperator in php.
I might have a look later...

If you figure something out, let me know. I don't have an issue adding or changing lines in scripts whatsoever.

Regards,
Nick

... "If at first you don't succeed, destroy all evidence that you tried."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello mark,

On 13 Oct 16 13:07, mark lewis wrote to Nicholas Boel:

i note that the newly hatched binkp.txt does not have the domains
listed like it used to do... i suspect that RJ hasn't completed his recovery of his setup yet...

That's exactly what it was, and I never bothered checking until Wilfred mentioned it. Should be all fixed up now, as I shouldn't have to rely on others
when I can easily do it myself.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

13 Oct 16 20:13, you wrote to Nicholas Boel:

There must be some compatible way to add a directory seperator in php.
I might have a look later...

does it use #IFDEF type stuff? if so


#IFDEF OS=winwhatever
dir-separator='\\';
#ELSE
dir-separator='/';
#ENDIF

then in the code, all hardcoded slashes would be replaced with $dir-separator or some such...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... The pornography of meat.
---
* Origin: (1:3634/12.73)

Hi,

On 2016-10-13 15:10:52, Nicholas Boel wrote to Wilfred van Velzen:
about: "Re: Logging issue":

FYI, I had to manually change line 296 from "\\" to "/" to work
on Linux, as it kept trying to look for a directory ending in a
backslash, but other than that it works great! Once binkd
reloaded config and looked at the newly generated file, there
were no more errors.

There must be some compatible way to add a directory seperator in
php. I might have a look later...

If you figure something out, let me know. I don't have an issue adding or changing lines in scripts whatsoever.

What you have now is compatible with Windows. Php auto translates / to \ if used in a path name on Windows. Or you can use the predefined constant DIRECTORY_SEPARATOR, which should work on every OS.

Bye, Wilfred.


--- FMail-W32 1.72.0.0
* Origin: Native IPv6 connectable node (2:280/464)

Hi,

On 2016-10-13 16:24:22, mark lewis wrote to Wilfred van Velzen:
about: "Logging issue":

There must be some compatible way to add a directory seperator in
php.
I might have a look later...

does it use #IFDEF type stuff?

PHP is an interpreted language, not a compiled one. It doesn't have preprocessor like C. So the simple answer is no. ;)

if so

#IFDEF OS=winwhatever

With some code you can detect the OS, but there is no need in this case, see my
previous message...


Bye, Wilfred.


--- FMail-W32 1.72.0.0
* Origin: Native IPv6 connectable node (2:280/464)

Re: Logging issue
By: Nicholas Boel to All on Thu Oct 13 2016 09:14:57

So lately I've been seeing some odd logging when starting binkd or when it automatically restarts after a config change:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

I had the same problem. Also had problems PW wise with some nodes. I always use the binkd.txt file so that I can connect to nodes not in my config. I remembered that the author of that file had not renewed it for a while and a new version had just come out. I commented out the line in the config file, and my problems went away
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

13 Oct 16 23:22, you wrote to me:

With some code you can detect the OS, but there is no need in this
case, see my previous message...

yeah, i just had a li'l LOL about it since it is the same basic idea :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I am Canadian Because....I can pronounce SASKATCHEWAN.
---
* Origin: (1:3634/12.73)

Hello Wilfred,
On 13 Oct 16 17:45, Wilfred van Velzen wrote to Nicholas Boel:

So lately I've been seeing some odd logging when starting binkd
or when it automatically restarts after a config change:
Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

Do/did you have those zones defined in the config? (Thought the default config already had those...)

These are repeated multiple times for each. Obviously I
understand that I don't have a zone 2, 3, or 4 address, but I do
have links in those zones. And I understand this is not breaking
anything. It's more of an annoyance than anything. Hundreds of
these log entries every time upon config change or startup just
seems like it could be avoided somehow.
Is there any way to specify that zones 1-4 all fall under the
'fidonet' domain so I don't get these errors in my logs?

Define them in the same way that zone 1 (in your case) is defined.

Since you see hundreds, I think you are using a BINKD.TXT that has the
nodes listed without the '@fidonet' part. So no 5D addresses. Which
causes binkd to generate those warnings when it reads the file, and
comes across nodes in different zones than your default.

As far as I know I'm using the same version of the Binkp node extractor that I was before, but I'll be going over every thing after I get all of my stuff out of storage.




Jame







--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

mark,

i note that the newly hatched binkp.txt does not have the domains listed like it used to do... i suspect that RJ hasn't completed his recovery of his setup yet...

Apparently not...<g> I'll be looking again after I get my stuff (including my servers & me dev PC; my laptop I've had with me) back out of storage next week, to see if I have a 'newer' version on my server. (Just got a new apartment after just recently getting a new job...)







Jame

--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Hello Rj,

On 15 Oct 16 12:26, Rj Clay wrote to Nicholas Boel:

Cannot find domain for zone 2, assuming 'fidonet'
Cannot find domain for zone 3, assuming 'fidonet'
Cannot find domain for zone 4, assuming 'fidonet'

Do/did you have those zones defined in the config? (Thought the
default config already had those...)

Why would you define addresses you don't have? I don't have a zone 2, 3, or 4 address. No need for defining.

These are repeated multiple times for each. Obviously I
understand that I don't have a zone 2, 3, or 4 address, but I do
have links in those zones. And I understand this is not breaking
anything. It's more of an annoyance than anything. Hundreds of
these log entries every time upon config change or startup just
seems like it could be avoided somehow.
Is there any way to specify that zones 1-4 all fall under the
'fidonet' domain so I don't get these errors in my logs?

Define them in the same way that zone 1 (in your case) is defined.

The reason it was happening is because BINKP.TXT did not have domains listed in
it. I have created my own binkp.txt and all is fine now.

Regards,
Nick

... "Take my advice, I don't use it anyway
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Re: Re: Logging issue
By: Rj Clay to Nicholas Boel on Sat Oct 15 2016 12:26:20

Define them in the same way that zone 1 (in your case) is defined.

Since you see hundreds, I think you are using a BINKD.TXT that has
the nodes listed without the '@fidonet' part. So no 5D addresses.
Which causes binkd to generate those warnings when it reads the file,
and comes across nodes in different zones than your default.

As far as I know I'm using the same version of the Binkp node extractor that I was before, but I'll be going over every thing after I get all of my stuff out of storage.

I had the same problem RJ. When I took binkd.txt out of the equation, my problems went away.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Hello Rj!

15 Oct 16 12:26, Rj Clay wrote to Nicholas Boel:

As far as I know I'm using the same version of the Binkp node extractor that I was before, but I'll be going over every thing after
I get all of my stuff out of storage.

I found this in my backups....

# BinkD-compatible nodelist extraction - Fri Mar 11 06:11:01 2016
#
# Created by binkd_nodelister.pl version 1.3 - 14 April 2007
# Copyright (c) 2002, 2003, 2007 by Jerry Schwartz and Write by Night
#


And this one was hatched yesterday

# BinkD-compatible nodelist extraction - Sat Oct 15 12:47:48 2016
#
# Created by binkd_nodelister.pl version 1.0 - 26 November 2002
# Copyright (c) 2002 by Jerry Schwartz and Write by Night


It looks like you need to locate v1.3 or higher.

--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)