Koozali.org: home of the SME Server

proftpd will not start

Offline crazybob

  • ****
  • 894
  • +0/-0
    • Stalzer R&D
proftpd will not start
« on: March 17, 2006, 08:05:31 AM »
Something happened to my server. Not sure what messed it up. I have everything back working except ftp. it does not restart, and if I try to restart it manually using "service start proftpd" I get an error message
Quote
Starting proftpd: server1.srdpc.com - fatal: Socket operation on non-socket
server1.srdpc.com - (Running from command line? Use ServerType standalone' in config file!)


I am lost. As soon as I get this streightened out I want to migrate to 7pre4

Any help would be appreciated

Bob
If you think you know whats going on, you obviously have no idea whats going on!

Offline byte

  • *
  • 2,183
  • +2/-0
proftpd will not start
« Reply #1 on: March 18, 2006, 09:08:05 PM »
Bob,

What does this command show?

db configuration show ftp

Also we don't use service anymore, you should correctly with SME use...

/etc/rc7.d/S**proftpd restart

** is the number of the proftpd which is run at
--[byte]--

Have you filled in a Bug Report over @ http://bugs.contribs.org ? Please don't wait to be told this way you help us to help you/others - Thanks!

Offline crazybob

  • ****
  • 894
  • +0/-0
    • Stalzer R&D
proftpd will not start
« Reply #2 on: April 03, 2006, 07:34:09 PM »
I did the upgrade to 7.0CR1. I find I am still having a problem. Here is the responce to what you asked

ftp=service
    LoginAccess=private
    TCPPort=21
    access=public
    status=enabled

I have installed remote user access to hold users to their ibays, but they can not access. I can as admin. Ibay permissions allow for ftp, I have allowed for ftp to be accessable from the web.

Thanks

Bob
If you think you know whats going on, you obviously have no idea whats going on!

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
proftpd will not start
« Reply #3 on: April 04, 2006, 04:31:53 PM »
Quote from: "crazybob"
I did the upgrade to 7.0CR1. I find I am still having a problem.


All such problems should be reported via the bug tracker.