• ftp & nntp woes

    From Netsurge@21:4/154 to All on Mon May 20 00:36:27 2019
    I have many of the following entries in my mis logs:

    FTP 1-S: 502 Command not implemented

    and

    NNTP 1-S: 500 Unknown command

    Before I start to reinvent the wheel, has anyone come across this before?

    frank!netsurge!demonic
    disksh0p!bbs ! bbs.diskshop.ca ! mystic goodness

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: !disksh0p!bbs! bbs.diskshop.ca ! mystic goodness ! (21:4/154)
  • From Avon@21:1/101 to Netsurge on Tue May 21 16:22:45 2019
    On 19 May 2019 at 08:36p, Netsurge pondered and said...
    I have many of the following entries in my mis logs:
    FTP 1-S: 502 Command not implemented
    NNTP 1-S: 500 Unknown command
    Before I start to reinvent the wheel, has anyone come across this before?

    Yes, in most cases it's commands sent by the client that the server does not understand. And in most cases I don't think they are game changes i.e. impact the basic functionality of things. You could if you felt keen try and get
    logs from both serer and client and post them here for g00r00 to look at when he's next active. If you do, be sure to state the client, OS etc. for completeness.

    Is there a problem getting either working for you? If so perhaps I can help :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Netsurge@21:4/154 to Avon on Tue May 21 00:58:01 2019
    Yes, in most cases it's commands sent by the client that the server does not understand. And in most cases I don't think they are game changes
    i.e. impact the basic functionality of things. You could if you felt
    keen try and get logs from both serer and client and post them here for g00r00 to look at when he's next active. If you do, be sure to state the client, OS etc. for completeness.

    It has nothing to do with any clients connecting. I have shut down ports 21
    and 119 from my firewall and verified that no clients are connected and I get both these errors exactly every second, my mis logs end up being 10-12 megs a day.

    When I do connect with a client, say an ftp client for example, I get a directory list but every time i try to cd into that dir I get "directory
    change failed. remote chdir failed"

    I get a similar error with an nntp client, if I try to subscribe to a
    newgroup, I get an error about not being able to connect to it.

    frank!netsurge!demonic
    disksh0p!bbs ! bbs.diskshop.ca ! mystic goodness

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: !disksh0p!bbs! bbs.diskshop.ca ! mystic goodness ! (21:4/154)
  • From Avon@21:1/101 to Netsurge on Tue May 21 17:26:56 2019
    On 20 May 2019 at 08:58p, Netsurge pondered and said...
    It has nothing to do with any clients connecting. I have shut down ports 21 and 119 from my firewall and verified that no clients are connected
    and I get both these errors exactly every second, my mis logs end up
    being 10-12 megs a day.

    When I do connect with a client, say an ftp client for example, I get a directory list but every time i try to cd into that dir I get "directory change failed. remote chdir failed"

    I get a similar error with an nntp client, if I try to subscribe to a newgroup, I get an error about not being able to connect to it.

    hmm, could it then be either something not set up correctly in your message base for news or a file permissions thing being you're on linux?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Netsurge@21:4/154 to Avon on Tue May 21 01:36:07 2019
    hmm, could it then be either something not set up correctly in your message base for news or a file permissions thing being you're on linux?

    Permissions seem fine, I have even tested the issue but making sure
    everything was 777. It's a mind boggling problem. I guess I have to wait till g00r00 pops his head back up.

    frank!netsurge!demonic
    disksh0p!bbs ! bbs.diskshop.ca ! mystic goodness

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: !disksh0p!bbs! bbs.diskshop.ca ! mystic goodness ! (21:4/154)
  • From Netsurge@21:4/154 to Avon on Tue May 21 04:16:28 2019
    hmm, could it then be either something not set up correctly in your message base for news or a file permissions thing being you're on linux?

    I figured it out. It seems that Mystic doesn't like you to use a "." in
    either the ftp name or the nntp name.

    I was naming each file area as "filegroup.filebase.name", I switched them all over to "filegroup_filebase_name" and behold: everything is working,
    including no more 10 meg log files.

    frank!netsurge!demonic
    disksh0p!bbs ! bbs.diskshop.ca ! mystic goodness

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: !disksh0p!bbs! bbs.diskshop.ca ! mystic goodness ! (21:4/154)
  • From Avon@21:1/101 to Netsurge on Tue May 21 23:36:07 2019
    On 21 May 2019 at 12:16a, Netsurge pondered and said...

    I figured it out. It seems that Mystic doesn't like you to use a "." in either the ftp name or the nntp name.

    I was naming each file area as "filegroup.filebase.name", I switched
    them all over to "filegroup_filebase_name" and behold: everything is working, including no more 10 meg log files.

    Good catch, I use - in my naming at that seems to work fine also :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)