search

filterfish / smith2

A complete rewrite of Smith
12 stars 7 forks source link

Running agency with -d causes agents not to startup #32

Open maetl opened 9 years ago

maetl commented 9 years ago

agency -d behaves differently to agency when starting agents—agents never make it past the initial startup phase.

Steps to reproduce:

  1. Startup Smith using agency -d
  2. Start an agent with smithctl start {AgentName}
  3. The logs for that agent don’t go past Transition [state]: :checked -> :starting
  4. Running smithctl list -la shows the agent as starting with pid 0 and a date of 1970/01/01 10:00:00
  5. The starting agent remains in that state indefinitely and doesn’t time out.

When starting an agent with agency running in the foreground, this problem doesn’t happen.

filterfish commented 9 years ago

The agent tries to search the directory hierarchy from the current working directory for a config file but given that the agent has it's current working directory to / it can't find it.