Vestacp 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

Источник

Operating System (OS/VERSION):

Ubuntu 16.04.5 LTS

VestaCP Version:

0.9.8-23

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:

In /var/log/apache2/error.log

[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: </VirtualHost> without matching <VirtualHost> 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:

<VirtualHost [IP_Server]:8443>

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

My main reason releasing this blog was to help people who want to use VPS while saving some bucks by avoiding cPanel usage so I posted many tutorials to install either LAMP or LNMP on VPS with no control panel at all. But then I started to rethink of that and decided to also write tutorials about installing and using free control panel on a VPS as an alternative to cPanel.

For that, I posted about how to install zPanel and ServerPilot. But then few weeks ago I found Vesta CP, a Russian-made free hosting control panel with a bunch of awesomeness. Lets say with zPanel you’ll get necessary software set up including Apache, PHP5, MYSQL, PHPMyAdmin, FTP, Mail server and DNS. Vesta CP comes with whole new awesomeness, it has almost all zPanel features plus Nginx and Varnish Cache out of the box.

About Vesta Control Panel

Vesta is an open source hosting control panel currently supports both RHEL flavoured Linux releases (Red Hat, CentOS) and Ubuntu LTS 12.04 and Ubuntu 13.04. It comes with all necessary software to run and manage your websites hosted on your VPS, including:

– Web Server (Apache with Nginx as Reverse Proxy)
– DNS server
– Database Server
– Mail Server
– FTP Server
– Nginx out of the box
– SSL certificates & SNI
– Wildcard support
– Configuration Templates
– DKIM support
– Fast Backups
– System Monitoring
– AntiSpam / Antivirus
– WHMCS billing support
– EPEL integration
– Simple and Clean GUI
– Powerfull CLI
– Reliable Platform
– Open Data Format

How to Install Vesta CP

Vesta CP works on RedHat, CentOS and Ubuntu but in today’s guide I will show you how to get it installed on CentOS 6.5. Here’s my inventory:

A VPS on DigitalOcean, I created a New York droplet with 512MB of RAM, 20GB SSD, 1TB Bandwidth and I select CentOS 6.5 64-bit.

What I like from DigitalOcean is its painless process of creating a VPS. I’ve told you that before.

So now the VPS is ready, lets start installing VestaCP.

Step 1 – First, login to your server’s shell via SSH as root, as always, for this task I use putty.

Step 2 – Next, download VestaCP installation script using curl command:

curl -O http://vestacp.com/pub/vst-install.sh

Step 3 – Next, issue this magic command to start installing VestaCP:

bash vst-install.sh

pic:

Step 4 – The installer asks to confirm disabling SELinux and start the install process. Type Y and hit Enter.

Step 5 – The installer also asks to enter valid email address. So type your valid email address and double-check it to make sure your email is correct because VestaCP will also send your admin password there.

Step 6 – Once you hit Enter on your keyboard, the installer starts. Sit tight and wait for the installer to process and finish its job.

Step 7 – As long as you found no fatal error, the installer should finish quicker and you will see something like this on your screen:

You can also check your mailbox just to ensure the password is delivered and mail server (Exim) works properly on your server.

Step 8 – Now open up your favorite browser and login to VestaCP web-based UI using your VPS IP at port 8083.

https://xxx.xxx.xxx.xxx:2083/

Login as admin and use given password,

As you may also aware that the link is https:// which means via secure connection (SSL) so you may have to add / confirm exception on your browser.

Voila! You should now see the main UI of Vesta hosting control panel.

*click on image to view larger size.

Congratulation! You now have Vesta CP installed and a ready-to-use VPS to host all your websites.

What’s next?

I can say that’s it for now. Upcoming: Basic Vesta CP Setup, How to add your first domain / website on VestaCP, using Nginx and Varnish Cache on VestaCP, setting up EXIM4 to use TLS, etc. I can’t promise you when will I write next article but stay tuned.

Part 2: Basic Vesta CP Setup

Part 3: How to Add New Website on Vesta CP.

About The Author