Vesta error httpd restart failed

I tried to resolve this as best I could by google search. I paid for support on vestacp.com website but no one has contacted me yet. I am really in hot water right now. I need a kind person to help me.

For the last 2 days the httpd does not want to restart. For a while nginx also did not want to restart but I got it fix.

In Vestacp I get this message when I click httpd to restart: Error: httpd restart failed.

In the Terminal after typing this command «service httpd restart» I get this message:
Job for httpd.service failed because the control process exited with error code. See «systemctl status httpd.service» and «journalctl -xe» for details.

systemctl status 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 Mon 2018-03-05 07:36:33 EST; 2min 46s ago
Process: 7234 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 7232 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 7232 (code=exited, status=1/FAILURE)

Mar 05 07:36:32 vps105566.vps.ovh.ca systemd[1]: Starting The Apache HTTP Server…
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using myserverdomain.com. Set the ‘ServerName’ directive globally to suppress this message
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: no listening sockets available, shutting down
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00015: Unable to open logs
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 05 07:36:33 vps105566.vps.ovh.ca kill[7234]: kill: cannot find process «»
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Failed to start The Apache HTTP Server.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Unit httpd.service entered failed state.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service failed.
—————————-

The no listening sockets available, shutting down
httpd port 8080 and 8443 are not used by any other services.

It could be the AH00015: Unable to open logs.

Vesta Control Panel — Forum

Cannot change apache web template

Cannot change apache web template

Post by webass » Wed Aug 17, 2016 8:03 pm

then it happened, that it deleted the conf completely.
and all domains got redirected to the domain running under a second user .

Then I had to install the complete thing in virtualbox to get my apache2.conf back.
Still the one domain makes thi sproblems, which uses the webtemplate I want to change.

Totally not getting why it doesnt write into it also anymore.
Sorry. Its hard to explain.
It doesnt work over the panel and also not over the CLI.
When I do it on a subdomain for example, I get:

which is anywhere in between the virtual hosts.
and apache restarts fine again.

But this doesnt work on the one domain which uses the «broken» web template I want it to stop to use
Very strange stuff.

Now, I wanted to delete the sub domain I changed the webtemplate on for testing, and it gives this:

Re: Cannot change apache web template

Post by webass » Thu Aug 18, 2016 7:19 am

Re: Cannot change apache web template

Post by webass » Thu Aug 18, 2016 7:27 am

One line free on top and also on /home/admin/conf/web/apache2.conf I did so.
and nothing helped.

I want to have the site use the default-tpl instead the other one, where I just wanted the fcgid to become with 256 MB memory limit. Thas why I created it long ago.

Re: Cannot change apache web template

Post by webass » Thu Aug 18, 2016 7:56 am

Well, not sure what you mean.

I did a rebuild web on admin the other day, that messed my whole server up.
I think you dont mean to make this again.

I go to panel or either do it on CLI when using another template.
Then it makes these errors.
In apache2.conf nothing happens other than the is ADDED anywhere.
The domain I want to change doesnt even HAVE a virtual host entry in apache2.conf.
When I add it manually it only is taken «by half».

LOL, now you know, when I go to the domain and save it WITH the template it anyway uses, then it saves without error, but in apache2.conf still no entry created for this domain. Thats why its not reachable at all over web.

And now, I tested it on another domain to set from default-tpl to fcgid-tpl.
result: It cannot restart apache2

Источник

Apache2 fails to restart because template is broken #1816

Operating System (OS/VERSION):

Ubuntu 16.04.5 LTS

VestaCP Version:

Installed Software (what you got with the installer):

Apache, Proxy Nginx, PHP, proFTP, mysql,

Steps to Reproduce:

Since a few days ago, I have noticed that Apache is not started and I have to run v-rebuilt-user admin to make it all work again.

Analyzing the server logs, I have observed the following:

[Mon Jan 28 04:33:04.392342 2019] [mpm_prefork:notice] [pid 13751] AH00171: Graceful restart requested, doing restart
[Tue Jan 29 04:33:04.080522 2019] [mpm_prefork:notice] [pid 26592] AH00171: Graceful restart requested, doing restart

Look the hour: 04:33

If I check the cron jobs:

`# crontab -l -u admin

15 02 * * * sudo /usr/local/vesta/bin/v-update-sys-queue disk

10 00 * * * sudo /usr/local/vesta/bin/v-update-sys-queue traffic

30 03 * * * sudo /usr/local/vesta/bin/v-update-sys-queue webstats

*/5 * * * * sudo /usr/local/vesta/bin/v-update-sys-queue backup

10 05 * * * sudo /usr/local/vesta/bin/v-backup-users

20 00 * * * sudo /usr/local/vesta/bin/v-update-user-stats

*/5 * * * * sudo /usr/local/vesta/bin/v-update-sys-rrd

33 4 * * * sudo /usr/local/vesta/bin/v-update-letsencrypt-ssl`

