We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Не запускается bind9 после обновления VESTA CP
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Не запускается bind9 после обновления VESTA CP
Добрый вечер. Обновил VESTA CP и понеслось.. Перестали работать Apache, Nginx, bind9.
Первые два кое как запустил. А вот bind9 не могу.
Пытаюсь перезапустить в панели пишет - Error: bind9 restart failed
Пытаюсь перезапустить через консоль:
root@lyskow:~# service bind9 restart
[....] Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused
. ok
[FAIL] Starting domain name service...: bind9 failed!
root@lyskow:~#
Делаю проверку:
root@lyskow:~# named -g -u bind
12-Mar-2017 15:20:26.680 starting BIND 9.8.4-rpz2+rl005.12-P1 -g -u bind
12-Mar-2017 15:20:26.681 built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2'
12-Mar-2017 15:20:26.681 ----------------------------------------------------
12-Mar-2017 15:20:26.681 BIND 9 is maintained by Internet Systems Consortium,
12-Mar-2017 15:20:26.681 Inc. (ISC), a non-profit 501(c)(3) public-benefit
12-Mar-2017 15:20:26.681 corporation. Support and training for BIND 9 are
12-Mar-2017 15:20:26.681 available at https://www.isc.org/support
12-Mar-2017 15:20:26.681 ----------------------------------------------------
12-Mar-2017 15:20:26.681 adjusted limit on open files from 4096 to 1048576
12-Mar-2017 15:20:26.681 found 2 CPUs, using 2 worker threads
12-Mar-2017 15:20:26.681 using up to 4096 sockets
12-Mar-2017 15:20:26.683 loading configuration from '/etc/bind/named.conf'
12-Mar-2017 15:20:26.684 /etc/bind/named.conf:30: zone '': is not a valid name
12-Mar-2017 15:20:26.684 loading configuration: failure
12-Mar-2017 15:20:26.684 exiting (due to fatal error)
root@lyskow:~#
Как решить проблему не знаю. Подскажите пожалуйста. Сайты открываются с приветствием It worked!
Первые два кое как запустил. А вот bind9 не могу.
Пытаюсь перезапустить в панели пишет - Error: bind9 restart failed
Пытаюсь перезапустить через консоль:
root@lyskow:~# service bind9 restart
[....] Stopping domain name service...: bind9rndc: connect failed: 127.0.0.1#953: connection refused
. ok
[FAIL] Starting domain name service...: bind9 failed!
root@lyskow:~#
Делаю проверку:
root@lyskow:~# named -g -u bind
12-Mar-2017 15:20:26.680 starting BIND 9.8.4-rpz2+rl005.12-P1 -g -u bind
12-Mar-2017 15:20:26.681 built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2'
12-Mar-2017 15:20:26.681 ----------------------------------------------------
12-Mar-2017 15:20:26.681 BIND 9 is maintained by Internet Systems Consortium,
12-Mar-2017 15:20:26.681 Inc. (ISC), a non-profit 501(c)(3) public-benefit
12-Mar-2017 15:20:26.681 corporation. Support and training for BIND 9 are
12-Mar-2017 15:20:26.681 available at https://www.isc.org/support
12-Mar-2017 15:20:26.681 ----------------------------------------------------
12-Mar-2017 15:20:26.681 adjusted limit on open files from 4096 to 1048576
12-Mar-2017 15:20:26.681 found 2 CPUs, using 2 worker threads
12-Mar-2017 15:20:26.681 using up to 4096 sockets
12-Mar-2017 15:20:26.683 loading configuration from '/etc/bind/named.conf'
12-Mar-2017 15:20:26.684 /etc/bind/named.conf:30: zone '': is not a valid name
12-Mar-2017 15:20:26.684 loading configuration: failure
12-Mar-2017 15:20:26.684 exiting (due to fatal error)
root@lyskow:~#
Как решить проблему не знаю. Подскажите пожалуйста. Сайты открываются с приветствием It worked!
Re: Не запускается bind9 после обновления VESTA CP
Вот исправить строку
12-Mar-2017 15:20:26.684 /etc/bind/named.conf:30: zone '': is not a valid name
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Re: Не запускается bind9 после обновления VESTA CP
эту строку я удалил, т.к удалил домен этой записи.Mr.Erbutw wrote:Вот исправить строку12-Mar-2017 15:20:26.684 /etc/bind/named.conf:30: zone '': is not a valid name
Это не решило проблему.
Re: Не запускается bind9 после обновления VESTA CP
"пересоздать" и потом с ново протестировать.
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Re: Не запускается bind9 после обновления VESTA CP
Все данные останутся?Mr.Erbutw wrote:
"пересоздать" и потом с ново протестировать.
Re: Не запускается bind9 после обновления VESTA CP
Не чего не должно удалиться , если где был затык обновиться информация.evgenkirov wrote: Все данные останутся?
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Re: Не запускается bind9 после обновления VESTA CP
Пересоздал - снова перестал включаться apache, nginx и bindMr.Erbutw wrote:Не чего не должно удалиться , если где был затык обновиться информация.evgenkirov wrote: Все данные останутся?
Re: Не запускается bind9 после обновления VESTA CP
В логах что ?evgenkirov wrote: Пересоздал - снова перестал включаться apache, nginx и bind
/var/log/nginx/error.log
/var/log/apache2/error.log
последние строки указывают на ошибки.
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Re: Не запускается bind9 после обновления VESTA CP
nginx:Mr.Erbutw wrote:В логах что ?evgenkirov wrote: Пересоздал - снова перестал включаться apache, nginx и bind
/var/log/nginx/error.log
/var/log/apache2/error.log
последние строки указывают на ошибки.
2017/03/12 13:54:49 [emerg] 6044#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 13:59:10 [emerg] 7161#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 13:59:12 [emerg] 7395#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 13:59:52 [emerg] 6028#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 14:01:51 [emerg] 6647#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 14:13:45 [emerg] 14760#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:564
2017/03/12 14:17:56 [error] 14972#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai"
2017/03/12 14:17:56 [error] 14972#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai"
2017/03/12 14:17:56 [error] 14972#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "http://146.185.243.151:8080/favicon.ico", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai", referrer: "http://xn--43-6kcaak9aj5chl4a3g.xn--p1ai/"
2017/03/12 14:17:56 [error] 14972#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai", referrer: "http://xn--43-6kcaak9aj5chl4a3g.xn--p1ai/"
2017/03/12 14:18:04 [error] 14972#0: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.132.81, server: _, request: "GET /robots.txt HTTP/1.1", upstream: "http://146.185.243.151:8080/robots.txt", host: "xn--43-vlclpmiim.xn--p1ai"
2017/03/12 14:18:04 [error] 14972#0: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.132.81, server: _, request: "GET /robots.txt HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-vlclpmiim.xn--p1ai"
2017/03/12 14:18:08 [error] 14972#0: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.142.7, server: _, request: "GET /sbornye_bukety HTTP/1.1", upstream: "http://146.185.243.151:8080/sbornye_bukety", host: "xn--43-vlclpmiim.xn--p1ai"
2017/03/12 14:18:08 [error] 14972#0: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.142.7, server: _, request: "GET /sbornye_bukety HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-vlclpmiim.xn--p1ai"
2017/03/12 14:19:07 [error] 14972#0: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.132.12, server: _, request: "GET /robots.txt HTTP/1.1", upstream: "http://146.185.243.151:8080/robots.txt", host: "meridian-kirov.ru"
2017/03/12 14:19:07 [error] 14972#0: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 141.8.132.12, server: _, request: "GET /robots.txt HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "meridian-kirov.ru"
2017/03/12 14:19:12 [error] 14972#0: *15 connect() failed (111: Connection refused) while connecting to upstream, client: 130.193.51.11, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/", host: "meridian-kirov.ru"
2017/03/12 14:19:12 [error] 14972#0: *15 connect() failed (111: Connection refused) while connecting to upstream, client: 130.193.51.11, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "meridian-kirov.ru"
2017/03/12 14:19:46 [error] 14972#0: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai"
2017/03/12 14:19:46 [error] 14972#0: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai"
2017/03/12 14:19:46 [error] 14972#0: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "http://146.185.243.151:8080/favicon.ico", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai", referrer: "http://xn--43-6kcaak9aj5chl4a3g.xn--p1ai/"
2017/03/12 14:19:46 [error] 14972#0: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 94.181.204.3, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-6kcaak9aj5chl4a3g.xn--p1ai", referrer: "http://xn--43-6kcaak9aj5chl4a3g.xn--p1ai/"
2017/03/12 14:20:18 [error] 14972#0: *24 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.64.150, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/", host: "xn--43-jlcenr2b.xn--p1ai"
2017/03/12 14:20:18 [error] 14972#0: *24 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.64.150, server: _, request: "GET / HTTP/1.1", upstream: "http://146.185.243.151:8080/error/50x.html", host: "xn--43-jlcenr2b.xn--p1ai"
2017/03/13 00:44:38 [emerg] 6037#0: invalid number of arguments in "server_name" directive in /home/admin/conf/web/nginx.conf:69
-
- Posts: 17
- Joined: Thu Mar 02, 2017 4:18 am
Re: Не запускается bind9 после обновления VESTA CP
в apache последние строкиMr.Erbutw wrote:В логах что ?evgenkirov wrote: Пересоздал - снова перестал включаться apache, nginx и bind
/var/log/nginx/error.log
/var/log/apache2/error.log
последние строки указывают на ошибки.
[Mon Mar 13 00:30:09 2017] [error] [client 130.193.50.28] File does not exist: /var/www/robots.txt
[Mon Mar 13 00:30:13 2017] [error] [client 130.193.50.28] File does not exist: /var/www/image
[Mon Mar 13 00:31:48 2017] [error] [client 130.193.50.28] File does not exist: /var/www/robots.txt
[Mon Mar 13 00:31:52 2017] [error] [client 130.193.50.28] File does not exist: /var/www/favicon.ico
[Mon Mar 13 00:32:06 2017] [error] [client 130.193.50.28] File does not exist: /var/www/robots.txt
[Sun Mar 12 17:32:10 2017] [error] [client 130.193.50.28] File does not exist: /var/www/image
[Mon Mar 13 00:33:08 2017] [error] [client 94.181.204.3] File does not exist: /var/www/favicon.ico, referer: http://homehit.shop/
[Mon Mar 13 00:34:17 2017] [error] [client 141.8.184.32] File does not exist: /var/www/favicon.ico
[Mon Mar 13 00:36:30 2017] [error] [client 5.228.98.127] File does not exist: /var/www/insikom, referer: http://yandex.ru/clck/jsredir?from=yand ... 7518628529
[Sun Mar 12 17:38:34 2017] [error] [client 66.249.64.34] File does not exist: /var/www/soviet_porcelain
[Mon Mar 13 00:38:52 2017] [error] [client 191.96.249.97] File does not exist: /usr/share/phpmyadmin/scripts
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory
[Sun Mar 12 17:44:06 2017] [notice] caught SIGTERM, shutting down
Failed loading /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: /usr/lib/php5/20131226/ioncube_loader_lin_5.6.sooo[PHP]: cannot open shared object file: No such file or directory