JobServer Troubleshooting



Troubleshooting Questions:

  1. I forgot my administrator password. What can I do?
  2. How do I keep the JobServer environment well maintained? Is there routine maintenance that needs to be performed?
  3. The JobServer scheduling engine does not seem to be starting up when I start it from the System Administration Tool Panel, what can I do?
  4. Where can I view detailed logs for GUI related errors when I use the JobServer Tool Panel apps?
  5. Where can I view system log messages related to job scheduling and job processing?
  6. Where can I view the list all the actively running jobs?
  7. Where can I view list of all queued jobs?
  8. Where can I get detailed job level messages, warnings and errors logged for each job run?
  9. Jobs seem to be running slower, how can check if performance is different from previous days?
  10. I get some kind of license errors when I start the JobServer environment, how can resolve this?
  11. Jobs are not getting scheduled, what can I do?
  12. Where can I see the list of jobs that are going to be schedule to run next in the future?
  13. I am getting out of memory exceptions, how can increase JVM memory for the servlet engine and job processing/scheduling engine?
  14. I installed JobServer on an amazon ec2 instance, but I get a UI error when trying to view a Tasklet's customizer GUI. The error refers to the GWT Compiler.

See Product FAQ



Troubleshooting Questions/Answers:

  1. I forgot my administrator password. What can I do?

    As the account administrator, you can use the jsmonitor command line program to reset the password for the JobServer "admin" user. See jsmonitor -help command line program for more details.


  2. How do I keep the JobServer environment well maintained? Is there routine maintanence that needs to be performed?

    There is a standard Tasklet called JobServerCleanup that comes with JobServer. It performs database and filesystem cleanup, trimming and other related tasks to keep the JobServer environment tuned.

    You should create a job and have it use this Tasklet. The Job can run daily, weekly or at some other regular frequency depending how often it is needed. This Tasklet is self explanatory via its GUI interface. See the Tasklet's GUI Customizer for details.

  3. The JobServer scheduling engine does not seem to be starting up when I start it from the System Administration Tool Panel, what can I do?

    There might be something wrong with your environment. Check the startup JobServer log. You can do this by going to the "System Administration->System Log" UI and select the "JobServer Startup Log". This log will show you the startup sequence when the scheduler was started. Check for any errors or warnings. Contact support with details.

  4. I am getting some low level errors when I use the JobServer GUI apps, where can I view detailed logs for GUI related errors when I use the JobServer Tool Panel apps?

    If you are getting low level GUI errors when using the JobServer Tools, you can see any related low level exceptions by going to the directory file "jobserver/sys/app/logs". This contains log files associated with the servlet engine that drives the GUI. You can also setup your environment to receive email alerts whenever any kind of low level error or exception is thrown. You can set this up by going to "System Administration->Alerts" and setup the alert emails.

  5. Where can I view system log messages related to job scheduling and job processing?

    If you are getting low level errors when jobs are running or when the job scheduler is trying to run or process jobs, check the JobServer runtime logs. You can do this by going to "System Administration->JobServer Runtime Log" UI. You can see the runtime logs for each particular start/stop sequence for the JobServer scheduler and job processor.

  6. Where can I view the list all the actively running jobs?

    You can see the list of all running jobs by going to "System Administration->Partitions" UI. This UI lists all the Partitions and all running jobs. Click on the link for running jobs to see the active list. You can also see the list of running jobs by search for running jobs in the "Job Tracker" app. Select the checkbox "Show Running Jobs Only" to see just the running jobs.

  7. Where can I view list of all queued jobs?

    You can see the list of all queued jobs by going to "System Administration->Partitions" UI. This UI lists all the Partitions and all queued jobs. Click on the link for queued jobs to see the active list.

  8. Where can I get detailed job level messages, warnings and errors logged for each job run?<

    You can search all job run history from the "Job Tracker" app. This app shows all the jobs that have run in your environment and allows you to filter by time and several other options. If you want to see the logs (messages, warnings, errors) for a particular job run, click on the job run you are interested in and this allows you to dive in and see the detailed taskbeans that ran in the job and view their detailed log messages and also view any associated custom UI that the taskbean has.

  9. Jobs seem to be running slower, how can check if performance is different from previous days?

    You can run a report that will allow you to show performance metrics for any job or group of jobs. Go the the app "Job Scheduler->Schedule Statistics" and set your filter options for the job(s) you are interested in get performance metrics for. You can use this to compare how any job or group of jobs have performed in the past.

  10. I get some kind of license errors when I start the JobServer environment, how can resolve this?

    You can check the license status of your JobServer environment by going to the app "Product Config->License". This view reports the status of your license among other information about your installation. If this UI is not available you can also check the license key manually by going the directory file "jobserver/conf/license.key". The license.key file holds your license key information. Contact support if your license key has expired.

  11. Jobs are not getting scheduled, what can I do?

    If your JobServer environment is running and your JobServer scheduling engine is also active and running but jobs that should be getting schedule are for some reason not getting scheduled on time, you need to check a number of things. First see if you are getting email alerts from JobServer and check the "System Administration->System Log" apps to see if there are any low level errors occuring. Common problems that might prevent jobs from being scheduled include bad database connections (or your database is down) or problems with your file system such as your file system being full or is corrupted or locked for some reason.

  12. Where can I see the list of jobs that are going to be schedule to run next in the future?

    You can go to the "Job Scheduler->Schedule Forecasting" app and run a report that will show you the list of jobs that are going to run next.

  13. I am getting out of memory exceptions, how can increase JVM memory for the servlet engine and job processing/scheduling engine?

    This might indicate you need to increase the maximum memory settings on your JVM servlet engine (that drives the GUI) or it might indicate you need to increase the the maximum memory setting on the JVM used by the job scheduling and processing engine that runs and schedules all jobs. You can edit/change the max JVM memory by manually editing the config file located at "jobserver/conf/system-config.properties". There are settings for configuring the JVM options for both the JobServer servlet engine and the JobServer scheduler and job processor.

  14. I installed JobServer on an amazon ec2 instance, but I get a UI error when trying to view a Tasklet's customizer GUI. The error refers to the GWT Compiler.

    Make sure you are not using the OpenJDK when running JobServer on ec2 instances. OpenJDK has a known problem with the GWT compiler. Switch to the Oracle/Sun Java 6 or higher JDK, instead of using the OpenJDK, in order to resolve the problem.