When I check status of libvirtd using the cmd: sudo systemctl status libvirtd the o/p is as follows:
● libvirtd.service - Virtualization daemon
Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2021-07-22 18:00:59 EDT; 1min 4s ago
TriggeredBy: ● libvirtd-admin.socket
● libvirtd.socket
● libvirtd-ro.socket
Docs: man:libvirtd(8)
https://libvirt.org
Process: 1717 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=0/SUCCESS)
Main PID: 1717 (code=exited, status=0/SUCCESS)
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: Starting Virtualization daemon...
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: Started Virtualization daemon.
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: libvirt version: 6.0.0, package: 0ubuntu8.11 (Christian Ehrhardt <christian.ehrhardt#canonical.com> Tue, 05 Jan 2021 13:48:48 +0100)
Jul 22 18:00:59 libvirtd[1717]: hostname: eb2-2259-lin04
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: invalid argument: Failed to parse user 'libvirt-qemu'
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: Initialization of QEMU state driver failed: invalid argument: Failed to parse user 'libvirt-qemu'
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: Driver state initialization failed
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: libvirtd.service: Succeeded.
The status is always inactive(dead). And I get lines invalid argument: Failed to parse user 'libvirt-qemu' , Initialization of QEMU state driver failed: invalid argument: Failed to parse user 'libvirt-qemu' and Driver state initialization failed
I also tried sudo systemctl start libvirtd
and sudo systemctl status libvirtd but the issue doesn't get resolved.
I was actually installing KVM2 driver for GPU support within minikube following the link [https://help.ubuntu.com/community/KVM/Installation][1]. According to the link KVM2 is successfully installed in Ubuntu if virsh list --all cmd does not return an error. For me all the steps returned no error except for the virsh list --all returned the following error.
error: failed to connect to the hypervisor
error: Cannot recv data: Connection reset by peer
and sometimes returns the following error
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
When I start minikube with kvm2 as the driver using the command minikube start --driver kvm2I get the following error
😄 minikube v1.15.1 on Ubuntu 20.04
💢 Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "virtualbox" driver, which is incompatible with requested "kvm2" driver.
💡 Suggestion: Delete the existing 'minikube' cluster using: 'minikube delete', or start the existing 'minikube' cluster using: 'minikube start --driver=virtualbox'
Please suggest me how to start minikube with kvm2 as driver.
Related
I upgraded my Apache on CentOS 7 from source code build, following instruction: https://httpd.apache.org/docs/2.4/install.html#upgrading
After upgrade, when I run
/etc/httpd/bin/apachectl -k start
It works fine.
But when I run
systemctl start httpd.service
It failed. Here is the error log:
-- Unit httpd.service has begun starting up.
Aug 12 10:19:03 httpd[10289]: httpd: Syntax error on line 57 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/conf.modules.d/00-base.conf: Cannot load modules/mod_access_compat.so into server: /etc/httpd/modules/mod_access_compat.so: undefined symbol: ap_get_useragent_host
Aug 12 10:19:03 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Aug 12 10:19:03 systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Aug 12 10:19:03 systemd[1]: Unit httpd.service entered failed state.
Aug 12 10:19:03 polkitd[19802]: Unregistered Authentication Agent for unix-process:10283:3601117961 (system bus name :1.142076, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 12 10:19:03 systemd[1]: httpd.service failed.
And when I check "httpd -v", it still shows the old version: "Apache/2.4.6 (CentOS)".
Maybe httpd.service is not pointing to the upgraded one, or some files permission not right. Anyone knows how to solve this?
Many thanks!
I uninstalled apache, php, mysql, proftpd, wordpress, cerbot and letsencrypt to get a new, fresh install of apache.
After uninstalling all packages and reinstalling apache, i got this error:
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apache2, action "restart" failed.
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-08-28 15:46:46 CEST; 23ms ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 10693 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Aug 28 15:46:46 raspberrypi systemd[1]: Starting The Apache HTTP Server...
Aug 28 15:46:46 raspberrypi apachectl[10693]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf: Could not open configuration file /etc/letsencrypt/options-ssl-apache.conf: No such file or directory
Aug 28 15:46:46 raspberrypi apachectl[10693]: Action 'start' failed.
Aug 28 15:46:46 raspberrypi apachectl[10693]: The Apache error log may have more information.
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.
Aug 28 15:46:46 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u8+rpi1) ...
I tried to remove all apache-related packages by
sudo apt-get remove apache2
sudo apt autoremove
but this didn't work either.
You have an typing error on line 225 of file /etc/apache2/apache2.conf
I flashed a new image onto the Pi because I couldn't make it run.
I have a problem with apache2 start.
When I try apache start i have the message:
root#ocsi:/var/log/apache2# **systemctl start apache2.service**
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
in systemctl status apache2.service
root#ocsi:/var/log/apache2# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-06-01 07:53:07 CEST; 19s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 3142 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Jun 01 07:53:07 ocsi systemd[1]: Starting The Apache HTTP Server...
Jun 01 07:53:07 ocsi apachectl[3142]: Action 'start' failed.
Jun 01 07:53:07 ocsi apachectl[3142]: The Apache error log may have more information.
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Failed with result 'exit-code'.
Jun 01 07:53:07 ocsi systemd[1]: Failed to start The Apache HTTP Server.
in journalctl -xe
root#ocsi:/var/log/apache2# journalctl -xe
Jun 01 07:54:31 ocsi multipathd[700]: sda: add missing path
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get udev uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sysfs uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sgio uid: No such file or directory
and in apache2 log is:
root#ocsi:/var/log/apache2# vi error.log
[Mon Jun 01 07:53:07.305344 2020] [perl:error] [pid 3149] Can't locate SOAP/Transport/HTTP.pm in #INC (you may need to install the SOAP::Transport::HTTP module) (#INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /etc/apache2) at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nBEGIN failed--compilation aborted at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nCompilation failed in require at (eval 16) line 1.\n
[Mon Jun 01 07:53:07.305621 2020] [perl:error] [pid 3149] Can't load Perl module Apache::Ocsinventory::Plugins::Apache for server localhost:0, exiting...
My system:
PHP Version : 7.4.3
Server version: Apache/2.4.41 (Ubuntu)
Description: Ubuntu 20.04 LTS
Ubuntu Linux 5.4.0-33-generic x86_64
How can I fix this error?
Looks like you need to install the SOAP::Lite module. That can be done by running:
$ sudo apt-get install libsoap-lite-perl
For more details, read on.
The error message is telling you that the Perl compiler can't find the module SOAP::Transport::HTTP (which is presumably used in some code used in your Apache start-up).
This module has never been part of a standard Perl distribution (you can test that by running corelist SOAP::Transport::HTTP). It, therefore, needs to be installed separately.
Perl modules are usually installed from CPAN. If you search for the module there, you'll see it's part of the SOAP-Lite distribution. Now you could install it directly from there using cpan but, given in this case, the easier approach is probably to install the pre-built package for your operating system. And that's done by running the command above.
I installed Nginx in Ubuntu and which was not working as expected so I removed and trying to install it again but it is not installing and throwing some exceptions:
The command I used: sudo apt install nginx
root#INDSRV09:~# sudo apt install nginx
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libgd3 libvpx3 nginx-common nginx-core
Suggested packages:
libgd-tools fcgiwrap nginx-doc
The following NEW packages will be installed:
libgd3 libvpx3 nginx nginx-common nginx-core
0 upgraded, 5 newly installed, 0 to remove and 138 not upgraded.
Need to get 0 B/1,316 kB of archives.
After this operation, 4,247 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Preconfiguring packages ...
Selecting previously unselected package libvpx3:amd64.
(Reading database ... 78639 files and directories currently installed.)
Preparing to unpack .../libvpx3_1.5.0-2ubuntu1_amd64.deb ...
Unpacking libvpx3:amd64 (1.5.0-2ubuntu1) ...
Selecting previously unselected package libgd3:amd64.
Preparing to unpack .../libgd3_2.1.1-4ubuntu0.16.04.10_amd64.deb ...
Unpacking libgd3:amd64 (2.1.1-4ubuntu0.16.04.10) ...
Selecting previously unselected package nginx-common.
Preparing to unpack .../nginx-common_1.10.3-0ubuntu0.16.04.3_all.deb ...
Unpacking nginx-common (1.10.3-0ubuntu0.16.04.3) ...
Selecting previously unselected package nginx-core.
Preparing to unpack .../nginx-core_1.10.3-0ubuntu0.16.04.3_amd64.deb ...
Unpacking nginx-core (1.10.3-0ubuntu0.16.04.3) ...
Selecting previously unselected package nginx.
Preparing to unpack .../nginx_1.10.3-0ubuntu0.16.04.3_all.deb ...
Unpacking nginx (1.10.3-0ubuntu0.16.04.3) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for ufw (0.35-0ubuntu2) ...
Setting up libvpx3:amd64 (1.5.0-2ubuntu1) ...
Setting up libgd3:amd64 (2.1.1-4ubuntu0.16.04.10) ...
Setting up nginx-common (1.10.3-0ubuntu0.16.04.3) ...
Setting up nginx-core (1.10.3-0ubuntu0.16.04.3) ...
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-27 09:42:27 CST; 14ms ago
Process: 9655 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Process: 9649 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Feb 27 09:42:25 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:25 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:26 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:26 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:27 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:27 INDSRV09 nginx[9655]: nginx: [emerg] still could not bind()
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Control process exited, code=exited status=1
Feb 27 09:42:27 INDSRV09 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Unit entered failed state.
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Failed with result 'exit-code'.
dpkg: error processing package nginx-core (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of nginx:
nginx depends on nginx-core (>= 1.10.3-0ubuntu0.16.04.3) | nginx-full (>= 1.10.3-0ubuntu0.16.04.3) | nginx-light (>= 1.10.3-0ubuntu0.16.04.3) | nginx-extras (>= 1.10.3-0ubuntu0.16.04.3); however:
Package nginx-core is not configured yet.
Package nginx-full is not installed.
Package nginx-light is not installed.
Package nginx-extras is not installed.
nginx depends on nginx-core (<< 1.10.3-0ubuntu0.16.04.3.1~) | nginx-full (<< 1.10.3-0ubuntu0.16.04.3.1~) | nginx-light (<< 1.10.3-0ubuntu0.16.04.3.1~) | nginx-extras (<< 1.10.3-0ubuntu0.16.04.3.1~); however:
Package nginx-core is not configured yet.
Package nginx-full is not installed.
Package nginx-light is not installed.
Package nginx-extras is not installed.
dpkg: error processing package nginx (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for ufw (0.35-0ubuntu2) ...
Errors were encountered while processing:
nginx-core
nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)
And I installed Apache and I stopped it later.
And another confusion is even I uninstalled and removed folders manually, I can see the Nginx on UI when I am trying to access :
I am struggling with this issue from last 4 days .
Can some body help me .
Thanks in Advance .
Hi,
Thanks for the response :
root#INDSRV09:~# service nginx status
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-27 09:42:27 CST; 18h ago
Feb 27 09:42:25 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:25 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:26 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:26 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:27 INDSRV09 nginx[9655]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Feb 27 09:42:27 INDSRV09 nginx[9655]: nginx: [emerg] still could not bind()
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Control process exited, code=exited status=1
Feb 27 09:42:27 INDSRV09 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Unit entered failed state.
Feb 27 09:42:27 INDSRV09 systemd[1]: nginx.service: Failed with result 'exit-code'.
Running sudo service rabbitmq-server start results in the following output:
Job for rabbitmq-server.service failed because the control process exited with error code.
See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
systemctl status output for rabbitmq-server.service is as follows:
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2019-01-30 13:45:25 +08; 4s ago
Process: 32710 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl shutdown (code=exited, status=69)
Process: 6836 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=64)
Main PID: 6836 (code=exited, status=64)
Jan 30 13:45:25 ip-172-31-1-92 systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=64/n/a
Jan 30 13:45:25 ip-172-31-1-92 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
Jan 30 13:45:25 ip-172-31-1-92 systemd[1]: Failed to start RabbitMQ broker.
Turns out the problem was I had set the environment variable RABBITMQ_CONFIG_FILE to /etc/rabbitmq/rabbitmq.config but created that file as rabbitmq.conf. The server crashed as a result trying to look for a file that didn't exist.