Table of Contents |
---|
Scope
- 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.
Jobs and
...
Job Chains
- The jobs and job
...
- chain configuration files are attached to this article: support.zip
Installation
- Download the attached configuration files and put store them to you $scheduleryour
$SCHEDULER_dataDATA/config/live
folder. There should be exist a subfolder sub-folder./support
after installationextracting the files from the archive. - Adjust the parameters for the database connection in the job
DB Statement
Job get_environment_data
This is a standalone job that
- uname
- detect running JobScheduler instances
- reads all environment variables
- executes a top command.
The output will be stored in the file
Parameter | Descriptin | Default |
---|---|---|
output_file_name | The name of the file, that contains 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 log file to the SOS support team.
execute_database_statement
Display feature availability StartingFromRelease 1.9
Job Chain get_support_data
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
- orders
- job chains
- jobs
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.
Job get_environment_data_linux and get_environment_windows
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.
- execute a
- 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 |
Configuration
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 entrydb
. - The order to start the job chain can be parameterized with the parameter
scheduler_id
. If empty, then thescheduler_id
of the current JobScheduler instance will be used.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
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
| ||||||
Code Block | ||||||
| ||||||
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 [03]: KB3135173 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[04]: KB3139907 2 root 20 0 0 [05]: KB3140741 0 0 S 0.0 0.0 0:00.03 kthreadd 3 root 20 0 0 0[06]: KB3140743 0 S 0.0 0.0 0:01.49 ksoftirqd/0 5 root 20 0 0 0 0 S[07]: KB3140768 0.0 0.0 0:07.73 kworker/u:0 6 root RT 0 0 0 0 S 0.0 0.0[08]: KB3144756 0:00.00 migration/0 7 root RT 0 0 0 0 S 0.0 0.0 2:00.53 watchdog/0[09]: KB3154132 8 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset [10]: KB3147458 Netzwerkkarte(n): 9 root 0 -20 0 7 0 Netzwerkadapter installiert. 0 S 0.0 0.0 0:00.00 khelper 10 root 20 0 0 [01]: VMware Virtual 0Ethernet Adapter for VMnet8 0 S 0.0 0.0 0:00.00 kdevtmpfs 11 root 0 -20 0 0 0 S 0.0 0.0 0Verbindungsname:00.00 netnsEthernet 3 12 root 20 0 0 0 0 S 0.0 0.0 0:00.86 sync_supers DHCP aktiviert: Ja 13 root 20 0 0 0 0 S 0.0 0.0 0:00.02 bdi-default 14 root DHCP-Server: 0 -20 192.168.146.254 0 0 0 S 0.0 0.0 0:00.00 kintegrityd 15 root 0 -20 0 0 0 SIP-Adresse(n) 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[01]: 192.168.146.1 17 root 20 0 0 0 0 S 0.0 0.0 0:00.27 khubd [02]: fe80::2956:c507:632a:b82f 18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md [02]: Astaro SSL VPN Adapter 21 root 20 0 0 0 0 S 0.0 0.0 0:00.09 khungtaskd Verbindungsname: Ethernet 2 22 root 20 0 0 0 0 S 0.0 0.0 0:09.69 kswapd0 23 root Status: 25 5 Medien getrennt 0 0 0 S 0.0 0.0 0:00.00 ksmd 24 root 39 19 [03]: VMware Virtual 0Ethernet Adapter for VMnet1 0 0 S 0.0 0.0 0:00.00 khugepaged 25 root 20 0 0 0 0 S 0.0 Verbindungsname: 0.0Ethernet 5 0:00.00 fsnotify_mark 26 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ecryptfs-kthrea 27 root DHCP aktiviert: Ja 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto 35 root 0 DHCP-20Server: 192.168.114.254 0 0 0 S 0.0 0.0 0:00.00 kthrotld 37 root 20 0 0 0 IP-Adresse(n) 0 S 0.0 0.0 0:00.00 scsi_eh_0 38 root 20 0 0 0 0 S 0.0 0.0 [01]: 192.168.114.1 0:00.00 scsi_eh_1 60 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 devfreq_wq [02]: fe80::71a5:b961:9dd3:2fd9 163 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 mpt_poll_0 164 root [04]: Intel(R) Centrino(R) Wireless-N 2230 Driver 0 -20 0 0 0 S 0.0 0.0 0:00.00 mpt/0 211 root 20 0Verbindungsname: WiFi 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_2 227 root 20 0 0 0 Status: 0 S 0.0 0.0 0:24.96 jbd2/sda1-8Medien getrennt 228 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ext4-dio-unwrit [05]: 314Realtek rootPCIe GBE Family Controller 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 0Verbindungsname:00.71 udevdEthernet 4 407 messageb 20 0 23940 996 820 S 0.0 0.1 0:01.17 dbus-daemon 411 syslog 20 0Status: 243m 1048 1048 S 0.0 0.1 Medien getrennt 0:29.21 rsyslogd 435 root 20 0 21448 524 356 S 0.0 0.1 0:00.10 udevd [06]: DisplayLink Network Adapter NCM 436 root 20 0 21448 548 364 S 0.0 0.1 0:00.08 udevd 611 root Verbindungsname: 20Ethernet 6 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 DHCP 0aktiviert:00.00 vsftpd Ja 635 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kpsmoused DHCP-Server: 192.11.0.1 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 IP-Adresse(n) 902 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty [01]: 192.11.0.12 906 root 20 0 15964 808 804 S 0.0 0.1 0:00.00 getty 907 root 20 [02]: 0 15964fe80::b16e:1cd6:9837:359e 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[07]: Bluetooth Device (Personal Area Network) 924 root 20 0 4320 552 548 S 0.0 0.1 0:00.00 acpid Verbindungsname: Bluetooth-Netzwerkverbindung 935 whoopsie 20 0 195m 3656 3296 S 0.0 0.4 0:15.45 whoopsie 936 mysql 20 0 537m 35m 1744Status: S 0.0 3.6 0:28.06 mysqld Medien getrennt Anforderungen fr Hyper-V: 939 root 20 Erweiterungen fr 0 19104 884den VM-šberwachungsmodus: Ja 800 S 0.0 0.1 0:00.33 cron 940 daemon 20 0 16900 216 216 S 0.0 0.0Virtualisierung in Firmware 0aktiviert:00.00 atdJa 1115 root 20 0 222m 8260 3148 S 0.0 0.8 0:15.21 apache2 Adressbersetzung der zweiten Ebene: Ja 1143 root 20 0 65132 1952 1472 S 0.0 0.2 0:00.04 login 1146 www-data 20 0 222m 5552Datenausfhrungsverhinderung 428 S 0.0 0.5 0:00.00 apache2 verfgbar: Ja .............................. running JobScheduler instances .............................. sos_jobscheduler_agent_44 2460 Services 1147 www-data 20 0 222m 55520 428 S 0.0 0.5 0:00.00 apache24.496 K scheduler.exe 1148 www-data 201284 Services 0 222m 5552 428 S 0.0 0.5 0:00.00 apache2 0 143.856 K scheduler.exe 1149 www-data 20 0 222m 5552 428 S 0.0 0.5 0:00.00 apache210444 Services 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 job_chain_get_support_data executes some db sql
to get
- the number of active orders
- the number of active tasks
- the number of configuration files for
- orders
- job chains
- jobs
Please note that the reporting interface have to be installed and activated.
The last step in the job chains reports 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.
Configuration
The job /support/DB Statement has the following parameters
Parameter | Description | Default |
---|---|---|
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 db user | |
db_password | The password for the db user |
You can find the values for your database in the file $SCHEDULER_DATA/config/factory.ini in the section [spooler] in the entry db
The order to start the job chain can be parameterized with the parameter scheduler_id
. If empty, the scheduler_id of the actual JobScheduler will be used.
...
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
|