Reading Solo system logs

[tcr3dr]

We need a section in "Troubleshooting" about reading and consuming Solo system logs.

• What process monitors logs? (syslogd?)
• Where are logs located? (/log/ ?)
• What processes generate what logs?
• What happens when the log directory is full?

[tcr3dr]

http://ffc6904fed514b42b88f87926328069c5c8149f4.s3-website-us-east-1.amazonaws.com/starting-troubleshooting.html

[tcr3dr]

Nick just asked if we know how to get the logs of Python scripts. Would be good to include also.

[tcr3dr]

@mrpollo Do you know who would be appropriate to pull in to fill some of this content?

[mrpollo]

Can you clarify on "logs of python scripts"? do you mean the smart shots?

Probably @johnfinley can confirm all of this.

[tcr3dr]

Particularly, if shotManager.py dies, where is the Python log one would dig into to get at it.

John, for sure, but also if anyone can help write the section in some detail, that would be helpful.

[eliao]

John can talk about the other logs, but here is my contribution:

Both Artoo/Solo logs are in /log. They roll every boot, such that the latest log is always .log, next is .log.1, .log.2, etc. We only save 20 logs, so filling up the logs should not be an issue.

ShotManager logs are named shotlog.log.n and contain various high level events triggered by the shots. If it happens to crash, in most cases the exception and callstack will be written to this log as the last event.

[tcr3dr]

Thanks @eliao! Added your content. 822dc87

Nominating this for a non-blocker considering the basics are covered.

[tcr3dr]

Also see #202

[franknitty69]

does advanced-logs satisfy this? if so can this be closed?

http://dev.3dr.com/advanced-logs.html