Re: Re: mis poll not polling
By: freq to deon on Sat Nov 01 2025 01:39 am
Howdy,
Increase the log level, it should provide more useful information.
I ran the log level on 1, 2 and 3. they all gave same output
So I didnt see the information that I expected with loglevel 3.
Here is an example of something that I played with about a month ago.
--------------------- POLL v1.12 A48 2023/01/15 Wed, Oct 01 2025 (loglevel 3) + 2025.10.01 22:37:16 Poll BINKP node via address lookup: 10:999/1
+ 2025.10.01 22:37:16 1-Polling 10:999/1 on slot 1 via BINKP
+ 2025.10.01 22:37:16 1-DEBUG ConnectMode=0
+ 2025.10.01 22:37:16 1-Connecting to 172.31.20.48 on port 24554
+ 2025.10.01 22:37:16 1-Using address 172.31.20.48
+ 2025.10.01 22:37:16 1-Connected by IPV4 to 172.31.20.48
+ 2025.10.01 22:37:16 1-S: NUL SYS New Mystic BBS
+ 2025.10.01 22:37:16 1-S: NUL ZYZ Sysop Name Here
+ 2025.10.01 22:37:16 1-S: NUL TIME Wed, 01 Oct 2025 22:37:16 0000
...
+ 2025.10.01 22:37:17 1-Mailer clrghouz/dev binkp/1.1
+ 2025.10.01 22:37:17 1-R: ADR 10:999/900.0@private 10:999/0.0@private
+ 2025.10.01 22:37:17 1-S: PWD
+ 2025.10.01 22:37:17 1-R: ERR You must support MD5 auth to talk to me
+ 2025.10.01 22:37:17 1-Authorization failed
+ 2025.10.01 22:37:18 Polled 1 systems
IE: Your log didnt show the "Using address...", nor the reason for the failed session.
If your loglevel 3 still shows the same output, then I would suggest your mystic is not resolving addresses (which is the next item in the log, that I see in my log, but not in yours).
...лоеп
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)