Hello g00r00,

I have been test polling Paul's 21:1/101 using BBBS here 1:1/128 and as Paul has mentioned Mystic refuses an unsecured session even when Mystic is setup to permit such sessions. While in the process of testing I attempted to poll Paul's 21:1/101 system using my Mystic A36 11/9 at 21:1/128.1. FIDOPOLL didn't seem to even try to poll Paul's system.

Part of the problem with my Mystic not polling (21:1/101) may be related to Mystic's compiling of the Fsxnet nodelist. When I do a ./MUTIL merge.ini MUTIL responds by indicating that "Merged 2 of 2 nodelist(s)" (Fidonet,
FSXNODE) were processed.

In further checking Mystic here can't poll any Fsxnet nodes with the exception of 21:1/128 (BBBS). Which ALSO expresses it's Fidonet AKA of 1:282/1031. When Mystic here pollls 1:282/1031 Mystic also grabs any mail/files addressed to it's AKA of 21:1/128.1.

Currently when it arrives or is acquired the Fsxnet nodelist FSXNODE.ZIP is placed in the specified directory "/home/bbs/mystic/files/nodelists/fsxnode" just as the Fido nodelist is placed in the specified directory "/home/bbs/mystic/files/nodelists/fidonet"

The respective filenames at processing time are:

/home/bbs/mystic/files/nodelists/fidonet/nodelist.z15 /home/bbs/mystic/files/nodelists/fsxnode/fsxnode.zip

I tried renaming the fsxnode.zip to fsxnode.z21 and the processing result is the same. I also tried extracting the raw Fsxnet nodelist file and processing result was the same. I did update the merge.ini file to reflect the filename changes.

Below is a log entry of MUTIL's nodelist processing. It appears to have completed without errors.

+ Nov 14 02:27:08 Startup using merge.ino
+ Nov 14 02:27:08 Process: Merging Nodelists
+ Nov 14 02:27:08 Merging nodelist
+ Nov 14 02:27:08 Extracting nodelist.z15
+ Nov 14 02:27:08 Merging /home/bbs/mystic/temputil/nodelist.315
+ Nov 14 02:27:08 Merging fsxnode
+ Nov 14 02:27:08 Extracting fsxnode.z21
+ Nov 14 02:27:08 Results: Merged 2 of 2 nodelist(s) in 0.02s
+ Nov 14 02:27:08 Shutdown Normal (0)

Even though the nodelists are processed without error Mystic can't poll a Fsxnet node address. The exception being if the Fsxnet node address is already setup as an Echonode. But poll's all Fidonet addresses that were polled fine.

If I do a search as in ./fidopoll search 21:1/101 I get a response of:

Listed 0 result(s)

But if I do the same search for 1:282/1031 I get a response of:

Address BBS Name Location Sysop Net
---------- --------------- ---------- ----------- -------------
1:282/1031 The Ouija Board Anoka, MN Jeff Smith YES

I hope this info helps.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 11/14/17, Jeff Smith pondered and said...

Part of the problem with my Mystic not polling (21:1/101) may be related to Mystic's compiling of the Fsxnet nodelist. When I do a ./MUTIL merge.ini MUTIL responds by indicating that "Merged 2 of 2 nodelist(s)" (Fidonet, FSXNODE) were processed.

That does not mean it's actually worked, what you are looking for is
something like this in your logs

[snip]

