Totally confused as to what is going on here, but I'll try to explain.

I use a D'Bridge instance as a hub for all the networks that I have joined. That hub then feeds both my WWIV and Mystic BBS for the various networks.

For reasons I can't explain, I am unable to get the hub to send any messages to
my Mystic BBS node. It doesn't pack any messages - even when I do a %RESCAN. I
watch it go through the %RESCAN and the packet that gets sent has no messages in it. AREAFIX says I'm subscribed to all the areas, but none arrive or are packed on the D'Bridge side.

I have verified my Mystic node exists in the echo's export list. All looks normal from that standpoint, including AREAFIX. I just can't get it to send anything at all.

If it didn't work with my WWIV BBS (which is just another node), I would think something else was wrong. Just very odd that even a %RESCAN doesn't end up packing anything.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)

On 03 Dec 16 09:14:18, Mark Hofmann said the following to All:

For reasons I can't explain, I am unable to get the hub to send any message to my Mystic BBS node. It doesn't pack any messages - even when I do a %RESCAN. I watch it go through the %RESCAN and the packet that gets sent ha no messages in it. AREAFIX says I'm subscribed to all the areas, but none arrive or are packed on the D'Bridge side.

The RESCAN functionality is heavily dependant on the state of your message areas. On *.MSG areas, it will rescan to the downlink the messages in each subscribed area when it receives that request. Needless to say if the *.MSG files are purged, or the area is Passthru, no rescanning can take place.
The ability to rescan messages was never written to be elaborate beyond this level of functionality. Any Rescan requests must also follow the security criteria defined in Config-Packet/Mail.

More to the point.... If D'Bridge is not sending messages to one system, but sending to others, the problem is most likely the BinkD stage-directory is missing. The stage directories are named in Base36 Queue format and DBUTIL QNAME can be used to determine the directory name.

For example, your Queue is in C:\QUEUE and you cannot send messages to 1:229/426. Type DBUTIL QNAME 1:229/426 and it returns 00106D.0BU. BinkD staging directories always start with "D-" so the directory C:\QUEUE\D-00106D.0BU should be created if it does not exist.

The storage method if the Mystic system is a point, is "-POINT" plus whatever the point address is. D-POINT.006 means .6 off your primary address. Currently, it is not possible to have multiple point addresses defined; but there is a workaround you can do with DBUTIL MOVE that I can explain further.

Nick

--- Renegade vY2Ka2
* Origin: Ten-year-olds shouldn't have a favourite Genesis album (1:229/426)

More to the point.... If D'Bridge is not sending messages to one system, but sending to others, the problem is most likely the BinkD
stage-directory is missing. The stage directories are named in Base36
Queue format and DBUTIL QNAME can be used to determine the directory
name.
For example, your Queue is in C:\QUEUE and you cannot send messages to 1:229/426. Type DBUTIL QNAME 1:229/426 and it returns 00106D.0BU. BinkD staging directories always start with "D-" so the directory C:\QUEUE\D-00106D.0BU should be created if it does not exist.

Thanks for the detailed information on the queue information. I had forgotten the method on figuring out the queue name vs. node information. That was a big
help in investigating - and was hoping that was the issue, but the directory for the Mystic node is there.

I'll try and explain the history on this as it makes no sense.

From my Mystic BBS, I AREAFIXed the Dovenet areas from my D'Bridge hub like I do with everything else. I also did a %RESCAN. That worked fine, but it never
downloaded ALL of the messages from each area. Not a big deal, but it seems to
get to a certain date and stop.

Fast forward to now, I never never received a single message to any echos on Dovenet on the Mystic side. I don't see them in the D'Bridge queue or anything. They are going to my WWIV BBS (different node), but not my Mystic Node.

I'm starting to think it is *.MSG related in those areas for some reason - espcially since the original %RESCAN never really picked up everything from the
get-go.

My D'Bridge hub is still working fine sending messages to my WWIV BBS, though. Just strange! Will do some more digging.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)