I have set up OVS on my Ubuntu 14.04 VM (https://github.com/openvswitch/ovs/blob/master/INSTALL.md) and am trying to add a bridge and port to the same. But it keeps throwing out this error and does not get added. Has anyone faced anything similar ? Screenshot of error attached.
OVS-VSCTL Error
I have already got my ODL controller ready on the same VM and need to get the bridge and port up on OVS to connect to it.
Thanks
The issue was solved when I used the netdev datapath type:
"-- set bridge br0 datapath_type=netdev".
Thanks,
Monica
Related
Q)After installing geth getting an error while attaching.How to fix this error?
geth attach
Fatal: Unable to attach to remote geth: no known transport for URL scheme "c"
If you're using 1.8, you need to include the IPC path:
geth attach ipc:\\.\pipe\geth.ipc
See https://github.com/ethereum/go-ethereum/issues/15746
If you using windows then try:
geth attach http://localhost:8545
this will properly work for windows work.
you don't have access to personal and mine objects using localhost ... eth.personal
undefined. Apparently you need to use ipc to get to the lower level objects
I'm running multiple SUMO simulations in parallel using TraCI.
Every so often one will fail with the message
Error: tcpip::Socket::accept() Unable to create listening socket: Address already in use
Quitting (on error).
I haven't found anyway to set the address to use on the configuration list at http://sumo.dlr.de/wiki/SUMO
I figure if I can set each instances address manually I should be able to avoid this.
The answer is right on the page you mention. The option --remote-port specifies the port number, so something like
sumo --remote-port 54323 -c my.sumocfg
should do the trick. Of course you need to give the same port when connecting from your traci client.
I need to debug my application , we are using version 2.65 (Diego)
.
I use the following wiki
http://docs.cloudfoundry.org/devguide/deploy-apps/ssh-apps.html
while running cf ssh myapp via cli
nothing happens , what should I do in order
1. To see the container FS
2. To be able to debug it ?
The application was deployed successfully to CF.
Im using nodejs app.
all other commands are working well.
When I run the command cf ssh myapp I got this error after two minutes :
FAILED
Error opening SSH connection: dial tcp 52.23.201.1:2277: getsockopt: operation timed out
It sounds like a platform issue using non-standard ssh port.
You can find a bit more ssh access manual steps/troubleshooting tips on https://docs.cloudfoundry.org/devguide/deploy-apps/ssh-apps.html
If you believe it is a instance issue, you can download a copy of droplet/fs using api, more on https://apidocs.cloudfoundry.org/213/apps/downloads_the_staged_droplet_for_an_app.html
I tried to run example from HornetQ and I got this error:
[java] HornetQServer_0 out: Deployment "JNDIServer" is in error due to: java.rmi.server.ExportException: Port already in use: 1098
Actually this is not the first time I got this kind of error. I can verify that port 1098 is indeed already in use (using Netstat command) but I just don't know which service using it. Is anybody has encountered such problem?
Thanks in advance for any response and help. :)
Could be JBOSS or Remote Admin Tool. Or something else like Outlook or Firefox.
While I was trying to start ApacheDS 1.5.7 on windows platform, An Error 04450 occurs and the apacheds-rolling.log contains:
[21:07:27] ERROR [org.apache.directory.shared.ldap.entry.DefaultServerAttribute] - ERR_04450 The value {0} is incorrect, it hasnt been added
[21:07:27] ERROR [org.apache.directory.server.Service] - Cannot start the server : reuseAddress can't be set while the acceptor is bound.
How can i fix this problem? Anybody could help me? many thanks!
The warning log message is a bit misleading, actually this is not a serious issue, the server should be running despite of this warning, this has been fixed a while back in the latest trunk code (which will be released as 2.0 instead of 1.5.8).
According to this post, the dc=example,dc=org context entry is not created by default anymore but no one has updated the documentation to reflect this. I installed 1.5.7 and it looks to me like the partition was created fine, but I'm getting the same error as described above. I suggest installing an older version.
The 2nd error message suggests that the port is already in use. Is there a chance that you already had another ApacheDS process running, or that another program is using the ports?
This isn't a domain controller perchance, is it? If so, the default LDAP ports 389 & 636 are already in use for Active Directory, so you'll need to choose another. However, I believe the defaults for ApacheDS are 10389 (LDAP) and 10636 (LDAPS), in which case they would typically be open on a Windows box.
You can check for processes on the ports with the netstat -abn command, and look through the list for the process listening on port 10389 or whichever custom port you chose.