You are hereApplication / Unix / Unix

Unix


7.1 : In the 2.0 UI, when trying to set up an Event for Unix Network not all Events are listed .

When trying to configure an Event for Unix Network there are only four options available:
• HighNetworkInputErrors
• HighNetworkInputPackets
• HighNetworkOutputErrors
• NetworkCollisions

The HighNetworkOutputPackets is missing. To correct this issue follow the steps below:

  1. Download the index-all.js file
  2. Navigate to \Longitude\tomcat\webapps\webui\web2.0\javascripts and rename the current index-all.js file to index-all.old and save the new file to this location

7.1: Unable to apply an action for Unix -> Filesystem when specific time restrictions are set in the Web 2.0 interface.

When trying to create an action for a Unix Filesystem event with a time restriction in the Web 2.0 interface, an error message stating “Error retrieving action:”appears. To correct this issue follow the steps listed below:

  1. Download the firenze-web2.jar file
  2. Stop the webui service.
  3. Navigate to \Longitude\tomcat\webapps\webui\WEB-INF\lib and rename the current firenze-web2.jar file to firenze-web2.old and save the new file to this location

Can I Monitor a 64 bit Server Server with 6.1.2?

Yes you can Monitor 64 bit Windows and Unix with 6.1.2. You cannot however install the management console on a 64 bit Server. If you would like the ability to have your management console and agents installed on 64 bit servers you will need to upgrade to version 6.2.

kb94: Unix CPU percentages on HPUX inaccurate.

Longitude uses the iostat command to collect the CPU_IDLE_PCT statistic. On HP-UX, this command may return inaccurate values, which can result in CPU Busy percentages over 100%, and CPU Idle percentages less than 0.

kb93: Metrics are reported as "-1" on AIX

The RUNNABLE_PROCESSES and SWAP_OUT_RATE metrics are not collected for AIX, so the values are set to -1 to indicate that these metrics are not available on AIX for the Unix application.

kb80: Invalid datatype row rejections for the Unix application.

The default shell for the account specified when adding the Longitude Unix application should be the Bourne shell. The Unix application may failed to archive data using other shells, as the command output may be rejected if it does not match the expected datatype. The error below is an example of what is returned when testing a collection in this case:

RowRejectException: Failed to process row
'[export:, ps:, usage:, 0, ps:, usage:, 0, ps:, usage:, 0]'

Caused by: com.heroix.firenze.dc.gp.RowRejectException: Input 'export:'

kb77: Unix registration fails with uname error

If you attempt to add the Unix application and it fails with the uname error below, make sure that you can ssh (rexec can be used if ssh is not enabled) to the target and run the uname -a command:

This collection is not registered. Error when registering a collection. Check Error Log for more details.
Fail to execute the command: uname -a
java.io.IOException: Server closed connection

kb75: Account privileges for monitoring Unix

When you add the Unix application, the account that you specify must have privilege to execute the following on the monitored computer:
All Platforms:

  • iostat
  • ps
  • df

Platform Specific:

  • AIX
    vmstat, lsattr, lsps, netstat
  • HP-UX
    vmstat, swapinfo, netstat, "grep Physical /var/adm/syslog/syslog.log"

    ***Note:If using a non-root account, verify it has execute privileges for /usr/sbin/swapinfo ***

kb74: Unix\Linux collections fail to register

Please see the requirements below if collections fail to register when you add the Unix application:

  1. The computer must support SSH or rexec access. If SSH is not enabled, then rexec is used.
    Note: Some SSH implementations may prohibit root from logging in to the system directly. You can use a non-root account to collect Unix metrics in most cases.
  2. If you configure Longitude to collect statistics from the computer as root, the computer must not be configured to disallow remote access as root.