We are trying to install OX but the instructions given on your site, here:
... contains many errors and do not work.
For instance, this part:
[[
a good idea is to add the Open-Xchange binaries to PATH:
$ echo PATH=$PATH:/opt/open-xchange/sbin/ >> ~/.bashrc && . ~/.bashrc
]]
There is an extra, erroneous space-dot-space after the &&
Next, this part:
[[
Now we have to initialize the Open-Xchange configdb database. This can
all be done by executing the initconfigdb script.
$ /opt/open-xchange/sbin/initconfigdb --configdb-pass=db_password -a
]]
I have no such file as /opt/open-xchange/sbin/initconfigdb on my system.
So I cannot proceed. Thus I cannot install and evaluate the product
and thus my client cannot decide whether to buy licences from you.
Previously, on my first, test run, I just installed *all* the
Open-Xchange packages with a wildcard. The got me slightly further,
with a huge waste of space, increase in attack-surface and so on.
However, I still could not complete the procedure as described as
necessary components were still missing.
However, getting further through the document revealed additional
errors in the instructions, for example...
This part:
[[
Important: For MAX_MEMORY_FOR_JAVAVM a rule of thumb for simple
installations is half available system memory. For production
environments please consult our Sizing Whitepaper.
$ /opt/open-xchange/sbin/oxinstaller --add-license=YOUR-OX-LICENSE-CODE \
--servername=oxserver --configdb-pass=db_password \
--master-pass=admin_master_password --ajp-bind-port=localhost
--servermemory MAX_MEMORY_FOR_JAVAVM
]]
Apparently it is "important" to set the right amount of memory, but
you do not specify the units to be used. kB? MB? GB? I cannot enter a
number without knowing what units! What if I enter 1024 for 1GB of RAM
but it is in GB - I will have told my server to use a terabyte of RAM.
We don't have that much in all the computers of all the company put
together, I think. What if I enter 1, for 1GB, and I assign it 1MB? I
suspect that will not work at all.
Next:
[[
Now is a good time to configure the way OX will authenticate to your
mail server. Edit the file /opt/open-xchange/etc/mail.properties and
change the com.openexchange.mail.loginSource to use. This is very
important for servers that require your full email address to log in
with.
# adjust com.openexchange.mail.loginSource
$ vim /opt/open-xchange/etc/mail.properties
]]
Apparently, here, $ refers to the admin or root prompt (which of
course is normally a hash sign: #
But # refers to a comment. In a line of commands to type, not in a script! Why?
Next, the logs:
[[
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
]]
This does not work. Firstly, the variable {APACHE_LOG_DIR} is undefined.
I manually hard-coded in the correct path.
Second, the log files on CentOS are called `error_log` and
`access_log`, not `error.log` and `access.log`. That is, underscores
not dots.
With so many errors, the document is nearly useless.
Can we have new instructions please?
... contains many errors and do not work.
For instance, this part:
[[
a good idea is to add the Open-Xchange binaries to PATH:
$ echo PATH=$PATH:/opt/open-xchange/sbin/ >> ~/.bashrc && . ~/.bashrc
]]
There is an extra, erroneous space-dot-space after the &&
Next, this part:
[[
Now we have to initialize the Open-Xchange configdb database. This can
all be done by executing the initconfigdb script.
$ /opt/open-xchange/sbin/initconfigdb --configdb-pass=db_password -a
]]
I have no such file as /opt/open-xchange/sbin/initconfigdb on my system.
So I cannot proceed. Thus I cannot install and evaluate the product
and thus my client cannot decide whether to buy licences from you.
Previously, on my first, test run, I just installed *all* the
Open-Xchange packages with a wildcard. The got me slightly further,
with a huge waste of space, increase in attack-surface and so on.
However, I still could not complete the procedure as described as
necessary components were still missing.
However, getting further through the document revealed additional
errors in the instructions, for example...
This part:
[[
Important: For MAX_MEMORY_FOR_JAVAVM a rule of thumb for simple
installations is half available system memory. For production
environments please consult our Sizing Whitepaper.
$ /opt/open-xchange/sbin/oxinstaller --add-license=YOUR-OX-LICENSE-CODE \
--servername=oxserver --configdb-pass=db_password \
--master-pass=admin_master_password --ajp-bind-port=localhost
--servermemory MAX_MEMORY_FOR_JAVAVM
]]
Apparently it is "important" to set the right amount of memory, but
you do not specify the units to be used. kB? MB? GB? I cannot enter a
number without knowing what units! What if I enter 1024 for 1GB of RAM
but it is in GB - I will have told my server to use a terabyte of RAM.
We don't have that much in all the computers of all the company put
together, I think. What if I enter 1, for 1GB, and I assign it 1MB? I
suspect that will not work at all.
Next:
[[
Now is a good time to configure the way OX will authenticate to your
mail server. Edit the file /opt/open-xchange/etc/mail.properties and
change the com.openexchange.mail.loginSource to use. This is very
important for servers that require your full email address to log in
with.
# adjust com.openexchange.mail.loginSource
$ vim /opt/open-xchange/etc/mail.properties
]]
Apparently, here, $ refers to the admin or root prompt (which of
course is normally a hash sign: #
But # refers to a comment. In a line of commands to type, not in a script! Why?
Next, the logs:
[[
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
]]
This does not work. Firstly, the variable {APACHE_LOG_DIR} is undefined.
I manually hard-coded in the correct path.
Second, the log files on CentOS are called `error_log` and
`access_log`, not `error.log` and `access.log`. That is, underscores
not dots.
With so many errors, the document is nearly useless.
Can we have new instructions please?