Project

General

Profile

Actions
Copy link

Bug #2919

closed

cf-agent seems to keep running for a long time sometimes

Added by Jonathan CLARKE over 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
System techniques
Target version:
2.4.0~rc2
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I'm not sure how to analyze this really, but we occasionnaly see cf-agent running for several hours on a server, and using up resources. cf-execd continues to run new cf-agents with no problem, but the old cf-agent hangs around...

A quick workaround would be to add a promise in the common Technique to kill any cf-agent that's been going for > 12 hours.

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - User story #3013: Create a new cron entry that checks if cf-execd AND cf-agent are running, and if not launches cf-agentReleasedMatthieu CERDA2012-11-19Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON about 12 years ago

  • Assignee deleted (Nicolas PERRON)
Actions
Copy link
 #2

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Actions
Copy link
 #3

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from 2 to Discussion

This seems like a duplicate of #3013

Actions
Copy link
 #4

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from Discussion to Rejected
Actions
Copy link

Also available in: Atom PDF