- The SOS Support Team relies on the completeness and accuracy of information that you provide about your JobScheduler environment.
- This article describes how to collect the information.
- Currently the collection process as explained with this article is available for Unix environments.
- The jobs and job chain configuration files are attached to this article: support.zip
- 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
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
Also the job get_environment_data_
linux|windows will be executed.
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 run the order get_support_data
and send the file specified in the parameter output_file_name
to the SOS Support Team.
The job according to the OS JobScheduler is running on the job ...linux or ....windows will be executed in the job chain. This job performs the following operations:
- Linux
- execute a
uname
command - detect any running JobScheduler instances
- read all environment variables
- execute a
top
command.
- Windows
- executing the command systeminfo
- detect any running JobScheduler instances
- read all environment variables
- get a processlist
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 |
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.
Hostname: HOST_name
Betriebssystemname: Microsoft Windows 10 Pro
Betriebssystemversion: 10.0.10586 Nicht zutreffend Build 10586
Betriebssystemhersteller: Microsoft Corporation
Betriebssystemkonfiguration: Eigenst„ndige Arbeitsstation
Betriebssystem-Buildtyp: Multiprocessor Free
Registrierter Benutzer: Windows User
Registrierte Organisation:
Produkt-ID: 00330-80000-00000-AA701
Ursprngliches Installationsdatum: 14.01.2016, 14:15:37
Systemstartzeit: 18.04.2016, 16:23:06
Systemhersteller: Dell Inc.
Systemmodell: Inspiron 7520
Systemtyp: x64-based PC
Prozessor(en): 1 Prozessor(en) installiert.
[01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~2101 MHz
BIOS-Version: Dell Inc. A11, 20.02.2014
Windows-Verzeichnis: C:\WINDOWS
System-Verzeichnis: C:\WINDOWS\system32
Startger„t: \Device\HarddiskVolume2
Systemgebietsschema: de;Deutsch (Deutschland)
Eingabegebietsschema: de;Deutsch (Deutschland)
Zeitzone: (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
Gesamter physischer Speicher: 8.067 MB
Verfgbarer physischer Speicher: 3.447 MB
Virtueller Arbeitsspeicher: Maximale GrӇe: 17.283 MB
Virtueller Arbeitsspeicher: Verfgbar: 9.139 MB
Virtueller Arbeitsspeicher: Zurzeit verwendet: 8.144 MB
Auslagerungsdateipfad(e): C:\pagefile.sys
Dom„ne: SOS
Anmeldeserver: Nicht zutreffend
Hotfix(es): 10 Hotfix(e) installiert.
[01]: KB3124200
[02]: KB3124263
[03]: KB3135173
[04]: KB3139907
[05]: KB3140741
[06]: KB3140743
[07]: KB3140768
[08]: KB3144756
[09]: KB3154132
[10]: KB3147458
Netzwerkkarte(n): 7 Netzwerkadapter installiert.
[01]: VMware Virtual Ethernet Adapter for VMnet8
Verbindungsname: Ethernet 3
DHCP aktiviert: Ja
DHCP-Server: 192.168.146.254
IP-Adresse(n)
[01]: 192.168.146.1
[02]: fe80::2956:c507:632a:b82f
[02]: Astaro SSL VPN Adapter
Verbindungsname: Ethernet 2
Status: Medien getrennt
[03]: VMware Virtual Ethernet Adapter for VMnet1
Verbindungsname: Ethernet 5
DHCP aktiviert: Ja
DHCP-Server: 192.168.114.254
IP-Adresse(n)
[01]: 192.168.114.1
[02]: fe80::71a5:b961:9dd3:2fd9
[04]: Intel(R) Centrino(R) Wireless-N 2230 Driver
Verbindungsname: WiFi
Status: Medien getrennt
[05]: Realtek PCIe GBE Family Controller
Verbindungsname: Ethernet 4
Status: Medien getrennt
[06]: DisplayLink Network Adapter NCM
Verbindungsname: Ethernet 6
DHCP aktiviert: Ja
DHCP-Server: 192.11.0.1
IP-Adresse(n)
[01]: 192.11.0.12
[02]: fe80::b16e:1cd6:9837:359e
[07]: Bluetooth Device (Personal Area Network)
Verbindungsname: Bluetooth-Netzwerkverbindung
Status: Medien getrennt
Anforderungen fr Hyper-V: Erweiterungen fr den VM-šberwachungsmodus: Ja
Virtualisierung in Firmware aktiviert: Ja
Adressbersetzung der zweiten Ebene: Ja
Datenausfhrungsverhinderung verfgbar: Ja
..............................
running JobScheduler instances
..............................
sos_jobscheduler_agent_44 2460 Services 0 4.496 K
scheduler.exe 1284 Services 0 143.856 K
scheduler.exe 10444 Services 0 114.248 K
..............................
environment variables
..............................
ALLUSERSPROFILE=C:\ProgramData
PROMPT=$P$G
SCHEDULER_HOST=HOST_name
SCHEDULER_PARAM_COUNT_JOB_CHAIN_FILES=16
SCHEDULER_PARAM_SCHEDULER.VARIABLE_NAME_PREFIX=SCHEDULER_PARAM_
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
APPDATA=C:\WINDOWS\system32\config\systemprofile\AppData\Roaming
CLASSPATH=C:\Program Files (x86)\Altova\xmlspy\XMLSpyInterface.jar
APR_ICONV_PATH=C:\Program Files (x86)\Subversion\iconv
windir=C:\WINDOWS
CommonProgramW6432=C:\Program Files\Common Files
SCHEDULER_HOME=C:/Program Files/sos-berlin.com/jobscheduler/scheduler_4198
COMPUTERNAME=UR_DELL
ComSpec=C:\WINDOWS\system32\cmd.exe
Devmgr_show_details=1
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_31
Devmgr_show_nonpresent_devices=1
FP_NO_HOST_CHECK=NO
SCHEDULER_SUPERVISOR_HOST=
SCHEDULER_SUPERVISOR_PORT=
LOCALAPPDATA=C:\WINDOWS\system32\config\systemprofile\AppData\Local
SCHEDULER_ORDER_ID=start
NUMBER_OF_PROCESSORS=8
PROCESSOR_REVISION=3a09
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\PROGRA~2\Borland\Delphi5\Projects\Bpl;C:\PROGRA~2\Borland\Delphi5\Bin;C:\oraclexe\app\oracle\product\11.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\PROGRA~2\F-Secure\Ssh;C:\Program Files (x86)\Subversion\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\IDM Computer Solutions\UltraEdit-32;C:\Program Files (x86)\Mscgen;C:\Program Files (x86)\Graphviz2.32\bin;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\GitExtensions\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\AMD\ATI.ACE\Core-Static;C:\Program Files\nodejs\;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ProgramW6432=C:\Program Files
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
SCHEDULER_JOB_CONFIGURATION_DIRECTORY=C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_4198/config/live/support_ur
TEMP=C:\WINDOWS\TEMP
PROCESSOR_LEVEL=6
prod_dir=c:\temp
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
SCHEDULER_UDP_PORT=4198
ProgramFiles(x86)=C:\Program Files (x86)
PSModulePath=C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
SystemDrive=C:
SOS_LOCALE=en
SCHEDULER_CONFIGURATION_DIRECTORY=C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_4198/config/live
sos_remote=gollum
SCHEDULER_PARAM_COUNT_ORDERS=2
SCHEDULER_PARAM_NUMBER_OF_ITERATIONS=3
SCHEDULER_TASK_ID=93
SVN_EDITOR="C:\Program Files (x86)\IDM Computer Solutions\UltraEdit-32\uedit32.exe"
SystemRoot=C:\WINDOWS
TMP=C:\WINDOWS\TEMP
USERDOMAIN=SOS
USERNAME=UR_DELL$
SCHEDULER_PARAM_JITL.SSH.USE_JSCH_IMPL=true
USERPROFILE=C:\WINDOWS\system32\config\systemprofile
SOS_INI=C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_4198/config/sos.ini
SCHEDULER_DATA=C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_4198
SCHEDULER_JOB_NAME=get_environment_data_window
SCHEDULER_PARAM_OPERATION_SYSTEM=windows
SCHEDULER_TCP_PORT=4198
SCHEDULER_ORDER_HISTORY_ID=26
SCHEDULER_TASK_TRIGGER_FILES=
SCHEDULER_JOB_CHAIN=get_support_data
SCHEDULER_JOB_CHAIN_CONFIGURATION_DIRECTORY=C:/Users/ur/Documents/sos-berlin.com/jobscheduler/scheduler_4198/config/live/support_ur
SCHEDULER_RETURN_VALUES=C:\WINDOWS\TEMP\sos7C60.tmp
SCHEDULER_PARAM_SCHEDULER.ORDER.KEEP_ORDER_CONTENT_ON_RESCHEDULE=false
SCHEDULER_PARAM_SCHEDULER_ID=scheduler_4198
SCHEDULER_PARAM_OUTPUT_FILE_NAME=sos_support.log
SCHEDULER_PARAM_COUNT_JOB_FILES=47
SCHEDULER_PARAM_COUNT_ORDER_FILES=61
SCHEDULER_PARAM_COUNT_TASKS=0
..............................
top command
..............................
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id SI ProcessName
Scheduler processes
744 46 369856 143856 3665 263,05 1284 0 scheduler
433 22 276272 112572 3570 6,72 10444 0 scheduler
741 44 338388 121844 3665 263,27 1284 0 scheduler
741 44 339728 122964 3665 263,33 1284 0 scheduler
Processes sorted by CPU
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id SI ProcessName
------- ------ ----- ----- ----- ------ -- -- -----------
1429 153 460548 370732 1230 1.773,23 3524 1 firefox
792 68 142828 137292 ...67 1.727,78 2900 0 MsMpEng
977 25 44860 19588 361 1.269,11 1808 0 DisplayLinkMan...
625 50 95876 72644 ...87 1.062,78 508 1 dwm
1153 96 705880 429680 35307 678,03 10548 1 eclipse
1869 0 1616 526268 611 668,89 4 0 System
707 40 10796 26328 181 443,16 6304 1 OneDrive
925 56 113512 111124 ...81 414,69 528 0 svchost
3516 329 134956 161884 ...23 405,81 5932 1 explorer
544 31 20548 25660 204 372,59 3000 1 SetPoint
356 21 26472 35016 ...72 284,72 4748 0 WmiPrvSE
2249 77 28204 49088 ...88 277,42 1288 0 svchost
740 44 339728 122996 3665 263,41 1284 0 scheduler
344 16 10060 18540 ...10 176,53 4432 0 WmiPrvSE
778 94 285856 228024 723 116,86 5092 1 thunderbird
0 0 0 4 0 0 0 Idle
Processes sorted by name
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id SI ProcessName
------- ------ ----- ----- ----- ------ -- -- -----------
449 19 3700 12460 103 0,47 6368 1 Amazon Music H...
625 28 24116 28412 ...94 1,30 14292 1 ApplicationFra...
111 8 1164 5220 54 0,03 2748 0 armsvc
214 10 2080 8364 96 0,63 3012 1 atieclxx
130 7 1072 4564 34 0,03 1088 0 atiesrxx
160 10 6260 10792 ...98 0,13 13920 0 audiodg
402 25 13976 35344 262 0,17 1848 1 CallsApp
1160 107 102660 6160 33641 54,73 8008 1 CCC
998 46 59100 36508 378 11,59 11144 1 chrome
243 22 39372 19648 231 1,11 14248 1 chrome
135 9 1484 5472 75 0,02 4636 1 chrome
303 23 42144 17296 250 1,81 5228 1 chrome
151 13 3140 10760 100 0,06 2280 1 ClassicStartMenu
40 4 4828 3200 ...72 0,08 9628 0 cmd
249 10 7300 9884 ...95 11,22 2296 0 WmiPrvSE
288 24 33208 26020 229 3,02 10908 1 Xming
2 active orders found in the database
0 active tasks found in the database
61 orders defined for 16 job chains
47 jobs defined