jobtap history plugin throws errors #5475
Comments
|
Just reporting that another user hit this same issue when trying to set up a small system instance. (using flux RPMs on TOSS) Looking at the code, the only way the history plugin returns an error from these callbacks is if if (!hola_list_insert (hist->users, int2ptr (userid), entry, false)) {
job_entry_destroy (entry);
return -1;
}Maybe adding a |
|
Ah, this user reports they are running jobs (and the flux-broker) as uid 0, which will cause |
|
I see this all the time in containers (with root) and I just ignore it. |
|
Well now we know you can suppress the errors with |
|
Nice! I'll add that to my containers. |
|
|
Problem: the history jobtap plugin uses an integer userid as a hash key, but the hash implementation won't accept a NULL key, so the root history cannot be stored. This results in errors like: jobtap: job.new: callback returned error jobtap: job.inactive.add: callback returned error Map userid 0 to (uid_t)-1 since that value is reserved in POSIX. Fixes flux-framework#5475
Problem: the job history plugin uses an integer userid as hash key, but the hash implementation won't accept a key (NULL) for userid 0. This results in errors like: jobtap: job.new: callback returned error jobtap: job.inactive.add: callback returned error Map userid 0 to (uid_t)-1 since that value is reserved in POSIX. Fixes flux-framework#5475
Problem: the job history plugin uses an integer userid as hash key, but the hash implementation won't accept a key (NULL) for userid 0. This results in errors like: jobtap: job.new: callback returned error jobtap: job.inactive.add: callback returned error Map userid 0 to (uid_t)-1 since that value is reserved in POSIX. Fixes flux-framework#5475
Problem: the job history plugin uses an integer userid as hash key, but the hash implementation won't accept a key (NULL) for userid 0. This results in errors like: jobtap: job.new: callback returned error jobtap: job.inactive.add: callback returned error Map userid 0 to (uid_t)-1 since that value is reserved in POSIX. Fixes flux-framework#5475
Problem: the job history plugin uses an integer userid as hash key, but the hash implementation won't accept a key (NULL) for userid 0. This results in errors like: jobtap: job.new: callback returned error jobtap: job.inactive.add: callback returned error Map userid 0 to (uid_t)-1 since that value is reserved in POSIX. Fixes flux-framework#5475
In one of @vsoch's cloudy experiments, in the output of a failing intel MPI job, we noticed two jobtap errors:
The only jobtap in-tree that registers
job.inactive-addishistory. Maybe there is something to run down here or at least a couple places where log messages could be added to give us something to go on next time.The text was updated successfully, but these errors were encountered: