Announcement

Collapse
No announcement yet.

Get stuck when starting open-xchange-groupware deamon

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Martin Heiland
    replied
    Originally posted by curVV View Post
    You obviously haven't heard of Schrodinger's Cat...
    Nope, not since it's dead...
    Last edited by Martin Heiland; 07-25-2007, 07:08 PM.

    Leave a comment:


  • curVV
    Guest replied
    Originally posted by Martin Braun View Post
    Keep in mind: If you shut down a service, it is not running anymore.
    You obviously haven't heard of Schrodinger's Cat...

    anyway, i admit that i'm a linux n00b. thanks for your help.

    Leave a comment:


  • Martin Heiland
    replied
    Er... ok, this are some basics about linux services...

    When you call the open-xchange-groupware script, the groupware is powered on, it does not hang or anything, there is just no output to the console. This is when you get "WebDAV Version: 0" which indicates that every thing is working. If you CTRL+C the open-xchange-groupware script, the groupware will be killed which gives you this 503 errors. I suppose you want to put the groupware service as a background service. Just append a " &" to the open-xchange-groupware command to start it in the background.

    Keep in mind: If you shut down a service, it is not running anymore.

    Greetings.
    Last edited by Martin Heiland; 07-25-2007, 06:13 PM.

    Leave a comment:


  • curVV
    Guest replied
    from http://my-server/servlet/webdav.version i now get:

    WebDAV: 0

    Before i was getting 503 after ctrl-c when /opt/open-xchange/sbin/open-xchange-groupware just hangs there like this:

    Code:
    root@fsn-org-xc:/# /opt/open-xchange/sbin/open-xchange-groupware
    /opt/open-xchange /
    if i leave it like that i now get: WebDAV: 0
    ...

    Leave a comment:


  • curVV
    Guest replied
    the only errors i see are those ajax ones.

    workers.properties:
    worker.ajp13_worker.port=8009
    worker.ajp13_worker.host=localhost
    worker.ajp13_worker.type=ajp13

    Leave a comment:


  • Martin Heiland
    replied
    Does the open-xchange.log.0 tells you anything interesting at the moment the 503 occurs?
    Does mod_jk use the same port as the groupware (8009)?

    Leave a comment:


  • curVV
    Guest replied
    only error i get in /var/log/apache2/mod_jk.log is:

    [Wed Jul 25 13:48:30 2007] [19210:38592] [error] ajp_service::jk_ajp_common.c (1794): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13_worker failed

    Leave a comment:


  • curVV
    Guest replied
    sorry ox.conf pointed to wrong workers.properties. i now get login screen at http://my-server
    and the following at http://my-server/servlet/webdav.version :

    Code:
    [B]Service Temporarily Unavailable[/B]
    
    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
    [I]Apache/2.2.3 (Ubuntu) mod_jk/1.2.18 PHP/5.2.1 Server at 192.168.0.230 Port 80[/I]
    it's a 503 so gotta search for mod_jk error...

    Leave a comment:


  • Martin Heiland
    replied
    The open-xchange installer does not change anything at you apache configuration. The Build process of the GUI just copies the GUI to /var/www by default after building it. I suppose this is something distribution specific and you should start by debugging services like apache/modjk and so on. Please make sure that tomcat is not running when using open-xchange.

    Leave a comment:


  • curVV
    Guest replied
    Hi MArtin,

    No, I can't access http://my-server/servlet/webdav.version - it times out.

    After open-xchange installation i cannot acces root of server at http://my-server

    Apache works though, as I get a "It Work's" at http://my-server/apache2-default/
    Last edited by Guest; 07-25-2007, 08:01 AM.

    Leave a comment:


  • Martin Heiland
    replied
    Hi,

    those ajax errors are about the missing classes for the admin gui which is not yet available at the public CVS. But these warnings do not create any problems from my experience, they are just missing plugins.

    The posted logfile does not show up anything critical as far as i can see.

    curVV, are you able to access the servlets? Just try to browse to:



    This should bring up some WebDAV information, if it brings up some kind of 503 or 404 error there's a problem with the apache configuration (mod_jk)

    Leave a comment:


  • curVV
    Guest replied
    Hi, I'm having same problem:

    Code:
    root@fsn-org-xc:/var/log/open-xchange# /opt/open-xchange/sbin/open-xchange-groupware
    /opt/open-xchange /var/log/open-xchange
    I see some AJAX errors in the open-xchange.log.0 file. don't really know what it all means. please have a look....
    Attached Files

    Leave a comment:


  • mosquito
    Guest replied
    Sorry, now I see the error on login page
    Code:
    split has no properties
    makeSplitCallback(undefined, " bottom ", false)global.js (line 3133)
    initAll2(login())global.js (line 3227)
    (no name)()global.js (line 2361)
    alt()global.js (line 162)
    (no name)()global.js (line 2379)
    [Break on this error] var parent = split.parentNode;
    Last edited by Guest; 07-06-2007, 12:47 AM.

    Leave a comment:


  • mosquito
    Guest replied
    I downloaded the new source files for open-xchange, admindeamon and GUI from CVS, build them and now I'm geting 503 error, service temporarily unavailable, when I'm trying to log in.. It doesn't seems to be any JS error on the login page.

    Leave a comment:


  • Martin Heiland
    replied
    Mh, ok then this error is fixed in CVS. Does some kind of JS error occur when loading the page? Try firebug (www.getfirebug.com) which is a nice debugging tool for js/html/css.

    Leave a comment:

Working...
X