Error Retrieving Running Agents
Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet Eclipse Newsletter Videos Participate Report a Bug Forums Mailing Lists Wiki IRC How to Contribute Working Groups Automotive Internet of Things LocationTech Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search Help Register Login Home Home» Archived» Test and Performance Tools Platform (TPTP)» Cannot retrieve agents in Eclipse 3.4 Show: Today's Messages :: Show Polls :: Message Navigator Cannot retrieve agents in Eclipse 3.4 [message #139920] Wed, 04 February 2009 17:28 Eric HamacherMessages: 4Registered: July 2009 Junior Member Eclipse 3.4 agntctrl.win_ia32-TPTP-4.5.0 cbe.win_ia32-TPTP-4.5.0 tptp.runtime-TPTP-4.5.0 I downloaded all the necessary dependencies for TPTP as described above. While setting up a remote connection, I get "Error retrieving running agents - see log for more details" when I get click the Agents tab. To do this, I went to Run -> Profile configurations -> New_configuration and configured a remote host under the Host tab. The connection test was successful. No other Agent Controller processes are running outside of Eclipse. I could not locate the log file the message spoke of. Could anybody help me out? Thanks Eric Report message to a moderator Re: Cannot retrieve agents in Eclipse 3.4 [message #140330 is a reply to message #139920] Thu, 12 February 2009 17:00 Eugene ChanMessages: 287Registered: July 2009 Senior Member Hi Eric, EMF dependencies of TPTP is not listed in your list. It is needed to complete a working TPTP dirver. Please refer to the download page for the version of EMF. Did you start any profiling agent as a standalone process for attach in the Agent tab? How about profiling a simply HelloWorld as a Java Application or External Java Application configurations? Does they work for you? The log file of Agent Controller is listed under AC installation/config/servicelog.log. Eugene "Eric Hamacher"
CommunityMarketplaceEventsPlanet EclipseNewsletterVideosParticipateReport a BugForumsMailing ListsWikiIRCHow to ContributeWorking GroupsAutomotiveInternet of ThingsLocationTechLong-Term SupportPolarSysScienceOpenMDM Toggle navigation Bugzilla – Full Text Bug Listing Home | New | Browse | Search | [?] | Reports | Requests | Help | Log In [x] | Forgot Password Login: [x] | Terms of Use | Copyright Agent Bug 198413 Summary: Linux ia32 AC 4.4.0.1 crashes when listing agents via port 10006 Product: z_Archived Reporter: Oliver Schoett
Sign in Pricing Blog Support Search GitHub This repository Watch 130 Star 674 Fork 181 aws/amazon-ecs-agent https://github.com/aws/amazon-ecs-agent/issues/530 Code Issues 72 Pull requests 5 Projects 0 Pulse Graphs New https://github.com/aws/amazon-ecs-agent/issues/488 issue Agent spamming logs with stats error #530 Closed jasonmoo opened this Issue Sep 16, 2016 · 2 comments Projects None yet Labels more info needed Milestone No milestone Assignees No one assigned 2 participants jasonmoo commented Sep error retrieving 16, 2016 • edited Experienced an event in our cluster where servers began running out of disk space. Found several gigs of logs in /var/logs/ecs/ecs-agent.log.YYYY-MM-DD-HH comprising only a few hours of logs. The agent appeared to be using 20-30% cpu in top. After clearing the logs and restarting the agent the server resumed error retrieving running normal function. This happened across several servers in our cluster. A possible external cause is exhausting server resources, however the cause within the agent is unclear. Found several closed pipe errors like the one below preceeding the too many open files errors. Possible path to explore is: connection errors not resulting in connection close. 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: io: read/write on closed pipe 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: dial unix /var/run/docker.sock: socket: too many open files 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: dial unix /var/run/docker.sock: socket: too many open files 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: dial unix /var/run/docker.sock: socket: too many open files 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: dial unix /var/run/docker.sock: socket: too many open files 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4ae447634f6d54: dial unix /var/run/docker.sock: socket: too many open files 2016-09-16T09:31:42Z [WARN] Error retrieving stats for container 408359b3cc6dbe097edbcbbb68833b662da73b9990f52f1cac4
Sign in Pricing Blog Support Search GitHub This repository Watch 130 Star 674 Fork 181 aws/amazon-ecs-agent Code Issues 72 Pull requests 5 Projects 0 Pulse Graphs New issue Too many open files #488 Closed jbergknoff opened this Issue Aug 17, 2016 · 20 comments Projects None yet Labels bug Milestone 1.12.1 Assignees No one assigned 12 participants jbergknoff commented Aug 17, 2016 Yesterday we upgraded our cluster from amzn-ami-2016.03.c-amazon-ecs-optimized to the latest, amzn-ami-2016.03.g-amazon-ecs-optimized. At some point overnight, two of the instances in our cluster (out of ~6 in ASG) began flooding logs of this nature (hundreds per second): Aug 17 07:21:17 Seelog error: open /log/ecs-agent.log.2016-08-17-14: too many open files Aug 17 07:21:17 2016-08-17T14:21:17Z [WARN] Error retrieving stats for container bcbd3d6d2a51f656ec2066e62296010f5432262e1a564678325a60f3e642a575: dial unix /var/run/docker.sock: socket: too many open files The two instances terminated without human interaction (not sure if that's a coincidence of auto-scaling). Near the end, these logs also appeared: Aug 17 07:21:17 2016-08-17T14:21:17Z [CRITICAL] Error saving state before final shutdown module="TerminationHandler" err="Multiple error: Aug 17 07:21:17 0: Timed out waiting for TaskEngine to settle Aug 17 07:21:17 1: Timed out trying to save to disk" We haven't experienced this on previous AMIs. 👍 4 jbergknoff commented Aug 17, 2016 I think this is a duplicate of #478. jbergknoff closed this Aug 17, 2016 Amazon Web Services member samuelkarp commented Aug 18, 2016 @jbergknoff Thanks for opening this. I've taken a look and I think this is actually a separate problem from #478. samuelkarp reopened this Aug 18, 2016 samuelkarp added the bug label Aug 18, 2016 samuelkarp added this to the 1.12.1 milestone Aug 18, 2016 samue