Я на Ubuntu 15.04, и я только что установил vsftpd . Когда я запускаю команду service vsftpd status , я получаю следующий вывод:
Я проверил /etc/vsftpd.conf , он существует, и я не нашел в этом ничего плохого. Как я могу это решить?
5 ответов
У меня были такие же симптомы, пытаясь запустить vsftpd на Ubuntu 16.04. В моем случае достаточно было прокомментировать эту строку в /etc/vsftpd.conf :
Я не знаю, почему я не работаю с ipv6 для меня, но у меня нет необходимости в IP-v6 и отключить его, решив проблему в моем случае.
шаг 1: проверьте vsftpd.conf
Шаг 2. Чтобы посмотреть, какая служба ftp работает, используйте
шаг 3: остановить xinetd
Шаг 4: после остановки xinetd перезапустите службу vsftpd, набрав
Это можно устранить, комментируя:
, и теперь я активен на vsftpd.
Ни один из этих решений не работал для меня. У меня даже отключена SELinux, поэтому это не было причиной, а файл конфигурации для vsftpd на 100% идеален, потому что service vstfpd start работает мгновенно, но просто не запускается при запуске.
Моим окончательным решением был этот скрипт bash, который работает с cron, постоянно проверяющим службу и отлично работающим сейчас, и запускает vsftp при запуске, проверяя и видя, что служба мертва и затем запускает ее.
Добрый день!
Помогите разобраться в чем проблема.
После автоматической установки сертификати LetsCrypt на Bitrix VM 7.3.4 получил ошыбку
- Вопрос задан 08 февр.
- 1077 просмотров
Feb 08 16:11:31 bitrix nginx[12233]: nginx: [emerg] unexpected end of file, expecting «>» in /etc/nginx/nginx.conf:79
секцию в конфиге не закрыли, о чем вам система и пишет.
А где ее закрывать? 79 это последний. Там должен быть символ «>»?
Ну давайте попробуем самое очевидное:
# Set additional websites
include bx/site_ext_enabled/*.conf;
>
Если ошибка останется, значит надо смотреть, что вы меняли во вложенных файлах.
для проверки синтаксиса можно в консоли писать команду nginx — t
fluffybear, Написал > в конце
При перечитівании конфигурации полуаю
I got a problem which I have been trying to fix for a few days now and I don’t know what to do, have been looking for answers but all of those I found didn’t help me.
I am kinda new here and I really hope that someone can help me. You can tell me which informations I need to give in hope for finding a solution.
# service nginx restart Restarting nginx (via systemctl): Job for nginx.service failed because the control process exited with error code. See «systemctl status nginx.service» and «journalctl -xe» for details. [FAILED] – daliborsb Mar 8 ’16 at 13:58
15 Answers 15
Try to run the following two commands:
sudo fuser -k 80/tcp
sudo fuser -k 443/tcp
sudo service nginx restart
If that worked, your hosting provider might be installing Apache on your server by default during a fresh install, so keep reading for a more permenant fix. If that didn’t work, keep reading to identify the issue.
Run nginx -t and if it doesn’t return anything, I would verify Nginx error log. By default, it should be located in /var/log/nginx/error.log .
You can open it with any text editor: sudo nano /var/log/nginx/error.log
Can you find something suspicious there?
The second log you can check is the following
sudo nano /var/log/syslog
When I had this issue, it was because my hosting provider was automatically installing Apache during a clean install. It was blocking port 80.
When I executed sudo nano /var/log/nginx/error.log I got the following as the error log:
What the above error is telling is that it was not able to bind nginx to port 80 because it was already in use.
To fix this, you need to run the following:
yum install net-tools
sudo netstat -tulpn
When you execute the above you will get something like the following:
You can see that port 80 is blocked by httpd (Apache). This could also be port 443 if you are using SSL.
Get the PID of the process that uses port 80 or 443. And send the kill command changing the
Note in my example the PID value of Apache was 1762 so I would execute sudo kill -2 1762
Aternatively you can execute the following:
sudo fuser -k 80/tcp
sudo fuser -k 443/tcp
Now that port 80 or 443 is clear, you can start Nginx by running the following:
sudo service nginx restart
It is also advisable to remove whatever was previously blocking port 80 & 443. This will avoid any conflict in the future. Since Apache (httpd) was blocking my ports I removed it by running the following:
yum remove httpd httpd-devel httpd-manual httpd-tools mod_auth_kerb mod_auth_mysql mod_auth_pgsql mod_authz_ldap mod_dav_svn mod_dnssd mod_nss mod_perl mod_revocator mod_ssl mod_wsgi
Hope this helps.
May come in handy to check syntax of Nginx’s configuration files by running:
In my case, it’s because of apache server is running somehow. So I stop apache then restart nginx. Work like a charm!
Try to debug with command:
Which outputs something like:
And fix those warnings
Then restart nginx
When something cannot bind to a port, it’s 5% because it’s not started by root (sticky suid bit, sudo) and 94% because another application is already bound to that port.
Make sure nginx is really shutdown and you don’t try to start it twice by accident.
Make sure you don’t have Apache or other services running that use port 80.
Utilize netstat -a | grep tcp to find out more.
change the port may help as 80 port is already using somewhere
Change the port:
And then restart the nginx server
or set back /etc/nginx/sites-available/default
location / <
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
>
I had the same problem when I used Vesta, which uses nginx with apache. The problem was that after applying all updates Apache started listening to 443 for https. The solution was just to comment out the 443 stuff in ports.conf. This is because nginx also uses this port.
The cause of the issue is this, I already had Apache web server installed and actively listening on port 80 on my local machine.
Apache and Nginx are the two major open-source high-performance web servers capable of handling diverse workloads to satisfy the needs of modern web demands. However, Apache serves primarily as a HTTP server whereas Nginx is a high-performance asynchronous web server and reverse proxy server.
The inability of Nginx to start was because Apache was already listening on port 80 as its default port, which is also the default port for Nginx .
One quick workaround would be to stop Apache server by running the command below
And then starting up Nginx server by running the command below
However, this same issue will arise again when we try to start Apache server again, since they both use port 80 as their default port.
Here’s how I fixed it
Run the command below to open the default configuration file of Nginx in Nano editor
When the file opens in Nano editor, scroll down and change the default server port to any port of your choice. For me, I chose to change it to port 85
Also, scroll down and change the virtual host port to any port of your choice. For me, I also chose to change it to port 85
Then exit the file by pressing on your keyboard
And then Press Y on your keyboard to save the changes.