Description of problem: It appears virtuoso was essentially DOSing my disk. Machine locked up on disk IO. Version-Release number of selected component: virtuoso-opensource-6.1.6-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_n27607.ini +wait crash_function: hit_next executable: /usr/bin/virtuoso-t kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 hit_next at Dkhashext.c:142 #1 dbs_registry_to_array at regist.c:482 #2 dbs_write_registry at regist.c:502 #3 dbs_cpt_recov at neodisk.c:1698 #4 dbs_from_file at disk.c:3490 #5 wi_open_dbs at disk.c:3572 #6 wi_open at disk.c:3639 #7 srv_global_init at sqlsrv.c:3804 Potential duplicate: bug 713530
Created attachment 712126 [details] File: backtrace
Created attachment 712127 [details] File: cgroup
Created attachment 712128 [details] File: core_backtrace
Created attachment 712129 [details] File: dso_list
Created attachment 712130 [details] File: environ
Created attachment 712131 [details] File: limits
Created attachment 712132 [details] File: maps
Created attachment 712133 [details] File: open_fds
Created attachment 712134 [details] File: proc_pid_status
Created attachment 712135 [details] File: smolt_data
Created attachment 712136 [details] File: var_log_messages
I have a similar problem. After login i receive a /usr/bin/virtuoso-t SIGSEGV. After all the desktop is fucking slow with some freeze-minutes. Sometimes i have to perform a hard-reset to get my computer (i7 16Gb ram) back to work for me. I am using the btrfs, maybe both openvirtuoso and the fs cause a problem. Please help!
It looks like, that virtuoso-opensource is required by KDE. Maybe we'd better adress this problem to the KDE guys. Is noboys @redhat/fedora interested with this issue ???
Yeah, my guess is that this is caused by akonadi. For what it's worth, it hasn't been an issue lately. I'm going to close this as fixed upstream.
Chris, Sorry I didn't see your other comment. I just replied to your last email. I reported this bug while running ext4, so I'm not sure it's a btrfs issue. My guess is that akonadi was maxing out the IO on the hard drive or at least putting a load on it when other processes are running. If you still think this issue is ongoing, let's keep it open. Scott
I also am getting a SEGV from virtuouso-t (same version but on i686) on every login. Have tried to report it using Abrt but that doesn't seem to do anything (the interface is so bad it's hard to tell, but that's another story). The error message is: virtuoso-t[2380]: segfault at 8 ip 0846adfb sp bfa6ee34 error 4 in virtuoso-t[8045000+9fa000]
Due to similar crash I had lodged a report. I had initially thought that it might have occurred due to my home partition filling up to 100%. The concerned bug report is: https://bugzilla.redhat.com/show_bug.cgi?id=1038890 But there was another crash right after I had cleared the home partition creating around 30GB of space & rebooting the system. Reporting through abrt, I got he following comment. --- Running report_uReport --- A bug was already filed about this problem: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=922864
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I ackn that Fedora 18 is over and 19 will be in short... however, I am afraid that this problem is far more frequent that this bug log seem to show up. Actually I'v caught/seen some of my users CLOSING or KILLING the ABRT imediatelly when it come up with the virtuoso stuff... And at coffee break I heard jokes about the virtuoso "tada" (noise that use to do M$ Win when open)... So my guess is that there are far more users with this problem and no one report because the abrt say: problem yet repported... I strongly suggest to reopen the issue. A solution would be really welcome and I know how bad is for the reputation to let "cristalyze" this kind of problems... I am actually realy short in time in order to be able do handle this at full (perso problems/divorce "alla siciliana") and will come later "in force" back on the matter. But for now, I will apreciate if anyone can take from the following hint. ??? mysld vs mariadb ??? here we go. With Fedora 20, I have 6 machines (some i686, some x86_64) and 4 of theses STILL give the seg fault at EVERY login !!! this, if the machine does not completely stop responding for minutes... just when the user is waiting to receive the hand... Realy anoying. 1 of theses machines is OUT OF the problema : dedicated web server / NO graphic services / NO Kde / No akonadi / and the only Virtuoso is the Admin-pianist. 4 machines give (always) SEG FAULT error at login time : - KDE / akonadi ... - mariadb INSTEAD of mysqld (i686 and x86_64) The last one of theses have : - KDE/akonadi/virtuoso but mysqld instead of mariadb and the problem does not show up (to yet ?) (i686) So: since virtuoso seems to be coupled/dependent in KDE to akonadi && since akonadi com installed with "akonadi-mysql" Could not we wonder if there is not some compatibility/bad interraction/issue with mariadb ? pearheaps some one feeling free with mariadb and mysqld could give a look in order to validate / invalidate this track? thanks. Lo.