Error Messages
This page describes error messages generated by pScheduler.
Note that this is not an exhaustive list, as some messages are either self-explanatory or would only be produced in exceptionally-rare circumstances. If you encounter an error not on this list, please consult with the development team.
Errors marked Internal Error indicate bugs in the pScheduler software. Please consult with the development team for help diagnosing the problem.
If directed to the system logs, these files contain relevant information:
-
/var/log/pscheduler/pscheduler.log. /var/log/httpd/error_log/var/log/httpd/ssl_error_log
Can't find pScheduler or BWCTL on x - pScheduler was unable to connect to and communicate with the pScheduler on host x and the BWCTL backward-compatibility software was unable to do the same. If the host is believed to be running perfSONAR, this is often caused by a firewall blocking the connection.
Cannot schedule runs more than x in advance - Internal Error, possibly related to a difference in the clocks between pScheduler servers.
Couldn't find a tool in common among the participants - The participants in a task did not have a common set of tools available to run the test specified for a given task. (For example, this error will arise when, in a throughput test, if one participant offers tools iperf2 and iperf3 as able to run a test and the other offers nuttcp.)
Didn't get a full set of tool responses - The pScheduler server leading a task failed to get a response from all of the participants when asking for tools.
Error getting tools from x: ... - The pScheduler server leading a task was unable to request a list of tools from one of the participants.
Error while tasking x: ... - One of the participants encountered a problem while the lead was trying to give it a task.
Expected one row; got x - Internal Error
Failed to archive x to y: ... - An unrecoverable error occurred while attempting to send a result to an archiver.
Gave up after too many scheduling conflicts - After repeated attempts to schedule a run when a conflict arose during the scheduling process, the scheduler elected to stop trying. This should be a very rare occurrence.
Gave up archiving x to y - All attempts to archive a result have failed and the retry policy says no more should happen.
x has no time available for this run - The scheduler was unable to find an available time on one of the participants to schedule a run of the task. This arises when there is contention for time on the schedule and can be alleviated by adding slip to the task.
Internal problem; see system logs. - Internal Error
Invalid transition between states - Internal Error
Limit processor is not initialized. See system logs. - The limit configuration in /etc/pscheduler/limits.conf is invalid. Use the pscheduler validate-limits command for more information and consult the system logs.
No API above x is supported - A request arrived on a pScheduler server that asked to use a version of the API it doesn't support. Usually this can be resolved by upgrading to the current version.
No common times for this run - The pScheduler servers participating in a task had times available for a run but none of them were the same.
No results returned; may be an internal problem - Internal Error
Resource not found. - Often seen when trying to retrieve the result of a run, this means no result was produced.
Run did not complete: x - The run failed to finish and/or start for reason x, where x is a run state.
Run is gone. Stopping. - A run disappeared from a participant's pScheduler server when the runner expected it to be there. This can happen when a server is rebuilt or reset.
Run was preempted. - A task with a higher priority had a run scheduled at the same time and this one was canceled because of it.
Run would result in a scheduling conflict - The lead participant attempted to schedule a run during a time when another was already on the schedule. Likely an internal error.
Starting x later than scheduled - A run was delayed far enough beyond its scheduled start time that it may not execute properly. This is often the result of high system load.
Task already exists. All participants must be on separate systems. - An attempt was made to specify a task whose participants are on the same system. pScheduler does not allow this.
Task forbidden by limits: ... - One or more of the pScheduler servers participating in a task is configured to deny the test it specified.
Task is gone from x - A task disappeared from a participant's pScheduler server when the scheduler expected it to be there. This can happen when a server is rebuilt or reset.
Unable to get participant data: ... - An error occurred while trying to gather data needed to run a test from one of the participants.
Unable to convert test spec: ... - One of the participants encountered an error when attempting to use a test plugin to decode a test specification. Depending on the message that follows, this may indicate an internal error or a system problem.
Unable to post task: Invalid task specification: Schema version x is not supported (highest is y) - One or more of the participants is running older software that does not support something requested by a task.