SiteScope Log Monitor error message “awk: line 1: syntax error at or near”

In SiteScope (SiS) the Log Monitor using "server-side processing" could throw the error message:

ERROR – Error during log parsing: awk: line 1: syntax error at or near, awk: line 1: syntax error at or near }

The cause is the awk version.

RedHat use GNU awk (GNU Awk 3.1.7), Debian mawk (mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan).

The Debian’s awk does not support 3th argument for match function.

SiteScope is not checking what it needs to execute the command correctly, and there is no adaption depending of the used awk version on the remote system.

To check the AWK version execute “awk –W version”.

To install the gawk on Debian like systems use “apt-get install gawk”.

To test manually the issue use the command:

tail -c +1 <PATH + LOG FILE> |

awk ‘BEGIN{sismatches=0; if("") { RS ="" }} \

{ if((regexp && match($0, "123",groups)) ||

(!regexp && index($0, "123"))) {sismatches=sismatches+1; print "sis-matches"; \

i=0; while("true") { if (i in groups) { print "sis-match-group"; print groups[i]; i=i+1 } else {break}}}} END {if(sismatches == 0) {print "sis-no-matches-found"}}’ regexp=;

On success the message will be : “sis-no-matches-found”.

Otherwise the message will be like “syntax error at or near”.

Advertisements

SiteScope monitor often encounters “System error 1219” for Windows Remote

System error 1219 is from Windows OS, not SiteScope error. That means, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When user configures Windows Remote and some monitors(i.e. CPU, Logfiles), user may encounter the 1219 error by perfex.

Here is a sample.

18:03:04 12/20/2011 good group.25 CPU_monitor no data due to Error: CPU Monitor error for machine \\10.0.0.1, exit code: 1219 3:19 n/a

This is one of the examples,

a. Customer configured Domain Administrator user as SiteScope Service account.

DOMAIN1\Administrator

b. Customer configured local administrator user as Windows Remote in SiteScope.

10.0.0.1\administrator

Since the SiteScope service runs as Domain Administrator user, the SiteScope may access to remote shared resource by the account.

CPU, Memory and Disk monitors used perfex command to monitor the remote server.

The credential is based on Windows Remote configuration in SiteScope.

To avoid this issue, we have two solution.

1. Using alias hostname for each monitored servers.

1-1. Add alias hostname to C:\Windows\System32\drivers\etc\hosts

i.e.

10.0.0.1 host-A host-A1

1-2. Edit Remote Server configuration in SiteScope

i.e.

Server: host-A1

Credentials: host-A1\administrator

SiteScope can access to Windows Remote server by using alias hostname instead of original configuration(i.e. IP address, original hostname).

Since SiteScope uses the alias name for perfex connection, the user never conflict.

or

2. Using -optionalSetupConnection as perfex option.

2-1. Add the follosing optin in \SiteScope\groups\master.config file

_perfexOptions=-optionalSetupConnection

2-2. Restart SiteScope service

It was recommended that SiteScope monitor uses Remote Windows servers configuration instead of running the service as a specific user. This works fine for most cases.

However, user will need to check the credential if all kind of monitor can work.

SiteScope monitor often encounters “System error 1219” for Windows Remote

System error 1219 is from Windows OS, not SiteScope error. That means, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When user configures Windows Remote and some monitors(i.e. CPU, Logfiles), user may encounter the 1219 error by perfex.

Here is sample.

Error repeating in log after 11.20 upgrade

Getting the following errors looping in the error.log:

2012-06-11 16:18:52,683 [ImportTimer] (SiSImportPolicy.java:363) ERROR – Failed to remove MDW template. Therefore import of new MDW template is ignored. Please, remove old MDW templates and tags manually.

2012-06-11 16:19:52,698 [ImportTimer] (ConfigManager.java:758) ERROR – Commit verification failed due to:

2012-06-11 16:19:52,698 [ImportTimer] (APITemplate.java:4124) ERROR – Dependency exception, cannot delete current entity due to dependencies found upon it, details: The entity is referenced by

Template entities:

%%host_dnsname%% %%host_username%%;

Please remove this reference before deleting current entity

This error occurs when SiteScope is trying to import a template/group/monitor and there is already one imported into SiteScope.

This behavior is standard sis behavior when importing silently from the hot folder (persistency/import): if a template container exists in persistency, a unique name violation prevents sis from importing the same template container from a file.

Removing\renaming the template container before import solves the problem, or if a merge/override is desired it is possible to do it from the UI starting in 11.12.

