Hi Jeff,
On Sun, Nov 18, 2012 at 10:58 PM, 任英杰 re...@neusoft.com wrote:
hi Simon,
I also re-make the directory /var/lock/one, and set the ownership/group to
oneadmin:cloud.
It works, and I can start one daemon.
But command onehost shows that some hosts are in error status.
I enable them
hi all,
I met across a poweroff accidentally, when I restart one daemon, error
occurs:
$ one start
/usr/bin/one: line 141: /var/run/one/oned.pid: No such file or directory
/usr/bin/one: line 154: /var/run/one/sched.pid: No such file or directory
Error: Cannot start oned, opening lock file
Hi Jeff,
On Nov 18, 2012 9:37 PM, 任英杰 re...@neusoft.com wrote:
hi all,
I met across a poweroff accidentally, when I restart one daemon, error
occurs:
$ one start
/usr/bin/one: line 141: /var/run/one/oned.pid: No such file or directory
/usr/bin/one: line 154: /var/run/one/sched.pid: No
Thanks for your response, Simon.
I checked the directory, and it didn't exist.
I tred to re-make it by myself, and one.pid can be re-generated, but the
lock file still disappear.
It shows:
Error: Cannot start oned, opening lock file /var/lock/one/one
I tried to rebuild a blank lock file named
hi Simon,
I also re-make the directory /var/lock/one, and set the ownership/group
to oneadmin:cloud.
It works, and I can start one daemon.
But command onehost shows that some hosts are in error status.
I enable them ,but Frontend still can't monitor hosts.
Thanks
Jeff
于 2012年11月19日 11:21, 任英杰
