VSFTPD service wont start or detect

English Network/Internet
#1

Hi,
In one of my machines vsftp will not start, can anyone help?
the vsftpd is installed.
using: opensuse 13.1 64 bits

this is what i get:

falsename:/usr/sbin # vsftpd status
500 OOPS: missing value in config file for: import re, os, sys

falsename:/usr/sbin # rcvsftpd start
rcvsftpd: no such service vsftpd

#2

On 2014-01-22 13:16, velhodechapeu wrote:
>
> Hi,
> In one of my machines vsftp will not start, can anyone help?
> the vsftpd is installed.
> using: opensuse 13.1 64 bits
>
> this is what i get:
>
> falsename:/usr/sbin # vsftpd status
> 500 OOPS: missing value in config file for: import re, os, sys

vsftp can be configured as a daemon or via xinit. Which one have you
configured?

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

#3

Hi robin,

I use it manually, with your question I decided to try it set to start at boot and it worked. I will fall back to manual start to see how it goes and will post the result.

#4

Back!
vsftpd works normally when loaded at boot. rcvsftpd start, stop, reload, all normal.

But, it does not work when set to start manually.

looks like you are right the problem seem to be in the inicialization method.

what you suggest?

#5

I do not think that is handled with what you suggest. It is all systemd nowadays.

#6

Hi hcvv,

Following your suggestion I found this article.

using systemctl worked perfectly.

thank you hcvv and robin for your help.

#7

On 2014-01-22 16:46, velhodechapeu wrote:
>
> Hi hcvv,
>
>
> Following your suggestion I found this ‘article.’
> (http://tinyurl.com/alj8e74)
>
> using systemctl worked perfectly.
>
> thank you hcvv and robin for your help.

There are two ways to start vsftpd. As a service, all the time present,
via systemd. Or, when an outside internet request comes to use the ftp
server, it is started automatically by the xinit daemon, which makes a
lot of sense for occasional use.

The configuration settings are just a bit different, and trying to use
the wrong one produces error messages similar to those you got.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)