2015-07-26, 21:18
(2015-07-26, 19:17)Milhouse Wrote: Then you might want to install it ASAP as your log is unfortunately worthless without it.
Hello to you too Millhouse,
Well, that really is very unfortunate of me... maybe kodi developers should take that eager quest for stacktraces instead of just plain logs and also package a debugger along with it, as a pre-requisite/dependency, that way kodi wouldn't 'spuriously' spew out worthless logs (when times like these would arise)... that is only a suggestion... from a faithful dumb user... not a sacred programmer... oh well...
Quote:There is currently no indication from the log that the crash of Kodi is SQL related...
Definitely right on that, it could be anything else. Nevertheless it consistently happened with mariadb structure being queried from kodi. Take a look at these if you mind.---> sprunge paste text facility
Quote:Also, you started out saying that the MariaDB server is crashing yet you are posting a Kodi crashlog. Which is it?
Millhouse did you actually read this thread in its entirety? I posted kodi crashlog to address fritsch's request. I did know that those were almost worthless. But those where the ones I had. What better way to prove it than to state what I had?
I know also that these systemd logs may be worthless now, but they are also all I got at the moment from the server side from when those crashes happened.
Quote:If the MariaDB process is crashing then you need to capture the stacktrace from the MariaDB process
Quote:you need...?
Wouldn't a "I need you to" be more straightforward?
Besides... you are right... I was the one interested in having this working... Guess what? It is already working.
And... Hey... what's a forum for after all? Guess I should come to this kodi forum more often so that maybe I could find out the answer to that exact question...
Yours.