+ Nov 15 20:42:04 Merging sportnet
+ Nov 15 20:42:04 Extracting SPORTNET.Z14
! Nov 15 20:42:04 unzip -oqqjC c:\bbs\files\sprt\spornode\SPORTNET.Z14 * -d c:\bbs\mystic\temputil\
+ Nov 15 20:42:04 Searching for "c:\bbs\files\sprt\spornode\sportnet.*"
+ Nov 15 20:42:04 Found "SPORTNET.TXT"
+ Nov 15 20:42:04 Found "SPORTNET.Z14"
+ Nov 15 20:42:04 Searching for "c:\bbs\mystic\temputil\sportnet.*"
+ Nov 15 20:42:04 Found "sportnet.314"
+ Nov 15 20:42:04 Compare sportnet.314 2017 / 1980
+ Nov 15 20:42:04 Result 1
+ Nov 15 20:42:04 Merging c:\bbs\mystic\temputil\sportnet.314
+ Nov 15 20:42:04 Merging fsxnet
+ Nov 15 20:42:04 Extracting FSXNET.Z21
! Nov 15 20:42:04 unzip -oqqjC c:\bbs\files\fsx\fsx_node\FSXNET.Z21 * -d c:\bbs\mystic\temputil\
+ Nov 15 20:42:04 Searching for "c:\bbs\files\fsx\fsx_node\fsxnet.*"
+ Nov 15 20:42:04 Found "FSXNET.Z21"
+ Nov 15 20:42:04 Searching for "c:\bbs\mystic\temputil\fsxnet.*"
+ Nov 15 20:42:04 Found "FSXNET.321"
+ Nov 15 20:42:04 Compare FSXNET.321 2017 / 1980
+ Nov 15 20:42:04 Result 1
+ Nov 15 20:42:04 Merging c:\bbs\mystic\temputil\FSXNET.321
+ Nov 15 20:42:04 Results: Merged 5 of 5 nodelist(s) in 7.11s

[snip]

In further checking Mystic here can't poll any Fsxnet nodes with the exception of 21:1/128 (BBBS). Which ALSO expresses it's Fidonet AKA of 1:282/1031. When Mystic here pollls 1:282/1031 Mystic also grabs any mail/files addressed to it's AKA of 21:1/128.1.

Makes sense :)

Currently when it arrives or is acquired the Fsxnet nodelist FSXNODE.ZIP is placed in the specified directory "/home/bbs/mystic/files/nodelists/fsxnode" just as the Fido nodelist is placed in the specified directory "/home/bbs/mystic/files/nodelists/fidonet"

OK

The respective filenames at processing time are:

/home/bbs/mystic/files/nodelists/fidonet/nodelist.z15 /home/bbs/mystic/files/nodelists/fsxnode/fsxnode.zip

I tried renaming the fsxnode.zip to fsxnode.z21 and the processing
result is the same. I also tried extracting the raw Fsxnet nodelist file and processing result was the same. I did update the merge.ini file to reflect the filename changes.

is your software case sensitive? If so try an uppercase entry in your [MergeNodeLists] stanza like this type of example

nodefile=/path/to/your/nodelist/dir/fsx_node/FSXNET

+ Nov 14 02:27:08 Startup using merge.ino
+ Nov 14 02:27:08 Process: Merging Nodelists
+ Nov 14 02:27:08 Merging nodelist
+ Nov 14 02:27:08 Extracting nodelist.z15
+ Nov 14 02:27:08 Merging /home/bbs/mystic/temputil/nodelist.315
+ Nov 14 02:27:08 Merging fsxnode
+ Nov 14 02:27:08 Extracting fsxnode.z21
+ Nov 14 02:27:08 Results: Merged 2 of 2 nodelist(s) in 0.02s
+ Nov 14 02:27:08 Shutdown Normal (0)

Level 2 or 3 logging?

I'm just not convinced it's finding the nodelist file to merge.

If you look in your data dir and check nodelist.txt do you see the fsxNet
nodes in there? If not, then it's not pulling them in, hence the fidopoll
will not work for you as you have detailed.

Hope that helps :)

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

On 11/15/17, Avon said the following...

is your software case sensitive? If so try an uppercase entry in your [MergeNodeLists] stanza like this type of example

I have tried filenames as the were received. I have also converted all filenames to lower case and get the same results. Linux does like lower case but will handle upper case or mixed case as long as the filenames match exactly.

Level 2 or 3 logging?

Level 2 logging currently.

I'm just not convinced it's finding the nodelist file to merge.
If you look in your data dir and check nodelist.txt do you see the fsxNet nodes in there? If not, then it's not pulling them in, hence the fidopoll will not work for you as you have detailed.

Converting all filenames to lower case and editing the merge.in to match I
get a MUTIL log entry of:

------------ MUTIL v1.12 A36 2017/11/09 Wed, Nov 15 2017 (loglevel 2)
+ Nov 15 09:16:04 Startup using merge.ini
+ Nov 15 09:16:04 Process: Merging Nodelists
+ Nov 15 09:16:04 Merging nodelist
+ Nov 15 09:16:04 Merging fsxnode
+ Nov 15 09:16:04 Results: Merged 2 of 2 nodelist(s) in 0.01s
+ Nov 15 09:16:04 Shutdown Normal (0)

