On Monday 27 January 2014 09:44 Kevin Krammer wrote:
> On Monday, 2014-01-27, 00:19:13, Thomas Tanghus wrote:
> > On Sunday 26 January 2014 23:48 Kevin Krammer wrote:
> > > On Sunday, 2014-01-26, 23:42:12, Thomas Tanghus wrote:
> > > > The past week or so I get this every 10-20 seconds in/var/log/syslog:
> > > >
> > > > kernel: [168098.800123] virtuoso-t[13981]: segfault at ffffffff ip
> > > > 0851efbb
> > > > sp a7143870 error 7 in virtuoso-t[8048000+aa0000]
> > > >
> > > Can you check if virtuoso is running as more than one user, maybe as a
> > > system daemon?
> >
> > $ ps aux|grep virtuoso
> > tol 15621 0.0 3.2 285344 266420 ? RNl 00:08 0:00
> > /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_lY1670.ini +wait
>
> Is that the PID that is then logged in syslog? I.e. is that the virtuoso
> crashing sometime later?
It doesn't seems so. The PID keeps incrementing both the ones in the process
list and the ones crashing, but they don't seem to be the same.
BTW, the crashing stops if I disable Akonadi Nepomuk Feeder, so I guess it's
somewhat Akonadi related. Or at least the data Akonadi stores in Nepomuk.
> I have no idea on how virtuoso works, but from the posted commandline I'd
> say one thing you could try is to start it manually.
As the processes keep crashing and removing the /tmp/virtuoso_XXXXXX.ini I
grabbed one of the ini files and saved it locally:
[Database]
DatabaseFile=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso.db
ErrorLogFile=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso.log
TransactionFile=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso.trx
xa_persistent_file=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso.pxa
[TempDatabase]
DatabaseFile=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso-temp.db
TransactionFile=/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso-temp.trx
MaxCheckpointRemap=1000
[Parameters]
LiteMode=1
ServerPort=7486
DisableTcpSocket=1
PrefixResultNames=0
ServerThreads=100
NumberOfBuffers=32000
MaxDirtyBuffers=21333
SchedulerInterval=5
FreeTextBatchSize=1000
CheckpointInterval=10
MinAutoCheckpointSize=200000
[I18N]
XAnyNormalization=3
I then shut down Nepomuk from System Settings->Desktop Search and ran:
/usr/bin/virtuoso-t +foreground +configfile ./virtuoso.ini +wait
Which gave:
Mon Jan 27 2014
18:21:47 OpenLink Virtuoso Universal Server
18:21:47 Version 06.01.3127-pthreads for Linux as of Sep 24 2013
18:21:47 uses parts of OpenSSL, PCRE, Html Tidy
18:21:47 Database version 3126
18:21:47 Entering Lite Mode
18:21:47 SQL Optimizer enabled (max 1000 layouts)
18:21:49 Compiler unit is timed at 0.001117 msec
18:21:50 Roll forward started
18:21:50 Roll forward complete
18:21:50 Checkpoint started
18:21:51 Checkpoint finished, log reused
18:21:53 Server online at 7486 (pid 14844)
And then nothing until I closed it by Ctrl-C. No crashes, nothing in syslog.
/home/tol/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-
virtuoso.log had dozens of:
Mon Jan 27 2014
00:39:49 GPF: bitmap.c:693 singleton bm not in use
But that looks rather benign.
--
Med venlig hilsen / Best Regards
Thomas Tanghus
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
