You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2015/04/03 20:39:54 UTC
[jira] [Closed] (TIKA-1592) It seems dbus and x11 server are
invoked, and fails for some reason too
[ https://issues.apache.org/jira/browse/TIKA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Palsulich closed TIKA-1592.
---------------------------------
Resolution: Invalid
Closing as Invalid. Feel free to create additional issues if you run into other problems with Tika!
Thank you for updating with the solution! I'm glad you found it. :) (I'm also glad this wasn't a Tika issue... Ha.)
> It seems dbus and x11 server are invoked, and fails for some reason too
> -----------------------------------------------------------------------
>
> Key: TIKA-1592
> URL: https://issues.apache.org/jira/browse/TIKA-1592
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.7
> Environment: CentOs 6.6, Java 1.7
> Reporter: Michael Couck
>
> Exception running unit tests:
> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
> Is Tika trying to start an x11 server using dbus? Why? This breaks the unit tests, the logging is a gig for each run, and even a 64 core server is 100% cpu during the failure. I am completely confounded. Any ideas?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)