"transient failure" means that the validator couldn't open
a directory containing an output file
(I'll change the message to make this clear).
This can happen if you're using NFS and the mount failed.
-- David
On 12-Sep-2013 2:24 AM, Radim Vančo wrote:
No, if validator works well, everything is ok, if it starts to marks them as
inconclusive, there is this:
2013-09-11 21:01:28.6961 [WU#6111094 ps_130910_20263_277] handle_wu(): No
canonical result yet
2013-09-11 21:01:28.7004 [debug] [WU#6111094 ps_130910_20263_277] Found 4
viable results
2013-09-11 21:01:28.7005 [debug] [WU#6111094 ps_130910_20263_277] Enough for
quorum, checking set.
2013-09-11 21:01:28.7006 [CRITICAL] check_set: init_result([RESULT#14692440
ps_130910_20263_277_0]) transient failure
2013-09-11 21:01:28.7007 [CRITICAL] check_set: init_result([RESULT#14692441
ps_130910_20263_277_1]) transient failure
2013-09-11 21:01:28.7008 [CRITICAL] check_set: init_result([RESULT#15596859
ps_130910_20263_277_2]) transient failure
2013-09-11 21:01:28.7009 [CRITICAL] check_set: init_result([RESULT#15616637
ps_130910_20263_277_3]) transient failure
2013-09-11 21:01:28.7009 [HOST#29989 AV#43] [outlier=0] Updating HAV in db.
pfc.n=335.000000->335.000000
2013-09-11 21:01:28.7010 [HOST#33276 AV#43] [outlier=0] Updating HAV in db.
pfc.n=183.000000->183.000000
2013-09-11 21:01:28.7011 [HOST#20844 AV#43] [outlier=0] Updating HAV in db.
pfc.n=0.000000->0.000000
2013-09-11 21:01:28.7011 [RESULT#15616637 ps_130910_20263_277_3] Inconclusive
[HOST#13946]
2013-09-11 21:01:28.7012 [HOST#13946 AV#43] [outlier=0] Updating HAV in db.
pfc.n=12.000000->12.000000
2013-09-11 21:01:28.8081 [WU#6118169 ps_130910_20288_242] handle_wu(): No
canonical result yet
2013-09-11 21:01:28.9177 [debug] [WU#6118169 ps_130910_20288_242] Found 3
viable results
2013-09-11 21:01:28.9179 [debug] [WU#6118169 ps_130910_20288_242] Enough for
quorum, checking set.
2013-09-11 21:01:28.9180 [CRITICAL] check_set: init_result([RESULT#14706758
ps_130910_20288_242_0]) transient failure
2013-09-11 21:01:28.9181 [CRITICAL] check_set: init_result([RESULT#14706759
ps_130910_20288_242_1]) transient failure
2013-09-11 21:01:28.9182 [CRITICAL] check_set: init_result([RESULT#15605864
ps_130910_20288_242_2]) transient failure
2013-09-11 21:01:28.9182 [HOST#14290 AV#43] [outlier=0] Updating HAV in db.
pfc.n=46.000000->46.000000
2013-09-11 21:01:28.9183 [HOST#13719 AV#39] [outlier=0] Updating HAV in db.
pfc.n=9.000000->9.000000
2013-09-11 21:01:28.9183 [RESULT#15605864 ps_130910_20288_242_2] Inconclusive
[HOST#13946]
2013-09-11 21:01:28.9184 [HOST#13946 AV#39] [outlier=0] Updating HAV in db.
pfc.n=1.000000->1.000000
2013-09-11 21:01:28.9215 [WU#6124461 ps_130910_20312_62] handle_wu(): No
canonical result yet
2013-09-11 21:01:28.9247 [debug] [WU#6124461 ps_130910_20312_62] Found 2
viable results
2013-09-11 21:01:28.9249 [debug] [WU#6124461 ps_130910_20312_62] Enough for
quorum, checking set.
2013-09-11 21:01:28.9251 [CRITICAL] check_set: init_result([RESULT#14719522
ps_130910_20312_62_0]) transient failure
2013-09-11 21:01:28.9252 [CRITICAL] check_set: init_result([RESULT#14719523
ps_130910_20312_62_1]) transient failure
2013-09-11 21:01:28.9253 [RESULT#14719522 ps_130910_20312_62_0] Inconclusive
[HOST#45463]
2013-09-11 21:01:28.9253 [HOST#45463 AV#43] [outlier=0] Updating HAV in db.
pfc.n=131.000000->131.000000
2013-09-11 21:01:28.9263 [RESULT#14719523 ps_130910_20312_62_1] Inconclusive
[HOST#9190]
2013-09-11 21:01:28.9265 [HOST#9190 AV#43] [outlier=0] Updating HAV in db.
pfc.n=502.000000->502.000000
It looks like some memory leaks or something similiar, but didn't figure it out
yet.
Dne 12.9.2013 07:46, David Anderson napsal(a):
Are there any error messages in the validator log file?
-- David
On 11-Sep-2013 1:19 PM, Radim Vančo wrote:
I am still trying to solve problem with my validator. It works well at start,
but after a few days, it starts marking all results as inconclusive. If I
restart the validator, it validates again well for a few days. I am attaching
source code of the validator if anyone would know where is the problem.
Thanks
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
