I'm trying to start the rabbitmq-server using:
me#me:~$ sudo invoke-rc.d rabbitmq-server start
...and when I try to check if it is running I get:
me#me:~$ sudo systemctl status rabbit-mq-server
● rabbit-mq-server.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
What is the missing file or directory?
Alright, well...I feel really dumb.
me#me:~$ sudo systemctl status rabbit-mq-server
Should have been:
me#me:~$ sudo systemctl status rabbitmq-server
Related
I am trying to install Devstack but it stopping in the middle
Currently trying to install openstack, but the long process of individual installation, so am using devstack, however i already install OSM release 5. I just need a vim to put the images. Anyway I am installing openstack using devstack. But it's stopping in the middle . This was the error i am getting,
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
chmod 644 /usr/lib/apache2/modules/mod_proxy_uwsgi.so
+lib/apache:install_apache_uwsgi:102 popd
~/devstack
+lib/apache:install_apache_uwsgi:104 sudo rm -rf /tmp/tmp.EgMQRfNaCS
+lib/apache:install_apache_uwsgi:106 is_ubuntu
+functions-common:is_ubuntu:466 [[ -z deb ]]
+functions-common:is_ubuntu:469 '[' deb = deb ']'
+lib/apache:install_apache_uwsgi:108 sudo a2enmod proxy
Module proxy already enabled
+lib/apache:install_apache_uwsgi:109 sudo a2enmod proxy_uwsgi
Considering dependency proxy for proxy_uwsgi:
Module proxy already enabled
Module proxy_uwsgi already enabled
+lib/apache:install_apache_uwsgi:115 restart_apache_server
+lib/apache:restart_apache_server:231 restart_service apache2
+functions-common:restart_service:2393 '[' -x /bin/systemctl ']'
+functions-common:restart_service:2394 sudo /bin/systemctl restart apache2
Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
+functions-common:restart_service:1 exit_trap
+./stack.sh:exit_trap:521 local r=1
++./stack.sh:exit_trap:522 jobs -p
+./stack.sh:exit_trap:522 jobs=
+./stack.sh:exit_trap:525 [[ -n '' ]]
+./stack.sh:exit_trap:531 '[' -f '' ']'
+./stack.sh:exit_trap:536 kill_spinner
+./stack.sh:kill_spinner:417 '[' '!' -z '' ']'
+./stack.sh:exit_trap:538 [[ 1 -ne 0 ]]
+./stack.sh:exit_trap:539 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:541 type -p generate-subunit
+./stack.sh:exit_trap:542 generate-subunit 1559639730 82 fail
+./stack.sh:exit_trap:544 [[ -z /opt/stack/logs ]]
+./stack.sh:exit_trap:547 /opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs
World dumping... see /opt/stack/logs/worlddump-2019-06-04-091653.txt for details
+./stack.sh:exit_trap:556 exit 1
)
Upon running apache restart, its gives this.
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for deta
So i tried to kill all pids then it's ok for once, after that it comes back up
stack#bozz-feedz:/etc/apache2$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since ti 2019-06-04 12:48:10 EEST; 3min 47s ago
Docs: man:systemd-sysv-generator(8)
Process: 2339 ExecStop=/etc/init.d/apache2 stop (code=exited, status=1/FAILURE)
Process: 2314 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
stack#bozz-feedz:/etc/apache2$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: inactive (dead) since ti 2019-06-04 12:52:15 EEST; 1s ago
Docs: man:systemd-sysv-generator(8)
Process: 10597 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 10555 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
Then after some seconds the error comes back. H
stack#bozz-feedz:/etc/apache2$ sudo service apache2 restart
Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
stack#bozz-feedz:/etc/apache2$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since ti 2019-06-04 12:53:29 EEST; 10s ago
Docs: man:systemd-sysv-generator(8)
Process: 13707 ExecStop=/etc/init.d/apache2 stop (code=exited, status=1/FAILURE)
Process: 13680 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
stack#bozz-feedz:/etc/apache2$
$)
Except i kill the pids again. I don't understand why this is happening.
I expect the devstack to install completely. It's just tiring
Try to reinstall apache2.
It worked for me.
sudo apt-get reinstall apache2
I Installed Redis Server on ubuntu 16.04. but when I try to start the redis service using
$ sudo systemctl start redis
I receive message:
Failed to start redis.service: Unit redis-server.service is masked.
I don't have any idea about this error.
I found the solution. I think it will help for others
| systemctl unmask servicename
$ sudo systemctl unmask redis-server.service
if redis.service file is missed in directory path /etc/systemd/system/redis.service so we have to create file into this directory using command like:
sudo nano /etc/systemd/system/redis.service and write following things
[Unit]
Description=Redis In-Memory Data Store
After=network.target
[Service]
User=redis
Group=redis
ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf
ExecStop=/usr/local/bin/redis-cli shutdown
Restart=always
[Install]
WantedBy=multi-user.target
Here
Unit is description and defining the network behavior,
Service is to specify the service's behavior and
Install define the systemd target that the service should attach to if enabled.
Then create redis user group and directories using
sudo adduser --system --group --no-create-home redis
sudo mkdir /var/lib/redis (Create directory)
sudo chown redis:redis /var/lib/redis (Change owner permission)
sudo chmod 770 /var/lib/redis
run the service sudo systemctl start redis
It will be work fine and check the status using
sudo systemctl status redis
1.sudo systemctl unmask redis-server.service
if redis.service file is missed in directory path
/etc/systemd/system/redis.service ,so we have to create file into this directory using command like:
sudo nano /etc/systemd/system/redis.service and write following things
[Unit]
Description=Redis In-Memory Data Store
After=network.target
[Service]
User=redis
Group=redis
ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf
ExecStop=/usr/local/bin/redis-cli shutdown
Restart=always
[Install]
WantedBy=multi-user.target
Then create redis user group and directories using
sudo adduser --system --group --no-create-home redis
sudo mkdir /var/lib/redis (Create directory)
sudo chown redis:redis /var/lib/redis (Change owner permission)
sudo chmod 770 /var/lib/redis
run the service sudo systemctl start redis It will be work fine and check the status using
sudo systemctl status redis
For Ubuntu users run
sudo systemctl restart redis-server
you must run code
sudo systemctl daemon-reload
VPS, Debian
After purging and reinstalling Apache2 through apt-get install apache2, it does not start. After starting service apache2 start, it does not give any message. systemctl status apache2 gives the following:
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2)
Drop-In: /lib/systemd/system/apache2.service.d
└─forking.conf
Active: inactive (dead) since Su 2016-10-16 23:24:07 KRAT; 14min ago
Process: 1953 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 1947 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
there is nothing hanging on port 80. simple http-servers (by Python eg) work ok.
there is nothing in log - all files are empty.
How to make apache work?
I've found the answer. thanx for your attention. For that here is what i did for solving this.
What I have done
I've found that I do not have /usr/sbin/apache2 AT ALL. Have no idea, how it's happend. sudo apachectl configtest told me about it.
Took /usr/sbin/apache2 from backup. surely I could reinstall it from apt-get.
After that, doing sudo apachectl configtest, I've found a message like that:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf:
Syntax error on line 2 of /etc/apache2/mods-enabled/access_compat.load:
Cannot load /usr/lib/apache2/modules/mod_access_compat.so into server:
/usr/lib/apache2/modules/mod_access_compat.so: cannot open shared object file: No such file or directory
Action 'configtest' failed.
it was cured by sudo apt-get --reinstall install apache2-bin
that's all. thank you
Solved:
$ sudo apt-get update
$ sudo apt-get install apache2
Source: https://www.digitalocean.com/community/tutorials/how-to-install-the-apache-web-server-on-ubuntu-16-04
Last time I try add new domain on localhost and I leave it on few weeks so now I try run my apache this command /etc/init.d/apache2 start and I get error
[....] Starting apache2 (via systemctl): apache2.serviceJob for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xe" for details.
failed!
If i tried to do reinstall apache2 but it is still not work.
I just did these two lines.It worked.
Two web servers cannot be active on the one port at the same time
this code for apache & nginx:
or
if error journalctl -xe used this code
sudo apt-get install psmisc
sudo lsof -t -i tcp:80 -s tcp:listen | sudo xargs kill
Virtual Host configuration might cause this error
I solved this same problem by configuring my virtual host .conf files properly.
I created a virtual host & then removed the exapmle.conf file form /etc/apache2/sites-avalable/ but I didn't deleted the examle.conf file from /etc/apache2/sites-enabled/ for this reason i was getting this error.
Then I removed the example.conf file from both the folders( ../sites-enabled & ../sites-available ) and solved this issue.
If you tried to setup any virtual host recently, then try this solution.
Best of Luck
Kill the running process on the port. Hope it will work!
sudo apt-get install psmisc
sudo fuser 80/tcp
sudo lsof -i tcp:80
sudo lsof -i tcp:80 -s tcp:listen
sudo lsof -t -i tcp:80 -s tcp:listen | sudo xargs kill
Go
sudo nano /etc/apache2/apache2.conf
remove this line:
Include /etc/phpmyadmin/apache.conf
Then
service apache2 start/restart
This problem may be a result of some configuration files in apache missing. One of the solutions would be to purge the apache2 file.
You can type:
sudo apt-get purge apache2
Then reinstall apache2 by typing:
sudo apt-get install apache2
As stated in the error message, we just have to execute :
systemctl status apache2.service
or
journalctl -xe
And you will have more detail about the error (line of the error, or command misspelled, or module not included in the configuration, ...) :
for example you can have following detail Invalid command 'SSLEngine', perhaps misspelled or defined by a module not included in the server configuration ==> you then need to execute a2enmod ssl, and then execute service apache2 restart
Also I notice a difference between service apache2 reload and service apache2 restart commands. In case of persisting errors you should execute service apache2 restart, and then execute journalctl -xe.
You type
sudo netstat -pant
You check are you using port 80. If used, `
sudo service 'service_name' stop
and
sudo service apache2 start
The problem is because some configuration files are deleted.
You can use the following command to replace configuration files that have been deleted, without purging the package:
sudo apt-get -o DPkg::Options::="--force-confmiss" --reinstall install apache2
execute sudo service apache2 status and check the result. it might be trying to bind to a port that is already in use
While i try to install server through yum install httpd and later when i start service it shows up following error :
[root#localhost ~]# systemctl enable httpd.service
ln -s '/usr/lib/systemd/system/httpd.service' '/etc/systemd/system/multi-user.target.wants/httpd.service'
[root#localhost ~]# systemctl start httpd.service
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
[root#localhost ~]#
Can any body please help on it??