What troubles me is that IF Mutil isn't finding or sucessfully processing the specified nodelists. Why is it indicating that it has done so?

I will conduct more tests using both the Windows and Linux versions of Mystic that I have installed here and keep you posted.


Jeff

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.1)

Part of the problem with my Mystic not polling (21:1/101) may be related to Mystic's compiling of the Fsxnet nodelist. When I do a ./MUTIL merge.ini MUTIL responds by indicating that "Merged 2 of 2 nodelist(s)" (Fidonet, FSXNODE) were processed.

Could it be that the accesses are messed up and Fidopoll cannot access the nodelist? The "compiled" nodelist is just a .txt file found in your DATA directory as "nodelist.txt" so you can see if it merged correctly or not and what its access/ownerships are.

--- Mystic BBS v1.12 A36 2017/11/14 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

Part of the problem with my Mystic not polling (21:1/101) may be related
to Mystic's compiling of the Fsxnet nodelist. When I do a ./MUTIL
merge.ini MUTIL responds by indicating that "Merged 2 of 2 nodelist(s)"
(Fidonet, FSXNODE) were processed.

Could it be that the accesses are messed up and Fidopoll cannot access the nodelist?

Everything including and below the /home/bbs directory is owned by the operating user "bbs" which includes read/write access. I checked the permissions of each directory in the involved path including the nodelist files
themselves. The path to the nodelist files currently is:

/home/bbs/mystic/files/nodelists/fidonet/nodelist.z14 /home/bbs/mystic/files/nodelists/fsxnet/fsxnode.zip

The current permissions for the fsxnode.zip file are:

-rw-rw-rw- 1 bbs bbs 7570 Nov 11 19:11 fsxnode.zip

The Fidonet nodelist file has the same read/write permissions as the Fsxnet nodelist file.

The Mutil log indicates that it processes both nodelists but upon inspection only the Fidonet data is placed in the nodelist.txt file. That would to my understanding explain why Fidopoll fails to poll Fsxnet nodes.

The "compiled" nodelist is just a .txt file found in your DATA
directory as "nodelist.txt" so you can see if it merged correctly or not and what its access/ownerships are.

The nodelist.txt file does have the required owner/access permissions.

When polling a Fido node AKA Fidopoll seems to access the nodelist.txt file in order to successfully poll a Fido node number. I would surmise that because of the missing Fsxnet nodelist data Fidopoll fails to poll Fsxnet node addresses.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 11/15/17, Jeff Smith pondered and said...

When polling a Fido node AKA Fidopoll seems to access the nodelist.txt file in order to successfully poll a Fido node number. I would surmise

So you do have a fidonet nodelist showing in your nodelist.txt file?

Check also you have a copy of unzip that is working ok and able to be called
by Mystic.. if it can't unzip things it will never extract and the import..

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

On 11/15/17, Jeff Smith pondered and said...

When polling a Fido node AKA Fidopoll seems to access the nodelist.txt
file in order to successfully poll a Fido node number. I would surmise

So you do have a fidonet nodelist showing in your nodelist.txt file?

Yes the Fidonet nodelist data shows up in the nodelist.txt file but no Fsxnet nodelist data.

Check also you have a copy of unzip that is working ok and able to be called by Mystic.. if it can't unzip things it will never extract and the import..

Yes Unzip 6.00 is available for use by Mutil. Mutil doesn't seem to have a problem unzipping the Fidonet nodelist. I am still looking into checking the situation out and will post any results or observations.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 11/15/17, Jeff Smith pondered and said...

Yes Unzip 6.00 is available for use by Mutil. Mutil doesn't seem to have
a problem unzipping the Fidonet nodelist. I am still looking into
checking the situation out and will post any results or observations.

I'd be interested to know if you have any issues manually decompressing the archive using your tools.

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

On 11/15/17, Jeff Smith pondered and said...

Yes Unzip 6.00 is available for use by Mutil. Mutil doesn't seem to have
a problem unzipping the Fidonet nodelist. I am still looking into
checking the situation out and will post any results or observations.

I'd be interested to know if you have any issues manually decompressing the archive using your tools.

First from the commandline I ran Unzip to test the Fsxnet nodelist archive fsxnode.zip. The response was:

testing: FILE_ID.DIZ OK
testing: FSXNET.321 OK

