Re: [gentoo-user] nepomuk/virtuoso using 100% cpu
On Tuesday 10 May 2011 15:59:22 Alan McKinnon wrote: Since the upgrade to kde-4.6.3, nepomuk and/or virtuoso insists on giving my cpu a stress workout. usage is pegged at 100% and .xession-errors is full of junk like this: /usr/bin/nepomukservicestub(13816) Soprano: SQLExecDirect failed on query 'sparql select distinct ?r ?reqProp1 where { { ?r http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#to ?v2 . ?v2 http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hasEmailAddress ?v3 . ?v3 http://www.semanticdesktop.org/ontologies/2007/03/22/nc' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ074: Line 1: SP030: SPARQL compiler, line 1: syntax error at '' before 'http:' at '' immediately before end of statement) and this: /usr/bin/nepomukservicestub(13066) Soprano: SQLExecDirect failed on query 'sparql uboku' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ074: Line 1: SP030: SPARQL compiler, line 1: syntax error at 'uboku') kdepim is 4.4.11.1. Everything else is at latest unstable. I remember having to deal with this once before with an ill-fated experiment at using kdepm-4.5.95, but cannot for the life of me find what I did to fix it. Anyone have some pointers? This bug: https://bugs.kde.org/show_bug.cgi?id=263730 It says that if If virtuoso is killed while nepomuk indexes the indexing does not stop and nepomuk spams the .xsession-errors file. Is your virtuoso running? Have you tried running kdedebug --off area to see if the error logging stop? I am just updating kde on an old machine (only runs sqlite instead of mysql) and hope I will not have such problems - or worse! -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] nepomuk/virtuoso using 100% cpu
Apparently, though unproven, at 22:53 on Tuesday 10 May 2011, Mick did opine thusly: On Tuesday 10 May 2011 15:59:22 Alan McKinnon wrote: Since the upgrade to kde-4.6.3, nepomuk and/or virtuoso insists on giving my cpu a stress workout. usage is pegged at 100% and .xession-errors is full of junk like this: /usr/bin/nepomukservicestub(13816) Soprano: SQLExecDirect failed on query 'sparql select distinct ?r ?reqProp1 where { { ?r http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#to ?v2 . ?v2 http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hasEmailAddress ?v3 . ?v3 http://www.semanticdesktop.org/ontologies/2007/03/22/nc' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ074: Line 1: SP030: SPARQL compiler, line 1: syntax error at '' before 'http:' at '' immediately before end of statement) and this: /usr/bin/nepomukservicestub(13066) Soprano: SQLExecDirect failed on query 'sparql uboku' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ074: Line 1: SP030: SPARQL compiler, line 1: syntax error at 'uboku') kdepim is 4.4.11.1. Everything else is at latest unstable. I remember having to deal with this once before with an ill-fated experiment at using kdepm-4.5.95, but cannot for the life of me find what I did to fix it. Anyone have some pointers? This bug: https://bugs.kde.org/show_bug.cgi?id=263730 That has a familiar ring to it. Not quite the full answer though, I'm hoping that will come after a restful night's sleep. It says that if If virtuoso is killed while nepomuk indexes the indexing does not stop and nepomuk spams the .xsession-errors file. Is your virtuoso running? Yes. I'd been having problems with this cpu usage most of the day, but I could live with it - any app that needed to do stuff would receive cpu time with a short latency lag. At the end of the work day, I suspended as normal and looked closer into it at home. I can't swear to it, but I'm certain virtuoso was running. It definitely was running (and the problem as a whole got much worse) after logging out of kde and logging back in. Oddly enough, manually killing kontact and everything relating to akonadi, nepomuk and virtuoso then restarting them made the issue go away. Next step I suppose is to log out and in again and see what gives then. Have you tried running kdedebug --off area to see if the error logging stop? I don't have such an app as kdedebug. What package provides it? I am just updating kde on an old machine (only runs sqlite instead of mysql) and hope I will not have such problems - or worse! -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] nepomuk/virtuoso using 100% cpu
Alan McKinnon writes: Apparently, though unproven, at 22:53 on Tuesday 10 May 2011, Mick did opine thusly: Have you tried running kdedebug --off area to see if the error logging stop? I don't have such an app as kdedebug. What package provides it? Bash, with 'alias kdedebug=kdebugdialog' in .bashrc. Wonko
Re: [gentoo-user] nepomuk/virtuoso using 100% cpu
* Alan McKinnon alan.mckin...@gmail.com [110510 17:26]: Apparently, though unproven, at 22:53 on Tuesday 10 May 2011, Mick did opine thusly: [SNIP] Have you tried running kdedebug --off area to see if the error logging stop? I don't have such an app as kdedebug. What package provides it? I think he meant kdebugdialog (from kde-base/kdebugdialog) Todd I am just updating kde on an old machine (only runs sqlite instead of mysql) and hope I will not have such problems - or worse! -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] nepomuk/virtuoso using 100% cpu
On Tuesday 10 May 2011 23:00:30 Alex Schuster wrote: Alan McKinnon writes: Apparently, though unproven, at 22:53 on Tuesday 10 May 2011, Mick did opine thusly: Have you tried running kdedebug --off area to see if the error logging stop? I don't have such an app as kdedebug. What package provides it? Bash, with 'alias kdedebug=kdebugdialog' in .bashrc. Yes, apologies - meant to write kdebugdialog, but was getting too late last night for the synapses to reach the keyboard accurately! o_O -- Regards, Mick signature.asc Description: This is a digitally signed message part.