So i'm trying to deploy a rails 4.2.5 app, and at the last step of it, while apache2 needs to be reloaded, it fails, and I don't have many informations about this.
I browsed the web, but there isn't many answers about this, so i don't know what to do...
Active: active (exited) (Result: exit-code) since dim. 2016-01-31 03:01:31 CET; 9min ago
Process: 10766 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 10993 ExecReload=/etc/init.d/apache2 reload (code=exited, status=1/FAILURE)
Process: 10773 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
janv. 31 03:08:47 vps240378.ovh.net systemd[1]: apache2.service: control process exited, code=exited status=1
janv. 31 03:08:47 vps240378.ovh.net systemd[1]: Reload failed for LSB: Apache2 web server.
janv. 31 03:10:52 vps240378.ovh.net apache2[10945]: Reloading web server: apache2 failed!
janv. 31 03:10:52 vps240378.ovh.net apache2[10945]: Apache2 is not running ... (warning).
janv. 31 03:10:52 vps240378.ovh.net systemd[1]: apache2.service: control process exited, code=exited status=1
janv. 31 03:10:52 vps240378.ovh.net systemd[1]: Reload failed for LSB: Apache2 web server.
janv. 31 03:11:23 vps240378.ovh.net apache2[10993]: Reloading web server: apache2 failed!
janv. 31 03:11:23 vps240378.ovh.net apache2[10993]: Apache2 is not running ... (warning).
janv. 31 03:11:23 vps240378.ovh.net systemd[1]: apache2.service: control process exited, code=exited status=1
janv. 31 03:11:23 vps240378.ovh.net systemd[1]: Reload failed for LSB: Apache2 web server.
Does anybody know how to deal with it ?
Thanks
Looking at your top three lines you look like you are stopping apache, trying to reload, which falls - because it's stopped. And them starting it again. Is that the issue? If so don't stop apache, just reload. Reload is there so you don't have to restart.
Apologies if this is not the issue just my first take.
Reload provides instructions to children to complete their current request and stop, while new requests are served by your new configuration. If apache is stopped, there's nothing to do.
Related
I was trying to install jenkins in ec2 ubuntu and amazon-linux but I am getting this error
jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-11-27 16:29:54 UTC; 1h 8min ago
Process: 18706 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE)
Main PID: 18706 (code=exited, status=1/FAILURE)
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: jenkins.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: jenkins.service: Failed with result 'exit-code'.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: Failed to start Jenkins Continuous Integration Server.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: jenkins.service: Scheduled restart job, restart counter is at 5.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: Stopped Jenkins Continuous Integration Server.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: jenkins.service: Start request repeated too quickly.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: jenkins.service: Failed with result 'exit-code'.
Nov 27 16:29:54 ip-172-31-19-156 systemd[1]: Failed to start Jenkins Continuous Integration Server.
root#ip-172-31-19-156:~# cd /car/usr
First I installed jenkins and was interrupted in between that I changed the ec2 volume for reset my ec2, after this I'm unable to install jenkins in ec2
After installing Java and Jenkins on my CentOS 7 server. I tried to start the Jenkins, and I am getting the below error message.
Job for jenkins.service failed. See "systemctl status jenkins.service"
and "journalctl -xe" for details.
When I run "systemctl status jenkins.service" to see what the issue is, I get the below output
● jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2022-08-18 14:23:02 UTC; 20s ago
Process: 8847 ExecStart=/usr/bin/jenkins (code=exited, status=0/SUCCESS)
Main PID: 8847 (code=exited, status=0/SUCCESS)
Aug 18 14:23:02 localhost.localdomain systemd[1]: Failed to start Jenkins Continuous Integration Server.
Aug 18 14:23:02 localhost.localdomain systemd[1]: Unit jenkins.service entered failed state.
Aug 18 14:23:02 localhost.localdomain systemd[1]: jenkins.service failed.
Aug 18 14:23:02 localhost.localdomain systemd[1]: jenkins.service holdoff time over, scheduling restart.
Aug 18 14:23:02 localhost.localdomain systemd[1]: Stopped Jenkins Continuous Integration Server.
Aug 18 14:23:02 localhost.localdomain systemd[1]: start request repeated too quickly for jenkins.service
Aug 18 14:23:02 localhost.localdomain systemd[1]: Failed to start Jenkins Continuous Integration Server.
Aug 18 14:23:02 localhost.localdomain systemd[1]: Unit jenkins.service entered failed state.
Aug 18 14:23:02 localhost.localdomain systemd[1]: jenkins.service failed.
Not quite sure how to fix this. Anybody with a solution? Thanks
can you please use journalctl -xe for more detailed logs.
also can you run Jenkins in interactive mode to see why its failing to start like -
java -jar jenkins.war
you can get command details in /usr/bin/jenkins file.
I have installed docker on Antergos (Arch Linux) and followed this guide: https://gist.github.com/simonhoye/3b7312c05a449cd9073f9dc9265f5213
But when I execute sudo sysytemctl start docker I get this error:
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
And this is the systemctl status docker.service command:
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor pres>
Active: failed (Result: exit-code) since Thu 2019-01-17 16:28:01 CET; 5s ago
Docs: https://docs.docker.com
Process: 17013 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAI>
Main PID: 17013 (code=exited, status=1/FAILURE)
ene 17 16:28:01 t480 systemd[1]: docker.service: Service RestartSec=100ms expir>
ene 17 16:28:01 t480 systemd[1]: docker.service: Scheduled restart job, restart>
ene 17 16:28:01 t480 systemd[1]: Stopped Docker Application Container Engine.
ene 17 16:28:01 t480 systemd[1]: docker.service: Start request repeated too qui>
ene 17 16:28:01 t480 systemd[1]: docker.service: Failed with result 'exit-code'.
ene 17 16:28:01 t480 systemd[1]: Failed to start Docker Application Container E>`
I have not idea what is happening... Because the guide and the steps to follow are very simple.
it can be due to many reason so I am listing some common one's
look inside /var/log/syslog for more info.
If you remove /var/lib/docker, you'll lose existing images but it works for many people
Doing so simply wipes all your docker data, and is the equivalent to a "factory reset".
it can also be due to missing kernel module aufs
deleting the /var/run/docker.sock directory that had been created presumably as the docker service was shutting down
I am trying to setup awslogs for docker.
The docs say to add this to daemon.json:
{
"log-driver": "awslogs",
"log-opts": {
"awslogs-region": "eu-central-1"
}
}
When I create on Ubuntu /etc/docker/daemon.json with the content above docker wont start again.
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Fr 2018-07-20 10:59:53 CEST; 11s ago
Docs: https://docs.docker.com
Process: 647 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
Main PID: 647 (code=exited, status=1/FAILURE)
Jul 20 10:59:53 dev01-ubuntu systemd[1]: Failed to start Docker Application Container Engine.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: docker.service: Unit entered failed state.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: Stopped Docker Application Container Engine.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: docker.service: Start request repeated too quickly.
Jul 20 10:59:53 dev01-ubuntu systemd[1]: Failed to start Docker Application Container Engine.
Can anybody explain this behaviour?
Not ever use it.
But from this: https://docs.docker.com/config/containers/logging/plugins/, it seems we need to install plugin for any new log driver, check it with docker plugin ls
Maybe it just available in amazon cloud environment, not available in local pc, just in case you did not notice that.
I am running Rstudio-server inside a centos container. But I am not able to get the logs from the running container. I have already tried RStudio Server - Application Logs as well as on stackoverflow answer, but they were not any help to me. I have tried various versions of Rstudio-servers.
In my CentOS 7 Docker container, and with my RStudio Server version 1.0.136, I've managed to access to the logs using:
journalctl -u rstudio-server
Some more logs can be found using
journalctl -f
In a more general point of view, there are many logs in the following folder: /var/log/anaconda
According to RStudio Server support, another solution would be to launch rstudio-server with --server-daemonize=0 in order for the output to be directly available on standard output & error.
i performed on my machine and i got all the logs
[root#ccanalytics-dev-dev01 rksharma]# journalctl -u rstudio-server
-- Logs begin at Wed 2017-05-17 15:43:44 EDT, end at Fri 2018-01-12 03:49:17 EST. --
May 18 08:14:00 ccanalytics-dev-dev01.netlink.com systemd[1]: Starting RStudio Server...
May 18 08:14:00 ccanalytics-dev-dev01.netlink.com systemd[1]: Started RStudio Server.
May 18 08:16:02 ccanalytics-dev-dev01.netlink.com rserver[40106]: ERROR system error 13 (Permission denied) [user-value=admin]; OCCURRED AT:
May 18 08:16:02 ccanalytics-dev-dev01.netlink.com rserver-pam[40159]: ERROR pam_authenticate failed: User not known to the underlying authent
May 18 08:44:16 ccanalytics-dev-dev01.netlink.com rserver[40106]: ERROR system error 13 (Permission denied) [user-value=rishabs]; OCCURRED AT
May 18 08:44:16 ccanalytics-dev-dev01.netlink.com rserver-pam[40193]: ERROR pam_authenticate failed: User not known to the underlying authent
May 23 05:17:06 ccanalytics-dev-dev01.netlink.com killall[20898]: rserver: no process found
May 23 05:17:06 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: control process exited, code=exited status=1
May 23 05:17:06 ccanalytics-dev-dev01.netlink.com systemd[1]: Unit rstudio-server.service entered failed state.
May 23 05:17:06 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service failed.
May 23 05:17:07 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service holdoff time over, scheduling restart.
May 23 05:17:07 ccanalytics-dev-dev01.netlink.com systemd[1]: Starting RStudio Server...
May 23 05:17:07 ccanalytics-dev-dev01.netlink.com systemd[1]: Started RStudio Server.
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: main process exited, code=killed, status=9/KILL
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com killall[20956]: rserver: no process found
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: control process exited, code=exited status=1
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: Unit rstudio-server.service entered failed state.
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service failed.
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service holdoff time over, scheduling restart.
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: Starting RStudio Server...
May 23 05:19:00 ccanalytics-dev-dev01.netlink.com systemd[1]: Started RStudio Server.
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com killall[20993]: rserver: no process found
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: control process exited, code=exited status=1
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: Unit rstudio-server.service entered failed state.
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service failed.
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service holdoff time over, scheduling restart.
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: Starting RStudio Server...
May 23 05:22:25 ccanalytics-dev-dev01.netlink.com systemd[1]: Started RStudio Server.
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: main process exited, code=killed, status=9/KILL
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com killall[21022]: rserver: no process found
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service: control process exited, code=exited status=1
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: Unit rstudio-server.service entered failed state.
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service failed.
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: rstudio-server.service holdoff time over, scheduling restart.
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: Starting RStudio Server...
May 23 05:22:51 ccanalytics-dev-dev01.netlink.com systemd[1]: Started RStudio Server.
May 23 05:23:10 ccanalytics-dev-dev01.netlink.com rsession-rksharma[21050]: ERROR session hadabend; LOGGED FROM: rstudio::core::Error