Hi Abhishek, I also noticed that the /var/run/oozie/oozie.pid is owned by oozie user, while the /var/lib/oozie/oozie-db/db.lck file is owned by root. I tried stopping oozie by issuing oozied.sh stop and it completed without errors, but again the oozie.pid gets created automatically and I'm unable to stop it...
Please advise.. Thanks Suresh. On Fri, Apr 22, 2016 at 10:15 AM, Suresh V <[email protected]> wrote: > Hi Abhishek, > > > I think it is Derby the default database. > Can you advise how I can check if it is in read-only mode and its status? > Never did this in the past... > > Thanks > Suresh. > > > > > > On Fri, Apr 22, 2016 at 8:59 AM, Abhishek Bafna <[email protected]> > wrote: > >> What database are you using here derby or any other database? >> Can you check the status of the database. It is in Read-Only mode and not >> able to write the data. >> >> On Fri, Apr 22, 2016 at 8:38 AM, Suresh V <[email protected]> wrote: >> >> > Hello >> > >> > We are trying to get oozie working in a small cluster set up in Amazon >> AWS. >> > >> > The oozie service is installed on the namenode and we can see the server >> > running on port 11000, and can see the GUI. >> > However, when we try to run a workflow, we get the following error: >> > Error: E0803 : E0803: IO error, E0603: SQL error in operation, >> > <openjpa-2.2.2-r422266:1468616 fatal store error> >> > org.apache.openjpa.persistence.RollbackException: The transaction has >> been >> > rolled back. See the nested exceptions for details on the errors that >> > occurred. FailedObject: org.apache.oozie.WorkflowJobBean@728178ac >> > >> > When I looked into /var/log/oozie/oozie.log, found this- >> > Caused by: <openjpa-2.2.2-r422266:1468616 fatal general error> >> > org.apache.openjpa.persistence.PersistenceException: An SQL data change >> is >> > not permitted for a read-only connection, user or database. {prepstmnt >> > 1261748784 INSERT INTO WF_JOBS (id, app_name, app_path, conf, >> created_time, >> > end_time, external_id, group_name, last_modified_time, log_token, >> > parent_id, proto_action_conf, run, sla_xml, start_time, status, >> user_name, >> > wf_instance) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, >> ?)} >> > [code=20000, state=25502] >> > FailedObject: >> > >> > I tried restarting the oozie service with /usr/lib/oozie/bin/oozied.sh >> stop >> > and then start. The stop didn't show any errors, but the start said pid >> is >> > found and start aborted. >> > >> > And the same error continues when trying to submit a workflow. >> > >> > Kindly assist on solving this issue. Please note that this is the first >> > time we are trying to run oozie jobs on this hadoop cluster. >> > >> > Thank you >> > Suresh. >> > >> > >
