Open Stack

Hi,

thank you for your answer. I have scp-ed all /etc/neutron and /etc/nova to
this node with no success.
I am starting to wonder why this table 22 exists on this problematic
compute node (there are no VMs on the system at the moment):
/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-ofctl dump-flows
br-int table=22
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=118.77s, table=22, n_packets=0, n_bytes=0,
idle_age=118, priority=0 actions=drop


When running exactly the same command on another (not-spammy auth.log
server):
/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-ofctl dump-flows
br-int table=22
NXST_FLOW reply (xid=0x4):

I wonder why is this "duration" parameter increasing only on this
"problematic" node, while on all other nodes there is no "cookie....
duration ... table=22" line on the output of ovs-ofctl dump-flows br-int
table=22 command.

Any further ideas will be greatly appreciated :-)

TIA, Matej


On Sat, Sep 27, 2014 at 11:49 PM, Anne Gentle <anne at openstack.org> wrote:

> I'm not exactly sure what's causing this, but read here:
> http://docs.openstack.org/admin-guide-cloud/content/root-wrap-reference.html
>
> and see if there's something different about the new compute node; root
> wrap folder, permissions or filters?
>
> Anne
>
> On Sat, Sep 27, 2014 at 4:31 PM, Matej <matej at tam.si> wrote:
>
>> I am still seeing bunch of those every 2 seconds.
>> What is the proper debugging method for such an issue? I have reinstalled
>> neutron and openvswitch, nothing unusual in any log files.
>>
>> Thanks,
>> Matej
>>
>>
>> ---------- Forwarded message ----------
>> From: Matej <matej at tam.si>
>> Date: Wed, Sep 17, 2014 at 9:30 PM
>> Subject: Flood of compute node's auth.log messages
>> To: "openstack at lists.openstack.org" <openstack at lists.openstack.org>
>>
>>
>> Hi all,
>>
>> I have added another compute node to our Openstack installation. Newly
>> created instances are successfully created on the system, also networking
>> via Neutron and GRE works as it should - I have copied the configuration
>> from the working compute nodes (except changing some IP addresses to the
>> new compute node's).
>>
>> But there are a lot of  the following messages:
>> Sep 17 21:26:52 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>> Sep 17 21:26:54 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>> Sep 17 21:26:56 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>> Sep 17 21:26:58 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>> Sep 17 21:27:00 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>> Sep 17 21:27:02 EagleNetCompute3 sudo:  neutron : TTY=unknown ; PWD=/ ;
>> USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
>> ovs-ofctl dump-flows br-int table=22
>>
>> Since messages of this kind are not present on other compute nodes and
>> those entries are filling my disk, I will be very grateful for any ideas on
>> how to find the root of why are they shown.
>>
>> Thank you very much for and ideas and time in advance.
>> Matej
>>
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20141001/834e72c7/attachment.html>