Error: System can not find the path specified|
This error is generally seen when using perl-based plug-in monitors and may refer to any path listed in the perl script.
This issue can usually be resolved by ensuring that perl exists where it should (default should be C:\perl\bin\perl) and that all paths referenced in the perl script are valid (e.g. ..\\tmp\\). |
Article InfoIndex: 551 OptionsQuick Links |
SAR error and SADC problems on AIX 5.3 | Rating | Views | |
|---|---|---|---|
|
|
By: uptime Support | Date Created: 9-23-2005 | Last Modified: 7-5-2011 | Index: 005 |
 
|
8323 |
How to find your HostID | Rating | Views | |
|---|---|---|---|
|
|
To find your up.time monitoring station HOSTID you will need to go through the following process. Your HOSTID is required in order to generate your permanent up.time license key. First, you MUST... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 9-7-2011 | Index: 253 |
|
3079 |
Process Check monitor does not check the full Solaris path | Rating | Views | |
|---|---|---|---|
|
|
Problem: At times the Check for a Process (Process Check) monitor may not check against a processes full path on Solaris systems. The up.time agent uses the "ps" command to match running processes.... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 9-9-2011 | Index: 236 |
|
4663 |
Excluding drives in the File System Capacity monitor | Rating | Views | |
|---|---|---|---|
|
This article outlines how to force the File System Capacity monitor to exclude specific drives or file systems. By: uptime Support | Date Created: 6-22-2007 | Last Modified: 6-28-2011 | Index: 187 |
|
3288 |
Metrics Monitored by Operating System | Rating | Views | |
|---|---|---|---|
|
|
This article lists the standard metrics that up.time monitors by operating system. By: uptime Support | Date Created: 6-6-2007 | Last Modified: 6-29-2011 | Index: 159 |
|
2996 |
