[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Strange behavior nepomuk/virtuoso: virtuoso-t segfault



Hi all,

I'm experiencing some troubles with nepomuk/virtuoso and I find it hard to 
start tackling the problem so I was hoping you might be able to help.

I run an up to date Wheezy system with the following kernel: Linux glimsplace 
3.2.0-2-686-pae #1 SMP Sun May 13 07:51:23 UTC 2012 i686 GNU/Linux


Every time I reboot the computer and login to KDE (clean session) I'm greeted 
with a crash of KDE Daemon (backtrace: http://pastebin.com/Pn5Qpjk5), shortly 
after followed by a crash of Nepomuk service hub (backtrace only mentions 
segfault), and sometimes another crash of a Nepomuk related program.

Meanwhile dmesg becomes flooded with messages like:
[  903.284711] virtuoso-t[14550]: segfault at ffffffff ip 0846818c sp a4a58580 
error 6 in virtuoso-t[8048000+985000]
[  915.942372] virtuoso-t[14888]: segfault at ffffffff ip 0846818c sp a47fb580 
error 6 in virtuoso-t[8048000+985000]
[  930.497110] virtuoso-t[14896]: segfault at ffffffff ip 0846818c sp a4abb580 
error 6 in virtuoso-t[8048000+985000]
[  944.587733] virtuoso-t[15297]: segfault at ffffffff ip 0846818c sp a4a5e580 
error 6 in virtuoso-t[8048000+985000]
[  958.400195] virtuoso-t[15674]: segfault at ffffffff ip 0846818c sp a499a580 
error 6 in virtuoso-t[8048000+985000]
[  972.318188] virtuoso-t[16064]: segfault at ffffffff ip 0846818c sp a4aaf580 
error 6 in virtuoso-t[8048000+985000]
[  986.541229] virtuoso-t[16075]: segfault at ffffffff ip 0846818c sp a43ea580 
error 6 in virtuoso-t[8048000+985000]
[ 1000.312140] virtuoso-t[16453]: segfault at ffffffff ip 0846818c sp a487d580 
error 6 in virtuoso-t[8048000+985000]
[ 1014.944242] virtuoso-t[16830]: segfault at ffffffff ip 0846818c sp a487d580 
error 6 in virtuoso-t[8048000+985000]
[ 1028.950065] virtuoso-t[16851]: segfault at ffffffff ip 0846818c sp a49e0580 
error 6 in virtuoso-t[8048000+985000]
[ 1042.638704] virtuoso-t[17214]: segfault at ffffffff ip 0846818c sp a49e0580 
error 6 in virtuoso-t[8048000+985000]
[ 1056.386821] virtuoso-t[17589]: segfault at ffffffff ip 0846818c sp a42a4580 
error 6 in virtuoso-t[8048000+985000]
[ 1070.230935] virtuoso-t[17595]: segfault at ffffffff ip 0846818c sp a4abb580 
error 6 in virtuoso-t[8048000+985000]
[ 1081.873626] virtuoso-t[17963]: segfault at ffffffff ip 0846818c sp a4c77580 
error 6 in virtuoso-t[8048000+985000]

Similar messages also appear in /var/log/syslog:
May 28 11:01:58 glimsplace kernel: [ 1028.950065] virtuoso-t[16851]: segfault 
at ffffffff ip 0846818c sp a49e0580 error 6 in virtuoso-t[8048000+985000]
May 28 11:02:12 glimsplace kernel: [ 1042.638704] virtuoso-t[17214]: segfault 
at ffffffff ip 0846818c sp a49e0580 error 6 in virtuoso-t[8048000+985000]
May 28 11:02:25 glimsplace kernel: [ 1056.386821] virtuoso-t[17589]: segfault 
at ffffffff ip 0846818c sp a42a4580 error 6 in virtuoso-t[8048000+985000]
May 28 11:02:39 glimsplace kernel: [ 1070.230935] virtuoso-t[17595]: segfault 
at ffffffff ip 0846818c sp a4abb580 error 6 in virtuoso-t[8048000+985000]
May 28 11:02:51 glimsplace kernel: [ 1081.873626] virtuoso-t[17963]: segfault 
at ffffffff ip 0846818c sp a4c77580 error 6 in virtuoso-t[8048000+985000]
May 28 11:03:03 glimsplace kernel: [ 1093.720221] virtuoso-t[18330]: segfault 
at ffffffff ip 0846818c sp a49e0580 error 6 in virtuoso-t[8048000+985000]
May 28 11:03:17 glimsplace kernel: [ 1107.650734] virtuoso-t[18340]: segfault 
at ffffffff ip 0846818c sp a4abb580 error 6 in virtuoso-t[8048000+985000]
May 28 11:03:30 glimsplace kernel: [ 1121.308906] virtuoso-t[18701]: segfault 
at ffffffff ip 0846818c sp a4a69580 error 6 in virtuoso-t[8048000+985000]

virtuoso-t and nepomukservices also enjoy to increase the load of the system. 
The load average is 1.75, 1.61, 1.20 on a dual core processor, with those two 
as main contributers.

When I look at the Nepomuk/Strigi server configuration I see that Strigi 
service is not running.

After some googling I found this bug: 
https://bugs.kde.org/show_bug.cgi?id=286690
that looks similar to my problem, however that should be fixed in KDE 4.7.4.

Anyone that experiences the same problems or that can help me to tackle this?

Cheers,

Robert


Reply to: