Closed GoogleCodeExporter closed 9 years ago
hi,
i found solution.
lsof | grep IPv4
kill -9 pid-ruby-on-rail
bug:)> pid no kill after /etc/ini.d/owp restart or stop/start
syncing physical servers state...
/opt/ovz-web-panel/vendor/rails/railties/lib/commands/runner.rb:47:
/usr/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection refused -
connect(2) (Errno::ECONNREFUSED)
Original comment by pirath...@gmail.com
on 12 Nov 2010 at 1:52
"Connection refused" error means that panel can't establish connection with
hw-daemon on target server. If hw-daemon was installed to the node and see this
error, probably daemon stop working. This can happen for example after machine
reboot. Then you connect new server using ssh, hw-daemon is installed on target
server. But init scripts are not implemented yet.
To solve the issue need to start daemon manually on problematic server:
sudo ruby /opt/ovz-web-panel/utils/hw-daemon/hw-daemon.rb restart
Original comment by sibprogrammer
on 12 Nov 2010 at 4:38
hi, thks reply
Great two solution run for me.
ruby /opt/ovz-web-panel/utils/hw-daemon/hw-daemon.rb restart
regard and nice work 1.6
Original comment by pirath...@gmail.com
on 12 Nov 2010 at 6:44
I can´t add my physical server
Log atached
Someone can help?
Original comment by elanogar...@gmail.com
on 23 Nov 2010 at 3:18
Attachments:
Did you try that I suggested in Comment 2 ? If hw-daemon is running, probably
need to check the firewall settings.
Original comment by sibprogrammer
on 23 Nov 2010 at 3:22
Closing issue due to lack of activity for two weeks.
Original comment by sibprogrammer
on 12 Dec 2010 at 5:40
Original issue reported on code.google.com by
pirath...@gmail.com
on 12 Nov 2010 at 12:19Attachments: