Vesta Control Panel - Forum

one wrote:

skurudo wrote:Если получится, то скиньте вывод команд сразу после перезагрузки:
service httpd status -l
service nginx status -l
service named status -l

По апачу как я понимаю вся проблема в FQD и как я могу предположить остальные сервисфы тоже тянут эту проблему.

[root@xxx-xx-xxx run]# service httpd status -l
Redirecting to /bin/systemctl status -l httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2016-04-14 19:04:47 EEST; 5min ago
Process: 335 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 246 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 246 (code=exited, status=1/FAILURE)

Apr 14 19:04:47 xxx-xx-xxx httpd[246]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using ::2. Set the 'ServerName' directive globally to suppress this message
Apr 14 19:04:47 xxx-xx-xxx httpd[246]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address xx.xx.xx.xx:8080
Apr 14 19:04:47 xxx-xx-xxx httpd[246]: no listening sockets available, shutting down
Apr 14 19:04:47 xxx-xx-xxx httpd[246]: AH00015: Unable to open logs
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Apr 14 19:04:47 xxx-xx-xxx kill[335]: kill: cannot find process ""
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: httpd.service: control process exited, code=exited status=1
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: Failed to start The Apache HTTP Server.
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: Unit httpd.service entered failed state.
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: httpd.service failed.

[root@xxx-xx-xxx run]# service nginx status -l
Redirecting to /bin/systemctl status -l nginx.service
● nginx.service - nginx - high performance web server
Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2016-04-14 19:04:47 EEST; 6min ago
Docs: http://nginx.org/en/docs/
Process: 244 ExecStartPre=/usr/sbin/nginx -t -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)

Apr 14 19:03:39 xxx-xx-xxx systemd[1]: Stopping nginx - high performance web server...
Apr 14 19:03:39 xxx-xx-xxx systemd[1]: Stopped nginx - high performance web server.
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: Starting nginx - high performance web server...
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: nginx.service: control process exited, code=exited status=1
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: Failed to start nginx - high performance web server.
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: Unit nginx.service entered failed state.
Apr 14 19:04:47 xxx-xx-xxx systemd[1]: nginx.service failed.
Apr 14 19:04:47 xxx-xx-xxx nginx[244]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Apr 14 19:04:47 xxx-xx-xxx nginx[244]: nginx: [emerg] bind() to xx.xx.xx.xx:80 failed (99: Cannot assign requested address)
Apr 14 19:04:47 xxx-xx-xxx nginx[244]: nginx: configuration file /etc/nginx/nginx.conf test failed

[root@xxx-xx-xxx run]# service named status -l
Redirecting to /bin/systemctl status -l named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2016-04-14 19:04:47 EEST; 6min ago
Process: 218 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=0/SUCCESS)
Process: 204 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
Main PID: 225 (named)
CGroup: /system.slice/named.service
└─225 /usr/sbin/named -u named

Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 199.7.91.13#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 198.41.0.4#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 192.5.5.241#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 192.58.128.30#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 2001:dc3::35#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 2001:7fd::1#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 2001:7fe::53#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 128.63.2.53#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving './NS/IN': 2001:500:3::42#53
Apr 14 19:04:47 xxx-xx-xxx named[225]: error (network unreachable) resolving 'C.ROOT-SERVERS.NET/AAAA/IN': xx.xx.xx.xx#53

one wrote:Да, еще заметил, на вкладке Сервер, выбираю настройки и указываю в поле Hostname host.domain.com после перезагрузки остается только host.

one wrote: По апачу как я понимаю вся проблема в FQD и как я могу предположить остальные сервисфы тоже тянут эту проблему.

skurudo wrote:

one wrote: По апачу как я понимаю вся проблема в FQD и как я могу предположить остальные сервисфы тоже тянут эту проблему.

Сомневаюсь, что проблема именно в этом. :(
Кривой хостнейм - не очень хорошо, но не смертельно в рамках мировой революции.

one wrote:Но ведь ошибка указывает на FQD.

Apr 14 19:04:47 xxx-xx-xxx httpd[246]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address xx.xx.xx.xx:8080
...
Apr 14 19:04:47 xxx-xx-xxx nginx[244]: nginx: [emerg] bind() to xx.xx.xx.xx:80 failed (99: Cannot assign requested address)

one wrote:Вы пропустили строку выше.

orka13 wrote:РЕШЕНО
Та же ситуация. Чистый VPS от hetzner.de, CentOS 7.2 minimal. Только там IP выдают внутренную и внешнюю (NAT IP association). Помогло решение из этой ветки - viewtopic.php?f=29&t=8200&p=25566&hilit ... ess#p25566 (начинайте с места где правка в /etc/sysctl.conf )