Announcement

**chasky** · 01-14-2009, 01:04 AM

Hi process91, i got the same problem. The origin of my problem was that i start the open xchange service with the script:

/opt/open-xchange/sbin/open-xchange-groupware

This script change the permissions of some files in /opt/open-xchange/ , so you have to make the following:

chown -R open-xchange.open-xchange /opt/open-xchange/

then:
netstat -tulpn
tcp6 0 0 :::8009 :::* LISTEN 10383/java

read this thread

Error 404 | Page not found

http://www.open-xchange.com/forum/showthread.php?p=10684

**process91** · 01-14-2009, 05:07 PM

Same error still

Chasky,

Thanks for your help

I tried your suggestion, but I'm still having the same problem. Here's some output:

ls -l

Code:

drwxr-xr-x 3 open-xchange open-xchange 4096 2009-01-14 09:56 bundles
drwxr-xr-x 4 open-xchange open-xchange 4096 2008-12-30 00:58 etc
drwxr-xr-x 2 open-xchange open-xchange 4096 2008-12-30 00:58 i18n
drwxr-xr-x 2 open-xchange open-xchange 4096 2008-12-30 00:58 lib
drwxr-xr-x 2 open-xchange open-xchange 4096 2008-10-09 06:37 libexec
drwxr-xr-x 2 open-xchange open-xchange 4096 2008-12-30 00:58 sbin

nmap 192.168.1.5

Code:

Interesting ports on my.computer.com (192.168.1.5):
Not shown: 1691 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
25/tcp    open  smtp
53/tcp    open  domain
80/tcp    open  http
110/tcp   open  pop3
111/tcp   open  rpcbind
139/tcp   open  netbios-ssn
143/tcp   open  imap
443/tcp   open  https
445/tcp   open  microsoft-ds
465/tcp   open  smtps
504/tcp   open  citadel
587/tcp   open  submission
993/tcp   open  imaps
995/tcp   open  pop3s
2000/tcp  open  callbook
2020/tcp  open  xinupageserver
2049/tcp  open  nfs
3306/tcp  open  mysql
5900/tcp  open  vnc
6543/tcp  open  mythtv
6544/tcp  open  mythtv
10000/tcp open  snet-sensor-mgmt

The same thing is returned if I nmap 127.0.0.1, and netstat -tulpn also does not show port 8009 as listening.

I had actually found and follows the steps indicated in the thread you mentioned previously but to no avail. The last post indicates that the problem was actually with the ajp.properties file, but I have checked that and my install did not have that issue. Here's my ajp.properties file.

Code:

# AJP Properties
# In this file, the configuration for the AJP implementation can be performed. 
# AJP is the protocol between the mod_jk module of the apache web server and the
# Open-Xchange groupware server (AJP verion 1.3).

# AJP Port
# tcp port where the groupware server listens for incoming AJP requests
AJP_PORT=8009

# initial number of instances held in memory for each available single threaded 
# servlet (single threaded servlets are deprecated and are not used by the 
# open-xchange server)
SERVLET_POOL_SIZE: 1

# Number of AJP server threads which create a client socket on an incoming 
# request. This is the number of threads processing new opened AJP sockets.
# AJP sockets are kept alive by default therefore only one thread is recommended
AJP_SERVER_THREAD_SIZE: 1

# AJP listener pool size
# number of initially created AJP listeners for processing incoming AJP requests
# This pool does grow dynamically but does not go below. 
AJP_LISTENER_POOL_SIZE: 1

# The amount of time in milliseconds a listener is going to wait (or block)
# while waiting to read the initial bytes from web server from input stream
# 0 stands for unlimited and should not be changed because if the server does
# close connections here the sticky sessions would break.
AJP_LISTENER_READ_TIMEOUT: 0

# This property defines, whether mod_jk is used or not, since some
# mod_jk implementations force that the servlet container must not close
# connections. If set to TRUE the property AJP_MAX_NUM_OF_SOCKETS
# will be ignored to avoid closing connections by the servlet container.
AJP_MOD_JK: TRUE