Last cronjob runs at the same time Apache has to restart.

If I run the v-update-letsencrypt-ssl script:

# v-update-letsencrypt-ssl domain.com Error: apache2 restart failed domain2.com Error: apache2 restart failed domain3.com Error: apache2 restart failed [. ]

All domains failed when apache restart :/

In script I see this:

msg=$($BIN/v-add-letsencrypt-domain $user $domain $aliases)
if [ $? -ne 0 ]; then
echo «$domain $msg»
fi

I see that these two lines are related:

echo «$domain $msg» domain.com Error: apache2 restart failed

Therefore, I have manually executed the following script:

v-add-letsencrypt-domain admin domain.com www.domain.com

And the output is this:

Error: apache2 restart failed Error: apache2 restart failed

After the error, I checked the Apache configuration file:

# apachectl -f pwd /sapache2.conf apache2: Syntax error on line 295 of /home/admin/conf/web/sapache2.conf: without matching section Action ‘-f /home/admin/conf/web/sapache2.conf’ failed. The Apache error log may have more information.

In the VirtualHost of the domain I have tried to renew the SSL, appears without the first line of VirtualHost:

I’ve also found that by changing the Apache template for the domain and then reapplying the one I had, the problem is solved.

The text was updated successfully, but these errors were encountered:

Источник

Vesta Control Panel — Forum

Не могу установить VestaCP.

Не могу установить VestaCP.

Post by Serhiyyy » Sat Jul 11, 2015 3:00 pm

Прошу у Вас помощи с установкой панели.
При вводе команды:
bash vst-install.sh
Запускается процесс установки и через 10 секунд после заполнения информации вылазит ошибка:
E: Malformed line 1 in source list /etc/apt/sources.list.d/nginx.list (dist parse)
E: The list of sources could not be read.
Reading package lists. Error!
E: Malformed line 1 in source list /etc/apt/sources.list.d/nginx.list (dist parse)
E: The list of sources could not be read.
E: The package lists or status file could not be parsed or opened.
Error: apt-get install failed

Помогите решить данную проблему.
ОС:

Distributor ID: Debian
Description: Debian GNU/Linux 8.1 (jessie)
Release: 8.1
Codename: jessie

Re: Не могу установить VestaCP.

Post by imperio » Sat Jul 11, 2015 3:45 pm

Re: Не могу установить VestaCP.

Post by mak » Sun Oct 04, 2015 6:31 pm

Re: Не могу установить VestaCP.

Post by imperio » Sun Oct 04, 2015 6:43 pm

Re: Не могу установить VestaCP.

Post by Shurik » Sun Oct 04, 2015 10:16 pm

Re: Не могу установить VestaCP.

Post by RUSb » Mon Oct 05, 2015 6:30 am

Re: Не могу установить VestaCP.

Post by skurudo » Mon Oct 05, 2015 7:06 am

Коллеги, посмотрите ваш файлик — /etc/apt/sources.list.d/nginx.list
Что-то с ним не так. Причем не так прямо в первой строке.
Покажите ее что ли.
Исправьте или закоментируйте.

PS: Возможно где-то она уже есть в source (но это вряд ли).

Re: Не могу установить VestaCP.

Post by RUSb » Mon Oct 05, 2015 7:24 am

skurudo wrote: Коллеги, посмотрите ваш файлик — /etc/apt/sources.list.d/nginx.list
Что-то с ним не так. Причем не так прямо в первой строке.
Покажите ее что ли.
Исправьте или закоментируйте.

PS: Возможно где-то она уже есть в source (но это вряд ли).

Ну там как бы 1 строчка, которая задаётся установочным скриптом, ну и проверяется она как я понимаю тоже при запуске самого скрипта. Пробовал править в самом скрипте, но что то тоже не очень вышло.

UPD
Может ему попросту ненравится debian 7.8 (собственно налетел на подобную проблему с установкой на 8ю версию дебиан (глаза же на затылок)) по каким то причинам, так как система чистая, и ставилась именно для установки панели и веб сервера, то попропбую сейчас накатить на centos

Источник

Vesta Control Panel — Forum

Error: httpd restart failed

Error: httpd restart failed

Post by ogeitblues » Mon Mar 05, 2018 1:29 pm

I tried to resolve this as best I could by google search. I paid for support on vestacp.com website but no one has contacted me yet. I am really in hot water right now. I need a kind person to help me.

