[openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration
Yipei Niu
newypei at gmail.com
Wed Feb 24 01:29:24 UTC 2016
Hi Joe and Zhiyuan,
My VM has recovered. When I re-install devstack in node1, I encounter the
following errors.
The info in stack.sh.log is as follows:
2016-02-23 11:18:27.238 | Error: Service n-sch is not running
2016-02-23 11:18:27.238 | +
/home/stack/devstack/functions-common:service_check:L1625: '[' -n
/opt/stack/status/stack/n-sch.failure ']'
2016-02-23 11:18:27.238 | +
/home/stack/devstack/functions-common:service_check:L1626: die 1626 'More
details about the above errors can be found with screen, with
./rejoin-stack.sh'
2016-02-23 11:18:27.238 | + /home/stack/devstack/functions-common:die:L186:
local exitcode=0
2016-02-23 11:18:27.239 | [Call Trace]
2016-02-23 11:18:27.239 | ./stack.sh:1354:service_check
2016-02-23 11:18:27.239 | /home/stack/devstack/functions-common:1626:die
2016-02-23 11:18:27.261 | [ERROR]
/home/stack/devstack/functions-common:1626 More details about the above
errors can be found with screen, with ./rejoin-stack.sh
2016-02-23 11:18:28.271 | Error on exit
2016-02-23 11:18:28.953 | df: '/run/user/112/gvfs': Permission denied
The info in n-sch.log is as follows:
stack at nyp-VirtualBox:~/devstack$ /usr/local/bin/nova-scheduler
--config-file /et ^Mc/nova/nova.conf & echo $!
>/opt/stack/status/stack/n-sch.pid; fg || echo "n-sch ^M failed to start" |
tee "/opt/stack/status/stack/n-sch.failure"
[1] 29467
/usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf
2016-02-23 19:13:00.050 ^[[00;32mDEBUG oslo_db.api [^[[00;36m-^[[00;32m]
^[[01;35m^[[00;32mLoading backend 'sqlalchemy' from
'nova.db.sqlalchemy.api'^[[00m ^[[00;33mfrom (pid=29467) _load_backend
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py:238^[[00m
2016-02-23 19:13:00.300 ^[[01;33mWARNING
oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m]
^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by
default for backward compatibility. SIGUSR1 will no longer be registered in
a future release, so please use SIGUSR2 to generate reports.^[[00m
2016-02-23 19:13:00.304 ^[[01;31mCRITICAL nova [^[[00;36m-^[[01;31m]
^[[01;35m^[[01;31mValueError: Empty module name
^[[00m
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mTraceback (most
recent call last):
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/usr/local/bin/nova-scheduler", line 10, in <module>
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
sys.exit(main())
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/opt/stack/nova/nova/cmd/scheduler.py", line 43, in main
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
topic=CONF.scheduler_topic)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/opt/stack/nova/nova/service.py", line 281, in create
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
db_allowed=db_allowed)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/opt/stack/nova/nova/service.py", line 167, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m self.manager
= manager_class(host=self.host, *args, **kwargs)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/opt/stack/nova/nova/scheduler/manager.py", line 49, in __init__
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m self.driver
= importutils.import_object(scheduler_driver)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
44, in import_object
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m return
import_class(import_str)(*args, **kwargs)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
30, in import_class
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
__import__(mod_str)
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00mValueError:
Empty module name
^[[01;31m2016-02-23 19:13:00.304 TRACE nova ^[[01;35m^[[00m
n-sch failed to start
Best regards,
Yipei
On Tue, Feb 23, 2016 at 10:23 AM, Yipei Niu <newypei at gmail.com> wrote:
> Hi Jeo,
>
> I have checked. The Neutron API has not started, but no process is
> listening 9696.
>
> Best regards,
> Yipei
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160224/ca8cc941/attachment.html>
More information about the OpenStack-dev
mailing list