+ Reply to Thread
Results 1 to 10 of 10

Thread: Site settings could not be loaded api error

  1. #1

    Question Site settings could not be loaded api error

    Folks,

    I have a new install of mindtouch core on a Fedora 14 x64 server. The install completes succesfully as does LDAP authentication and everything appears to be great.

    However every few days after very minmimal usage the wiki appears to go offline with the following error :
    Site settings could not be loaded
    We were unable to locate the API to request site settings. Please see below for debugging information. If this is a new install, try refreshing - the API is simply taking its time loading up!

    HTTP Response Status Code: 0
    Operation timed out after 300001 milliseconds with 0 bytes received
    The last entries in the log are as follows (log is at "DEBUG") No new connections register anything on log file


    [harps@PYTHIA ~]$ tail /var/log/dekiwiki/deki-api.log
    2011-03-11 09:56:42,868 [286] DEBUG MindTouch.Dream.Http.HttpTransport - Request
    Handler(GET, http://localhost:8081/deki/license?d...hp&dream.in.ho
    st=10.44.0.226&dream.in.scheme=http&dream.in.origi n=10.44.34.101&apikey=7osga7nu
    ipFD6HLaldOLz18TIOnyGjuo)
    2011-03-11 09:56:42,870 [DispatchThread #24] DEBUG MindTouch.Deki.WikiManagement
    .InstanceManager - retrieving instance for wiki id 'default'
    2011-03-11 09:56:42,873 [DispatchThread #5] INFO DekiWikiService_default - Fini
    shed [GET:/deki/license] [Ok] request-time-ms=4; mysql-queries=2; mysql-time-ms=
    2;
    2011-03-11 09:56:42,873 [DispatchThread #5] DEBUG MindTouch.Deki.Data.MySql.MySq
    lDekiDataSession - concurrent sessions left: 1
    2011-03-11 09:56:42,876 [DispatchThread #24] INFO DekiWikiService_default - Fin
    ished [GET:/deki/license] [Ok] request-time-ms=6; mysql-queries=2; mysql-time-ms
    =3;
    2011-03-11 09:56:42,877 [DispatchThread #24] DEBUG MindTouch.Deki.Data.MySql.MyS
    qlDekiDataSession - concurrent sessions left: 0
    2011-03-11 09:56:42,902 [270] DEBUG MindTouch.Dream.Http.HttpTransport - Request
    Handler(GET, http://localhost:8081/deki/pages/22/...t.format=php&d
    ream.in.host=10.44.0.226&dream.in.scheme=http&drea m.in.origin=10.44.34.101&mode=
    view)
    2011-03-11 09:56:42,903 [DispatchThread #24] DEBUG MindTouch.Deki.WikiManagement
    .InstanceManager - retrieving instance for wiki id 'default'
    2011-03-11 09:56:42,916 [293] DEBUG MindTouch.Dream.Http.HttpTransport - Request
    Handler(GET, http://localhost:8081/deki/pages/22/...t.format=php&d
    ream.in.host=10.44.0.226&dream.in.scheme=http&drea m.in.origin=10.44.34.101&mode=
    view)
    2011-03-11 09:56:42,917 [DispatchThread #10] DEBUG MindTouch.Deki.WikiManagement
    .InstanceManager - retrieving instance for wiki id 'default'
    It appears the process is running

    [harps@PYTHIA ~]$

    [harps@PYTHIA ~]$ sudo /etc/init.d/dekiwiki status
    MindTouch is running: 8699
    [harps@PYTHIA ~]$ sudo /etc/init.d/httpd status
    httpd (pid 1343) is running...
    Mono is up to date and the path to the binary is correct.

    Restarting dekiwiki
    [harps@PYTHIA ~]$ sudo /etc/init.d/dekiwiki stop
    Stopping MindTouch API: mindtouch.host.exe.
    [harps@PYTHIA ~]$ sudo /etc/init.d/dekiwiki start
    Starting MindTouch API: mindtouch.host.exe.
    [harps@PYTHIA ~]$ sudo /etc/init.d/dekiwiki status
    MindTouch is running: 15814
    Restores access.

    If I could figure out why it is falling over I can figure out a fix, but I am not having much joy with the log files at the moment.

    Any ideas ?

    BTW - OS is a vanilla install of Fedora 14 with latest greatest versions of all packages, mindtouch was installed from rpm using the repository created for Fedora 13 : http://repo.mindtouch.com/Fedora_13/

  2. #2

    Default

    Update :

    Wiki has hung again : here is the tail of the log file :

    [harps@PYTHIA ~]$ tail deki-api.log
    tail: cannot open `deki-api.log' for reading: No such file or directory
    [harps@PYTHIA ~]$ tail /var/log/dekiwiki/deki-api.log
    2011-03-11 14:34:07,616 [DispatchThread #15] DEBUG MindTouch.Deki.Data.MySql.MyS
    qlDekiDataSession - concurrent sessions left: 1
    2011-03-11 14:34:07,617 [DispatchThread #15] DEBUG MindTouch.LuceneService.Lucen
    eService - Adding document for 'http://default//@api/deki/files/11' to index
    2011-03-11 14:34:07,628 [DispatchThread #15] DEBUG MindTouch.LuceneService.Lucen
    eService - completed indexing 'http://default//@api/deki/files/11'
    2011-03-11 14:34:07,628 [DispatchThread #15] DEBUG MindTouch.LuceneService.Updat
    eRecordDispatcher - finished dispatch of update record 'http://default//@api/dek
    i/files/11'
    2011-03-11 14:34:07,641 [DispatchThread #26] INFO DekiWikiService_default - Fin
    ished [GET:/deki/pages/95] [Ok] request-time-ms=50; mysql-queries=27; mysql-time
    -ms=30;
    2011-03-11 14:34:07,642 [DispatchThread #26] DEBUG MindTouch.Deki.Data.MySql.MyS
    qlDekiDataSession - concurrent sessions left: 0
    2011-03-11 14:34:07,647 [148] DEBUG MindTouch.Dream.Http.HttpTransport - Request
    Handler(GET, http://localhost:8081/deki/pages/95/...eam.out.format
    =php&dream.in.host=10.44.0.226&dream.in.scheme=htt p&dream.in.origin=10.44.34.101
    )
    2011-03-11 14:34:07,649 [DispatchThread #26] DEBUG MindTouch.Deki.WikiManagement
    .InstanceManager - retrieving instance for wiki id 'default'
    2011-03-11 14:34:07,671 [DispatchThread #26] INFO DekiWikiService_default - Fin
    ished [GET:/deki/pages/95/files,subpages] [Ok] request-time-ms=23; mysql-queries
    =12; mysql-time-ms=15;
    2011-03-11 14:34:07,672 [DispatchThread #26] DEBUG MindTouch.Deki.Data.MySql.MyS
    qlDekiDataSession - concurrent sessions left: 0

  3. #3

    Default

    Any ideas of any debugs or anything else I can do to trouble shoot ? Its just about unusable as it is.

  4. #4
    Join Date
    Apr 2011
    Posts
    61

    Default

    I'm going to check in with our developers and see what we can come up with for you, hang tight.

  5. #5

    Default

    Quote Originally Posted by cathyn View Post
    I'm going to check in with our developers and see what we can come up with for you, hang tight.
    Hi Cathyn,

    Have you heard anything from the dev's ? Im happy to troubleshoot why it would be falling over if I just knew where to look.

  6. #6

    Default

    **bump** ?

  7. #7
    Join Date
    Apr 2011
    Posts
    61

    Default

    Quote Originally Posted by wookietramp View Post
    **bump** ?
    Sorry for the delay - they've been swamped. I'll check with them again.

  8. #8
    Join Date
    Apr 2011
    Posts
    61

    Default

    To confirm, the issue is the site needs to be restarted? Can you please clarify what version of Mintouch and what version of mono you're running. This will help us fix your issue.

  9. #9

    Default

    Quote Originally Posted by cathyn View Post
    To confirm, the issue is the site needs to be restarted? Can you please clarify what version of Mintouch and what version of mono you're running. This will help us fix your issue.
    Running : MindTouch Core (version 10.0.8)

    Mono Version :

    [root@PYTHIA ~]# mono -V
    Mono JIT compiler version 2.6.7 (tarball Tue Mar 15 00:07:37 UTC 2011)
    Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com
    TLS: __thread
    GC: Included Boehm (with typed GC and Parallel Mark)
    SIGSEGV: altstack
    Notifications: epoll
    Architecture: amd64
    Disabled: none

    To resolve the issue I have to restart mindtouch:

    /etc/init.d/dekiwiki restart

    -----

    As this issue was seriously affecting the credibility of the solution I have migrated the wiki to the VMWare Appliance running of of an ESX server for our live environment. I still have the other machine running if you need me to do any diags.

  10. #10
    Join Date
    Apr 2011
    Posts
    61

    Default

    We recommend you upgrade to 2.10.2 as 2.6.7 is not supported.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts