Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#30634 - [vsftpd] systemd starts vsftpd failed. Force listening ipv6?

Attached to Project: Community Packages
Opened by Gao Xiang (zasdfgbnm) - Wednesday, 11 July 2012, 10:11 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 17 July 2012, 06:43 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


[code]$ systemctl status vsftpd.service
vsftpd.service - vsftpd daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; enabled)
Active: failed (Result: exit-code) since Wed, 11 Jul 2012 17:54:41 +0000; 5s ago
Process: 1208 ExecStart=/usr/sbin/vsftpd -olisten_ipv6=yes (code=exited, status=2)
CGroup: name=systemd:/system/vsftpd.service[/code]
And I get no errors by execute vsftpd with no parameters, but I get error when run the command:
[code]# vsftpd -olisten_ipv6=yes
500 OOPS: run two copies of vsftpd for IPv4 and IPv6[/code]
And I don't understand why vsftpd's rc.d command is
[code]vsftpd &[/code]
while the systemd's vsftpd.service is
[code]vsftpd -olisten_ipv6=yes[/code]
It seems strange to force listening ipv6.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Tuesday, 17 July 2012, 06:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  vsftpd 3.0.0-4
Comment by Dave Reisner (falconindy) - Monday, 16 July 2012, 12:46 GMT
Have you disabled ipv6?
Comment by Gao Xiang (zasdfgbnm) - Monday, 16 July 2012, 12:50 GMT
$ grep listen_ipv6 /etc/vsftpd.conf
# with the listen_ipv6 directive.
The listen_ipv6=YES is commented
Comment by Dave Reisner (falconindy) - Monday, 16 July 2012, 13:03 GMT
No, I meant have you disabled ipv6 functionality systemwide
Comment by Gao Xiang (zasdfgbnm) - Monday, 16 July 2012, 13:07 GMT
No, I didn't:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 60:eb:69:9e:fa:12 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:26:c7:85:d4:72 brd ff:ff:ff:ff:ff:ff
inet brd scope global wlan0
inet6 fe80::226:c7ff:fe85:d472/64 scope link
valid_lft forever preferred_lft forever
6: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 5e:4c:84:b0:e3:af brd ff:ff:ff:ff:ff:ff