For the last 2 days the httpd does not want to restart. For a while nginx also did not want to restart but I got it fix.

In Vestacp I get this message when I click httpd to restart: Error: httpd restart failed.

In the Terminal after typing this command «service httpd restart» I get this message:
Job for httpd.service failed because the control process exited with error code. See «systemctl status httpd.service» and «journalctl -xe» for details.

systemctl status 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 Mon 2018-03-05 07:36:33 EST; 2min 46s ago
Process: 7234 ExecStop=/bin/kill -WINCH $ (code=exited, status=1/FAILURE)
Process: 7232 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 7232 (code=exited, status=1/FAILURE)

Mar 05 07:36:32 vps105566.vps.ovh.ca systemd[1]: Starting The Apache HTTP Server.
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using myserverdomain.com. Set the ‘ServerName’ directive globally to suppress this message
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: no listening sockets available, shutting down
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00015: Unable to open logs
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 05 07:36:33 vps105566.vps.ovh.ca kill[7234]: kill: cannot find process «»
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Failed to start The Apache HTTP Server.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Unit httpd.service entered failed state.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service failed.
—————————-

The no listening sockets available, shutting down
httpd port 8080 and 8443 are not used by any other services.

It could be the AH00015: Unable to open logs.

Источник

Vesta Control Panel — Forum

Nginx fails to restart after enabling SSL Support; Site goes down

Nginx fails to restart after enabling SSL Support; Site goes down

Post by h2p » Sat Dec 17, 2016 3:52 pm

After Enabling SSL Support and entering required keys, and then hitting Save, the settings get saved but the site goes down and nginx fails to restart.

Nginx error log gives the following:

CODE: SELECT ALL
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: still could not bind()
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: still could not bind()

BUT if I reboot the server, Nginx starts up and I can access the site with both ‘http’ and with ‘https’ but I get 500 Internal Server on the page and 502 Bad Gateway in browser console. This error goes away if I disable the SSL support from VestaCP panel and reboot the server.

For your consideration:

nginx version: nginx/1.10.2
vesta — core package Version:0.9.8 (amd64) Release:16

Источник

Не могу перезапустить httpd, сервер лежит.
Centos, панель vestacp.

Сегодня производил yum update пакетов, не помню сразу ли httpd отвалился или эти события никак не связаны.
Nginx тоже не стартует. Доступ к самой панеле есть.

До этого, также сегодня оказались пустыми все базы mysql на сервере….
Хотя в /var/lib/mysql базы лежат с инфой!
Пока так и не понял взлом был какой-то или сбой сервера…
Базы все существуют, но они пустые, 1кб (не в /var/lib/mysql).
Все базы были под разными юзерами. Сервис mysql в строю.

Бегло конфиги такие же как на других серверах под Vestacp, там все работает.

Ошибка при рестарте httpd:

service httpd restart
httpd: apr_sockaddr_info_get() failed for name32
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Stopping httpd: [FAILED]

[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 91.23.210.178:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.210:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.211:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.208:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 168.35.8.209:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 145.202.134.179:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.49:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.48:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.51:8080 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.51:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 158.35.234.50:8443 has no VirtualHosts
[Fri Dec 11 01:17:31 2015] [warn] NameVirtualHost 145.202.135.49:8443 has no VirtualHosts
(99)Cannot assign requested address: make_sock: could not bind to address 158.35.234.48:80
no listening sockets available, shutting down
Unable to open logs
Starting httpd: [FAILED]

nginx error.log

2015/12/11 02:35:07 [emerg] 7147#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)
2015/12/11 02:36:10 [emerg] 7205#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)
2015/12/11 02:48:37 [emerg] 3806#0: bind() to XX.XX.XXX.XXX:80 failed (99: Cannot assign requested address)

логов httpd error свежих нет, последняя строка

[Thu Dec 10 17:50:39 2015] [notice] caught SIGTERM, shutting down

файлы XX.XX.XXX.XXX.conf присутствуют, в них это:

NameVirtualHost XX.XX.XXX.XXX:8080
Listen XX.XX.XXX.XXX:8080
NameVirtualHost XX.XX.XXX.XXX:8443
Listen XX.XX.XXX.XXX:8443

вместо иксов ip.
юзеров в панеле пересоздавать пробовал.

hosts выглядит так (где XX.XX.XXX.XXX первый основной ip):

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   localhost.localdomain localhost
XX.XX.XXX.XXX   ns3008.ip-98-24-201.eu ns3008

Пробовал переставить httpd, все тоже самое осталось.

I’m restarting my apache server by this command «service httpd restart» and getting the following message:

Stopping httpd: [FAILED]
Starting httpd: [ OK ]

Before the problem happened, what I’ve done is simply to replace an old database file with new one. This database file will be used by another php file. When I did the replacement, I didn’t stop httpd.

After failing to restart apache server, I surfed the web to find solution and tried the following methods.

1) Try this «netstat -lnp | grep httpd» and «lsof -i:80» to find if there’s any process binding port 80. The result is none process.

