[原]openstack-kilo--issue(十五) WARNING keystonemiddleware.auth_token Authorization failed for token Co...

 在创建vm的时候在controller node报错:

2017-01-17 18:36:26.942 17143 INFO neutron.wsgi [req-a815cde4-f49c-4d23-b9c3-030bfc2a75d4 ] 10.68.124.5 - - [17/Jan/2017 18:36:26] "GET /v2.0/security-groups.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3 HTTP/1.1" 200 2746 0.023965
2017-01-17 18:36:26.964 17143 WARNING keystonemiddleware.auth_token [req-a815cde4-f49c-4d23-b9c3-030bfc2a75d4 ] Authorization failed for token
2017-01-17 18:36:26.964 17143 WARNING keystonemiddleware.auth_token [req-a815cde4-f49c-4d23-b9c3-030bfc2a75d4 ] Identity response: {"error": {"message": "Could not find token: 0ce97969662946be861fb02ce4381be4", "code": 404, "title": "Not Found"}}
2017-01-17 18:36:26.965 17143 WARNING keystonemiddleware.auth_token [req-a815cde4-f49c-4d23-b9c3-030bfc2a75d4 ] Authorization failed for token
2017-01-17 18:36:26.965 17143 INFO neutron.wsgi [req-a815cde4-f49c-4d23-b9c3-030bfc2a75d4 ] 10.68.124.5 - - [17/Jan/2017 18:36:26] "POST /v2.0/ports.json HTTP/1.1" 401 282 0.020042
2017-01-17 18:36:30.964 17143 INFO neutron.wsgi [req-2ccbadfc-ba0c-46c9-9334-d0b08f719ca0 ] 10.68.124.5 - - [17/Jan/2017 18:36:30] "GET /v2.0/ports.json?device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 200 226 0.023853
2017-01-17 18:36:30.969 17143 WARNING keystonemiddleware.auth_token [req-2ccbadfc-ba0c-46c9-9334-d0b08f719ca0 ] Authorization failed for token
2017-01-17 18:36:30.969 17143 INFO neutron.wsgi [req-2ccbadfc-ba0c-46c9-9334-d0b08f719ca0 ] 10.68.124.5 - - [17/Jan/2017 18:36:30] "PUT /v2.0/ports/None.json HTTP/1.1" 401 282 0.001208
2017-01-17 18:36:31.054 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:36:31] "GET /v2.0/ports.json?device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 200 226 0.023567
2017-01-17 18:36:31.058 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:36:31.059 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:36:31] "PUT /v2.0/ports/None.json HTTP/1.1" 401 282 0.001111
2017-01-17 18:36:47.052 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:36:47.053 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:36:47] "GET /v2.0/ports.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3&device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 401 282 0.001328
2017-01-17 18:37:47.049 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:37:47.050 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:37:47] "GET /v2.0/ports.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3&device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 401 282 0.001886
2017-01-17 18:38:48.054 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:38:48.056 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:38:48] "GET /v2.0/ports.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3&device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 401 282 0.001782
2017-01-17 18:39:48.055 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:39:48.056 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:39:48] "GET /v2.0/ports.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3&device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 401 282 0.001976
2017-01-17 18:40:49.053 17143 WARNING keystonemiddleware.auth_token [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] Authorization failed for token
2017-01-17 18:40:49.054 17143 INFO neutron.wsgi [req-f5942e6a-35b8-4711-a3a9-b999076b51f0 ] 10.68.124.5 - - [17/Jan/2017 18:40:49] "GET /v2.0/ports.json?tenant_id=f57b892b5c50426bb90414d31f0e77f3&device_id=fe82e41c-b566-4f40-885c-39d970b83395 HTTP/1.1" 401 282 0.001853

 google了一下,居然没有找到我想找的那种解决方案:

回头再看看官方文档,如果token过期了需要重新取得一个token

[root@controller ~]# openstack token issue
+------------+----------------------------------+
| Field      | Value                            |
+------------+----------------------------------+
| expires    | 2017-01-17T12:23:07.968593Z      |
| id         | fb65e088c00b4ca8ab69364ef6f5a7ac |
| project_id | f57b892b5c50426bb90414d31f0e77f3 |
| user_id    | 60c0bf61f8f847e88d5562d419d8c367 |
+------------+----------------------------------+

重启neutron 所有的agent

恢复正常:)

转载于:https://www.cnblogs.com/horizonli/p/6294262.html

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
在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'来查看错误信息并解决问题: ```bash $ 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'命令来查看系统日志,找到与服务启动相关的错误信息: ```bash $ 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服务器地址和端口号正确。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值