moog67
Has this happened just once? I see it happened around 4am - this is when the ltm syslog service does a reload of the configuration daily (you can double check this is var/log/messages). It looks like the offending daemaon is the mcpd one - and this manages the config on the box...amongst other things.
Does it crash if you update the config or do a config sync?
I'm not sure exactly what might cause this but there is a Known Issue with the mcpd daemon and ltm v10.2.0 - see http://support.f5.com/kb/en-us/solutions/public/12000/100/sol12176.html so I would think about applying a hotfix to see if that sorts the issue.
Hope this helps,
N