Open Stack

Hi Ruben,

If you have configured congress through devstack, the default way of
starting congress server would be
python /usr/local/bin/congress-server --node-id=allinonenode --config-file
/etc/congress/congress.conf ,
but the way you start the service sounds ok, as others would be default
parameters.

Devstack by default should set all the default configurations in
congress.conf required for setting up congress, so make sure you have all
the required services up (nova, glance) from which congress polls data. If
you have an issue with initial setup of congress itself, as Eric suggested
would be better to restack again, as devstack does its job to re-configure
congress again from start.

If you still see the issue, I suggest you join #congress IRC channel , so
that anyone from congress team should be able to help you.

Best Regards,
Anusha

On 6 November 2016 at 22:18, Ruben <r.manganiello1 at studenti.unisa.it> wrote:

> Hi Eric,
> also with the old congress.conf file there is the error.
> I've used devstack with a single-process congress deployment.
>
> To stop the congress server I make: screen -x stack and Ctrl-C in the
> congress window.
> To restart the congress server I make: screen -x stack and sudo
> /usr/local/bin/congress-server --debug in the congress window.
>
> Is it possible that I should rejoin the stack?
>
> Ruben
>
> ----- Original Message -----
> From: "Eric" <ekcs.openstack at gmail.com>
> To: openstack-dev at lists.openstack.org
> Cc: "Ruben" <r.manganiello1 at studenti.unisa.it>
> Sent: Friday, November 4, 2016 7:23:50 PM
> Subject: Re: [Congress] Restart Congress server
>
> Hi Ruben,
>
> Awesome to hear about your progress!
>
> The error seems to be independent of adding a new driver.
>
> Could you try using the unchanged congress.conf and restarting again to
> see if the same problem shows up?
>
> Also, could you give the command you¹re using the launch congress-server?
>
> Mainly I want to understand whether you¹re using single-process congress
> deployment or multi-process congress deployment. If multi-process, it¹s
> possible that the datasources process was stopped but wasn¹t restarted.
>
>
> If your screen listing (access by pressing Ctrl-A followed by ") shows
> three congress windows like this, then you¹re running in multi-process
> mode:
> 29 congress-api
>                                                             $(L)
>   30 congress-engine
>                                                               $(L)
>   31 congress-datasources
>                                                               $(L)
>
> To launch Congress, make sure all three are running properly.
>
> A simpler alternative (but takes some time) is to deploy devstack from
> scratch (saving your work somewhere of course) using the latest versions
> (defaults to single process), which should reduce complications from
> multiple processes and make everything easier for dev-testing.
>
> All the best!
>
>
>
> On 11/4/16, 4:53 AM, "Ruben" <r.manganiello1 at studenti.unisa.it> wrote:
>
> >Hi everyone,
> >I've tried to write a datasource driver for Magnum and the unit test for
> >it.
> >So I've add this datasource driver in
> >/opt/stack/congress/congress/datasources/ and the unit test in
> >/opt/stack/congress/congress/tests/datasources/ to test it.
> >Moreover, I've add the driver to /etc/congress/congress.conf, but when I
> >try to restart Congress server I've some errors.
> >
> >
> >"2016-11-04 12:13:00.390 TRACE congress.service     self.service_id,
> >service, table)
> >2016-11-04 12:13:00.390 TRACE congress.service   File
> >"/opt/stack/congress/congress/dse2/dse_node.py", line 468, in
> >subscribe_table
> >2016-11-04 12:13:00.390 TRACE congress.service     {'table': table})
> >2016-11-04 12:13:00.390 TRACE congress.service   File
> >"/opt/stack/congress/congress/dse2/dse_node.py", line 355, in
> >invoke_service_rpc
> >2016-11-04 12:13:00.390 TRACE congress.service     raise
> >exception.NotFound(msg % service_id)
> >2016-11-04 12:13:00.390 TRACE congress.service NotFound: service 'nova'
> >could not be found
> >2016-11-04 12:13:00.390 TRACE congress.service
> >2016-11-04 12:13:00.537 DEBUG oslo_concurrency.lockutils [-] Acquired
> >semaphore "singleton_lock" from (pid=24411) lock
> >/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212
> >2016-11-04 12:13:00.538 DEBUG oslo_concurrency.lockutils [-] Releasing
> >semaphore "singleton_lock" from (pid=24411) lock
> >/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225"
> >
> >I don't know what to do to solve it and even if the driver I've written
> >works.
> >Maybe I make mistakes when I restart Congress server..
> >What should I do to restart Congress server?
> >What could I do to test the datasource and solve these problems?
> >
> >Ruben
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161107/fb9c8b5c/attachment.html>