search for: nuted

Displaying 13 results from an estimated 13 matches for "nuted".

Did you mean: noted
2016 Jul 13
2
Best practice to shutdown hosts which has not NUT via upssched
...it does not work", what are the symptoms? Does >> shutdown-all-hosts.sh get called? > System has installed far away (in China) and there is bad Internet > connection, so I might have ability to connect and check log files in a > few day or weeks. Now I know exactly only that NUTed hosts shutdown via > NUT as expected and no one host listed in shutdown-all-hosts.sh script > don't. > Roger, I would appreciate if you give me a hint how to "reproduce the > NUT protocol ... ". Do you mean getting feedback to CMDSCRIPT about the > "no NUTed&q...
2016 Jul 13
2
Best practice to shutdown hosts which has not NUT via upssched
On Wed, 13 Jul 2016, Dmitri Stepanov wrote: > Hi > > ?? I need to shutdown a number of hosts which has not NUT from one which has it. > > ?? I tried to do it from upssched script (after upssched's timer) like this: > > case $1 in > ??????? earlyshutdown) > ??????????????? logger -t upssched-cmd "Early shutdown is started" > ??????????????? /bin/sh
2016 Jul 13
0
Best practice to shutdown hosts which has not NUT via upssched
...gt;When you say "it does not work", what are the symptoms? Does >shutdown-all-hosts.sh get called? System has installed far away (in China) and there is bad Internet connection, so I might have ability to connect and check log files in a few day or weeks. Now I know exactly only that NUTed hosts shutdown via NUT as expected and no one host listed in shutdown-all-hosts.sh script don't. > >> ?? Also I read somewhere that it is not a good idea to shutdown other hosts from the CMDSCRIPT. > >The User Manual chapter 7.2: > ><< It?s not a good idea to call yo...
2016 Jul 14
0
Best practice to shutdown hosts which has not NUT via upssched
...t;, what are the symptoms? Does >>> shutdown-all-hosts.sh get called? > >> System has installed far away (in China) and there is bad Internet >> connection, so I might have ability to connect and check log files in a >> few day or weeks. Now I know exactly only that NUTed hosts shutdown via >> NUT as expected and no one host listed in shutdown-all-hosts.sh script >> don't. > >> Roger, I would appreciate if you give me a hint how to "reproduce the >> NUT protocol ... ". Do you mean getting feedback to CMDSCRIPT about the &...
2013 Mar 18
0
[linux-linus test] 17325: regressions - trouble: broken/fail/pass
flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop
2013 Mar 29
0
[linux-linus test] 17454: regressions - FAIL
flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail
2013 Apr 10
0
[linux-linus test] 17612: regressions - FAIL
flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail
2013 May 05
0
[linux-linus test] 17901: regressions - FAIL
flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4
2013 May 07
0
[linux-linus test] 17916: regressions - FAIL
flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4
2013 Jun 16
0
[linux-linus test] 18150: regressions - FAIL
flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as
2013 Jun 23
0
[linux-linus test] 18181: regressions - trouble: broken/fail/pass
flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as
2013 Aug 29
0
[linux-linus test] 18805: regressions - FAIL
flight 18805 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as
2013 Aug 29
0
[linux-linus test] 18844: regressions - FAIL
flight 18844 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18844/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 12557 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail