can anyone help here I have a fresh Centos 7 installation I was trying to install the qemu-guest-agent after installation I'm trying to start it, but getting the bellow error :
[root#localhost ~]# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.
and here is journalctl -xe :
--
-- Unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed.
--
-- The result is timeout.
May 03 14:06:57 localhost.localdomain systemd[1]: Dependency failed for QEMU Guest Agent.
-- Subject: Unit qemu-guest-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit qemu-guest-agent.service has failed.
--
-- The result is dependency.
May 03 14:06:57 localhost.localdomain systemd[1]: Job qemu-guest-agent.service/start failed with result 'dependency'.
May 03 14:06:57 localhost.localdomain systemd[1]: Startup finished in 1.474s (kernel) + 4.095s (initrd) + 2min 5.416s (userspace) = 2min 10.985s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required 1474322 microseconds.
--
-- Initial RAM disk start-up required 4095564 microseconds.
--
-- Userspace start-up required 125416032 microseconds.
May 03 14:06:57 localhost.localdomain systemd[1]: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'.
May 03 14:06:57 localhost.localdomain polkitd[624]: Unregistered Authentication Agent for unix-process:7214:4088 (system bus name :1.22, object path /org/freedesktop/PolicyKit1/Authenticatio
May 03 14:07:59 localhost.localdomain sudo[8162]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl enable qemu-guest-agent
May 03 14:07:59 localhost.localdomain sudo[8162]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 03 14:07:59 localhost.localdomain polkitd[624]: Registered Authentication Agent for unix-process:8164:19324 (system bus name :1.24 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object
May 03 14:07:59 localhost.localdomain systemd[1]: Reloading.
May 03 14:07:59 localhost.localdomain polkitd[624]: Unregistered Authentication Agent for unix-process:8164:19324 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/Authenticati
May 03 14:07:59 localhost.localdomain sudo[8162]: pam_unix(sudo:session): session closed for user root
May 03 14:08:01 localhost.localdomain polkitd[624]: Registered Authentication Agent for unix-process:8182:19565 (system bus name :1.25 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object
May 03 14:09:31 localhost.localdomain systemd[1]: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out.
May 03 14:09:31 localhost.localdomain systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device.
-- Subject: Unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed.
--
-- The result is timeout.
May 03 14:09:31 localhost.localdomain systemd[1]: Dependency failed for QEMU Guest Agent.
-- Subject: Unit qemu-guest-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit qemu-guest-agent.service has failed.
--
-- The result is dependency.
May 03 14:09:31 localhost.localdomain systemd[1]: Job qemu-guest-agent.service/start failed with result 'dependency'.
May 03 14:09:31 localhost.localdomain polkitd[624]: Unregistered Authentication Agent for unix-process:8182:19565 (system bus name :1.25, object path /org/freedesktop/PolicyKit1/Authenticati
May 03 14:09:31 localhost.localdomain systemd[1]: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'.
Can someone please assist me, Thank you so much.
Related
MySql randomly stopped working. ive tried EVERYTHING to fix it but i havnt been successfull.
heres the output from "service mysql status"
* mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-05-12 09:55:36 MSK; 1min 52s ago
Process: 668983 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)
CPU: 8ms
May 12 09:55:36 myhiddenthostname.com systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
May 12 09:55:36 myhiddenthostname.com systemd[1]: Stopped MySQL Community Server.
May 12 09:55:36 myhiddenthostname.com systemd[1]: mysql.service: Start request repeated too quickly.
May 12 09:55:36 myhiddenthostname.com systemd[1]: mysql.service: Failed with result 'exit-code'.
May 12 09:55:36 myhiddenthostname.com systemd[1]: Failed to start MySQL Community Server.
Heres the output from "journalctl -xe"
-- A start job for unit mysql.service has finished with a failure.
--
-- The job identifier is 16383 and the job result is failed.
May 12 09:59:12 myhiddenhostname.com systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit mysql.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 12 09:59:12 myhiddenhostname.com systemd[1]: Stopped MySQL Community Server.
-- Subject: A stop job for unit mysql.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit mysql.service has finished.
--
-- The job identifier is 16453 and the job result is done.
May 12 09:59:12 myhiddenhostname.com systemd[1]: mysql.service: Start request repeated too quickly.
May 12 09:59:12 myhiddenhostname.com systemd[1]: mysql.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit mysql.service has entered the 'failed' state with result 'exit-code'.
May 12 09:59:12 myhiddenhostname.com systemd[1]: Failed to start MySQL Community Server.
-- Subject: A start job for unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit mysql.service has finished with a failure.
--
-- The job identifier is 16453 and the job result is failed.
Any help or suggestions is needed. would really appreciate a response or suggestion as all my clients are experiencing downtime because of this.
I was trying to install pterodactyl using the following script but mariadb was constantly having problem during loading
https://github.com/vilhelmprytz/pterodactyl-installer
while running journalctl -xe I get the following output
root#ryno-pterodactyl:~# journalctl -xe
-- A start job for unit mariadb.service has begun execution.
-- The job identifier is 1400.
Apr 06 11:54:54 ryno-pterodactyl PackageKit[22129]: daemon quit Apr 06 11:54:54 pterodactyl systemd[1]: packagekit.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- The unit packagekit.service has successfully entered the 'dead' state. Apr 06 12:01:01 ryno-pterodactyl CRON[22315]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 06 12:01:01 ryno-pterodactyl CRON[22316]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 06 12:01:01 ryno-pterodactyl CRON[22315]: pam_unix(cron:session): session closed for user root Apr 06 12:04:50 ryno-pterodactyl systemd[1]: mariadb.service: start operation timed out. Terminating. Apr 06 12:04:52 ryno-pterodactyl systemd[1]: mariadb.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- The unit mariadb.service has entered the 'failed' state with result 'timeout'. Apr 06 12:04:52 ryno-pterodactyl systemd[1]: Failed to start MariaDB 10.3.34 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- A start job for unit mariadb.service has finished with a failure.
-- The job identifier is 1400 and the job result is failed. Apr 06 12:04:52 ryno-pterodactyl systemd[1]: mariadb.service: Consumed 1.363s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- The unit mariadb.service completed and consumed the indicated resources. lines 3832-3866/3866 (END)```
So i have been running k3s on a stack of raspberry pi 4 and 3s for a while but one node always fails. Here is my setup
Servers: Raspberry pi 4-8GB and 2x Raspberry pi 4-4GB
Workers: 3 Raspberry pi 3Bs
My second raspberry pi 4 - 4GB keeps failing. All 6 nodes are connected to GB ethernet and Samsung 500 GB SSDs
I’m running an HA environment with an external sql database connected to my NAS (192.168.1.200) as shown below.
So here are some of the errors I’m getting
When I run Sudo systemctl status k3s I get (changed user/pass for privacy):
k3s.service - Lightweight Kubernetes
Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2021-07-04 01:59:29 BST; 609ms ago
Docs: https://k3s.io
Process: 14637 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
Process: 14639 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 14640 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Process: 14641 ExecStart=/usr/local/bin/k3s server --tls-san 192.168.1.100 --datastore-endpoint mysql://user:pass#tcp(192.168.1.200:3306)/k3s --disable traefik (code=exited, status=1/FAILURE)
Main PID: 14641 (code=exited, status=1/FAILURE)
When I run journalctl -xe I get:
-- Subject: A start job for unit k3s.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit k3s.service has begun execution.
--
-- The job identifier is 325190.
Jul 04 02:13:46 node50 sh[18386]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
Jul 04 02:13:46 node50 sh[18386]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
Jul 04 02:13:47 node50 k3s[18390]: time="2021-07-04T02:13:47.365627432+01:00" level=info msg="Starting k3s v1.19.12+k3s1 (559d0c47)"
Jul 04 02:13:47 node50 k3s[18390]: time="2021-07-04T02:13:47.366403382+01:00" level=info msg="Cluster bootstrap already complete"
Jul 04 02:13:47 node50 k3s[18390]: time="2021-07-04T02:13:47.418216205+01:00" level=fatal msg="starting kubernetes: preparing server: creating storage endpoint: building kine: Error 1129: Host is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'"
Jul 04 02:13:47 node50 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit k3s.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jul 04 02:13:47 node50 systemd[1]: k3s.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit k3s.service has entered the 'failed' state with result 'exit-code'.
Jul 04 02:13:47 node50 systemd[1]: Failed to start Lightweight Kubernetes.
-- Subject: A start job for unit k3s.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit k3s.service has finished with a failure.
As per this error I have logged into MySQL instance and ran mysqladmin flush-hosts and it fixes the issue for a few hours and then happens all over again. So I am a bit at a loss on why this issue is only happening one one Pi. Otherwise the Pi works fine. Can run docker and other programs with no issues.
I’ve also bumped my max connections in my.cnf from 100 to 10000
Anybody have any ideas?
I installed mysql in my server. But it failed to start.
The error shows here:
the systemctl status mysqld.service info:
[root#localhost run]# systemctl status mysqld.service
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sat 2021-05-29 10:47:55 CST; 35s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 256566 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=217/USER)
May 29 10:47:55 localhost.localdomain systemd[1]: Failed to start MySQL Server.
May 29 10:47:55 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
May 29 10:47:55 localhost.localdomain systemd[1]: mysqld.service failed.
May 29 10:47:55 localhost.localdomain systemd[1]: mysqld.service holdoff time over, sche...t.
May 29 10:47:55 localhost.localdomain systemd[1]: Stopped MySQL Server.
May 29 10:47:55 localhost.localdomain systemd[1]: start request repeated too quickly for...ce
May 29 10:47:55 localhost.localdomain systemd[1]: Failed to start MySQL Server.
May 29 10:47:55 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
May 29 10:47:55 localhost.localdomain systemd[1]: mysqld.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
thejournalctl -xeinfo:
May 29 10:48:00 localhost.localdomain postfix/master[21438]: warning: process /usr/libexec/postfix/pickup pid 257074 exit status 127
May 29 10:48:00 localhost.localdomain postfix/master[21438]: warning: /usr/libexec/postfix/pickup: bad command startup -- throttling
May 29 10:49:00 localhost.localdomain postfix/master[21438]: warning: process /usr/libexec/postfix/pickup pid 263057 exit status 127
May 29 10:49:00 localhost.localdomain postfix/master[21438]: warning: /usr/libexec/postfix/pickup: bad command startup -- throttling
May 29 10:50:00 localhost.localdomain postfix/master[21438]: warning: process /usr/libexec/postfix/pickup pid 269083 exit status 127
May 29 10:50:00 localhost.localdomain postfix/master[21438]: warning: /usr/libexec/postfix/pickup: bad command startup -- throttling
May 29 10:50:01 localhost.localdomain systemd[1]: Started Session 2986 of user root.
-- Subject: Unit session-2986.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-2986.scope has finished starting up.
--
-- The start-up result is done.
I tried to run chown -R mysql:mysql /var/lib/mysql, It shows like this:
chown: invalid user: ‘mysql:mysql’
How can I start mysql?
You can fix this in few steps
Execute this command to check if mysql user exists: cat /etc/passwd | grep mysql
Validate if you have mysql in this file. It should look something like : mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/false
If mysql user is not present please create that user like this : useradd -d /var/lib/mysql mysql
If mysql user is present then make sure mysql user home path in /etc/passwd file actually exists and owned by mysql user (in the above case I mentioned /var/lib/mysql is home path and it has to be owned by mysql user)
Note: from what ever you have mentioned it looked like mysql user doesn't exist in your system. So it looks like creating the user with home path as /var/lib/mysql should solve the problem.
I have a problem to start MySQL after an upgrade from Ubuntu 18.04 to 20.04 (MySQL 5.7 to 8). When I tried to start the mysql service kit stops at "Starting MySQL Community Server...".
USER#SERVER:~$ systemctl status mysql.service
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: activating (start) since Wed 2020-08-19 11:38:13 CEST; 576ms ago
Process: 18006 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 18014 (mysqld)
Status: "Server startup in progress"
Tasks: 13 (limit: 1110)
Memory: 261.6M
CGroup: /system.slice/mysql.service
└─18014 /usr/sbin/mysqld
Aug 19 11:38:13 SERVER systemd[1]: Starting MySQL Community Server...
The journal gives me back the following.
USER#SERVER:~$ journalctl -xe
--
-- The job identifier is 24060.
Aug 19 11:38:17 boris-dev systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit mysql.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Aug 19 11:38:17 boris-dev systemd[1]: mysql.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit mysql.service has entered the 'failed' state with result 'exit-code'.
Aug 19 11:38:17 boris-dev systemd[1]: Failed to start MySQL Community Server.
-- Subject: A start job for unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit mysql.service has finished with a failure.
--
-- The job identifier is 24060 and the job result is failed.
Aug 19 11:38:17 boris-dev systemd[1]: mysql.service: Scheduled restart job, restart counter is at 139.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit mysql.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 19 11:38:17 boris-dev systemd[1]: Stopped MySQL Community Server.
-- Subject: A stop job for unit mysql.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit mysql.service has finished.
--
-- The job identifier is 24126 and the job result is done.
Aug 19 11:38:17 boris-dev systemd[1]: Starting MySQL Community Server...
-- Subject: A start job for unit mysql.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit mysql.service has begun execution.
--
-- The job identifier is 24126.
There are a few databases and it would be nice to keep them, but not necessary.
Any idea what's best to do?
Thanks in advance
Bo