Job for vsftpd.service failed because the control process exited with error code Announcing...
What is best way to wire a ceiling receptacle in this situation?
Did any compiler fully use 80-bit floating point?
macOS: Name for app shortcut screen found by pinching with thumb and three fingers
How to report t statistic from R
Maximum summed subsequences with non-adjacent items
What does it mean that physics no longer uses mechanical models to describe phenomena?
Significance of Cersei's obsession with elephants?
Sum letters are not two different
How many morphisms from 1 to 1+1 can there be?
What makes a man succeed?
In musical terms, what properties are varied by the human voice to produce different words / syllables?
Why weren't discrete x86 CPUs ever used in game hardware?
What does Turing mean by this statement?
How does light 'choose' between wave and particle behaviour?
What is the difference between a "ranged attack" and a "ranged weapon attack"?
Is there public access to the Meteor Crater in Arizona?
Google .dev domain strangely redirects to https
Why do early math courses focus on the cross sections of a cone and not on other 3D objects?
What does this say in Elvish?
Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?
Girl Hackers - Logic Puzzle
What is the chair depicted in Cesare Maccari's 1889 painting "Cicerone denuncia Catilina"?
A term for a woman complaining about things/begging in a cute/childish way
How would a mousetrap for use in space work?
Job for vsftpd.service failed because the control process exited with error code
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionChange the listening address to IPv4 from IPv6Linux kernel 3.3 power regressionvsftpd won't start: “systemd[1]: vsftpd.service: main process exited, code=exited, status=2/INVALIDARGUMENT”tomcat 8 will not start after initial installKdump.service FAILED centOS 7VSFTPD FileZilla GnuTLS error -15 (unexpected TLS packet was received)Can't restart the network service on CentOSFedora 27: Getting error repeatedly “Job for <xxx.service> failed because the control process exited with error code”On starting sssdVery slow login + very slow response - dbus error? - Ubuntu 18.04.1 LTS - on Virtualbox 5.2.18 r124319 (Qt5.6.3) - on MacOS High Sierra 10.13.6systemd - mount mount process exited, code=exited status=32
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I can not restart the vsftpd
.
[root@localhost vsftpd]# service vsftpd restart
Redirecting to /bin/systemctl restart vsftpd.service
Job for vsftpd.service failed because the control process exited with error code. See "systemctl status vsftpd.service" and "journalctl -xe" for details.
I use the systemctl status vsftpd -l
to check:
[root@localhost ~]# systemctl status vsftpd -l
● vsftpd.service - Vsftpd ftp daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-06-18 17:14:15 CST; 2h 49min ago
Process: 33103 ExecStart=/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf (code=exited, status=1/FAILURE)
Jun 18 17:14:12 localhost.localdomain systemd[1]: Starting Vsftpd ftp daemon...
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service: control process exited, code=exited status=1
Jun 18 17:14:15 localhost.localdomain systemd[1]: Failed to start Vsftpd ftp daemon.
Jun 18 17:14:15 localhost.localdomain systemd[1]: Unit vsftpd.service entered failed state.
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service failed.
And be attention, in my /etc/vsftpd/vsftpd.conf
, I have changed the :
listen=YES
listen_ipv6=NO
I use the journalctl -xe
, I get the below information:
[root@localhost vsftpd]# journalctl -xe
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
li
linux centos vsftpd
bumped to the homepage by Community♦ 24 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I can not restart the vsftpd
.
[root@localhost vsftpd]# service vsftpd restart
Redirecting to /bin/systemctl restart vsftpd.service
Job for vsftpd.service failed because the control process exited with error code. See "systemctl status vsftpd.service" and "journalctl -xe" for details.
I use the systemctl status vsftpd -l
to check:
[root@localhost ~]# systemctl status vsftpd -l
● vsftpd.service - Vsftpd ftp daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-06-18 17:14:15 CST; 2h 49min ago
Process: 33103 ExecStart=/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf (code=exited, status=1/FAILURE)
Jun 18 17:14:12 localhost.localdomain systemd[1]: Starting Vsftpd ftp daemon...
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service: control process exited, code=exited status=1
Jun 18 17:14:15 localhost.localdomain systemd[1]: Failed to start Vsftpd ftp daemon.
Jun 18 17:14:15 localhost.localdomain systemd[1]: Unit vsftpd.service entered failed state.
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service failed.
And be attention, in my /etc/vsftpd/vsftpd.conf
, I have changed the :
listen=YES
listen_ipv6=NO
I use the journalctl -xe
, I get the below information:
[root@localhost vsftpd]# journalctl -xe
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
li
linux centos vsftpd
bumped to the homepage by Community♦ 24 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Please update your question withsystemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.
– ddnomad
Jun 18 '17 at 10:51
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@three-blocks Check if hostname matchespasv_address=
in /etc/vsftpd/vsftpd.conf
– Ivan Chau
Jun 20 '17 at 8:15
@IvanChau No, there is nopasv_address
pattern the file's content.
– three-blocks
Jun 26 '17 at 16:14
Thejournalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with--no-pager
.
– JigglyNaga
Oct 12 '18 at 15:26
add a comment |
I can not restart the vsftpd
.
[root@localhost vsftpd]# service vsftpd restart
Redirecting to /bin/systemctl restart vsftpd.service
Job for vsftpd.service failed because the control process exited with error code. See "systemctl status vsftpd.service" and "journalctl -xe" for details.
I use the systemctl status vsftpd -l
to check:
[root@localhost ~]# systemctl status vsftpd -l
● vsftpd.service - Vsftpd ftp daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-06-18 17:14:15 CST; 2h 49min ago
Process: 33103 ExecStart=/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf (code=exited, status=1/FAILURE)
Jun 18 17:14:12 localhost.localdomain systemd[1]: Starting Vsftpd ftp daemon...
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service: control process exited, code=exited status=1
Jun 18 17:14:15 localhost.localdomain systemd[1]: Failed to start Vsftpd ftp daemon.
Jun 18 17:14:15 localhost.localdomain systemd[1]: Unit vsftpd.service entered failed state.
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service failed.
And be attention, in my /etc/vsftpd/vsftpd.conf
, I have changed the :
listen=YES
listen_ipv6=NO
I use the journalctl -xe
, I get the below information:
[root@localhost vsftpd]# journalctl -xe
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
li
linux centos vsftpd
I can not restart the vsftpd
.
[root@localhost vsftpd]# service vsftpd restart
Redirecting to /bin/systemctl restart vsftpd.service
Job for vsftpd.service failed because the control process exited with error code. See "systemctl status vsftpd.service" and "journalctl -xe" for details.
I use the systemctl status vsftpd -l
to check:
[root@localhost ~]# systemctl status vsftpd -l
● vsftpd.service - Vsftpd ftp daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-06-18 17:14:15 CST; 2h 49min ago
Process: 33103 ExecStart=/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf (code=exited, status=1/FAILURE)
Jun 18 17:14:12 localhost.localdomain systemd[1]: Starting Vsftpd ftp daemon...
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service: control process exited, code=exited status=1
Jun 18 17:14:15 localhost.localdomain systemd[1]: Failed to start Vsftpd ftp daemon.
Jun 18 17:14:15 localhost.localdomain systemd[1]: Unit vsftpd.service entered failed state.
Jun 18 17:14:15 localhost.localdomain systemd[1]: vsftpd.service failed.
And be attention, in my /etc/vsftpd/vsftpd.conf
, I have changed the :
listen=YES
listen_ipv6=NO
I use the journalctl -xe
, I get the below information:
[root@localhost vsftpd]# journalctl -xe
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: /etc/polkit-1/rules.d/49-p
(pkla-check-authorization:
'
Jun 18 20:09:46 localhost.localdomain polkitd[33643]: Error evaluating authoriza
li
linux centos vsftpd
linux centos vsftpd
edited Jun 18 '17 at 12:12
three-blocks
asked Jun 18 '17 at 9:24
three-blocksthree-blocks
228718
228718
bumped to the homepage by Community♦ 24 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 24 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Please update your question withsystemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.
– ddnomad
Jun 18 '17 at 10:51
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@three-blocks Check if hostname matchespasv_address=
in /etc/vsftpd/vsftpd.conf
– Ivan Chau
Jun 20 '17 at 8:15
@IvanChau No, there is nopasv_address
pattern the file's content.
– three-blocks
Jun 26 '17 at 16:14
Thejournalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with--no-pager
.
– JigglyNaga
Oct 12 '18 at 15:26
add a comment |
Please update your question withsystemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.
– ddnomad
Jun 18 '17 at 10:51
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@three-blocks Check if hostname matchespasv_address=
in /etc/vsftpd/vsftpd.conf
– Ivan Chau
Jun 20 '17 at 8:15
@IvanChau No, there is nopasv_address
pattern the file's content.
– three-blocks
Jun 26 '17 at 16:14
Thejournalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with--no-pager
.
– JigglyNaga
Oct 12 '18 at 15:26
Please update your question with
systemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.– ddnomad
Jun 18 '17 at 10:51
Please update your question with
systemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.– ddnomad
Jun 18 '17 at 10:51
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@three-blocks Check if hostname matches
pasv_address=
in /etc/vsftpd/vsftpd.conf– Ivan Chau
Jun 20 '17 at 8:15
@three-blocks Check if hostname matches
pasv_address=
in /etc/vsftpd/vsftpd.conf– Ivan Chau
Jun 20 '17 at 8:15
@IvanChau No, there is no
pasv_address
pattern the file's content.– three-blocks
Jun 26 '17 at 16:14
@IvanChau No, there is no
pasv_address
pattern the file's content.– three-blocks
Jun 26 '17 at 16:14
The
journalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with --no-pager
.– JigglyNaga
Oct 12 '18 at 15:26
The
journalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with --no-pager
.– JigglyNaga
Oct 12 '18 at 15:26
add a comment |
1 Answer
1
active
oldest
votes
According to vsftpd config file
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
so comment out listen_ipv6=NO
and try again .
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f371764%2fjob-for-vsftpd-service-failed-because-the-control-process-exited-with-error-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to vsftpd config file
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
so comment out listen_ipv6=NO
and try again .
add a comment |
According to vsftpd config file
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
so comment out listen_ipv6=NO
and try again .
add a comment |
According to vsftpd config file
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
so comment out listen_ipv6=NO
and try again .
According to vsftpd config file
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
so comment out listen_ipv6=NO
and try again .
edited Oct 12 '18 at 15:20
JigglyNaga
4,0621035
4,0621035
answered Oct 12 '18 at 14:52
Babasaheb ShindeBabasaheb Shinde
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f371764%2fjob-for-vsftpd-service-failed-because-the-control-process-exited-with-error-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please update your question with
systemctl status vsftpd -l
so output won't be ellipsized. It give some extra intel to look into.– ddnomad
Jun 18 '17 at 10:51
@ddnomad See my edit
– three-blocks
Jun 18 '17 at 12:05
@three-blocks Check if hostname matches
pasv_address=
in /etc/vsftpd/vsftpd.conf– Ivan Chau
Jun 20 '17 at 8:15
@IvanChau No, there is no
pasv_address
pattern the file's content.– three-blocks
Jun 26 '17 at 16:14
The
journalctl
output you've pasted was truncated at 80 characters (the usual width of a terminal), so we can't see the useful part of the error message. Please try again with--no-pager
.– JigglyNaga
Oct 12 '18 at 15:26