I am removing some volttron agents and I keep running into errors. It is usually the case when I do "vctl status" or try to remove or stop some already installed agents. I also encounter it when shutting down so that I have to manually enter the .volttron directory and remove the keystore files, and delete all the directories for agents.
I see an almost similar question was asked here: volttron.platform.vip.agent.core ERROR: Possible conflicting identity. But I go through the installation process to install my agents and don't run from Eclipse at all.
python scripts/install-agent.py -s Node611/PredAgent/ -c Node611/PredAgent/config -t p11
These are the errors:
2019-08-06 11:00:12,070 () volttron.platform.vip.agent.core ERROR: No response to hello message after 10 seconds.
2019-08-06 11:00:12,070 () volttron.platform.vip.agent.core ERROR: A common reason for this is a conflicting VIP IDENTITY.
2019-08-06 11:00:12,070 () volttron.platform.vip.agent.core ERROR: Another common reason is not having an auth entry onthe target instance.
2019-08-06 11:00:12,071 () volttron.platform.vip.agent.core ERROR: Shutting down agent.
2019-08-06 11:00:12,071 () volttron.platform.vip.agent.core ERROR: Possible conflicting identity is: control.connection
remove: operation timed out
Are there other warning messages in the log before this error? Do you see any authentication errors/warnings before this error message? You would have to explicitly authorize an agent to access VOLTTRON platform. You can either do a 'vctl auth add' for a single agent or in case development or testing environment allow access to all agents by setting credentials=/.*/ when doing 'vctl auth add'
Another possible reason for this could be connection issues with broker. Are you using ZMQ or RabbitMQ message bus? If using RabbitMQ could you check the rabbitmq log to see if there are any errors?
Related
I'm trying to get the matlab agent in Linux connected to the standalone agent in Windows. I start by setting up a platform (using vcfg) on Volttron. However, I get this error when I try to define an IP address and port on the volttron instance:
What is the vip address? [tcp://127.0.0.1]: tcp://192.168.56.101 What
is the port for the vip address? [22916]:
ERROR: That address has already been bound to. What is the vip
address? [tcp://192.168.56.101]: tcp://192.168.56.155 What is the port
for the vip address? [22916]: ERROR: That address has already been
bound to.
No matter the address I give, it says it has already been bound to. I removed the .volttron directory that contains the known_hosts, etc. but to no avail. The only IP address that seems to work is 127.0.0.2. However with that the standalone agent does not connect to the Volttron platform. I added the authentication credentials of the standalone agent in volttron and made sure the keys were correctly configured. This is all that I get:
2019-08-08 10:24:16,059 volttron.platform.vip.agent.core DEBUG: identity: standalone_matlab
2019-08-08 10:24:16,059 volttron.platform.vip.agent.core DEBUG: agent_uuid: None
2019-08-08 10:24:16,059 volttron.platform.vip.agent.core DEBUG: serverkey: None
2019-08-08 10:24:16,069 volttron.platform.vip.agent.core DEBUG: AGENT RUNNING on ZMQ Core standalone_matlab
2019-08-08 10:24:16,072 volttron.platform.vip.zmq_connection DEBUG: ZMQ connection standalone_matlab
After a while, it times out:
2019-08-08 10:25:14,540 volttron.platform.vip.zmq_connection DEBUG: ********************************************************************
2019-08-08 10:25:14,542 volttron.platform.vip.zmq_connection DEBUG: Closing connection to ZMQ: standalone_matlab
2019-08-08 10:25:14,542 volttron.platform.vip.zmq_connection DEBUG: ********************************************************************
I am missing this line which indicates that a connection has been made.
volttron.platform.vip.agent.core INFO: Connected to platform: router: ebae9efa-5e8f-49e3-95a0-2020ddff9e8a version: 1.0 identity: standalone_matlab
Also, I already set my network adapter to host-only. Can someone please help me know what I'm doing wrong?
I finally figured out what the problem was. It was a ZMQ issue. ZMQ was refusing to bind to the address that I was giving to the wizard. It threw up this error:
Traceback (most recent call last): File "", line 1, in
File "zmq/backend/cython/socket.pyx", line 495, in
zmq.backend.cython.socket.Socket.bind
(zmq/backend/cython/socket.c:5327) File
"zmq/backend/cython/checkrc.pxd", line 25, in
zmq.backend.cython.checkrc._check_rc
(zmq/backend/cython/socket.c:9542) zmq.error.ZMQError: Cannot assign
requested address
The fix was simply to do "ifconfig" and find the IP address that was assigned to my Linux system and provide that to the wizard.
I just finished building my app and I sent a build with no certificate and it worked...now on adding an android certificate, it reports a build error on my codename one dashboard. A help will be appreciated.
FAILURE: Build failed with an exception. * What went wrong: Execution
failed for task '
:transformClassesAndResourcesWithProguardForRelease'. >
java.io.IOException: Please correct the above warnings first.
Warning: Exception while processing task java.io.IOException: Please correct the above warnings first.
:transformClassesAndResourcesWithProguardForRelease FAILED
:transformClassesAndResourcesWithProguardForRelease (Thread[Daemon
worker,5,main]) completed. Took 4.163 secs.
I will need the full error as that point is already too low. I recall seeing some failures when punctuation was used in one of the certificate properties as Android chokes on that. It should appear in the error logs.
Got lost with my VSTS CI build which stoped working overnight with a random 404 error message:
[debug] C:\a\1\Nuget\tempNuGet_293.config
[command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... C:\a\1\Nuget\tempNuGet_293.config
Using credentials from config. UserName: VssSessionToken
Response status code does not indicate success: 404 (Not Found).
... and further the failed publisher result:
[debug]rc:1
[debug]success:false [debug]rm -rf C:\a\1\Nuget\tempNuGet_293.config
[error]Error: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... failed with return code: 1
[error]Packages failed to install
[debug]task result: Failed [error]Return code: 1
Twelve hours ago the Publisher task reported success:
[debug] C:\a\1\Nuget\tempNuGet_285.config
[command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\... C:\a\1\Nuget\tempNuGet_293.config
Using credentials from config. UserName: VssSessionToken
Your package was pushed.
A ran the build multiple times with the same result. Any idea what is going on?
It turned out this was an issue of VSTS and was resolved; presumably by Microsoft. I just had to wait some hours and the problem disappeared.
Our deployments for the default module of a particular app are failing, seemingly at random, at least 50% of the time, which is constantly disrupting our workflow.
With verbose logging turned on via appcfg.py update app.yaml --verbose, this error appears on the terminal:
03:43 PM Uploaded 4 files and blobs.
03:43 PM Compilation starting.
2015-09-23 15:43:51,886 INFO appcfg.py:1735 Send: /api/appversion/precompile, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
03:43 PM Compilation completed.
03:43 PM Starting deployment.
2015-09-23 15:43:54,215 INFO appcfg.py:1735 Send: /api/appversion/deploy, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
2015-09-23 15:43:56,341 INFO appcfg.py:2601 HTTP Error (HTTP Error 400: Bad Request Unexpected HTTP status 400)
03:43 PM Rolling back the update.
2015-09-23 15:43:56,341 INFO appcfg.py:1735 Send: /api/appversion/rollback, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
Error 400: --- begin server output ---
Client Error (400)
The request is invalid for an unspecified reason.
--- end server output ---
The failure is extremely consistent, in that most of the time we try deploying the module after not having deployed for a few hours, the deployment attempt will fail with the above output.
Then, without changing any app code, retrying the deployment usually succeeds (but at times, the second attempt also fails, requiring subsequent deployment attempts).
This problem started happening earlier this year. Once the problem started occurring, it has not ceased. Before it occurred, we had no no issues with deployments.
The version of the module being deployed has no effect on the rate of deployment success. We are using the Python runtime for this module.
I have already emailed a Solutions Architect from Google about this, but apart from upgrading to a paid support plan to ensure someone looks into this, he suggested I post on here with the hope that the App Engine support team gets back to me.
App Engine support team - can you find out what is going on (and ideally provide a fix)? If you need more information (such as my app ID), please let me know.
As part of the deployment process of a Glide project (http://glide-gae.appspot.com/docs/intro step 3 of 2nd section) you need to authenticate using oauth2. My browser popped up with the token as expected but the process didn’t wait for me to copy the code in, it just carried on with the following error...
22:30:12.713 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] Daemon is busy, sleeping until state changes.
22:30:12.733 [INFO] [org.gradle.launcher.daemon.server.exec.LogToClient] About to start relaying all logs to the client via the connection.
22:30:12.734 [INFO] [org.gradle.launcher.daemon.server.exec.LogToClient] The client will now receive all logging from the daemon (pid: 12557). The daemon log file: /.gradle/daemon/1.8/daemon-12557.out.log
22:30:12.739 [DEBUG] [org.gradle.launcher.daemon.server.SynchronizedDispatchConnection] thread 14: received class org.gradle.launcher.daemon.protocol.CloseInput
22:30:12.740 [DEBUG] [org.gradle.launcher.daemon.server.DefaultDaemonConnection] Received IO message from client: CloseInput[id=069864b2-2948-4a9d-abea-0705274136a1.2]
22:30:12.741 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] Closing daemon's stdin at end of input.
22:30:12.742 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] The daemon will no longer process any standard input.
22:30:12.747 [INFO] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] Executing build with daemon context: DefaultDaemonContext[uid=3901cff0-8d50-41b6-9459-e31f7b78f1e3,javaHome=/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home,daemonRegistryDir=.gradle/daemon,pid=12557,idleTimeout=10800000,daemonOpts=-XX:MaxPermSize=256m,-Xmx512m,-Dfile.encoding=UTF-8]
Please enter code: Encountered a problem: No line found
Please see the logs [/var/folders/c8/vx2jf50j68x1z3_pysy6kxjm0000gp/T/appcfg2389447403250678065.log] for further information.
Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt.
----- End of the daemon log -----
org.gradle.tooling.GradleConnectionException: Could not execute build using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.8-bin.zip'.
What can I do to be able to deploy my application? How can I force the process to wait for me to enter the code?
If that's (glide deploy) not working for you, the easiest option is to export the app as a standard gradle project and then execute the gaeUpdate task.
glide -a somedir/yourapp -o where/you/want/to/export/app export
Note that the export is command at the end, -o tell the location where it should be exported.
Then from the exported project run: gradle gaeUpdate
A work around is to manually set your credentials in the GAE build.gradle file.
Update the following file:
/glide/install/generated/app-name/build.gradle
appcfg {
email = ‘email-address'
password = ‘password'
app {
id = ‘app-id'
}
}
This means that the values from the __glide.groovy file are ignored, but at least you can get the application deployed