• Strange Tickit errors

    From Dumas Walker@VERT/CAPCITY2 to ALL on Saturday, December 28, 2019 18:48:00
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990711.TIC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
    - Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709
    Fri Oct 25 08:05:09 2019 UTC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/micronet.zip' length mismatch. File is 8210, expected 8614.
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990717.TIC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
    - Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709
    Fri Oct 25 08:05:09 2019 UTC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/mininfo.zip' length mismatch. File is 19194, expected 19598.

    The file length mismatch is causing the files not to be tossed, and causing
    my downlinks not to receive updated nodelists, etc. This seems to happen
    with pretty much any file from any source except my fido connection with
    Janis at 1:261/38.

    I am guessing that is a part of the TIC standard or something, but is there
    a way to turn it off? These both seem to be off by 404 bytes. Not sure
    what would cause that (different OSes, the transfer protocol used by binkp/binkit, etc.), but it is not at all a difference that I am worried
    about so I would really prefer that tickit would ignore this error and go
    on about its business.

    I was able to comment out a few lines in tickit.js (after copying to /mods)
    and now it ignores the file length mismatch. I would guess maybe that is
    not good, for some reason, in all cases?


    * SLMR 2.1a * A part of the 57% that -didn't- vote for Clinton. Thrice.

    ---
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Digital Man@VERT to Dumas Walker on Saturday, December 28, 2019 17:03:13
    Re: Strange Tickit errors
    By: Dumas Walker to ALL on Sat Dec 28 2019 06:48 pm

    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990711.TIC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
    - Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709 Fri Oct 25 08:05:09 2019 UTC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/micronet.zip' length mismatch. File is 8210, expected 8614.
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990717.TIC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
    - Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709
    Fri Oct 25 08:05:09 2019 UTC
    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/mininfo.zip' length mismatch. File is 19194, expected 19598.

    The file length mismatch is causing the files not to be tossed, and causing my downlinks not to receive updated nodelists, etc. This seems to happen with pretty much any file from any source except my fido connection with Janis at 1:261/38.

    I am guessing that is a part of the TIC standard or something, but is there a way to turn it off? These both seem to be off by 404 bytes. Not sure what would cause that (different OSes, the transfer protocol used by binkp/binkit, etc.), but it is not at all a difference that I am worried about so I would really prefer that tickit would ignore this error and go
    on about its business.

    I was able to comment out a few lines in tickit.js (after copying to /mods) and now it ignores the file length mismatch. I would guess maybe that is not good, for some reason, in all cases?

    Are the received files okay (e.g. the CRCs match, they pass zip verification)?

    It would be pretty odd for the CRCs to match, but the lengths not to. I can't think of an explanation for that one. If the files were modified (e.g. zip comments replaced or stripped) after the .tic file was generated, then I would expect the file CRC to be different as well (and not match the value in the .tic file).

    digital man

    Synchronet/BBS Terminology Definition #65:
    SMTP = Simple Message Transfer Protocol
    Norco, CA WX: 54.4F, 70.0% humidity, 1 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Dumas Walker on Sunday, December 29, 2019 14:07:13
    Re: Strange Tickit errors
    By: Dumas Walker to ALL on Sat Dec 28 2019 18:48:00


    Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/mininfo.zip' length mismatch. File is 19194, expected 19598.

    i've seen this a few times, too... i'm suspecting that their systems are adding archive comments or some system advertising file after the TIC has been generated...

    the main reason for this check and the skipping of the file is for interrupted downloads where the rest of the file will come in later...

    if the file size is failing, the checksum should also be failing... i think the checksum check comes after the size check, though... better to bail earlier than later if the file is not fully downloaded...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Sunday, December 29, 2019 13:36:00
    Are the received files okay (e.g. the CRCs match, they pass zip verification)?

    Actually the CRCs did not match, either, so I disabled that also.

    It would be pretty odd for the CRCs to match, but the lengths not to. I can't t
    ink of an explanation for that one. If the files were modified (e.g. zip commen
    s replaced or stripped) after the .tic file was generated, then I would expect >he file CRC to be different as well (and not match the value in the .tic file).

    I am not 100% sure, but I think that tickit is not deleting the *.TIC files after it processes them, and binkit is not overwritting them when it
    receives a new one by the same name. Reason I think that is because one of
    my downlinks pointed out that the TIC file mentions the wrong version of
    the file in question, in addition to the file length and CRC being wrong.

    The other possibility is that my hub is resending old TIC
    files with the new attachments each time. I am not so sure about that possibility, though, as there are a lot of old TIC files in /fido/inbound
    and many, many file does not exist errors thrown by tickit in the syslog. If
    I look for the files on my system, they've already been processed to their destination directories. Also, this is happening with multiple hubs
    and not just the one, and they use different software.


    * SLMR 2.1a * Press any key to continue. No, not THAT one!

    ---
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Rampage@VERT/SESTAR to Dumas Walker on Sunday, December 29, 2019 20:25:53
    Re: Strange Tickit errors
    By: Dumas Walker to DIGITAL MAN on Sun Dec 29 2019 13:36:00


    I am not 100% sure, but I think that tickit is not deleting the *.TIC files after it processes them

    tickit won't delete them unless it processes them successfully...

    you really need to find out why those files are not the same size as the TIC says they should be... something on the sending end is not right...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Dumas Walker@VERT/CAPCITY2 to RAMPAGE on Monday, December 30, 2019 18:42:00
    you really need to find out why those files are not the same size as the TIC sa
    s they should be... something on the sending end is not right...

    Since it is happening at multiple sending ends, with different softwares, I
    am suspicious that something is not right on this end with binkit or tickit.

    That said, I am starting with one of the hubs. Once we get it figured out
    I will move to the next one until it is hopefully squared away.


    * SLMR 2.1a * Overdrawn? No way! I still have checks left!

    ---
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP