Ampath use the latest LTS ubuntu server in a production settings :) The steps that you need to do to clean up previous OpenMRS installation are: - remove the runtime properties - remove the database - remove the database user that gets created by previous wizard (usually it's openmrs_user).
I think you didn't remove the database user from previous wizard. That's why you're getting the failure on creating database user step :) And I tried using root in the runtime properties and gets the same connection issue a while ago. On Tue, Feb 21, 2012 at 4:30 AM, Mhawila <[email protected]> wrote: > Hey Charles, > I have tried to go through the entire thread but, for some reason I do not > seem to catch the possible reason for the failure. I am not saying that I am > an expert but I have gone through this kind of stuff several times. > > Can you post your machine specs and then explain in brief how you start > doing the install until it fails > > regards, > Willa. > > On 02/21/2012 12:40 AM, Charles C. Chou wrote: > > This is the latest openmrs.war I downloaded from the openmrs.org site, > titled OpenMRS 1.8.3 dated 13-December-2011. > > I have tried everything I could think of, even re-installed tomcat with the > 6.0.29 version, all with the same result. If I remove the openmrs database > and the .OpenMRS directory I get the install stuck in create database user > with the error I reported in my first post on 2/8: > > Create database user > > Number of actions completed so far: 2 > > Server log file output: > WARN - OpenmrsUtil.getRuntimeProperties(2321) |2012-02-20 11:32:56,465| > Unable to find a runtime properties file. Initial setup is needed. View the > webapp to run the setup wizard. > WARN - OpenmrsUtil.getRuntimeProperties(2274) |2012-02-20 11:32:56,767| > Unable to find a runtime properties file at > /usr/share/apache-tomcat-6.0.29/openmrs-runtime.properties > WARN - OpenmrsUtil.getRuntimeProperties(2304) |2012-02-20 11:32:56,768| > Unable to find properties file: > /usr/share/tomcat6/.OpenMRS/openmrs-runtime.properties > WARN - OpenmrsUtil.getRuntimeProperties(2321) |2012-02-20 11:32:56,769| > Unable to find a runtime properties file. Initial setup is needed. View the > webapp to run the setup wizard. > ERROR - Context.getServiceContext(253) |2012-02-20 11:33:34,948| > serviceContext is null. Creating new ServiceContext() > > if I remove the openmrs database, manually create the > openmrs-runtime.properties file (with root username and password) > under.OpenMRS, restart tomecat and re-deploy the openmrs.war file, click on > the openmrs app I immediately get the throw-up I reported before regarding > failure to connect to database. > > Again, am I the only person trying to install this on a Linux server? > > On 2/20/2012 9:39 AM, Ben Wolfe wrote: > > The standalone works on linux too. :-) > > If root user gives you that error then there is something else going on. > > 1) Which version of openmrs are you using? > 2) Are you sure the database you're connecting to is either empty of all > tables or non existent when you start the wizard? > > Ben > > On Mon, Feb 20, 2012 at 2:12 PM, Charles C. Chou <[email protected]> wrote: >> >> Thanks, Ben. I already had the standalone running the first time I tried >> the install. I wanted to set up a real environment, with server being linux >> as it is the dominant platform for web servers. >> >> I have tried manually creating the properties file with root login and it >> gave the connection error (see my earlier post on 2/17 below.) >> >> If I am the only person having issues with Linux install then I will just >> keep trying different things. >> >> Regards, >> Charles Chou >> >> On 2/20/2012 8:39 AM, Ben Wolfe wrote: >> >> Have you tried just downloading and using the standalone? >> https://wiki.openmrs.org/display/docs/OpenMRS+Standalone >> >> If you are manually creating the file the easiest solution is to use your >> root username/pw. If you want a new user, you have to create the user in >> the dbms, give it rights to the new db, then use that in the RP file. >> >> The catalina file looks like its logging the deployment server, not >> necessarily the webapps. Is it writing to your system log for those? >> >> Ben >> >> On Mon, Feb 20, 2012 at 11:12 AM, Charles C. Chou <[email protected]> wrote: >>> >>> So when you manually create the properties file to bypass the install >>> bug, what username/password should you use? Remember this is at install time >>> and the database is yet to be created. >>> >>> Here are the 2 log files from 2/17. You will see the numerous failed >>> attempts. >>> >>> BTW my Linux distro is fedora but I believe the packages are the same as >>> ubuntu. >>> >>> >>> On 2/20/2012 5:42 AM, Ben Wolfe wrote: >>> >>> Nope, not encrypted, thats just what our randomly generated passwords >>> look like! :-) >>> >>> The wizard uses "openmrs_user" by default when creating a new user. That >>> user will /only/ have permissions on the database you're creating, not on >>> all databases. If you want a user with permissions on all, you have edit >>> that user or use the root user in your RP file. So if you're trying to use >>> a user that was created previously, that user might not have permission to >>> read the new db. >>> >>> The default install of Tomcat on ubuntu has several log files, perhaps >>> you were looking at one of those bogus ones? Can you can send the one(s) >>> you found for confirmation? (I really don't like the setup of tomcat on >>> ubuntu with apt-get, so I always manually download and unzip into the /opt >>> folder.) >>> >>> Ben >>> >>> On Mon, Feb 20, 2012 at 10:16 AM, Charles C. Chou <[email protected]> wrote: >>>> >>>> The location of the properties file is in /usr/share/tomcat6/.OpenMRS >>>> and I had saved a copy of the generated one from that one time the >>>> installation was successful (which was a fluke as I manually created >>>> openmrs-runtime-properties which was wrong). Here is the content of that >>>> file: >>>> >>>> [cchou@localhost .OpenMRS]$ cat openmrs-runtime.properties >>>> >>>> #Auto generated by OpenMRS initialization wizard >>>> #Wed Feb 08 09:41:46 HST 2012 >>>> module.allow_web_admin=true >>>> >>>> connection.url=jdbc:mysql://localhost:3306/openmrs?autoReconnect=true&sessionVariables=storage_engine=InnoDB&useUnicode=true&characterEncoding=UTF-8 >>>> connection.username=openmrs_user >>>> auto_update_database=false >>>> connection.password=t&y7p43LDYjy >>>> >>>> Notice the username and password created by the install program. BTW the >>>> username should be just openmrs, not openmrs_usr and the password is >>>> obviously encrypted. >>>> >>>> If you like I can send you the tomcat logs. There is no info on where it >>>> was looking for the properties file. >>>> >>>> Thanks, >>>> Charles Chou >>>> >>>> >>>> On 2/20/2012 4:43 AM, Ben Wolfe wrote: >>>> >>>> Can you check the tomcat server logs? They should write out where >>>> openmrs is looking the runtime properties file. >>>> >>>> The password in the RP file does not need to be encrypted, it is plain >>>> text. This is why we tell users to physically protect their machine. >>>> (Technical explanation: That password needs to be unhashable by openmrs to >>>> be used, so encrypting it there would be a false sense of security) >>>> >>>> Can you test the connection manually using the username/password you are >>>> putting in the file? Also make sure mysql is running, sometimes it doesn't >>>> start up automatically. >>>> >>>> Ben >>>> >>>> On Fri, Feb 17, 2012 at 7:47 PM, Charles C. Chou <[email protected]> wrote: >>>>> >>>>> There is no other .OpenMRS in the user home directory. >>>>> >>>>> Now the old trick I used by manually creating the >>>>> openmrs-runtime.properties doesn't work anymore. I think the connect >>>>> password needs to be encrypted or something. I get the following errors >>>>> each >>>>> time: >>>>> >>>>> java.lang.RuntimeException: Error occurred while trying to get the >>>>> updates needed for the database. Unable to get a connection to the >>>>> database. >>>>> Please check your openmrs runtime properties file and make sure you have >>>>> the >>>>> correct connection.username and connection.password set >>>>> at >>>>> org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:578) >>>>> at >>>>> org.openmrs.util.DatabaseUpdater.updatesRequired(DatabaseUpdater.java:257) >>>>> at org.openmrs.web.Listener.setupNeeded(Listener.java:170) >>>>> at org.openmrs.web.Listener.contextInitialized(Listener.java:142) >>>>> at >>>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205) >>>>> at >>>>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4704) >>>>> at >>>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) >>>>> at >>>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) >>>>> at >>>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) >>>>> at >>>>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) >>>>> at >>>>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563) >>>>> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1397) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at >>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>>>> at >>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke(Method.java:616) >>>>> at >>>>> org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) >>>>> at >>>>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:857) >>>>> at >>>>> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:795) >>>>> at >>>>> org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1500) >>>>> at >>>>> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:252) >>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) >>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>> at >>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) >>>>> at >>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>> at >>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) >>>>> at >>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) >>>>> at >>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) >>>>> at >>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) >>>>> at >>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) >>>>> at >>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >>>>> at >>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) >>>>> at >>>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) >>>>> at >>>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) >>>>> at >>>>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) >>>>> at java.lang.Thread.run(Thread.java:679) >>>>> Caused by: java.lang.Exception: Unable to get a connection to the >>>>> database. Please check your openmrs runtime properties file and make sure >>>>> you have the correct connection.username and connection.password set >>>>> at >>>>> org.openmrs.util.DatabaseUpdater.getLiquibase(DatabaseUpdater.java:337) >>>>> at >>>>> org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:564) >>>>> ... 35 more >>>>> >>>>> >>>>> >>>>> >>>>> Can we fix this install bug first? i.e., If this is a fresh install, >>>>> create the openmrs-runtime.properties based on the info collected. >>>>> >>>>> >>>>> On 2/17/2012 10:09 AM, Wyclif Luyima wrote: >>>>> >>>>> Can you just try deleting the one under your user home directory, there >>>>> is an order the install wizard follows when looking up the runtme >>>>> properties >>>>> file and application data directory, when i look at the complete >>>>> stacktrace >>>>> from your previous email, the error message states there is already an >>>>> existing 'liquibasechangelog' file which implies that there is an existing >>>>> database with this table and this database could be the one pointed to by >>>>> the runtime-properties file under the user home directory. >>>>> >>>>> Wyclif >>>>> >>>>> On Fri, Feb 17, 2012 at 2:48 PM, Charles C. Chou <[email protected]> >>>>> wrote: >>>>>> >>>>>> Hi Wyclif, >>>>>> /usr/share/tomcat6 is the home directory for tomcat6. The error >>>>>> seems to indicate a problem in updating the database. I have since >>>>>> removed >>>>>> the openmrs database again and tried the install process from scratch and >>>>>> this time the error messages are displayed in red on top of the Wizard >>>>>> page, >>>>>> after it tried to create database openmrs: >>>>>> >>>>>> There was an error while updating the database to the latest. file: >>>>>> liquibase-schema-only.xml. Error: liquibase.exception.JDBCException: >>>>>> Error >>>>>> executing SQL CREATE TABLE `liquibasechangeloglock` (`ID` INT NOT NULL, >>>>>> `LOCKED` TINYINT(1) NOT NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` >>>>>> VARCHAR(255), CONSTRAINT `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>> See >>>>>> the error log for more details >>>>>> There was an error while updating the database to the latest. file: >>>>>> liquibase-demo-data.xml. Error: liquibase.exception.JDBCException: Error >>>>>> executing SQL CREATE TABLE `liquibasechangeloglock` (`ID` INT NOT NULL, >>>>>> `LOCKED` TINYINT(1) NOT NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` >>>>>> VARCHAR(255), CONSTRAINT `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>> See >>>>>> the error log for more details >>>>>> There was an error while updating the database to the latest. file: >>>>>> liquibase-update-to-latest.xml. Error: liquibase.exception.JDBCException: >>>>>> Error executing SQL CREATE TABLE `liquibasechangeloglock` (`ID` INT NOT >>>>>> NULL, `LOCKED` TINYINT(1) NOT NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` >>>>>> VARCHAR(255), CONSTRAINT `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>> Error while trying to update to the latest database version >>>>>> >>>>>> Also I had the update database option left to No (default). I had >>>>>> it set to Yes one previous time and it seems to not want to forget that. >>>>>> >>>>>> Thanks, >>>>>> Charles Chou >>>>>> >>>>>> On 2/17/2012 9:08 AM, Wyclif Luyima wrote: >>>>>> >>>>>> Hi Charles, >>>>>> >>>>>> I'm not sure how you have set up your environment, but by default the >>>>>> application data directory '.OpenMRS' should be located in the user home >>>>>> directory and not '/user/share/tomcat6', So you need to delete the one >>>>>> in >>>>>> the home directory. >>>>>> >>>>>> Wyclif >>>>>> >>>>>> On Fri, Feb 17, 2012 at 1:27 PM, Charles C. Chou <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> I am now trying to re-install OpenMRS on the same Linux server. >>>>>>> After removing the openmrs database from mysql and removing the .OpenMRS >>>>>>> from /usr/share/tomcat6, undeployed openmrs from the tomcat manager >>>>>>> app, I >>>>>>> proceeded with deploying the openmrs.war file again and got the same >>>>>>> runtime >>>>>>> properties not found error. I then created one manually as suggested by >>>>>>> James and now I got: >>>>>>> >>>>>>> The following error occurred at startup: >>>>>>> Error occurred while trying to get the updates needed for the >>>>>>> database. liquibase.exception.JDBCException: Error executing SQL CREATE >>>>>>> TABLE `liquibasechangeloglock` (`ID` INT NOT NULL, `LOCKED` TINYINT(1) >>>>>>> NOT >>>>>>> NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` VARCHAR(255), CONSTRAINT >>>>>>> `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>>> >>>>>>> java.lang.RuntimeException: Error occurred while trying to get the >>>>>>> updates needed for the database. liquibase.exception.JDBCException: >>>>>>> Error >>>>>>> executing SQL CREATE TABLE `liquibasechangeloglock` (`ID` INT NOT NULL, >>>>>>> `LOCKED` TINYINT(1) NOT NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` >>>>>>> VARCHAR(255), CONSTRAINT `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>>> at >>>>>>> org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:578) >>>>>>> at >>>>>>> org.openmrs.util.DatabaseUpdater.updatesRequired(DatabaseUpdater.java:257) >>>>>>> at org.openmrs.web.Listener.setupNeeded(Listener.java:170) >>>>>>> at >>>>>>> org.openmrs.web.Listener.contextInitialized(Listener.java:142) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4704) >>>>>>> at >>>>>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) >>>>>>> at >>>>>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) >>>>>>> at >>>>>>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) >>>>>>> at >>>>>>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563) >>>>>>> at >>>>>>> org.apache.catalina.startup.HostConfig.check(HostConfig.java:1397) >>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>>>> at >>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>>>>>> at >>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>>>> at java.lang.reflect.Method.invoke(Method.java:616) >>>>>>> at >>>>>>> org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) >>>>>>> at >>>>>>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:857) >>>>>>> at >>>>>>> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:795) >>>>>>> at >>>>>>> org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1500) >>>>>>> at >>>>>>> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:252) >>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) >>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >>>>>>> at >>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) >>>>>>> at >>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) >>>>>>> at >>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) >>>>>>> at >>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) >>>>>>> at >>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >>>>>>> at >>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) >>>>>>> at >>>>>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) >>>>>>> at >>>>>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) >>>>>>> at >>>>>>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) >>>>>>> at java.lang.Thread.run(Thread.java:679) >>>>>>> Caused by: liquibase.exception.LockException: >>>>>>> liquibase.exception.JDBCException: Error executing SQL CREATE TABLE >>>>>>> `liquibasechangeloglock` (`ID` INT NOT NULL, `LOCKED` TINYINT(1) NOT >>>>>>> NULL, >>>>>>> `LOCKGRANTED` DATETIME, `LOCKEDBY` VARCHAR(255), CONSTRAINT >>>>>>> `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>>> at liquibase.lock.LockHandler.waitForLock(LockHandler.java:176) >>>>>>> at liquibase.Liquibase.listUnrunChangeSets(Liquibase.java:518) >>>>>>> at >>>>>>> org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:566) >>>>>>> ... 35 more >>>>>>> Caused by: liquibase.exception.JDBCException: Error executing SQL >>>>>>> CREATE TABLE `liquibasechangeloglock` (`ID` INT NOT NULL, `LOCKED` >>>>>>> TINYINT(1) NOT NULL, `LOCKGRANTED` DATETIME, `LOCKEDBY` VARCHAR(255), >>>>>>> CONSTRAINT `PK_LIQUIBASECHANGELOGLOCK` PRIMARY KEY (`ID`)) >>>>>>> at >>>>>>> liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:55) >>>>>>> at >>>>>>> liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:86) >>>>>>> at >>>>>>> liquibase.database.AbstractDatabase.checkDatabaseChangeLogLockTable(AbstractDatabase.java:755) >>>>>>> at liquibase.lock.LockHandler.waitForLock(LockHandler.java:145) >>>>>>> ... 37 more >>>>>>> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: >>>>>>> Table '`openmrs`.`liquibasechangeloglock`' already exists >>>>>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native >>>>>>> Method) >>>>>>> at >>>>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) >>>>>>> at >>>>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) >>>>>>> at >>>>>>> java.lang.reflect.Constructor.newInstance(Constructor.java:532) >>>>>>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) >>>>>>> at com.mysql.jdbc.Util.getInstance(Util.java:381) >>>>>>> at >>>>>>> com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030) >>>>>>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) >>>>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3536) >>>>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3468) >>>>>>> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1957) >>>>>>> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2107) >>>>>>> at >>>>>>> com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2642) >>>>>>> at >>>>>>> com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2571) >>>>>>> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:769) >>>>>>> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:612) >>>>>>> at >>>>>>> liquibase.database.template.JdbcTemplate$1ExecuteStatementCallback.doInStatement(JdbcTemplate.java:78) >>>>>>> at >>>>>>> liquibase.database.template.JdbcTemplate.execute(JdbcTemplate.java:48) >>>>>>> ... 40 more >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> BTW anyway to see the deployment code? It seems kind of sensitive, >>>>>>> maybe limited to just the Linux platform. >>>>>>> >>>>>>> Regards, >>>>>>> Charles Chou >>>>>>> >>>>>>> On 2/8/2012 9:47 AM, Charles C. Chou wrote: >>>>>>> >>>>>>> Thanks James. After creating the openmrs-runtime-properties as >>>>>>> suggested I got the installation to complete successfully. The system >>>>>>> is now >>>>>>> running. Thanks again! >>>>>>> >>>>>>> Regards, >>>>>>> Charles Chou >>>>>>> On 2/8/2012 8:49 AM, James Arbaugh wrote: >>>>>>> >>>>>>> Hi again Charles. >>>>>>> >>>>>>> >>>>>>> >>>>>>> It sounds like you ran into a bug. Recent versions of OpenMRS should >>>>>>> create the runtime properties file if it doesn’t exist. >>>>>>> >>>>>>> >>>>>>> >>>>>>> You could try to do it manually with the details on this page. >>>>>>> >>>>>>> >>>>>>> https://wiki.openmrs.org/display/docs/Overriding+OpenMRS+Default+Runtime+Properties >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> James >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: [email protected] [mailto:[email protected]] On >>>>>>> Behalf Of Charles C. Chou >>>>>>> Sent: Wednesday, February 08, 2012 12:42 PM >>>>>>> To: [email protected] >>>>>>> Subject: Re: [OPENMRS-IMPLEMENTERS] Linux server installation >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> The installation wizard is now stuck at Create database user and >>>>>>> will not continue. The output details is as follows: >>>>>>> >>>>>>> Create database user >>>>>>> >>>>>>> >>>>>>> Number of actions completed so far: 2 >>>>>>> >>>>>>> Server log file output: >>>>>>> >>>>>>> WARN - OpenmrsUtil.getRuntimeProperties(2274) |2012-02-08 >>>>>>> 07:34:04,225| Unable to find a runtime properties file at >>>>>>> /usr/share/tomcat6/openmrs-runtime.properties >>>>>>> WARN - OpenmrsUtil.getRuntimeProperties(2304) |2012-02-08 >>>>>>> 07:34:04,351| Unable to find properties file: >>>>>>> /usr/share/tomcat6/.OpenMRS/openmrs-runtime.properties >>>>>>> WARN - OpenmrsUtil.getRuntimeProperties(2321) |2012-02-08 >>>>>>> 07:34:04,352| Unable to find a runtime properties file. Initial setup is >>>>>>> needed. View the webapp to run the setup wizard. >>>>>>> WARN - InitializationFilter.verifyConnection(455) |2012-02-08 >>>>>>> 07:34:27,881| Error while checking the connection user account >>>>>>> ERROR - Context.getServiceContext(253) |2012-02-08 07:35:13,877| >>>>>>> serviceContext is null. Creating new ServiceContext() >>>>>>> >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> On 2/8/2012 7:05 AM, Charles C. Chou wrote: >>>>>>> >>>>>>> Thanks. That was the problem. There were 2 users created, tomcat and >>>>>>> tomcat6, during the installation of tomcat somehow (I guess one is from >>>>>>> the >>>>>>> distro package and one is from apache-tomcat-6.0.29) The webapps >>>>>>> directory >>>>>>> was owned by tomcat6 where the tomcat6 process was running as user >>>>>>> tomcat. >>>>>>> After changing the webapps ownership to tomcat.tomcat the deployment of >>>>>>> openmrs.war was successful. I have removed the confusing user tomcat6. >>>>>>> >>>>>>> Thanks again! >>>>>>> Charles Chou >>>>>>> >>>>>>> On 2/8/2012 6:19 AM, Michael Downey wrote: >>>>>>> >>>>>>> Hi Charles, >>>>>>> >>>>>>> On Wed, Feb 8, 2012 at 11:00 AM, Charles C. Chou<[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Feb 7, 2012 10:17:09 AM org.apache.catalina.core.ApplicationContext >>>>>>> log >>>>>>> SEVERE: HTMLManager: FAIL - Deploy Upload Failed, Exception: null >>>>>>> >>>>>>> A quick Google search suggests this is probably a file permissions >>>>>>> issue. Make sure all of your files are owned by the user that is >>>>>>> running the Tomcat process. >>>>>>> >>>>>>> Hope this helps get you started! >>>>>>> >>>>>>> Best regards, >>>>>>> Michael Downey >>>>>>> OpenMRS Community Infrastructure Team >>>>>>> [email protected] - http://openmrs.org/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ________________________________ >>>>>>> >>>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>>>> >>>>>>> ________________________________ >>>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>>>> >>>>>>> >>>>>>> ________________________________ >>>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>>>> >>>>>>> >>>>>>> ________________________________ >>>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>>> >>>>>> >>>>>> ________________________________ >>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>>> >>>>>> >>>>>> ________________________________ >>>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>> >>>>> >>>>> ________________________________ >>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>>> >>>>> >>>>> ________________________________ >>>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>> >>>> >>>> ________________________________ >>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>>> >>>> >>>> ________________________________ >>>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>> >>> >>> ________________________________ >>> Click here to unsubscribe from OpenMRS Implementers' mailing list >>> >>> >>> ________________________________ >>> Click here to unsubscribe from OpenMRS Implementers' mailing list >> >> >> ________________________________ >> Click here to unsubscribe from OpenMRS Implementers' mailing list >> >> >> ________________________________ >> Click here to unsubscribe from OpenMRS Implementers' mailing list > > > ________________________________ > Click here to unsubscribe from OpenMRS Implementers' mailing list > > > ________________________________ > Click here to unsubscribe from OpenMRS Implementers' mailing list > > > > -- > Mhawila A. > > ________________________________ > Click here to unsubscribe from OpenMRS Implementers' mailing list -- Thanks, Nyoman Ribeka _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