Related Quixy information:

http://quixy.deu.hp.com/quixy/query/detail.php?ISSUEID=QCCR1I48464

http://quixy.deu.hp.com/quixy/query/detail.php?ISSUEID=QCCR1I32269

Check to see if there are any files in the sitescope/peristency/import directory.

Rename any files in this directory and restart SiteScope.

SiteScope System Health – how to install on Linux

SiteScope System Health on Linux is available since SiteScope 11.10, however it requires a patch to act as System Health.

Install SiteScope 11.10 on Linux, choose "HP SiteScope" as option (System Health is NOT available at that time)

Stop SiteScope

Install patch

SIS_00173 (for Linux SiteScope 11.10 32-bit)

or

SIS_00174 (for Linux SiteScope 11.10 64-bit)

In the example below SiteScope 11.10 64 bit has been installed on a 64 bit RH Linux system, thus patch SIS_00174 needs to be downloaded and installed:

# unzip SIS_00174.zip

Archive: SIS_00174.zip

creating: linux64/package/

inflating: linux64/package/SystemHealth-11.10.000-Linux2.6_64.rpm

inflating: linux64/package/SystemHealth-11.10.000-Linux2.6_64.rpm.xml

inflating: linux64/postinstall_launch_sis_config.sh

inflating: linux64/readme.txt

inflating: linux64/SIS_patch.sh

# cd linux64

# ls

package postinstall_launch_sis_config.sh readme.txt SIS_patch.sh

# chmod +x SIS_patch.sh

# ./SIS_patch.sh

INFO: This script will remove following rpm packages:

1. SiteScope-11.10.000-Linux.rpm

2. SiteScopeProduct-11.10.000-Linux.rpm

Script will install:

SystemHealth-11.10.000-Linux<32/64>.rpm (SystemHealth content)

If you want to proceed the action input Y and press ENTER

otherwise input N and press ENTER >

The script will executed

INFO: (./SIS_patch.sh) Validating SiteScope installation

INFO: (SIS_patch.sh) Installation verified

INFO: (SIS_patch.sh) Checking existence of: SiteScope-11.10.000

INFO: (SIS_patch.sh) Checking existence of: SiteScopeProduct-11.10.000

INFO: (SIS_patch.sh) Uninstalling: SiteScope-11.10.000

INFO: (SIS_patch.sh) Uninstalling: SiteScopeProduct-11.10.000

INFO: (SIS_patch.sh) Installing: SystemHealth-11.10.000-Linux2.6_64.rpm

INFO: Executing configuration wizard

Unable to perform a ‘copy to template’ on some groups

If you are unable to perform a ‘copy to template’ and get the following error:

Failed to copy template entity, Class:
TemplateProxy
copyInfoTemplate,Method(1)..

This error will be written to the error.log on the SiteScope server this operation was being performed on:
2012-06-25 10:43:55,522 [http-8080-Processor21] (TemplateProxy.java:1798) ERROR – Runtime exception occurred during copy into template, details: null

Edit the Group by adding an entry into group description. Then try the "copy to template" again.

Use global search and replace to change the group tags on all monitors in the group which will resolve the problem.

Sitescope (SiS) RunMonitor.log throws exception: java.io.IOException: The pipe is being closed The pipe is being closed

(SingleProcess.java:273) ERROR – processID 15 onFailure processID 15 : Failed to write to stdout: E:\SiteScope\tools\perfex.exe *3860 \\<<remote_server_name -connect -u <user_name> -p <password> -timeout 120 -a, Process=15, exception: java.io.IOException: The pipe is being closed The pipe is being closed

The exceptions caused the Service monitors (total count = 20) to change their error/good counter status constantly.

In addition, Sitescope reported a huge number of Perfex Process Pool double failures.

Sitescope installation: Virtual machine with Windows 2003 server 32-bit, 1GB physical memory.

SiS sizing was performed without success.

During the troubleshooting session the traffic between SiteScope and Remote server by WireShark was attempted to be captured.

The traffic analysis shows that each time a monitor is in error status no traffic occurred.

It was also observed that the count of perfex processes within Sitescope service tree appeared to be unusually low.

This is also confirmed by the huge number of Server Statistics>Perfex Process Pool>double failures, displayed by the Health>connection Statistics Monitor>Process Manager: double failures counters as well.

It was concluded, the perfex processes did not have enough allocated memory to be performed, though JVM sizing performed.

The resolution is to increase the physical memory (e.g. 1GB to 2GB) for SiS environment so one can operate flawlessly.