[2.21 86] Config processes dint come up after rebooting the node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Undecided
|
Unassigned | ||
R2.20 |
New
|
High
|
Unassigned |
Bug Description
Build : 2.21-86
cores : {}
CoreLocation : /cs-shared/
LogsLocation : http://
Report : http://
Topology :
Config Nodes : [u'nodeb8']
Control Nodes : [u'nodeb8']
Compute Nodes : [u'nodeb8']
Openstack Node : nodeb8
WebUI Node : nodeb8
Analytics Nodes : [u'nodeb8']
Required logs copied to : /cs-shared/
Seen particularly on CentOS 6.5. Sundar is aware of the issue.
While provisioning when supervisor/
[root@nodeb8 contrail-test]# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
== Contrail Control ==
supervisor-control: active
contrail-control initializing (Number of connections:4, Expected:5)
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics ==
supervisor-
contrail-
contrail-
contrail-collector initializing (Discovery:
contrail-
contrail-
contrail-topology active
== Contrail Config ==
supervisor-config: inactive
unix://
== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-
== Contrail Database ==
supervisor-
contrail-database active
contrail-
== Contrail Support Services ==
supervisor-
rabbitmq-server active
[root@nodeb8 contrail]# openstack-status
== Nova services ==
openstack-nova-api: active
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
== Glance services ==
openstack-
openstack-
== Keystone service ==
openstack-keystone: active
== Horizon service ==
openstack-
== Cinder services ==
openstack-
openstack-
openstack-
== Support services ==
mysqld: active
httpd: active
libvirtd: active
rabbitmq-server: active
memcached: active
== Keystone users ==
Warning keystonerc not sourced
contrail-
08/25/2015 03:09:44 PM [nodeb8:
wokeup and found a line
process:
contrail-api:0 with pid:4702 exited abnormally
supervisord-
2015-08-25 15:09:17,521 INFO success: contrail-
2015-08-25 15:09:17,521 INFO success: contrail-schema entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-08-25 15:09:17,521 INFO success: contrail-
2015-08-25 15:09:25,483 INFO exited: 0 (exit status 1; not expected)
2015-08-25 15:09:25,801 INFO spawned: '0' with pid 6658
2015-08-25 15:09:26,800 INFO success: 0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-08-25 15:09:47,081 INFO stopped: ifmap (terminated by SIGTERM)
2015-08-25 15:09:47,083 INFO stopped: contrail-
2015-08-25 15:09:47,383 INFO stopped: 0 (terminated by SIGKILL)
2015-08-25 15:09:47,664 INFO stopped: 0 (terminated by SIGKILL)
2015-08-25 15:09:48,669 INFO stopped: contrail-
2015-08-25 15:09:49,674 INFO stopped: contrail-schema (terminated by SIGKILL)
2015-08-25 15:09:50,680 INFO stopped: contrail-
tags: | added: config |
Changed in juniperopenstack: | |
assignee: | Raj Reddy (rajreddy) → nobody |
tags: | added: releasenote |
information type: | Proprietary → Public |
Pavana, can you see what the syslog says wrt supervisor-config service..
It seems someone is issuing ‘service supervisor-config stop'
thanks,
> On Aug 25, 2015, at 11:59 PM, Pavana <email address hidden> wrote: k/r2.20 /bugs.launchpad .net/bugs/ 1488783 test_runs/ nodeb8/ 2015_08_ 26_03_29_ 50 10.204. 216.50/ Docs/logs/ 2.21-86_ 2015_08_ 26_03_29_ 50/logs/ 10.204. 216.50/ Docs/logs/ 2.21-86_ 2015_08_ 26_03_29_ 50/junit- noframes. html test_runs/ nodeb8/ 2015_08_ 26_03_29_ 50 API/IFMAP are restarted, the rest of the processes are triggered for restart but they donot come up. vrouter- agent initializing (Collector, Discovery: Collector, Discovery: dns-server, Discovery: xmpp-server connection down) vrouter- nodemgr active control- nodemgr active analytics: active analytics- api initializing (Discovery: OpServer, Discovery:Collector connection down) analytics- nodemgr active Collector connection down) query-engine active snmp-collector active /tmp/supervisor d_config. sockno webui-middlewar e active database: active database- nodemgr active support- service: active
>
> ** Changed in: juniperopenstac
> Assignee: (unassigned) => Raj Reddy (rajreddy)
>
> --
> You received this bug notification because you are a member of Contrail
> Systems engineering, which is subscribed to Juniper Openstack.
> https:/
>
> Title:
> [2.21 86] Config processes dint come up after rebooting the node
>
> Status in Juniper Openstack:
> New
> Status in Juniper Openstack r2.20 series:
> New
>
> Bug description:
> Build : 2.21-86
> cores : {}
> CoreLocation : /cs-shared/
> LogsLocation : http://
> Report : http://
> Topology :
> Config Nodes : [u'nodeb8']
> Control Nodes : [u'nodeb8']
> Compute Nodes : [u'nodeb8']
> Openstack Node : nodeb8
> WebUI Node : nodeb8
> Analytics Nodes : [u'nodeb8']
>
> Required logs copied to : /cs-
> shared/
>
> Seen particularly on CentOS 6.5. Sundar is aware of the issue.
> While provisioning when supervisor/
>
> [root@nodeb8 contrail-test]# contrail-status
> == Contrail vRouter ==
> supervisor-vrouter: active
> contrail-
> contrail-
>
> == Contrail Control ==
> supervisor-control: active
> contrail-control initializing (Number of connections:4, Expected:5)
> contrail-
> contrail-dns active
> contrail-named active
>
> == Contrail Analytics ==
> supervisor-
> contrail-
> contrail-
> contrail-collector initializing (Discovery:
> contrail-
> contrail-
> contrail-topology active
>
> == Contrail Config ==
> supervisor-config: inactive
> unix://
>
> == Contrail Web UI ==
> supervisor-webui: active
> contrail-webui active
> contrail-
>
> == Contrail Database ==
> supervisor-
> contrail-database active
> contrail-
>
> == Contrail Support Services ==
> supervisor-
>...