mirror of
https://github.com/sibprogrammer/owp.git
synced 2026-04-24 23:15:51 +03:00
[GH-ISSUE #52] Unable to start owp #30
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/owp#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alex3137 on GitHub (Jan 8, 2015).
Original GitHub issue: https://github.com/sibprogrammer/owp/issues/52
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 ?
@sibprogrammer commented on GitHub (Jan 11, 2015):
Most probably it means lack of resources (RAM).
@alex3137 commented on GitHub (Jan 11, 2015):
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 ?
@cybernet commented on GitHub (Jan 11, 2015):
+1
@afiskon commented on GitHub (Oct 26, 2015):
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/
@afiskon commented on GitHub (Oct 27, 2015):
For the record: I have found a workaround. You can remove
> /dev/null 2>&1code from /etc/init.d/owp script to see error messages. In my case it was: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!