Hi Periya, Try removing both .lck (lock) files in the metastore_db folder. The derby db can only support one user. So if you have used hive from cli it is probably for another user.
Cheers, Jasper Op 18 dec. 2011 17:42 schreef "Periya.Data" <periya.d...@gmail.com> het volgende: > Hi Vivek, > Tried doing with sudo and later also changed the permissions. None of > them worked. > > root@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# ls -l > total 4 > drwxr-xr-x 5 root root 4096 2011-12-18 03:19 metastore_db > root@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# chmod 777 > metastore_db/ > root@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# ls -l > total 4 > drwxrwxrwx 5 root root 4096 2011-12-18 03:19 metastore_db > root@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# > > root@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# hive --service > hiveserver > Starting Hive Thrift Server > ^Croot@domU-12-31-39-0E-C9-33:/var/lib/hive/metastore# > > > -PD > > On Sun, Dec 18, 2011 at 4:34 AM, Vivek Mishra > <vivek.mis...@impetus.co.in>wrote: > >> try issuing with "sudo". as metastore_db is locked for root user. >> else do sudo chmod 777 <metastore_db> folder. >> >> >> Vivek >> ________________________________________ >> From: Periya.Data [periya.d...@gmail.com] >> Sent: 18 December 2011 10:29 >> To: user@hive.apache.org >> Subject: Hive server not starting...on EC2 Ubuntu 10.04 instance >> >> Hi all, >> I am trying to start hive server, but, after the command, it looks >> like nothing is happening. I am not even getting a prompt. Here are some >> details: >> >> - machine - EC2 Ubuntu 10.04 LTS >> - Hive version - 0.7.1-cdh3u2 (as seen from hive-default.xml) >> - Hadoop version - 0.20.2 >> - I currently have an embedded Derby database as my metastore. >> (Plan to move it to a remote MySQL DB later. For now, i am the only user). >> >> root@domU-12-31-39-0E-C9-33:/usr/lib/hive/conf# hive --service hiveserver >> Starting Hive Thrift Server >> >> <it just hangs here...nothing happens for 10 min..had to Ctrl-c to get >> out.> >> Looks like to it is unable to talk to the metastore. I am able to run >> hive shell, create, drop tables and run queries from the shell. >> ----------- >> >> I did the following: >> - # HIVE_PORT=10000 hive --service hiveserver (same problem) >> - Tried changing ports, but, same problem. >> >> >> Log File (/tmp/<user>/hive.log) >> >> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool >> error Could not create a validated object, cause: A read-only user >> or a user in a read-only database is not permitted to disable read-only >> mode on a connection. >> at org.apache.hadoop.hive.ql.metadata.Hive.getDatabase(Hive.java:1028) >> at >> org.apache.hadoop.hive.ql.metadata.Hive.databaseExists(Hive.java:1013) >> at org.apache.hadoop.hive.ql.exec.DDLTask.showTables(DDLTask.java:1712) >> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:289) >> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:130) >> at >> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57) >> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1063) >> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:900) >> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:748) >> at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:209) >> at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:286) >> at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:485) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.apache.hadoop.util.RunJar.main(RunJar.java:186) >> Caused by: javax.jdo.JDOFatalDataStoreException: Cannot get a connection, >> pool error Could not create a validated object, cause: A read-only >> user or a user in a read-only database is not permitted to disable >> read-only mode on a connection. >> NestedThrowables: >> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool >> error Could not create a validated object, cause: A read-only user >> or a user in a read-only database is not permitted to disable read-only >> mode on a connection. >> at >> org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:298) >> at >> org.datanucleus.jdo.JDOPersistenceManagerFactory.freezeConfiguration(JDOPersistenceManagerFactory.java:601) >> at >> org.datanucleus.jdo.JDOPersistenceManagerFactory.createPersistenceManagerFactory(JDOPersistenceManagerFactory.java:286) >> at >> org.datanucleus.jdo.JDOPersistenceManagerFactory.getPersistenceManagerFactory(JDOPersistenceManagerFactory.java:182) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at javax.jdo.JDOHelper$16.run(JDOHelper.java:1958) >> at java.security.AccessController.doPrivileged(Native Method) >> at javax.jdo.JDOHelper.invoke(JDOHelper.java:1953) >> at >> javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1159) >> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:803) >> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:698) >> at >> org.apache.hadoop.hive.metastore.ObjectStore.getPMF(ObjectStore.java:234) >> at >> org.apache.hadoop.hive.metastore.ObjectStore.getPersistenceManager(ObjectStore.java:261) >> ............ >> >> >> What could be going wrong? Am I missing something? >> >> Thanks, >> PD. >> >> ________________________________ >> >> New Impetus webcast on-demand ‘Big Data Technologies for Social Media >> Analytics’ available at http://bit.ly/nFdet0. >> >> Visit http://www.impetus.com to know more. Follow us on >> www.twitter.com/impetuscalling >> >> >> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. >> > >
