Top
Systemwalker Desktop Patrol Operation Guide: for Administrators
FUJITSU Software

3.2.13 Checking the Operational Status of CS/DS

This section explains how to check the operational status of the distribution server feature and inventory collection feature of CS/DS.

The operational status of CS/DS can be checked:

Executing logchecksv.exe (CS/DS operation status check)

Execute the following command:

cs/dsInstallDir\FJSVsbtrs\bin\logchecksv.exe

Refer to the Reference Manual for details on this command.

Table 3.11 [Items that can be checked on command prompt or in file]

Category

Item

Description

Type

Basic Information

Server Type

Basic information set in the environment setup window.

CS, DS

CS/DS Name

CS, DS

Host Name

CS, DS

Higher Host Name

DS

Host name resolution

Whether names can be resolved using the host name or upstream host name.

If successful, the IP address will be displayed.

CS, DS

Upstream host name resolution

DS

Windows host name

Windows information.

If not successful, then it will not be displayed.

CS, DS

Windows IPv4 address

CS, DS

Windows IPv6 address

CS, DS

Version information

Version information for CS/DS.

Example: V15.1.0-R1.1-SN1501

CS, DS

Communication setting

Connection interval with the support center

Content of the communication settings set in the Settings of CS window, Settings of DS window, or set using CustomPolicy.exe.

CS

Connection interval with upstream CS/DS

DS

Time frame for communicating with the support center

CS

Time frame for receiving the distributed software

DS

The maximum number of concurrent connections from a downstream DS or CT

CS, DS

Polling Interval

CS, DS

Policy information

Datetime of software dictionary creation

Datetime when the software dictionary on CS/DS was created.

CS, DS

Datetime of software dictionary update

Datetime when the software dictionary on CS/DS was updated.

CS, DS

Datetime of CS setting update

Datetime when the Settings of CS window was updated.

CS

Datetime of DS setting update

Datetime when the Settings of DS window was updated.

DS

Datetime of policy group update

Update datetime and error information for each policy group.

CS, DS

Datetime of unapplied patch detection information update

Datetime of unapplied patch detection information update and error.

CS, DS

Datetime of next unapplied patch detection operation

Next scheduled operation time for the unapplied patch detection schedule.

CS

Datetime of next connection to upstream servers

Next communication time for communication with an upstream server.

CS, DS

Distribution server feature status

Distribution server feature status

Status of the distribution server feature.

CS, DS

Heap memory size of distribution server (MB)

CS, DS

Insufficient memory status

CS, DS

Datetime of overflow of maximum concurrent connections from a downstream DS or CT

CS, DS

Status of connection to upstream servers

CS, DS

Inventory collection server feature status

Inventory collection server feature status

Status of the inventory collection server feature.

CS, DS

Heap memory size of inventory collection server (MB)

CS, DS

Insufficient memory status

CS, DS

Datetime of overflow of maximum concurrent connections from a downstream DS or CT

CS, DS

Software or file distribution status

Software distributed successfully to CS

Number of software distributed successfully.

Example: 15

CS

Updaters distributed successfully to CS

Number of updaters distributed successfully.

Example: 5

CS

Security patches distributed successfully to CS

Number of software distributed successfully.

Example: 300

CS

Files distributed successfully to CS

Number of software distributed successfully.

Example: 10

CS

Software distributed successfully to DS

Number of software distributed successfully.

Example: 15

DS

Updaters distributed successfully to DS

Number of updater distributed successfully.

Example: 5

DS

Security patches distributed successfully to DS

Number of software distributed successfully.

Example: 300

DS

Files distributed successfully to DS

Number of software distributed successfully.

Example: 10

DS

Software or file being prepared for distribution

Number of software or file being prepared for distribution.

Example: 10

DS

Distribution error information

Information about error during software or file distribution.

Example: Insufficient available capacity in software directory

DS

Software directory path name

Name of the software directory path.

CS, DS

Software directory size (set value/usage amount/available capacity)

Information about the software directory.

Example: 300MB/150.015MB/1010.938MB

CS, DS

Software directory path name for extension

Name of the software directory path for extension.

CS, DS

Software directory size for extension (set value/usage amount/available capacity)

Information about the software directory for extension.

Example: No setting/150.343MB/55023.023MB

CS, DS

Installation path

Name of the installation directory path to compare with the software directory.

CS, DS

Table 3.12 Content displayed in Distribution server feature status and Inventory collection server feature status

Item

Details

Description

Server feature status

