I guess ovsdbmonitor assumes that ovsdb-client is in /usr/bin, but you
have it in /usr/local/bin. I'll make a note to fix that assumption in
ovsdbmonitor.
On Wed, Oct 12, 2011 at 08:38:01AM +0800, Te-Yen Liu wrote:
> Hi, Ben
> Thanks for your response. I still got "Remote command failed" after
> modifying the connect target with no "p".
> The error log is as follows:
>
> 08:32:12 127.0.0.1: Executing /usr/bin/ovsdb-client transact
> unix:/usr/local/var/run/openvswitch/db.sock '["Open_vSwitch",
> {"op":"select","table":"Bridge", "where":[]}]'
> SSH connection to 127.0.0.1 established
> +++ Channel failure: Remote command failed (rc=127)
> Closing SSH session due to failure
> Transport reset for 127.0.0.1
> Remote command failed (rc=127)
>
>
>
> On Tue, Oct 11, 2011 at 11:54 PM, Ben Pfaff <[email protected]> wrote:
>
> > On Tue, Oct 11, 2011 at 04:55:32PM +0800, Te-Yen Liu wrote:
> > > Hi,
> > > I installed openvswitch and executed it as following commands:
> > >
> > > sudo ovsdb-server
> > > --remote=punix:/usr/local/var/run/openvswitch/db.sock \
> > > --remote=db:Open_vSwitch,manager_options \
> > > --private-key=db:SSL,private_key \
> > > --certificate=db:SSL,certificate \
> > > --bootstrap-ca-cert=db:SSL,ca_cert \
> > > --pidfile --detach
> > > sudo ovs-vsctl --no-wait init
> > > sudo ovs-vswitchd --pidfile --detach
> > >
> > > The result is OK.
> > > But, when I tried to run ovsdbmonitor to connect ovsdb at localhost, I
> > got
> > > error message "remote command failed (rc=127)"
> > > Host : 127.0.0.1
> > > SSH Password: ******
> > > Connect target: punix:/usr/local/var/run/openvswitch/db.sock
> > >
> > > Does anyone know what is going wrong?
> >
> > The connect target should be
> > unix:/usr/local/var/run/openvswitch/db.sock (no "p").
> >
> > There could be other problems too.
> >
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
