Hi all, It is easy to end up with a full hard disk when a BOINC process logs a recurring error message. For example, over the weekend we had this situation because a validator process kept outputting lines similar to these:
2010-09-27 11:44:52.6131 [CRITICAL] [WU#3662461 iq64AT2_100702a_6_26] assign_credit_set() returned -161 2010-09-27 11:44:52.6141 [CRITICAL] get_pfc() [RESULT#4404635]: No AVP 495!! 2010-09-27 11:44:52.6141 [CRITICAL] get_pfc() error: -161 2010-09-27 11:44:52.6141 [CRITICAL] [WU#3662461 iq64AT2_100702a_6_26] assign_credit_set() returned -161 2010-09-27 11:44:52.6151 [CRITICAL] get_pfc() [RESULT#4404635]: No AVP 495!! 2010-09-27 11:44:52.6151 [CRITICAL] get_pfc() error: -161 2010-09-27 11:44:52.6151 [CRITICAL] [WU#3662461 iq64AT2_100702a_6_26] assign_credit_set() returned -161 2010-09-27 11:44:52.6169 [CRITICAL] get_pfc() [RESULT#4404635]: No AVP 495!! 2010-09-27 11:44:52.6169 [CRITICAL] get_pfc() error: -161 2010-09-27 11:44:52.6169 [CRITICAL] [WU#3662461 iq64AT2_100702a_6_26] assign_credit_set() returned -161 By today (Monday) we had a 28GB log file and a full disk, with an inconsistent database and all sorts of other problems. Would it be possible to change the way BOINC processes deal with such situations? For example, in the above case it would be better if the validator would just give up on this result, or at least limit the number of log entries. Thanks. -Kamran _______________________________________________ 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.