Running (Start datetime:2014/09/18 10:10:30)

The server feature is running.

The datetime indicates the start time for the server feature.

Restarting

Automatic restart is being performed.

Not running (Services are not running)

Server feature has been stopped due to the services stopped.

Not running (Port number 2922 being used)

Sever feature has been stopped due to the port number 2922 being used by another application.

Not running (Port number 2856 being used)

Sever feature has been stopped due to the port number 2856 being used by another application.

Not running (Other errors)

Sever feature has been stopped due other errors.

Insufficient memory status

None

Memory insufficiency has not occurred.

2014/09/17 15:15:40

Datetime when memory insufficiency occurred.

Displays the datetime of the 5 most recent occurrences.

Datetime of overflow of maximum concurrent connections from a downstream DS or CT

None

Overflow of maximum concurrent connections has not occurred.

2014/09/17 17:30:15

Datetime when overflow of maximum concurrent connections occurred.

Displays the datetime of the 5 most recent occurrences.

Status of connection to upstream servers

Completed

Connection to the upstream server has completed successfully.

None

Connection to the upstream server has not been performed.

Connecting

Connection to the upstream server is being performed.

Display example for command prompt
----------------------------------------------------------------
Basic Information
---------------------------------------------------------------
Server Type: DS
CS/DS Name: dsServer1
Host Name: ds1.exmaple.com
Higher Host Name: cs.example.com
Host name resolution: Successful (192.0.2.0)
Upstream host name resolution: Successful (198.51.100.0)
Windows host name: ds1.example.com
Windows IPv4 address: 192.0.2.0
Windows IPv6 address: 2001:db8::%10
Version information: V15.0.0-R1.0-SN1400

--------------------------------------------------------------
Communication setting
--------------------------------------------------------------
Connection interval with upstream CS/DS: 5 minutes
Time frame for receiving the distributed software: 08:00 - 17:00
The maximum number of concurrent connections from a downstream DS or CT: 30
Polling Interval: 5 minutes

--------------------------------------------------------------
Policy information
--------------------------------------------------------------
Datetime of software dictionary creation at the support center: 2014/09/09 10:52:24
Datetime of software dictionary update: 2014/09/09 10:52:34
Datetime of DS setting update: 2014/09/09 10:52:24
Datetime of unapplied patch detection information update: 2014/09/09 11:02:11
Datetime of next connection to upstream servers: 2014/09/09 11:02
========Policy Group========
Status   Group Name    Update Date/Time
OK   CS (2014/09/10 15:40)
OK   DS1 (2014/09/10 16:45)
OK   DS2 (2014/09/09 10:20)
Failed   policyGroup1 (2014/09/10 11:10)
OK   policyGroup2 (2014/09/10 11:10)
Error information: policyGroup2 (GrpPolicy.5) Failed to write to files

--------------------------------------------------------------
Distribution server feature status
--------------------------------------------------------------
Running Status: Running (Start datetime: 2014/09/18 15:20:25)
Heap memory size: 256MB
Insufficient memory status: 
2014/09/15 13:20:45
2014/09/16 10:10:35
2014/09/16 13:34:10
2014/09/16 16:05:04
2014/09/17 09:30:25
Datetime of overflow of maximum concurrent connections from a downstream DS or CT: None
Status of connection to upstream servers: Completed

--------------------------------------------------------------
Inventory collection server feature status
--------------------------------------------------------------
Running Status: Running (Start datetime: 2014/09/18 15:22:10)
Heap memory size: 128MB
Insufficient memory status: None
Datetime of overflow of maximum concurrent connections from a downstream DS or CT: 
2014/09/15 13:20:45
2014/09/16 10:10:35
2014/09/16 13:34:10
2014/09/16 16:05:04
2014/09/17 09:30:25

--------------------------------------------------------------
Software or file distribution status
--------------------------------------------------------------
Software distributed successfully to DS: 10
Updaters distributed successfully to DS: 3
Security patches distributed successfully to DS: 150
Files distributed successfully to DS: 20
Software or file being prepared for distribution to DS: 10
Distribution error information: Insufficient available capacity in software directory
Software dictionary: D:\DesktopPatrol\swc
Software directory size (set value/usage amount/available capacity): 300MB/150.015MB/1010.938MB
Software directory for extension: No setting
Software directory size for extension (set value/usage amount/available capacity): No setting/150.343MB/55023.023MB
Installation path: C:\Program Files\Fujitsu\Systemwalker Desktop Patrol