Failed to start nova-scheduler.service: Unit not found.

根据提供的引用内容，出现"Failed to start nova-scheduler.service: Unit not found"错误的原因是找不到nova-scheduler服务单元。这可能是由于服务单元未正确安装或配置引起的。

要解决此问题，可以尝试以下步骤：

1. 确保已正确安装nova-scheduler服务单元。可以使用以下命令检查服务单元是否已安装：

   systemctl status nova-scheduler.service

如果服务单元未安装，请使用适当的包管理器（如apt、yum）安装nova-scheduler服务单元。

2. 如果服务单元已安装但仍无法启动，请检查服务单元的配置文件是否正确。可以使用以下命令查看配置文件的位置：

   systemctl show -p FragmentPath nova-scheduler.service

然后，检查配置文件中的参数是否正确设置。

3. 如果配置文件正确，但服务单元仍无法启动，请检查系统日志以获取更多详细信息。可以使用以下命令查看系统日志：

   journalctl -u nova-scheduler.service

查看日志以确定导致服务单元启动失败的具体原因。

请注意，以上步骤仅提供了一般性的解决方案。具体的解决方法可能因系统配置和环境而异。如果问题仍然存在，请提供更多详细信息以便进一步帮助解决。

相关问题

su: user cinder does not exist Failed to execute operation: No such file or directory Failed to restart openstack-cinder-api.service: Unit openstack-cinder-api.service failed to load: No such file or directory. Failed to restart openstack-cinder-scheduler.service: Unit openstack-cinder-scheduler.service failed to load: No such file or directory.如何解决

这些错误提示表明在执行操作时找不到用户cinder和openstack-cinder相关的服务。可能是由于缺少相关的软件包或服务未正确安装所致。您可以尝试以下步骤来解决此问题：

1. 检查您的系统是否已正确安装所有必需的软件包。您可以根据您正在使用的Linux发行版的不同，使用不同的命令来检查和安装软件包。例如，如果您正在使用Ubuntu，您可以使用以下命令安装OpenStack Cinder软件包：

   sudo apt-get update
   sudo apt-get install -y cinder-api cinder-scheduler

2. 如果软件包已正确安装，请检查相关服务的状态。您可以使用以下命令检查服务状态：

   sudo systemctl status openstack-cinder-api.service
   sudo systemctl status openstack-cinder-scheduler.service

如果服务未运行，请尝试启动它们：

   sudo systemctl start openstack-cinder-api.service
   sudo systemctl start openstack-cinder-scheduler.service

3. 如果您仍然无法解决问题，请检查您的OpenStack配置文件以确保已正确配置Cinder服务。您可以在以下位置找到配置文件：

   /etc/cinder/cinder.conf

确保该文件中设置了正确的参数，例如数据库连接和认证信息等。

如果您仍然无法解决问题，请提供更多详细信息，以便我可以更准确地帮助您解决问题。

Job for openstack-nova-scheduler.service failed because the control process exited with error code.

在Linux系统中，当服务启动失败时，通常会提示“Job for xxx.service failed because the control process exited with error code. See 'systemctl status xxx.service' and 'journalctl -xe' for details.”这个错误信息。这个错误信息提示我们可以通过运行'systemctl status xxx.service'和'journalctl -xe'来查看详细的错误信息。

对于'Job for openstack-nova-scheduler.service failed because the control process exited with error code.'这个错误，我们可以按照以下步骤来解决：

1. 运行'systemctl status openstack-nova-scheduler.service'命令来查看服务的状态和错误信息。

2. 运行'journalctl -xe'命令来查看系统日志，找到与服务启动相关的错误信息。

3. 根据错误信息来修复问题。可能的解决方案包括重新安装服务、更新配置文件、检查依赖项等。

以下是一个例子，演示如何通过运行'systemctl status'和'journalctl -xe'来查看错误信息并解决问题：

$ systemctl status openstack-nova-scheduler.service
● openstack-nova-scheduler.service - OpenStack Nova Scheduler Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-scheduler.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2021-11-02 10:00:00 CST; 5s ago
  Process: 1234 ExecStart=/usr/bin/nova-scheduler (code=exited, status=1/FAILURE)
 Main PID: 1234 (code=exited, status=1/FAILURE)

Nov 02 10:00:00 server systemd[1]: Starting OpenStack Nova Scheduler Server...
Nov 02 10:00:00 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
Nov 02 10:00:01 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.
Nov 02 10:00:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 4 seconds.
Nov 02 10:00:07 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 8 seconds.
Nov 02 10:00:15 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 16 seconds.
Nov 02 10:00:31 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 32 seconds.
Nov 02 10:01:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 64 seconds.
Nov 02 10:02:07 server systemd[1]: openstack-nova-scheduler.service: main process exited, code=exited, status=1/FAILURE
Nov 02 10:02:07 server systemd[1]: Failed to start OpenStack Nova Scheduler Server.

从上面的输出中，我们可以看到服务启动失败，错误信息是“Unable to connect to AMQP server: [Errno 111] ECONNREFUSED.”。这个错误提示我们无法连接到AMQP服务器，可能是由于AMQP服务器未启动或配置错误导致的。

接下来，我们可以运行'journalctl -xe'命令来查看系统日志，找到与服务启动相关的错误信息：

$ journalctl -xe
...
Nov 02 10:00:00 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
Nov 02 10:00:01 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.
Nov 02 10:00:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 4 seconds.
Nov 02 10:00:07 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 8 seconds.
Nov 02 10:00:15 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 16 seconds.
Nov 02 10:00:31 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 32 seconds.
Nov 02 10:01:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 64 seconds.
...

从上面的输出中，我们可以看到与服务启动相关的错误信息是“Unable to connect to AMQP server: [Errno 111] ECONNREFUSED.”，这个错误信息与'systemctl status'命令输出的错误信息是一致的。

因此，我们可以得出结论，服务启动失败是由于无法连接到AMQP服务器导致的。我们需要检查AMQP服务器是否已启动，并确保配置文件中的AMQP服务器地址和端口号正确。