-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start owp #52
Comments
Most probably it means lack of resources (RAM). |
No I have plenty of RAM left (1 GB+). Actually the problem is I updated to Ruby 1.9 but owp seems only compatible with Ruby 1.8. Would it be possible to make it compatible with more recent versions of Ruby ? |
+1 |
Same issue here
You can easily reproduce it by creating centos6 box in Vagrant and trying to install owp according to Installation section at http://owp.softunity.com.ru/ |
For the record: I have found a workaround. You can remove
Solution was found on stackoverflow: http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror
Than remove /var/lock/owp to get rid of:
... error. Now OWP should start! |
Hello.
owp was working fine until I tried to connect to it. I wanted to restart it, here is the output of /etc/init.d/owp restart:
root[/home/alex]# /etc/init.d/owp restart
Stopping OpenVZ Web Panel server...
Stopping hardware node daemon...
[FAIL] Unable to stop hardware node daemon.
Stopping watchdog daemon...
[FAIL] Unable to stop watchdog daemon.
Starting OpenVZ Web Panel...
Starting watchdog daemon...
[FAIL] Unable to start watchdog daemon.
Starting web server webrick on 0.0.0.0:3000...
[FAIL] Unable to start web server.
Starting hardware node daemon...
[FAIL] Unable to start hardware node daemon.
Syncing hardware nodes states...
[FAIL] Unable to sync information about hardware nodes.
Any clue what to try / where to look ?
The text was updated successfully, but these errors were encountered: