• file areas

    From bcw142@21:1/145 to All on Wednesday, January 04, 2017 08:48:00
    With that new impure release I noticed all my file areas were gone. Looked at paths and data and everything is there and normal moved an area to see if
    that worked, still nothing there. It shows files 0 new 0 last Upload 01 Jan 1980, just like a new filebase. I have no idea of when it went bad, I deleted the original upload and recreated it as index 17 (was 1 of course) and up it came (after mass upload). I hate to recreate them all, but it looks like the only way - anyone find another way to recover when all the areas seem to be there but not there?

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, January 04, 2017 10:11:00
    On 01/04/17, bcw142 said the following...

    With that new impure release I noticed all my file areas were gone.
    Looked at paths and data and everything is there and normal moved an
    area to see if that worked, still nothing there. It shows files 0 new 0 last Upload 01 Jan 1980, just like a new filebase. I have no idea of
    when it went bad, I deleted the original upload and recreated it as
    index 17 (was 1 of course) and up it came (after mass upload). I hate to recreate them all, but it looks like the only way - anyone find another way to recover when all the areas seem to be there but not there?

    This sounds like an issue I reported to g00r00. If the first file base data file doesn't exist, then the mass upload or even file base scan will abort.
    He supposedly fixed it, but it may not have been fixed in this latest alpha. Recreating the first file base data file was the only way to fix the problem.

    "No matter where you go, there you are!" - Buckaroo Bonzai

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)
  • From bcw142@21:1/145 to All on Wednesday, January 04, 2017 09:26:00
    Really weird problem. Just now I copied index 4 which was FSX_ARTS and pasted it back (now index 18). Deleted index 4 moved to area 18 and did the mass upload and it worked fine! Really weird - at least it's pretty easy to move them and fix them, but why? And why does a new copy work and the original not? Seems like the linking in the Mystic BBS itself is the cause even though it looks OK (I hacked the files using hexedit to view them and they look OK).

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From bcw142@21:1/145 to Gryphon on Wednesday, January 04, 2017 11:38:00
    On 01/04/17, Gryphon said the following...
    This sounds like an issue I reported to g00r00. If the first file base data file doesn't exist, then the mass upload or even file base scan
    will abort. He supposedly fixed it, but it may not have been fixed in
    this latest alpha. Recreating the first file base data file was the only way to fix the problem.

    Could be, I'll do some more looking at the ones that aren't working and what files exist for them in data and then add it back and see what files exist on the new one to see what's going on. I copy the original area, paste it back with a new index. Then I go back and delete the original and do a mass upload to the new one and I'm back up and normal.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, January 04, 2017 11:05:00
    On 01/04/17, bcw142 said the following...

    On 01/04/17, Gryphon said the following...
    This sounds like an issue I reported to g00r00. If the first file ba data file doesn't exist, then the mass upload or even file base scan will abort. He supposedly fixed it, but it may not have been fixed in this latest alpha. Recreating the first file base data file was the o way to fix the problem.

    Could be, I'll do some more looking at the ones that aren't working and what files exist for them in data and then add it back and see what
    files exist on the new one to see what's going on. I copy the original area, paste it back with a new index. Then I go back and delete the original and do a mass upload to the new one and I'm back up and normal.

    By deleting the original, you need to delete it from disk, not just when
    using the config page.

    "No matter where you go, there you are!" - Buckaroo Bonzai

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)
  • From bcw142@21:1/145 to Gryphon on Wednesday, January 04, 2017 15:17:00
    On 01/04/17, Gryphon said the following...
    On 01/04/17, bcw142 said the following...
    files exist on the new one to see what's going on. I copy the origina area, paste it back with a new index. Then I go back and delete the original and do a mass upload to the new one and I'm back up and norm

    By deleting the original, you need to delete it from disk, not just when using the config page.

    "No matter where you go, there you are!" - Buckaroo Bonzai

    I see some of what you mean, I just noticed the older fsx_art.* files are
    there (data) so will delete them. I think it may reuse the names that are there, I also noticed a 'reset' in the filebase edit menu, wouldn't that basically empty the files (put pointers back to the start)? I'm not sure I
    need to delete and recreate those files as fsx_arts started working fine and received the newer impure art files. Maybe 'reset' reset all the file areas? Still even if it did they wouldn't mass upload till I changed the index, it's weird.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From bcw142@21:1/145 to All on Thursday, January 05, 2017 07:13:00
    I found the real problem just now, root had taken ownership from pi on the files data files for unknown reasons! Had to sudo chown -R pi:pi /mystic
    again. Then everything came back to normal. Why just the files area is
    unknown. It's really weird, just the files area files were owned by root out
    of all the data files.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Gryphon@21:1/120 to bcw142 on Tuesday, January 10, 2017 08:59:00
    On 01/05/17, bcw142 said the following...

    I found the real problem just now, root had taken ownership from pi on
    the files data files for unknown reasons! Had to sudo chown -R pi:pi /mystic again. Then everything came back to normal. Why just the files area is unknown. It's really weird, just the files area files were owned by root out of all the data files.

    Do you have some sort of 3rd party file processor that is running as root?
    Are you mutil cron jobs running as root maybe?

    "No matter where you go, there you are!" - Buckaroo Bonzai

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)
  • From bcw142@21:1/145 to Gryphon on Tuesday, January 10, 2017 11:47:00
    On 01/10/17, Gryphon said the following...
    the files data files for unknown reasons! Had to sudo chown -R pi:pi /mystic again. Then everything came back to normal. Why just the file

    Do you have some sort of 3rd party file processor that is running as
    root? Are you mutil cron jobs running as root maybe?

    Nope no cron, no third party stuff. The files are on a large USB drive, but
    it is mounted by fstab so it's there with the same setup each time (unlike automount). It's really weird as I've said from the start. It was the files
    in /mystic/data not on the USB files drive itself, so just really weird.
    Mystic A31 should be the only thing touching them. Maybe pack file bases from mutil went wrong somehow.

    ...Today is the tomorrow you worried about yesterday.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Terra-X@21:1/123 to All on Saturday, May 05, 2018 00:17:58
    Does mystic have the capability to work with smb?
    ie: path for a file directory for an area would something like smb://foocomputer/share/shared files?


    T-X!

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: -=THE VOiD=- (21:1/123)
  • From Solaris@21:2/1202 to sysop on Tuesday, May 11, 2021 06:57:59
    So if the files are landing but not sorting make sure your passwords are correct , otherwise im guessing its a file are setting issue , make sure you sort your files area with a z group . Also make sure you guve mystic some
    place to put it for example .

    say your fsx file group is group 3 so for FSX_ART for example the grouping would be something like s10z3 . s(security level) 10 z ( file group ) 3 .
    VS message grouping which is s10g3 , G for message group z for file group .

    sample from Error 1202 BBS

    Base Name FSXnet uploaded ANSI Art
    FTP Name ANSI_Art_-_Groups,_Individuals_etc.
    Echo Tag FSX_ARTS
    Net Address 21:2/1202 (FSXnet)
    Export To 1 node(s)
    List ACS s10z3
    Upload ACS s10z3
    Download ACS s10z3
    Hatch ACS s255z3
    FTP ACS s10z3
    Sysop ACS s255z3
    List ACS
    Data File FSX_ARTS
    FIle Path C:\mystic1202\echonets\files\FSX_ARTS\

    Hope this helps

    Sysop SolaRis
    Error 1202 and Error 404 BBS !
    FSXnet HuB 2 Tholian AdmiN !

    --- Mystic BBS v1.12 A46 2020/08/25 (Windows/64)
    * Origin: Error 1202 BBS (21:2/1202)