You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
- The SOS Support Team relies on the completeness and accuracy of information that you provide about your JobScheduler environment.
- Currently the collection process as explained with this article is available for Unix environments.
- This article describes how to provide the information.
- The jobs and job chains are attached to this article.
- Download the attached configuration files and store them to your
$SCHEDULER_DATA/config/live folder. There should exist a sub-folder ./support after extracting the files from the archive. - Adjust the parameters for the database connection in the job
execute_database_statement
FEATURE AVAILABILITY STARTING FROM RELEASE 1.9
This standalone job performs the following operations:
- execute a
uname command - detect any running JobScheduler instances
- read all environment variables
- execute a
top command.
The output of this job will be stored in a file that is specified like this:
| Parameter | Description | Default |
|---|
output_file_name | The name of the file, that collects the information the SOS Support Team needs. Please attach this file to your ticket. | ./sos_support.log |
number_of_iterations | The number of top command iterations | 1 |
Please run the job and send the output file to the SOS Support Team.
Linux vmubuntu2 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
running JobScheduler instances
..............................
test 12759 1 0 Feb25 ? 00:00:00 /bin/sh /home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../bin/jobscheduler_agent_watchdog.sh -4447
test 12760 12759 0 Feb25 ? 00:03:25 /usr/bin/java -DLOGFILE=/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs/jobscheduler_agent_4447 -Xms100m -classpath /home/test/temp:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/log/log4j/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/jdbc/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/3rd-party/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/sos/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/ com.sos.scheduler.engine.agent.main.AgentMain -http-port=4447 -log-directory=/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs -kill-script=/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../bin/jobscheduler_agent_kill_task.sh -job-java-options=-Dlog4j.configuration=file:///home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/stdout/log4j.xml
test 13801 13795 0 05:05 ? 00:00:00 grep scheduler
environment variables
..............................
DISPLAY='localhost:11.0'
HOME='/home/test'
IFS='
'
IP_ADDRESS_OPTION=''
JAVABIN='/usr/bin/java'
JAVA_OPTIONS='-Xms100m'
JOB_JAVA_OPTIONS='-Dlog4j.configuration=file:///home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/stdout/log4j.xml'
KILL_TASK_LOG_FILE='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs/agent_kill_task_4447.log'
LANG='de_DE.UTF-8'
LOGNAME='test'
MAIL='/var/mail/test'
NLSPATH='/usr/dt/lib/nls/msg/%L/%N.cat'
OLDPWD='/home/test'
OPTIND='1'
PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games'
PPID='12760'
PS1='$ '
PS2='> '
PS4='+ '
PWD='/home/test/sos-berlin.com/jobscheduler_universal_agent'
SCHEDULER_CLASSPATH='/home/test/temp:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/log/log4j/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/jdbc/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/3rd-party/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/sos/*:/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../lib/'
SCHEDULER_CONFIGURATION_DIRECTORY='C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_current/config/live'
SCHEDULER_CRASH_FILE='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs/kill_tasks_after_crash_4447.sh'
SCHEDULER_HOME='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/..'
SCHEDULER_HOST='ur_dell'
SCHEDULER_HTTP_PORT='4447'
SCHEDULER_ID='scheduler_current'
SCHEDULER_JOB_CONFIGURATION_DIRECTORY='C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_current/config/live'
SCHEDULER_JOB_NAME='get_environment_data'
SCHEDULER_KILL_SCRIPT='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../bin/jobscheduler_agent_kill_task.sh'
SCHEDULER_LOGFILE='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs/jobscheduler_agent_4447'
SCHEDULER_LOG_DIR='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs'
SCHEDULER_PARAM_NUMBER_OF_ITERATIONS='1'
SCHEDULER_PARAM_OUTPUT_FILE_NAME='/home/test/logs/top.log'
SCHEDULER_PID_FILE='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs/jobscheduler_agent_4447.pid'
SCHEDULER_PID_FILE_DIR='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/../logs'
SCHEDULER_RETURN_VALUES='/tmp/sos-6571614061486009242.tmp'
SCHEDULER_SUPERVISOR_HOST=''
SCHEDULER_SUPERVISOR_PORT=''
SCHEDULER_TASK_ID='18367852'
SCHEDULER_TASK_TRIGGER_FILES=''
SCHEDULER_TCP_PORT='4000'
SCHEDULER_UDP_PORT='4000'
SHELL='/bin/bash'
SHLVL='1'
SSH_CLIENT='192.11.0.12 58002 22'
SSH_CONNECTION='192.11.0.12 58002 192.11.0.116 22'
SSH_TTY='/dev/pts/0'
TERM='vt100'
USER='test'
XDG_SESSION_COOKIE='1d23ce1f2422f47d161527f400000173-1456377517.352046-609560642'
XFILESEARCHPATH='/usr/dt/app-defaults/%L/Dt'
_='/home/test/sos-berlin.com/jobscheduler_universal_agent/bin/jobscheduler_agent_4447.sh'
top command
..............................
top - 05:05:47 up 2 days, 1:20, 2 users, load average: 0.00, 0.14, 0.22
Tasks: 77 total, 1 running, 76 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.5%us, 0.2%sy, 0.0%ni, 99.1%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1012360k total, 731712k used, 280648k free, 61728k buffers
Swap: 1046524k total, 10180k used, 1036344k free, 370176k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12760 test 20 0 2152m 169m 17m S 2.0 17.1 3:25.47 java
1 root 20 0 24304 2024 1276 S 0.0 0.2 0:02.52 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.03 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:01.49 ksoftirqd/0
5 root 20 0 0 0 0 S 0.0 0.0 0:07.73 kworker/u:0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
7 root RT 0 0 0 0 S 0.0 0.0 2:00.53 watchdog/0
8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset
9 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
12 root 20 0 0 0 0 S 0.0 0.0 0:00.86 sync_supers
13 root 20 0 0 0 0 S 0.0 0.0 0:00.02 bdi-default
14 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
17 root 20 0 0 0 0 S 0.0 0.0 0:00.27 khubd
18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
21 root 20 0 0 0 0 S 0.0 0.0 0:00.09 khungtaskd
22 root 20 0 0 0 0 S 0.0 0.0 0:09.69 kswapd0
23 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
24 root 39 19 0 0 0 S 0.0 0.0 0:00.00 khugepaged
25 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
26 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ecryptfs-kthrea
27 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
35 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
37 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
38 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
60 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 devfreq_wq
163 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 mpt_poll_0
164 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 mpt/0
211 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_2
227 root 20 0 0 0 0 S 0.0 0.0 0:24.96 jbd2/sda1-8
228 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ext4-dio-unwrit
314 root 20 0 17356 544 516 S 0.0 0.1 0:00.07 upstart-udev-br
318 root 20 0 21580 968 808 S 0.0 0.1 0:00.71 udevd
407 messageb 20 0 23940 996 820 S 0.0 0.1 0:01.17 dbus-daemon
411 syslog 20 0 243m 1048 1048 S 0.0 0.1 0:29.21 rsyslogd
435 root 20 0 21448 524 356 S 0.0 0.1 0:00.10 udevd
436 root 20 0 21448 548 364 S 0.0 0.1 0:00.08 udevd
611 root 20 0 49948 2364 2248 S 0.0 0.2 0:03.04 sshd
633 root 20 0 23344 928 924 S 0.0 0.1 0:00.00 vsftpd
635 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kpsmoused
825 root 20 0 15180 196 196 S 0.0 0.0 0:00.00 upstart-socket-
897 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty
902 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty
906 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty
907 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty
910 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty
924 root 20 0 4320 552 548 S 0.0 0.1 0:00.00 acpid
935 whoopsie 20 0 195m 3656 3296 S 0.0 0.4 0:15.45 whoopsie
936 mysql 20 0 537m 35m 1744 S 0.0 3.6 0:28.06 mysqld
939 root 20 0 19104 884 800 S 0.0 0.1 0:00.33 cron
940 daemon 20 0 16900 216 216 S 0.0 0.0 0:00.00 atd
1115 root 20 0 222m 8260 3148 S 0.0 0.8 0:15.21 apache2
1143 root 20 0 65132 1952 1472 S 0.0 0.2 0:00.04 login
1146 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2
1147 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2
1148 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2
1149 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2
1150 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2
1316 root 20 0 570m 3628 2496 S 0.0 0.4 0:02.53 console-kit-dae
1384 root 20 0 182m 2744 2124 S 0.0 0.3 0:00.99 polkitd
1394 admin_su 20 0 27468 8536 1700 S 0.0 0.8 0:00.87 bash
9812 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:1
10294 root 20 0 0 0 0 S 0.0 0.0 0:07.41 flush-8:0
11865 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 hci0
12759 test 20 0 4392 612 508 S 0.0 0.1 0:00.00 jobscheduler_ag
13307 root 20 0 0 0 0 S 0.0 0.0 0:01.97 kworker/0:2
13312 root 20 0 81876 3844 2988 S 0.0 0.4 0:00.01 sshd
13482 test 20 0 82024 1852 968 S 0.0 0.2 0:00.06 sshd
13483 test 20 0 23520 4584 1696 S 0.0 0.5 0:00.74 bash
13544 test 20 0 12768 944 768 S 0.0 0.1 0:00.05 sftp-server
13698 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kworker/0:0
13770 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:1
13795 test 20 0 4392 612 504 S 0.0 0.1 0:00.02 sh
13802 test 20 0 17344 1216 932 R 0.0 0.1 0:00.00 top
The job chain executes some database statements to collect
- the number of running orders
- the number of running tasks
- the number of configuration files for
Please note that the JobScheduler Reporting Interface has to be installed and active. The job chain /sos/reporting/Inventory has to be processed in order to create an up-to-date inventory of job-related objects.
The last step in the job chain reports the following information to the order log.
Example
2016-04-13 16:09:58.336+0200 [info] (Task support/report:18367873) 10 active orders found in the database
2016-04-13 16:09:58.342+0200 [info] (Task support/report:18367873) 0 active tasks found in the database
2016-04-13 16:09:58.353+0200 [info] (Task support/report:18367873) 19 orders defined for 24 job chains
2016-04-13 16:09:58.364+0200 [info] (Task support/report:18367873) 46 jobs defined
Please send the order log to the SOS Support Team.
The job ./support/execute_database_statement makes use of the following parameters:
| Parameter | Description | Default / Example |
|---|
db_class | SOSConnection class | SOSOracleConnection |
db_driver | The jdbc driver class | oracle.jdbc.driver.OracleDriver |
db_url | The JDBC connection string | jdbc:oracle:thin:@//d_host:1521/db_name |
db_user | The database schema user | |
db_password | The password for the user | |
- Find the values for your JobScheduler database connection in the file
$SCHEDULER_DATA/config/factory.ini in the section [spooler] with the entry db. - The order to start the job chain can be parameterized with the parameter
scheduler_id. If empty, then the scheduler_id of the current JobScheduler instance will be used.