LogicalDoc Install Instructions

I been faced with a simple task to install LogicalDoc on a Centos Machine which is actually  a XenServer Virtual Machine. The LogicalDoc install instruction are how helpful i leave the users of the blog to decide. The simple job became a roller coaster ride and i was not able to find answer to some of the questions.

Lets get started on How we install LogicalDoc on a XenServer VM. First step offcourse is to install the XenServer. We are using XenServer 6.1 on a Dell R720 Machine with Two Quad Core CPU and 64 Gb Rams. Yes it is very mean machine.

Any way, the LogicalDoc is to be installed on CentOS with 2 Cores out of 24 Cores available in XenServer with 8 Gb of Ram. Installing a CentOS on a VM is again out of scope of this post. There are a number of examples on how to install a CentOS on XenServer VM. We are using CentOS 6.3.

If you land on this page http://dist.logicaldoc.com/dist/logicaldoc/ and read about dependencies i.e. Java SDK 6+ aka jdk6u then you are for a surprise as you find one of the important thing is missing in the instructions in this page http://dist.logicaldoc.com/dist/logicaldoc/howto/cross-platform.html

Off course, you need to install the jdk6u+ but once you try to fire that from the command line you will not be able to do that.

Reason is this page is not complete instructions. Here is the complete instruction for Linux install from this page http://help.logicaldoc.com/en/installation/install-on-linux.html

Install on Linux

On Linux the MySQL automatic installation is not provided as for Windows. So make sure to have a MySQL 5.0(or later) up and running in your system.
On Linux we suggest to install and execute LogicalDOC as root user, to make sure to log-in as root before continuing, since this guide assumes you perform all thing as root.

Also since the LogicalDOC installer is a graphical application, you need to launch it from KDE or GNOME.

It would have been nice if the same are mentioned in the same page of link is given. Any way, first Road Block was solved using VNC for XenServer. Follow this post to set that up

https://maanasroyy.wordpress.com/2012/12/19/vnc-server-on-xen-server-centos-vm/

Once you are done the other important thing is you need to install this as root user. Do not attempt as any other user you might encounter this error.

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: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

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: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

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: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

And the LogicalDoc Enterprise support team will not be able to help you citing liability issues which I fail to understand what it is.

Any way once this is out of the way, It is pretty much straight install. It is recommended that you make mysql db and user account to manage that db in advance as the same will be required during install.

Other thing you can change is the tomcat port which defaults to 8080, 8443. Since we are running a VM i changed it to 80 and 443.

Once done then you need to start the tomcat using the start.sh script located in tomcat/bin folder. I m still to find a way to put in init.d to respawn on failure

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s