Bugzilla – Full Text Bug Listing
| Summary: | Readme - Cannot import log file | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Radu Negulescu <rnegu> |
| Component: | Hyades | Assignee: | Kari Halsted <khalsted> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | Documentation |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Solaris | ||
| Whiteboard: | |||
|
Description
Radu Negulescu
More precisely, the symptom is: A log view opens with no log records in it. Reopening the log view after the import operation terminates also displays no log records. Dave, please take a look This problem is a known problem when the Agent Controller is not started with root privileges. Radu started Agent Controller with his own user ID. When doing remote import, the Generic Log Adapter parses the log file and logs any error messages to a file called hgla.log in the current directory which on Solaris is /var/tmp. If this file already exists and cannot be overwritten, say because Generic Log Adpater process does not have write permission to the file, the log import operation will fail. In this case, /var/tmp/hgla.log existed and was created by root with 644 permissions. The Agent Controller launches the Generic Log Adapter process under the same user privileges as it was started with so Generic Log Adapter cannot overwrite the /var/tmp/hgla.log file. I will re-assign this to the doc component to have a readme item added for this case. This problem has been fixed in later releases with bugzilla 69772. Here is the explanation of the two symptoms mentioned: 1) Error message is issued on the Solaris console: sh: sysdef: not found This is another known unrelated problem that is already documented in the Hyades 3.0.1 Release Notes. 2) Error signal is recorded in hs*.log files /var/temp/ Unexpected Signal : 11 occurred at PC=0xFECF1EE0 Function=[Unknown. Nearest: JVM_GetClassLoader+0x724] Library=/usr/j2se/jre/lib/sparc/client/libjvm.so This exception is generated as a result of GLA not being able to create the hgla.log file and the error is not being handled properly. Fixing this will have no effect on the original problem of not being able to create the hgla.log file. The remote log import operation will still fail. Again, this problem is fixed in subsequent releases with bugzilla 69772. The following readme item should be added to the Hyades v3.0.1 and v3.0.2 readmes under Log and Trace Analyzer: Problem: Cannot import a log file from a remote system. Sometimes when importing a log file from a remote system no data is shown in the Log View and no error message is displayed. Error messages may be logged on the remote system in a file called hgla.log. The hgla.log file will be located on the remote system in the /tmp or /var/tmp directory if running on a UNIX or Linux system or in c:\Documents and Settings\userid\Local Settings\Temp if running on a Windows system. Please note, the remote log import operation will fail if the hgla.log file cannot be created or written to. If hgla.log exists on the remote system before the remote log import operation begins, it must have the necessary permissions for the user that started Agent Controller on the remote system to write to the file, in order for the log import operation to be successful. To ensure this condition exists, either delete the hgla.log file on the remote system or restart the Agent Controller on the remote system as root user before importing the remote log file. Added to 301 and 302 readmes setting target based on last change date, please adjust if not correct Closing based on comments |