# Defines the max. number of open sockets. Any sockets opened beyond
# will be closed automatically if AJP_MOD_JK is set to FALSE.
AJP_MAX_NUM_OF_SOCKETS: 150

# Defines whether to use ajp connection pool or not. The pool holds instances of
# AJP connection objects. This saves the time to create new objects. 
AJP_CONNECTION_POOL: FALSE

# The ajp connection pool size. This property only takes effect if 
# AJP_CONNECTION_POOL is set to TRUE and defines the number of instances hold
# in the pool. 
AJP_CONNECTION_POOL_SIZE: 100

# Defines whether to use ajp request handler pool or not. The pool holds 
# instances of AJP request handlers. This saves time to create new objects.
AJP_REQUEST_HANDLER_POOL: FALSE

# The ajp request handler pool size. This property only takes effect if 
# AJP_REQUEST_HANDLER_POOL is set to TRUE and defines the number of instances 
# hold
AJP_REQUEST_HANDLER_POOL_SIZE: 100

# Enable/Disable AJP watcher. The watcher is a thread that checks every 
# AJP_WATCHER_FREQUENCY if AJP requests are taking longer than 
# AJP_WATCHER_MAX_RUNNING_TIME. If AJP_WATCHER_PERMISSION is true, those 
# requests will be terminated otherwise logged into the groupware log.
AJP_WATCHER_ENABLED: TRUE

# Enable/Disable AJP watcher permission to stop & re-init system
AJP_WATCHER_PERMISSION: FALSE

# DEFINE MAX AJP LISTENER RUNNING TIME in milliseconds
AJP_WATCHER_MAX_RUNNING_TIME: 60000

# DEFINE MAX AJP WATCHER'S FREQUENCY in milliseconds
AJP_WATCHER_FREQUENCY: 30000

# SET HOST'S UNIQUE JVM ROUTE IMPORTANT FOR LOAD BALANCING. This value is
# added to the cookie JSESSIONID so that mod_jk does know to which server
# the requests to route. This is needed to bind a session to one specific
# Open-Xchange server in a cluster.
AJP_JVM_ROUTE:APP1

# Define if the mandatory first two bytes of an incoming AJP package
# (magic bytes) must exactly match the sequence 0x12 0x34 or if just one byte
# must match at proper position. It is recommended to leave that true.
AJP_CHECK_MAGIC_BYTES_STRICT: TRUE

# DEFINE THE DIRECTORY PATH THAT CARRIES SERVLETS' CONFIGURATION PROPERTIES.
# THE PROPERTIES DEFINED FOR A SERVLET CONSIST OF THREE PARTS:
# 1. THE GLOBAL PROPERTIES DIRECTLY LOCATED IN DIRECTORY PATH SPECIFIED BY
#    THIS PROPERTY. THESE PROPERTIES APPLY TO ALL SERVLET INSTANCES
# 2. THE PATH-SPECIFIC PROPERTIES DEFINED IN A SUBDIRECTORY EQUAL TO
#    SERVLET'S PATH
# 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL
#    TO SERVLET CLASS' CANONICAL NAME WITH THE COMMON ".properties" PROPERTY
#    FILE EXTENSION
# IF THIS VALUE IS LEFT TO "null" THIS PROPERTY FALLS BACK TO DEFAULT PATH:
# "oxgroupwaresysconfdir@/servletConfig"
AJP_SERVLET_CONFIG_DIR: null

# defines the address to which the opened AJP server socket will be bound to.
# A socket to all available interfaces will be bound if set to "*"
AJP_BIND_ADDR=*

# Logs corresponding AJP forward request if an unexpected empty body request
# is detected
AJP_LOG_FORWARD_REQUEST: FALSE

Thanks again for your help!

**mike** · 04-03-2009, 04:35 PM

Did you find a solution? I have exactly the same problem on my test system.

Michael

**process91** · 04-03-2009, 10:30 PM

No, I still have this problem on any system I've setup. It's too bad, I really like everything else about Open-Xchange.

