Ask Your Question

Sahara: Error database when reboot server

asked 2014-08-13 03:41:54 -0500

datts gravatar image


I have installed Sahara in Openstack Icehouse. It's worked!

But if reboot server Openstack. When i run sahara-api, received error messages:

ERROR sahara.openstack.common.periodic_task [-] Error during SaharaPeriodicTasks.update_job_statuses: (OperationalError) no such table: job_executions u'SELECT job_executions.created_at AS job_executions_created_at, job_executions.updated_at AS job_executions_updated_at, AS job_executions_id, job_executions.tenant_id AS job_executions_tenant_id, job_executions.job_id AS job_executions_job_id, job_executions.input_id AS job_executions_input_id, job_executions.output_id AS job_executions_output_id, job_executions.start_time AS job_executions_start_time, job_executions.end_time AS job_executions_end_time, job_executions.cluster_id AS job_executions_cluster_id, AS job_executions_info, job_executions.progress AS job_executions_progress, job_executions.oozie_job_id AS job_executions_oozie_job_id, job_executions.return_code AS job_executions_return_code, job_executions.job_configs AS job_executions_job_configs, job_executions.extra AS job_executions_extra \nFROM job_executions \nWHERE job_executions.end_time IS NULL' ()

In sahara.conf, i set:


However, if i delete old /tmp/sahara.db and run "sahara-venv/bin/sahara-db-manage --config-file sahara-venv/etc/sahara.conf upgrade head". Then start sahara-api, sahara can continue to work.

Can you help me fix it? Thank you very much!

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-08-13 05:14:19 -0500

dmitrymex gravatar image

I think that your /tmp is cleaned during the reboot. Try moving sahara.db to a different directory.

edit flag offensive delete link more


Thanks @dmitrymex,

I did as you said: /tmp/sahara.db changed to /home/cloud (example). Then, when start sahara-api, it's worked, that error 's been resolved.

However, when I ssh into the cluster (it was created before rebooting the server). When i run the job, message:

14/08/13 11:33:12 INFO ipc.Client: Retrying connect to server: demo-cluster-01-aio-node-001/ Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
java.lang.RuntimeException: Call to demo-cluster-01-aio-node-001/ failed on connection exception: Connection refused

If i create a new cluster, it run nomally.

datts gravatar imagedatts ( 2014-08-13 07:29:01 -0500 )edit

Sahara doesn't add hadoop processes to startup scripts. That's why all processes need to be restarted manually after VM restart. I've filed bp for Sahara to update startup scripts during VM configuration: .

alazarev gravatar imagealazarev ( 2014-08-13 10:06:27 -0500 )edit

Thanks @alazarev,

After VM restart, if i want restart all processes of hadoop. I will have to run what commands? Because "/etc/init.d/hadoop-* restart" or "service hadoop-* restart" is not running and i can not find the file start hadoop.


datts gravatar imagedatts ( 2014-08-13 12:52:43 -0500 )edit

Actually there is no one file to restore all processes. We do not recommend to reboot VM with hadoop running. Restoring processes depends on hadoop version you use. For vanilla 1.2.1 it is 'sudo su -c "/usr/sbin/ start X" hadoop' where X is hadoop process.

alazarev gravatar imagealazarev ( 2014-08-14 09:59:22 -0500 )edit

Thanks alazarev :)

datts gravatar imagedatts ( 2014-08-14 11:13:33 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-08-13 03:41:54 -0500

Seen: 397 times

Last updated: Aug 13 '14