Is it possible to get logs from a 3850 Cisco member switch in a stack?

[TechGromit1]

%STACKMGR-1-STACK_LINK_CHANGE: MEMBER: 4 stack-mgr:  Stack port 2 on switch 4 is down
%STACKMGR-1-STACK_LINK_CHANGE: STANDBY:2 stack-mgr:  Stack port 1 on switch 2 is down  (OC-SWTCH)
%STACKMGR-6-SWITCH_REMOVED: STANDBY:2 stack-mgr:  Switch 3 has been removed from the stack.

I recieved errors on a 3850 switch 3 in my stack, it's removed from my stack and after 5 minutes it comes back up. I want to know what the switch was doing for those 5 minutes, is it possible to get the log files for only switch 3? Telneting to the switch stack or connecting a console cable directly to switch 3 only gives me the logs for master switch logs. Ideally when a switch reconnects to a stack, the master switch should ask the joining switch for it's logs, and merge them into it's own logs so it has a record of the switch did when it wasn't communitating.

[Brian Schultz]

Were you able to determine what caused this issue?  I'm having an identical problem where one 3850 in a stack is rebooting randomly, but unable to determine why.

[TechGromit]

I never determined the specific cause of the issue since I was unable to get the logs for switch 3, but I inserted the 2nd power supply into the switch and connected the power interconnect cables between all the switches. This resolved the issue, so I'm going to say the power supply was the issue. If you don't have two power supplies for each switch, I would connect the power interconnect cables for switch stacks. You can connect the cables without causing the switch to reboot, unlike data interconnect cables, which do reboot the switches when connected.

[Brian Schultz]

Thanks.  Turned out to be power related in my case as well.  

On a side note, we did discover there is a way to view logs from each switch by issuing a 'show crashinfo-1, show crashinfo-2, etc.'