New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to find instance to delegate to for agent #7133
Comments
I have this issue as well after upgrading from 1.1.4 to 1.2.1. I'm running server on docker 1.11.2 on Amazon Linux AMI 2016.09. Hosts are running ubuntu. |
Same problem here, I thought first a problem with volumes while deploying a stack using them but even a clean restart of rancher server raises this exception that loops : 2016-12-29 16:55:08,337 ERROR [:] [] [] [] [ecutorService-1] [.p.c.v.i.ConfigItemStatusManagerImpl] Error updating item(s) [configscripts, services, agent-instance-scripts, monit, agent-instance-startup, node-services, ipsec, ipsec-hosts, hosts, iptables, healthcheck] on [agent:8] com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Delegate [delegate:///?vnetId=3&networkServiceProviderId=4] has no instance associated Rancher version : 1.2.2 |
Same problem here: 2017-01-12 15:46:39,051 ERROR [:] [] [] [] [ecutorService-7] [.p.c.v.i.ConfigItemStatusManagerImpl] Error updating item(s) [agent-instance-scripts, healthcheck, services, iptables, configscripts, hosts, ipsec-hosts, ipsec, node-services, agent-instance-startup, monit] on [agent:22404] com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Delegate [delegate:///?vnetId=594&networkServiceProviderId=1] has no instance associated |
Happening for us as well - the message is spamming as fast as it can print. Rancher Server 1.3.2
|
+1 |
And again. Rancher version : 1.4.0 / Cattle
|
Docker version: 1.12.1
This eventually causes Rancher to stop responding to web requests. Temporary fix is to stop the container, remove it, and re-create a new container (pointed to the same existing external DB), this proved ~2 days of up time, before it stops responding to web requests again. |
Hi there, I had the same error with rancher and a local database. The mysql database was corrupt.
the errors went away and rancher was reachable again. |
@CLEMARCx I dont think you have the same issue as the others in this thread. It looks like there are orphaned agents, there might be an entry for the agent that doesnt match any existing host. Does this query return anything: |
+1 for the error with rancher 1.3.3, upgraded sequentially from 1.1.4 (original installation). |
@aemneina executing your statement returned for me 246 rows / results |
Hi any resolution here? I am seeing something similar: #8308 |
I made this quit by finding the row in the agent table in the rancher database (use the delegate message from your log messages):
Then I marked the record as purged and restarted rancher server.
This stopped the spam, but I'm not sure if it had any other effect. So far so good. |
@sra in my case it returns an empty set |
@sankaet try this: |
Thanks. That's worked for me.
|
This should have since been resolved in newer versions of rancher. Please file a new issue if there are any issues surfacing post upgrades. |
Rancher Version:
v1.2.1
Docker Version:
1.11.3
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu Trusty, AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Rancher HA w/ external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Upgraded from v1.1.4 to v1.2.1 and now the Rancher server is logging this error regularly. Possibly an orphaned agent?
Results:
Expected:
The text was updated successfully, but these errors were encountered: