Capistrano对linked_files和linked_dirs的许多失败状态是什么意思？

Question

OK so all is working perfectly well as far as I can see, but I do see a lot of "failed" status on most of the linked_files and linked_dirs tasks and I am wondering if they deserve any attention. Here are a few examples:

DEBUG [423a17e1] Running [ -L /home/caluebat/www/ravenfort/releases/20160312213815/tmp/pids ] on xxx.xxx.xxx.xxx
DEBUG [423a17e1] Command: [ -L /home/caluebat/www/ravenfort/releases/20160312213815/tmp/pids ]
DEBUG [423a17e1] Finished in 0.470 seconds with exit status 1 (failed).
DEBUG [541d2f8a] Running [ -d /home/caluebat/www/ravenfort/releases/20160312213815/tmp/pids ] on xxx.xxx.xxx.xxx
DEBUG [541d2f8a] Command: [ -d /home/caluebat/www/ravenfort/releases/20160312213815/tmp/pids ]
DEBUG [541d2f8a] Finished in 0.476 seconds with exit status 1 (failed).

I was unable to find any detail on the capistrano official docs and they send either here or the mailing list for questions.

I would appreciate any clarification on the above failures. Thank you very much.

Answer 1

Don't worry about it!

Whenever cap runs a command that returns a non-zero result, it prints the line in red and says "failed". This can be misleading, because it runs a lot of commands just to see what already exists. For instance [ -d foo ] means "Is there a directory named foo?" It's not actually a failure, it's just cap inspecting the target machine to find out what work it needs to do.

If cap hits a real error, it will quit early and you'll get a stack trace and/or actual error message.