Re: Re: mis poll not polling
By: freq to deon on Sun Nov 02 2025 07:24 am

The host that the hub runs on doesnt respond to pings - so dont think of that as the issue.

As stated in last reply, I can ping the hub from my phone.

Unlikely, as the hub doesnt respond to pings.

But in your previous reply you stated that you could telnet to the hub's binkp port - so that validates you have network connectivity and your host is resolving addresses OK.

So I suggest you give a higher log level than 2, because the hub has many mystic nodes feeding from it, so there is something a miss here...

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.

"mis poll forced" from a command line will do it.

|11ogg
|11SysOp, Altair IV BBS
|11altairiv.ddns.net:2323

... They say there's always one weirdo on the bus, but I couldn't find them!

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (21:2/147)

So I suggest you give a higher log level than 2, because the hub has many mystic nodes feeding from it, so there is something a miss here...

Make Mystic do a poll regardless of whether it has mail or not. Not sure how you do that, I'm sure somebody here will chime in on how to do that.

Been polling with mis poll forced, then tried mis poll send, also mis poll 21:3/100 and mis poll n3.z21.bbs.dege.au manually and have mis poll send setup hourly in events.

Here is a snippet from level 3 logs

--------------------- POLL v1.12 A48 2023/01/15 Sun, Nov 02 2025 (loglevel 3) + 2025.11.02 16:21:04 Poll BINKP node via address lookup: 21:3/100
+ 2025.11.02 16:21:04 Queued 2 files (4,089 bytes) for 21:3/100
+ 2025.11.02 16:21:04 1-Polling 21:3/100 on slot 1 via BINKP
+ 2025.11.02 16:21:04 1-DEBUG ConnectMode=0
+ 2025.11.02 16:21:04 1-Connecting to n3.z21.bbs.dege.au on port 24554
+ 2025.1101:12 Polled 1 systems

Shift-Ins in draw mode pastes - just figured that out.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: mis poll not polling
By: freq to All on Fri Oct 31 2025 12:46 pm

Howdy,

POLL v1.12 A48 2023/01/15 Fri, Oct 31 2025 (loglevel 2)
Polled 1 systems

Increase the log level, it should provide more useful information.


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

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

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

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)

You know what, freq??? F***ing go tear it up!! Hit MGM - have fun @
Or are you a show kinda gent??

My brother manages MGM, so i get comp tickets to the shows. Already have ticket for the Awakening at the Wynn. Expecting to get 2 more shows in. Will be fun!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)