**Martin Heiland** · 04-03-2009, 10:35 PM

Hi,

could you also check this post: http://www.open-xchange.com/forum/showthread.php?t=3184

And just try to chown the whole /opt/open-xchange directory recursive to the open-xchange user, just to be sure. What java version are you using? (java -version).

Greetings

**process91** · 04-03-2009, 10:39 PM

I did chown with the same result. "java -version" returns

java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing)

**process91** · 05-07-2009, 02:23 PM

Still a problem

This is still an issue, any other suggestions? I really am sick of using egroupware, and open-xchange is so much more polished but if it has errors I'm stuck.

**kaliweed** · 07-09-2009, 04:45 PM

AJP is not listening on port 8009

Hi everybody,

I've got the same problem since i updated my openxchange.

AJP port is not listening on port 8009

Have you solved your problem Process91 ?

Thanks,

kaliweed

**process91** · 07-09-2009, 09:50 PM

Still a problem

I never got this figured out. I'm using eGroupware which isn't nearly as nice as Open-Xchange but at least it works.

**Martin Heiland** · 07-10-2009, 12:19 AM

@kaliweed and others, please provide log files that contain error messages, version numbers of all ox packages, java version, operating system and so on, we can't help you by guessing what's going on. Having port 8009 unreachable or HTTP503 popping up usually means that not all services inside ox have been start up which can have various reasons.

**idgl** · 07-12-2009, 07:28 PM

Open-Xchange Server 6 on Ubuntu 8.04

Originally posted by Martin Braun View Post

@kaliweed and others, please provide log files that contain error messages, version numbers of all ox packages, java version, operating system and so on, we can't help you by guessing what's going on. Having port 8009 unreachable or HTTP503 popping up usually means that not all services inside ox have been start up which can have various reasons.

I have the same problem - these messages in /var/log/apache2/error.log:
[Sun Jul 12 18:40:43 2009] [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (127.0.0.1) failed
[Sun Jul 12 18:40:43 2009] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sun Jul 12 18:40:43 2009] [error] proxy: AJP: failed to make connection to backend: 127.0.0.1

I am trying to log in from a Firefox 3.05 browser under FC9 attached to the same LAN as the OX server.

Versions are:
1. Ubuntu 8.04 LTS Server - burned the CD off www.ubuntu.com and installed it.
2. OX installed as per instructions in http://wiki.open-xchange.com/wiki/in...e_Installation. I executed aptitude install for 6.10 as opposed to for SP5.
3. Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
4. All 32 of the open-xchange packages are version 6.8.1-3
5. Apache 2.2.8(ubuntu)

Today I performed a similar install of the OX6 Server on Fedora 9 which worked, as far as logging in with testuser/secret goes, after having had to stop iptables on the server.

Douglas Laing, Johannesburg

**Martin Heiland** · 07-13-2009, 10:12 AM

Hi Douglas,

sadly this apache ajp.log entries only tell us what the browsers already tells you - the backend cannot be reached. Please check the Open-Xchange Server log files for suspicious entries after server startup.

Greetings

**idgl** · 07-13-2009, 12:29 PM

open xchange logs from working FC9 and failing ubuntu systems

I have looked at the logs but cannot see what is wrong - please have a look at them for me.
Thanks - Douglas Laing, Johannesburg

Attached Files

**Martin Heiland** · 07-13-2009, 12:43 PM

Thanks for providing those logs. The ubuntu log seems not to be complete from what i can see - or is that all what is written to the log? The FC9 log looks okay, the user can login but a lot of errors are thrown because the mail account cannot be reached. I suppose FC9 works fine.
If the ubuntu log is "complete" then we may have a problem since not all plug-ins (bundles) are loaded. Please execute the following command on that machine and post it:

Code:

 
/opt/open-xchange/sbin/listbundles
dpkg -la | grep open-xchange

Greetings

Announcement

Error: 503 - Service Temporarily Unavailable

Error: 503 - Service Temporarily Unavailable

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment