• Tickit

    From Zazz@1:103/705 to All on Friday, August 02, 2019 09:33:17
    I just setup tickit. Not to difficult but did run in to a problem. The first one was telling me no password but tic file had password. I checked with the feed and passwords given is what I have. Still same password issue, so I found in Global Options to set IgnorePassword=True. I manually ran tickit and it process the file.

    This morning I see a file in inbound folder and it was not processed so I manually ran it and it processed. I thought tickit was supposed to run automatically when there was a file in the inbound folder.

    So what am I missing?

    I am doing this to help out a downlink using Synchronet and wants me to feed him files. So I do need to get a better handle on this before he gets frustrated.

    [originally posted in wrong area]
    Ruben Figueroa
    aka Zazz
    PBSync Prison BBS
    [1:124/5014.4]

    ---
    Synchronet PBSync Prison BBS - wcalt.rdfig.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Zazz@1:103/705 to All on Tuesday, August 06, 2019 09:40:01
    Ok, I believe I have everything right. I am getting new files that are processed into the correct folders. However, they do not appear in the listing when I log into bbs. So, I run addfiles - -szn and then they show up.

    So what ever is happening is the tic files are seen and processed and file(s) are sent to the correct folder, but the listing and file descriptions are not updated.

    I thought addfiles was to automatically run or am I wrong?

    Ruben Figueroa
    aka Zazz
    PBSync Prison BBS
    [1:124/5014.4]

    ---
    Synchronet PBSync Prison BBS - wcalt.rdfig.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Zazz@1:103/705 to All on Monday, August 19, 2019 09:29:04
    Have things working but noticed every now and then a file is not processed because a CRC was expected and it didn't match. One specifically is the z1daily files and I checked it and it is good.

    So question is this, besides manually placing the file in sbbs, is there a way to bypass, add an exeception, etc so tickit will process it?

    Ruben Figueroa
    aka Zazz
    PBSync Prison BBS
    [1:124/5014.4]

    ---
    Synchronet PBSync Prison BBS - wcalt.rdfig.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From echicken@1:103/705 to Zazz on Monday, August 19, 2019 13:18:49
    Re: Tickit
    By: Zazz to All on Mon Aug 19 2019 09:29:04

    Have things working but noticed every now and then a file is not processed
    because a
    CRC was expected and it didn't match. One specifically is the z1daily
    files and I
    checked it and it is good.

    Do you have some output from TickIT (a log message) mentioning this CRC error that you can share? Can you post the file somewhere so we can check it out?

    How did you check the file to confirm that it's good? Extracted it and inspected visually?

    So question is this, besides manually placing the file in sbbs, is there a
    way to
    bypass, add an exeception, etc so tickit will process it?

    I wouldn't want to bypass functionality that's meant to keep corrupted files out of your system. Better that we figure out why it's happening in the first place. Either something needs to be fixed in TickIT or Synchronet, or on the other end (wherever you're getting these files from).

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    Synchronet electronic chicken bbs - bbs.electronicchicken.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From mark lewis@1:3634/12.73 to Zazz on Tuesday, August 20, 2019 09:23:40
    On 2019 Aug 19 09:29:04, you wrote to All:

    Have things working but noticed every now and then a file is not processed because a CRC was expected and it didn't match. One specifically is the z1daily files and I checked it and it is good.

    you should not be getting CRC mismatches on Z1DAILY files unless

    1. the wrong file has been sent,
    2. already exists in your inbound,
    3. or has been modified since it was hatched...
    (eg: bbs archive comment or ad added)

    So question is this, besides manually placing the file in sbbs, is
    there a way to bypass, add an exeception, etc so tickit will process
    it?

    there is no "skip CRC" option in tickit (at this time)... personally speaking, i wouldn't want one, either...

    on archives with numerical extensions like FTN nodelists (Zxx), there can be only 100 files anyway... 00 through 65/66 will be duplicated four times a year... 66/67 through 99 will be duplicated three times a year...

    eg:
    00 through 99 == Z00 through Z99
    100 through 199 == Z00 through Z99
    200 through 299 == Z00 through Z99
    300 through 365/366 == Z00 through Z65/Z66

    so, chekc your inbound and remove older archives that do not have matching TIC files within some minutes of the file's time stamp...

    NOTE: your mailer /may/ increment the extension number if an inbound file if a file of same name already exists in your inbound... this will certainly throw off TIC processing...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set
    them free. But that only permitted other men with machines to enslave them. ... A man of my spiritual intensity does not eat corpses. - G. B. Shaw
    ---
    * Origin: (1:3634/12.73)
  • From Zazz@1:103/705 to echicken on Tuesday, August 20, 2019 17:24:14
    Re: Tickit
    By: echicken to Zazz on Mon Aug 19 2019 13:18:49

    Do you have some output from TickIT (a log message) mentioning this CRC error that you can share? Can you post the file somewhere so we can check it out?

    How did you check the file to confirm that it's good? Extracted it and inspected visually?


    I inspected the file visually. I used an old app (Shez) and it did not see any
    corruption in the file. I could read the contents.

    I ran jsexec tickit and I saw screen output. It was the only file and the last thing said it expected a specific CRC but got something else instead (a different CRC)

    Ruben Figueroa
    aka Zazz
    PBSync Prison BBS
    [1:124/5014.4]

    ---
    Synchronet PBSync Prison BBS - wcalt.rdfig.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Zazz@1:103/705 to echicken on Tuesday, August 20, 2019 17:47:54
    Re: Tickit
    By: echicken to Zazz on Mon Aug 19 2019 13:18:49

    processed because a
    CRC was expected and it didn't match. One specifically is the z1daily files and I
    checked it and it is good.

    Do you have some output from TickIT (a log message) mentioning this CRC error that you can share? Can you post the file somewhere so we can check it out?


    Here is image of what I saw.

    https://imgur.com/zzRr0mD


    Ruben Figueroa
    aka Zazz
    PBSync Prison BBS
    [1:124/5014.4]

    ---
    Synchronet PBSync Prison BBS - wcalt.rdfig.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From echicken@1:103/705 to Zazz on Tuesday, August 20, 2019 22:08:01
    Re: Tickit
    By: Zazz to echicken on Tue Aug 20 2019 17:24:14

    I ran jsexec tickit and I saw screen output. It was the only file and the
    last thing said it
    expected a specific CRC but got something else instead (a different CRC)

    Sounds like you're not the only one who had this problem. Either TickIT left an old file behind (and didn't overwrite it when a new one with the same name came in) or your uplink send an old copy of the file, but a new version of the .tic (with a different checksum in it). Not sure which.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    Synchronet electronic chicken bbs - bbs.electronicchicken.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)