Error Message

The Oracle application in Longitude 6.3 has a new "InstanceSpace" collector that collects the size of Free and Used space for instances. The default column size for these values in the backend MaxDB database has needed to be increased at some sites. See Collections fail with "Number is too big" error message for additional details.

To increase the maximum value for the FreeSpace and UsedSpace values, do the following:

Longitude writes the metrics it collects to tables in a backend MaxDB database. When an application is first monitored, it creates a table with predefined column sizes for each metric which specify the number of digits and amount of precision to use for the data.

For example, the error message:

Number 148694592 is too big for column size 10 having precision 2

means that the data being collected (148,694,592.00) is being written to a column with a maximum value of 99,999,999.99 (10 digits total, with 2 digits of precision).

When you add application monitoring for a server, Longitude checks the name of the supplied server in DNS and attempts to resolve the supplied name to a fully qualified domain name (FQDN).

We have seen instances in Longitude 6.3 where the call to get the FQDN has taken longer than expected, causing the Web UI to time out and produce a pop-up message with the error that Longitude "Failed to canonicalize" the requested name.

If you receive this error, do the following:

1. Verify that you can ping the server by the supplied name
2. Dismiss the error pop up message

WMI based collections require Local Administrator privileges on the target server. The Longitude Statistics Server Agent uses the permissions assigned to its service account to access WMI.

The following list displays the types of accounts that can be used to give the Statistics Server sufficient permissions to collect WMI data:

• Domain account that is a member of the Local Administrator group on the target server.
• Domain account that is a member of the Domain Administrator group, and will be a Local Administrator member on all domain servers by default.

To speed up SLA reports in Longitude 6.2.1, the data for the report is first summarized and written to a summary table - reports are run from this summary table.

If you try to run a report that does not use the same time selections written to the summary table, the report will display an error message that data is missing. Reports without a time selection (running from 00:00 --> 23:59) will display without this error.

To display SLA reports for specific time periods, define the SLA collection times to only be during the times of interest.

If you get this message when trying to register a collection please do the following.

1. Determine which agent you were using to try and register the collection.
2. Restart the agent that you tried to register the collection with from Services.msc or Administration > Component Management >Start-up/Shutdown.
3. Try and register the collection again.

On some Windows 2008 R2 servers, Longitude may experience one or more of the following problems:

• Time archived by Longitude is in GMT
• WMI collections fail with errors like Exception Thrown while performing operation: $1
• Component status in Administration >> Component Management >> Display Status is red, even through components are running

 
 
To patch these errors, please do the following:

Firefox 3.6 requires Selenium 1.04 or higher. If you are using these versions of Firefox and Selenium to create Internet macros for the Internet application, you will get an error message that Longitude is "unable to delete" a file named "parent.lock".

This is fixed by an updated selenium-server.jar file. To put this in place, do the following:

1. Download the updated selenium-server.jar file.
2. Stop the Longitude services.

In Longitude 6.2, if you suspend all collections in Manage Monitoring, the MONITOR APPLICATION, REMOVE APPLICATIONS, and SUSPEND APPLICATIONS buttons are not available on the page, and you will see the following message:

Data is not loaded. Please try again in a few minutes.

To display the suspended servers and the management buttons:

1. Go to the main Monitoring page.
2. In the Manage Applications menu, click the Add link
3. Register a ping transaction for a server that is not suspended