2) Remove locked subsys by this «rm -f /var/lock/subsys/httpd» and restart httpd again, but the result is the same as the above message:

Stopping httpd:                                            [FAILED]
Starting httpd:                                            [  OK  ]

3) It didn’t seem to work even if I reboot the server

How to tackle this problem?

The error_log shows the following message:


[Thu Aug 09 15:10:34 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Aug 09 15:10:34 2012] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Aug 09 15:10:34 2012] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Aug 09 15:10:34 2012] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Aug 09 15:10:34 2012] [info] Init: Initializing (virtual) servers for SSL
[Thu Aug 09 15:10:34 2012] [info] Server: Apache/2.2.3, Interface: mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Thu Aug 09 15:10:34 2012] [notice] Digest: generating secret for digest authentication ...
[Thu Aug 09 15:10:34 2012] [notice] Digest: done
[Thu Aug 09 15:10:34 2012] [debug] util_ldap.c(2052): LDAP merging Shared Cache conf: shm=0x8541df0 rmm=0x8541e20 for VHOST: localhost.localdomain
[Thu Aug 09 15:10:34 2012] [info] APR LDAP: Built with OpenLDAP LDAP SDK
[Thu Aug 09 15:10:34 2012] [info] LDAP: SSL support available
[Thu Aug 09 15:27:26 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Aug 09 15:27:26 2012] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Aug 09 15:27:26 2012] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Aug 09 15:27:26 2012] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Aug 09 15:27:26 2012] [info] Init: Initializing (virtual) servers for SSL
[Thu Aug 09 15:27:26 2012] [info] Server: Apache/2.2.3, Interface: mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Thu Aug 09 15:27:26 2012] [notice] Digest: generating secret for digest authentication ...
[Thu Aug 09 15:27:26 2012] [notice] Digest: done
[Thu Aug 09 15:27:26 2012] [debug] util_ldap.c(2052): LDAP merging Shared Cache conf: shm=0x97f4df0 rmm=0x97f4e20 for VHOST: localhost.localdomain
[Thu Aug 09 15:27:26 2012] [info] APR LDAP: Built with OpenLDAP LDAP SDK
[Thu Aug 09 15:27:26 2012] [info] LDAP: SSL support available ssl_error_log:
[Thu Aug 09 15:10:34 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Aug 09 15:10:34 2012] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Aug 09 15:10:34 2012] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Aug 09 15:10:34 2012] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Aug 09 15:10:34 2012] [info] Init: Initializing (virtual) servers for SSL
[Thu Aug 09 15:10:34 2012] [info] Server: Apache/2.2.3, Interface: mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Thu Aug 09 15:10:34 2012] [notice] Digest: generating secret for digest authentication ...
[Thu Aug 09 15:10:34 2012] [notice] Digest: done
[Thu Aug 09 15:10:34 2012] [debug] util_ldap.c(2052): LDAP merging Shared Cache conf: shm=0x8541df0 rmm=0x8541e20 for VHOST: localhost.localdomain
[Thu Aug 09 15:10:34 2012] [info] APR LDAP: Built with OpenLDAP LDAP SDK
[Thu Aug 09 15:10:34 2012] [info] LDAP: SSL support available
[Thu Aug 09 15:27:26 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Aug 09 15:27:26 2012] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Aug 09 15:27:26 2012] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Aug 09 15:27:26 2012] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Aug 09 15:27:26 2012] [info] Init: Initializing (virtual) servers for SSL
[Thu Aug 09 15:27:26 2012] [info] Server: Apache/2.2.3, Interface: mod_ssl/2.2.3, Library: OpenSSL/0.9.8e-fips-rhel5
[Thu Aug 09 15:27:26 2012] [notice] Digest: generating secret for digest authentication ...
[Thu Aug 09 15:27:26 2012] [notice] Digest: done
[Thu Aug 09 15:27:26 2012] [debug] util_ldap.c(2052): LDAP merging Shared Cache conf: shm=0x97f4df0 rmm=0x97f4e20 for VHOST: localhost.localdomain
[Thu Aug 09 15:27:26 2012] [info] APR LDAP: Built with OpenLDAP LDAP SDK
[Thu Aug 09 15:27:26 2012] [info] LDAP: SSL support available

Thanks for any help!