I then from the command line ran Unzip to uncompress the nodelist file from the archive. The response/result was:

Archive: /home/bbs/mystic/files/nodelists/fsxnet/fsxnode.zip inflating: /home/bbs/mystic/temputil/FILE_ID.DIZ inflating: /home/bbs/mystic/temputil/FSXNET.321

My conclusion is that when called Unzip is able to successfully extract the nodelist files from the archive. When the command ./mutil merge.ini is run from the Mystic PC the resulting MUTIL log entry is:

----------------- MUTIL v1.12 A36 2017/11/09 Wed, Nov 15 2017 (loglevel 2)
+ Nov 15 19:27:26 Startup using merge.ini
+ Nov 15 19:27:26 Process: Merging Nodelists
+ Nov 15 19:27:26 Merging nodelist
+ Nov 15 19:27:26 Extracting nodelist.z15
+ Nov 15 19:27:26 Merging /home/bbs/mystic/temputil/nodelist.315
+ Nov 15 19:27:26 Merging fsxnode
+ Nov 15 19:27:26 Extracting fsxnode.z21
+ Nov 15 19:27:26 Results: Merged 2 of 2 nodelist(s) in 0.02s
+ Nov 15 19:27:26 Shutdown Normal (0)

But again when checking the contents of the nodelist.txt file after the nodelist files have been processed. Only the Fidonet nodelist data is present.


Jeff



--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 11/15/17, Jeff Smith pondered and said...

2) + Nov 15 19:27:26 Startup using merge.ini
+ Nov 15 19:27:26 Process: Merging Nodelists
+ Nov 15 19:27:26 Merging nodelist

Can you send me by file attach email a copy of this ini please.

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

First from the commandline I ran Unzip to test the Fsxnet nodelist archive fsxnode.zip. The response was:
testing: FILE_ID.DIZ OK
testing: FSXNET.321 OK

I then from the command line ran Unzip to uncompress the nodelist file
from the archive. The response/result was:

Archive: /home/bbs/mystic/files/nodelists/fsxnet/fsxnode.zip
inflating: /home/bbs/mystic/temputil/FILE_ID.DIZ
inflating: /home/bbs/mystic/temputil/FSXNET.321

My conclusion is that when called Unzip is able to successfully extract
the nodelist files from the archive. When the command ./mutil merge.ini
is run from the Mystic PC the resulting MUTIL log entry is:

----------------- MUTIL v1.12 A36 2017/11/09 Wed, Nov 15 2017 (loglevel 2)
+ Nov 15 19:27:26 Startup using merge.ini
+ Nov 15 19:27:26 Process: Merging Nodelists
+ Nov 15 19:27:26 Merging nodelist
+ Nov 15 19:27:26 Extracting nodelist.z15
+ Nov 15 19:27:26 Merging /home/bbs/mystic/temputil/nodelist.315
+ Nov 15 19:27:26 Merging fsxnode
+ Nov 15 19:27:26 Extracting fsxnode.z21
+ Nov 15 19:27:26 Results: Merged 2 of 2 nodelist(s) in 0.02s
+ Nov 15 19:27:26 Shutdown Normal (0)

But again when checking the contents of the nodelist.txt file after the nodelist files have been processed. Only the Fidonet nodelist data is present.

A better late than never observation is that the Fsxnet nodelist archive being used fsxnode.zip contains two files FILE_ID.DIZ and FSXNET.321.

But in the MUTIL log entry it states:

+ Nov 15 19:27:26 Merging fsxnode
+ Nov 15 19:27:26 Extracting fsxnode.z21

I don't see the fsxnode.zip file being used containing a fsxnode.z21 file. As noted above the fsxnode file contains a FILE_ID.DIZ and a FSXNET.321 file. So, my question then is where is MUTIL seeing or expecting a fsxnode.z21 file?


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

Hello Avon,

On 11/16/17, Avon said the following...

Can you send me by file attach email a copy of this ini please.

On it's way to you.


Jeff

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.1)

On 11/15/17, Jeff Smith pondered and said...

A better late than never observation is that the Fsxnet nodelist archive being used fsxnode.zip contains two files FILE_ID.DIZ and FSXNET.321.

But in the MUTIL log entry it states:

+ Nov 15 19:27:26 Merging fsxnode
+ Nov 15 19:27:26 Extracting fsxnode.z21

