Hello everybody!

Using a fresh install of Mystic A39 4/21/18 I noticed that when I try to process
a Fidonet nodelist. That the Mutil log says that it processed a nodelist. There is no nodelist.txt created in the data directory.

The first Mutil log entry is with a compressed nodelist in the /home/files/fido/nodelists
directory.

----------------- MUTIL v1.12 A39 2018/04/21 Sat, Jun 23 2018 (loglevel 3)
+ Jun 23 02:17:58 Startup using merge.ini
- Jun 23 02:17:58 EXEC MergeNodeLists
+ Jun 23 02:17:58 Process: Merging Nodelists
+ Jun 23 02:17:58 Merging
+ Jun 23 02:17:58 Searching "/home/files/fido/nodelists/* for archive ""
+ Jun 23 02:17:58 Searching "/home/files/fido/nodelists/* for nodelist ""
+ Jun 23 02:17:58 Searching "/home/bbs/mystic/temputil/* for nodelist ""
+ Jun 23 02:17:58 Results: Merged 1 of 1 nodelist(s) in 0.00s
+ Jun 23 02:17:58 Shutdown Normal (0)

The second Mutil log is with the nodelist file removed. Mutil still indicates that a nodelist was processed.

----------------- MUTIL v1.12 A39 2018/04/21 Sat, Jun 23 2018 (loglevel 3)
+ Jun 23 02:24:09 Startup using merge.ini
- Jun 23 02:24:09 EXEC MergeNodeLists
+ Jun 23 02:24:09 Process: Merging Nodelists
+ Jun 23 02:24:09 Merging
+ Jun 23 02:24:09 Searching "/home/files/fido/nodelists/* for archive ""
+ Jun 23 02:24:09 Searching "/home/files/fido/nodelists/* for nodelist ""
+ Jun 23 02:24:09 Searching "/home/bbs/mystic/temputil/* for nodelist ""
+ Jun 23 02:24:09 Results: Merged 1 of 1 nodelist(s) in 0.00s
+ Jun 23 02:24:09 Shutdown Normal (0)

I even tried placing a uncompressed nodelist in the specified directory and Mutil still says that it processed a nodelist but no nodelist.txt is created.

I also see that Mutil doesn't actually specify what nodelist file name was processed. I also noticed that I currently can only poll Fidonet nodes that
are listed/configured in Mystic as echomail nodes as Fidopoll doesn't know
what FQDN to use for a specified Fidonet address..


Jeff

--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (21:1/128)

On 06/23/18, Jeff Smith pondered and said...

Using a fresh install of Mystic A39 4/21/18 I noticed that when I try to process
a Fidonet nodelist. That the Mutil log says that it processed a
nodelist. There is no nodelist.txt created in the data directory.

OK so that tells me it's not finding the nodelist.

Can you post your [MergeNodeLists] stanza Jeff?

Do you have unzip installed on your Linux/Pi system (I'm assuming it's Linux
as you are using this/style/of/pathing :)

I think we will be able to solve this fairly quickly for you.

was processed. I also noticed that I currently can only poll Fidonet
nodes that are listed/configured in Mystic as echomail nodes as Fidopoll doesn't know what FQDN to use for a specified Fidonet address..

Yep correct without a compiled nodelist fidopoll does not have info to look
up.

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hello Avon!

23 Jun 18 20:59, you wrote to me:

On 06/23/18, Jeff Smith pondered and said...

Using a fresh install of Mystic A39 4/21/18 I noticed that when I
try to process a Fidonet nodelist. That the Mutil log says that
it processed a nodelist. There is no nodelist.txt created in the
data directory.

OK so that tells me it's not finding the nodelist.

That was my thought also.

Can you post your [MergeNodeLists] stanza Jeff?

[MergeNodeLists]

; Finds the latest nodelists and merges them together in the mystic data
; folder.
;
; Set nodefile value one per line. The value should contain the full path
; and the base filename of the nodelist.
;
; examples:
; nodefile=c:\nodelist\nodelist
; nodefile=c:\nodelist\agoranet
;

[...]

; If no nodelists are found, Mystic will not overwrite the current
; nodelist. Comments are stripped while merging to lower filesize and
; increase search performance.

; Strip nodes marked as DOWN?
strip_down = true

; Strip nodes marked as PRIVATE?
strip_private = true

nodefile=/home/files/fido/nodelists/nodelist
; nodefile=d:\nodelists\agoranet


I made a change to the location of the nodelist files and changed the path to reflect the change. I moved the files from /home/files/fido/nodelists to /home/bbs/files/fido/nodelists. And changed the stanza to read:

nodefile=/home/bbs/files/fido/nodelists/nodelist

Now Mutil specifies that an actual nodelist is being processed. Seems that Mystic
didn't see the files if they were not in or below the user directory. In this case /home/bbs.

Do you have unzip installed on your Linux/Pi system (I'm assuming it's Linux as you are using this/style/of/pathing :)

Yes I do.

I think we will be able to solve this fairly quickly for you.

I think I can consider it fixed. It might have also been a quirk in Linux. Even though I did give user "bbs" ownership and permissions to the /home/files directory.



Jeff


--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (21:1/128)

On 06/24/18, Jeff Smith said the following...

nodefile=/home/files/fido/nodelists/nodelist
; nodefile=d:\nodelists\agoranet

In each ftn you are setup with you'll create it's own nodefile= entry
including the filename of the nodefile. For example:

nodefile=/home/files/fido/nodelists/fsxnet <-- this last fsxnet would
signify to mystic that it should look for a nodelist file called fsxnet.*

Hope that helps.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Digital Wurmhole | digitalwurmhole.ddns.net:2323 (21:4/113)

Hello CyntaxX!

nodefile=/home/files/fido/nodelists/nodelist
; nodefile=d:\nodelists\agoranet

In each ftn you are setup with you'll create it's own nodefile= entry including the filename of the nodefile. For example:

nodefile=/home/files/fido/nodelists/fsxnet <-- this last fsxnet would signify to mystic that it should look for a nodelist file called
fsxnet.*

This Mystic install will be strictly Fidonet. So only a single nodelist specification is necessary. The fix in my case was to move the filebase directory from /home/files/ to /home/bbs/files. The stanza therefore had
to be changed from nodefile=/home/files/fido/nodelists/nodelist to nodefile=/home/bbs/files/fido/nodelists/nodelist. Seems Mystic/Linux had
a problem with the /files/ directory being below the Linux user directory
of /bbs/. The Mystic root directory is /home/bbs/mystic.


Jeff


--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (21:1/128)

On 06/24/18, Jeff Smith said the following...

This Mystic install will be strictly Fidonet. So only a single nodelist specification is necessary. The fix in my case was to move the filebase

Ahh okay. Glad you got it sorted.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Digital Wurmhole | digitalwurmhole.ddns.net:2323 (21:4/113)

On 06/24/18, Jeff Smith pondered and said...

; Strip nodes marked as PRIVATE?
strip_private = true

I leave this as false for me but do strip the down nodes. At least that way I have an option of sending netmail routed via a HUB to nodes that are PVT

nodefile=/home/files/fido/nodelists/nodelist

I made a change to the location of the nodelist files and changed the path to reflect the change. I moved the files from /home/files/fido/nodelists to /home/bbs/files/fido/nodelists. And
changed the stanza to read:

nodefile=/home/bbs/files/fido/nodelists/nodelist

OK

Now Mutil specifies that an actual nodelist is being processed. Seems
that Mystic
didn't see the files if they were not in or below the user directory. In this case /home/bbs.

[snip]

I think I can consider it fixed. It might have also been a quirk in

Good stuff, well done Jeff.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)