While adding a service i forgot to add a part in the url, should be xxx/yyy/zzz but input xxx/zzz.
After stopping the stack and trying to correct the error i get the following error:
Validation failed in API: imageUuid
I've tried removing all stacks and reinserting the service. It however won't add it again and i've found no way to remove it from the server.
Think this is a bug, i'm using a private repository, so the address is:
private.dns.name:8080/project/tools/toola
This is not supported by Rancher, the following does work:
private.dns.name:8080/tools/toola
Related
I have a situation where I want to import my graph data to database.I am having janusgraph(latest version) running with cassandra(version 3) and elasticsearch(version 6.6.0) using Docker.I have been suggested to use gryo format.So I have tried this command
graph.io(IoCore.gryo()).reader().create().readGraph(ToInputStream.from("my_graph.kryo"), graph);
but ended up with an error
No such property: ToInputStream for class: Script4
The documentation I am following is here.Please take a look and put me in a right procedure. Thanks in advance!
ToInputStream is not a function of Gremlin or JanusGraph. I believe that it is only a function of IBM Compose so unless you are running JanusGraph on that specific platform, this command will not work.
Versions of JanusGraph that utilize TinkerPop 3.4.x will support the io() step and this is the preferred manner in which to load gryo (as well as graphson and graphml) files.
Graph graph = ... // setup JanusGraph instance
GraphTraversalSource g = traversal().withGraph(graph); // might use withRemote() here instead depending on how you are connecting I suppose
g.io("graph.kryo").read().iterate()
Note that if you are connecting remotely - it seems you are sending scripts to the Docker instance given your error - then be sure that that "graph.kryo" file path is accessible to Docker. That's what's nice about ToInputStream from Compose as it allows you to access remote sources.
I'm using nebula docker but it throws me an error when I connected first. Then I retried everything is ok. Why is that? Must I retry every time?
This is likely caused by setting the heartbeat_interval_secs value to fetch data from the meta server. Conduct the following steps to resolve:
If meta has registered, check heartbeat_interval_secs value in console with the following command.
nebula> GET CONFIGS storage:heartbeat_interval_secs
nebula> GET CONFIGS graph:heartbeat_interval_secs
If the value is large, change it to 1s with the following command.
nebula> UPDATE CONFIGS storage:heartbeat_interval_secs=1
nebula> UPDATE CONFIGS graph:heartbeat_interval_secs=1
Note the changes take effect in the next period.
I want to scale the number of replicas on a service using the Go SDK.
This is the function that (I think) accomplishes this:
func (cli *Client) ServiceUpdate(ctx context.Context, serviceID string, version swarm.Version, service swarm.ServiceSpec, options types.ServiceUpdateOptions) (types.ServiceUpdateResponse, error)
Whenever I run it, however, I get an error:
Error response from daemon: rpc error: code = Unknown desc = update out of sequence
I'm pretty sure this occurs because the update sequence is out of order, and the version no. is used to order this.
But I don't know how to find the right version index!
Ah I figured it out!
Docker requires that you pass the same version and ServiceSpec when updating a service to avoid out-of-sequence updates, which was the issue I ran into.
You can easily get this through ServiceInspectWithRaw, which returns a swarm.Service, which has a version in its Meta.Version field. I totally missed that beforehand.
i'm working on a tuleap project that's run in a docker container , i added new classes and i want to apply a refresh to the autoload file so
this the Link that help me to do this,
https://tuleap.net/doc/en/developer-guide/autoload.html
But when i execute
make autoload-docker
I have this error
docker:unauthorized authentication required
Any one can help me to resolve this issue ?Thx.marwen
So I basically do this.
OObjectDatabaseTx result = OObjectDatabasePool.global().acquire( "local:orientdb", "admin", "admin");
//dostuff
result.close;
The problem is that when I redeploy my webapp (without restarting the Java EE container) I get the folling error:
com.orientechnologies.orient.core.exception.OStorageException: Cannot open local storage 'orientdb' with mode=rw
which I interpret to mean "Tomcat still has a filelock from the last app".
So my question is how do I cleanly exit in this scenario? I've tried:
OObjectDatabasePool.global().close()
and
new OObjectDatabaseTx("local:orientdb").close()
but neither seem to work. Any ideas? The documentation isn't exactly clear on this issue.
Set the property "storage.keepOpen" to false:
java ... -Dstorage.keepOpen=false ...
or via Java code:
OGlobalConfiguration.STORAGE_KEEP_OPEN.setValue( false );