• A35 Mystic MIS 2

    From Necromaster@21:1/122 to All on Tuesday, September 12, 2017 09:03:23
    Well I switched to Mystic MIS2 A35, and when semaphores are created (echomail.in, echomail.out) and such, they just hang there. I am running the Windows 64 bit version. Anyone else having these issues? Thanks.

    --- Mystic BBS v1.12 A35 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)
  • From Pequito@21:1/126 to Necromaster on Tuesday, September 12, 2017 18:31:09
    On 09/12/17, Necromaster said the following...

    Well I switched to Mystic MIS2 A35, and when semaphores are created (echomail.in, echomail.out) and such, they just hang there. I am
    running the Windows 64 bit version. Anyone else having these issues? Thanks.

    My guess is events where never added to MIS2 yet so they do not check for the semaphores yet. I could be wrong but I found the same issue and re-loaded
    MIS due to their being no events triggered with just MIS2 A35.

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A35 (Linux/32)
    * Origin: Twinkle BBS # (21:1/126)
  • From quickshot@21:2/134 to Necromaster on Tuesday, September 12, 2017 17:58:14
    Well I switched to Mystic MIS2 A35, and when semaphores are created (echomail.in, echomail.out) and such, they just hang there. I am
    running the Windows 64 bit version. Anyone else having these issues? Thanks.

    As far as i know, the event system does not exist in MIS2 yet.

    Scott Miller
    ---Quickshot
    ----Troybbs.com

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Troy's Den * troybbs.com (21:2/134)
  • From Necromaster@21:1/122 to Pequito on Wednesday, September 13, 2017 09:51:11
    On 09/12/17, Pequito said the following...

    On 09/12/17, Necromaster said the following...

    Well I switched to Mystic MIS2 A35, and when semaphores are created (echomail.in, echomail.out) and such, they just hang there. I am running the Windows 64 bit version. Anyone else having these issues? Thanks.

    My guess is events where never added to MIS2 yet so they do not check
    for the semaphores yet. I could be wrong but I found the same issue and re-loaded MIS due to their being no events triggered with just MIS2 A35.

    Cheers!
    Pequito

    I switched back to MIS and everything is working again. Thanks

    --- Mystic BBS v1.12 A35 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)
  • From Skuz@21:1/105 to Necromaster on Wednesday, September 13, 2017 17:28:26
    13 Sep 17 09:51, you wrote to Pequito:

    On 09/12/17, Pequito said the following...

    I switched back to MIS and everything is working again. Thanks

    Would you happen to know of hand if you have any iREX system that poll your MIS

    server. If your not sure, you can check your binkp.log for Find Text VER Internet Rex. I'd be interested in knowing that multiple file transfer are working between the two systems. I'm asking this because I have 3 iREX systems linked to mine that will fail doing any multiple file tranfers, so I like to know if the issue is happening on other mystic systems. I've already seen that MIS2 does have issues with all iREX mailers over here anyway.

    --- GoldED+/W32-MSVC 1.1.5-b20160201
    * Origin: flupH * fluph.darktech.org (21:1/105)
  • From Necromaster@21:1/122 to Skuz on Thursday, September 14, 2017 09:15:50
    Would you happen to know of hand if you have any iREX system that poll your MIS
    server. If your not sure, you can check your binkp.log for Find Text VER

    So far most of the systems that are in my network at Mystic based. But I
    will check and find out.

    --- Mystic BBS v1.12 A35 (Windows/64)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)
  • From bcw142@21:1/145.3 to Skuz on Thursday, September 14, 2017 14:22:19
    On 09/13/17, Skuz said the following...
    Would you happen to know of hand if you have any iREX system that poll your MIS

    You might have missed it, but Avon mentioned the same problem - iRex will get the first packet correctly and then fail each time. Then on next connect it gets the next packet and fails - at least I think that was what he had said.

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Skuz@21:1/105 to bcw142 on Thursday, September 14, 2017 18:05:30
    14 Sep 17 14:22, you wrote to me:

    On 09/13/17, Skuz said the following...
    Would you happen to know of hand if you have any iREX system that
    poll your MIS

    You might have missed it, but Avon mentioned the same problem - iRex
    will get the first packet correctly and then fail each time. Then on
    next connect it gets the next packet and fails - at least I think that
    was what he had said.

    I did miss it, the only thing I've seen him saying was in this echo on the 12th

    Sept where is post his log with iRex connected with his MIS successfully. No transfers where shown in the log he posted then. So he said that he see no issues. Anywhy, I'm glad to know that I'm not the only one who has been seeing this happening. I'm positive that I've even posted in the fidonet mystic echo multiple times ... back even before fsxnet ever started it's own network about this issue/problem.

    What you stated (above) is exacty what I see happening here. If Mystic has a Query of multiple files+TIC, bundles or packets totaling 20 files (no multiple networks)... It will take 20 new connections to get them all.

    This is also probably the main reason I dumpped iRex well over a year or so ago

    and stated running a pure native Mystic system. If memory serves me, I've ran Mystic with fastecho, Allfix and iRex from 2/2011 to early in 2016. At that time I felt mystic had become so stable that I'd be better off removing everything else. I know of several other boards.. that have done the same.
    --- GoldED+/W32-MSVC 1.1.5-b20160201
    * Origin: flupH * fluph.darktech.org (21:1/105)
  • From Avon@21:1/101 to Skuz on Friday, September 15, 2017 11:53:38
    On 09/14/17, Skuz pondered and said...

    You might have missed it, but Avon mentioned the same problem - iRex will get the first packet correctly and then fail each time. Then on next connect it gets the next packet and fails - at least I think tha was what he had said.

    I'm going to have to find what you refer to as I can't recall it. But there were some issues I was having with a IPv6 system recently using MIS2 that appeared to be like what you mention above.

    I did miss it, the only thing I've seen him saying was in this echo on
    the 12th
    Sept where is post his log with iRex connected with his MIS
    successfully. No transfers where shown in the log he posted then. So he said that he see no issues. Anywhy, I'm glad to know that I'm not the

    That's correct. No issues here with Irex that I could see based on logs I checked.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Vk3jed@21:1/109 to Necromaster on Sunday, September 17, 2017 12:29:00
    Necromaster wrote to Skuz <=-

    @TZ: 40f0
    Would you happen to know of hand if you have any iREX system that poll your MIS
    server. If your not sure, you can check your binkp.log for Find Text VER

    So far most of the systems that are in my network at Mystic based. But
    I will check and find out.

    So far, after an upgrade to A35, I'm having to poll out to be sade. :)


    ... Moderator Rule #1: Warnings are for wimps, cut links!
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Skuz on Sunday, September 17, 2017 12:35:00
    Skuz wrote to bcw142 <=-

    and stated running a pure native Mystic system. If memory serves me,
    I've ran Mystic with fastecho, Allfix and iRex from 2/2011 to early in 2016. At that time I felt mystic had become so stable that I'd be
    better off removing everything else. I know of several other boards..
    that have done the same.

    Mystic's mailer works well, and for non Mystic systems, I like binkd (which I use on my Synchroner board). Sure, it's BSO (might be an issue if you're used to a FD style mailer), but it's solid, and also has full IPv6 support (for people like me who have IPv6 available). Mystic's only halfway to IPv6 - incoming works if you use MIS2, but outbound is IPv4 only, because fidopoll hasn't been updated to support IPv6 yet.
    ... Hypochondria is the only disease I haven't got.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)