I don't see the fsxnode.zip file being used containing a fsxnode.z21
file. As noted above the fsxnode file contains a FILE_ID.DIZ and a FSXNET.321 file. So, my question then is where is MUTIL seeing or expecting a fsxnode.z21 file?

The latter. So you are not using the usual nodelist file I send out but
rather are downloading the zip file I publish via bbs.geek.nz - interesting. Well I would suggest you use the file sent to FSX_NODE as your source of nodelist to import...

Yes it's something related to the file your are using and the way the stanza
is keyed to look for things... remember the nodelist is called fsxnet.xxx
where xxx is the calendar date of the year e.g. fsxnet.322

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Yes Unzip 6.00 is available for use by Mutil. Mutil doesn't seem to have
a problem unzipping the Fidonet nodelist. I am still looking into
checking the situation out and will post any results or observations.

Have you tried running MUTIL with debug logging?

--- Mystic BBS v1.12 A36 2017/11/15 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello Avon,

On 11/15/17, Jeff Smith pondered and said...

The latter. So you are not using the usual nodelist file I send out but rather are downloading the zip file I publish via bbs.geek.nz - interesting.

Initially for testing I grabbed the zip file from bbs.geek.nz. Later I did use the FSXNET.Znn file to test the nodelist processing.

Well I would suggest you use the file sent to FSX_NODE as your source of nodelist to import...
Yes it's something related to the file your are using and the way the stanza is keyed to look for things... remember the nodelist is called fsxnet.xxx where xxx is the calendar date of the year e.g. fsxnet.322

Actually the files sent to FSX_NODE are FSXNET.Znn and contain FSXNET.nnn. Linux sees and considers FSXNET.Znn a different file than fsxnet.znn. Does case
matter to Mutil or is case only relevant to what is specified in the nodefile stanza? I can and will test case as it relates to Linux or if needed convert case prior to processing. It may be as simple as setting the nodefile stanza to
expect upper case if Mutil doesn't care.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

Hello g00r00,

Yes Unzip 6.00 is available for use by Mutil. Mutil doesn't seem to have
a problem unzipping the Fidonet nodelist. I am still looking into
checking the situation out and will post any results or observations.

Have you tried running MUTIL with debug logging?

I have now. Silly of me not to have thought of that! <sigh>

One thing I did notice though is that throughout the testing that I have done Mutil has always exited indicating that 2 of 2 nodelists were processed with a "Shutdown Normal (0)". Even when only one nodelist was actually successfully processed. Is it possible that if Mutil doesn't see, find, fails to uncompress,
Etc. that Mutil will make some indication of that when exiting?

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

This is what I have in my nodelist merge .ini file, I might be way off on
what is causing your problem but hey I'll throw it out there.

nodefile=c:\mystic\files\fsx\fsx_node\fsxnet
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
Directory where original |
nodelist is stored. FSXNET.Z21 |
|
This is the actual nodelist file name, But
I leave the extension off and it works
every time.

Just change what you need to for Linux but in the past when I had problems
this was the fix.

See how you go.

Cheers
Lloyd

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: - Micro Link BBS - QLD, OZ (21:1/103)

Jeff,

The case has to be correct in the .ini file in order for mutil to find and import the nodelist. The fsxnet nodelist file (such as FSXNET.321) comes in upper case, so it needs to be upper case in the .ini as well. Try:

nodefile=/home/bbs/files/fsx/node/FSXNET

That works for me, if it's lower case, it does not import it.

Immortal

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 11/16/17, Immortal said the following...

The case has to be correct in the .ini file in order for mutil to find
and import the nodelist. The fsxnet nodelist file (such as FSXNET.321) comes in upper case, so it needs to be upper case in the .ini as well. Try:
nodefile=/home/bbs/files/fsx/node/FSXNET

The common cheat for linux is two lines : nodefile=/home/bbs/files/fsx/node/FSXNET nodefile=/home/bbs/files/fsx/node/fsxnet

So both upper and lower case will work, it will only read one as it's either upper or lower. Some oddball networks use mixed case, but that could be added as other lines and still work. There is a lower case flag in mutil to force things to lower case.

--- Mystic BBS v1.12 A36 2017/11/15 (Linux/64)
* Origin: Workpoint (21:1/145.3)