Sign In

phperror.log file filled with "File does not exist" errors

The default up.time error logging level is ALL messages. This can cause a large number of messages to be registered in the phperror.log file. Some example messages are:

[Fri Sep 29 17:25:17 2006] [error] [client 10.1.1.125] File does not exist: /opt/uptime4/GUI/images/reports.gif, referer: http://host/footer.php
[Fri Sep 29 17:25:17 2006] [error] [client 10.1.1.125] File does not exist: /opt/uptime4/GUI/images/globalscan.gif, referer: http://
host/footer.php

These messages have no direct impact on up.time performance or functionality and should therefore not be a cause for concern.

To remove these messages, disable logging of PHP warnings in Apache by following these steps:

Edit the <uptime_dir>/apache/php/php.ini file.
Modify the line from error_reporting = E_ALL to error_reporting = E_ERROR.
Delete the phperror.log file and restart the up.time Web Server or uptime_httpd service (depending on your platform).

Article Info

Index: 478
Author: CSS
Created: 8-13-2010
Updated: 8-13-2011
Views: 2126
Rating:

Options

Rate This Article

Email This Article

Print This Article

Quick Links

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		3128

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

3128

How many exclusions can the File System Capacity Monitor use?	Rating	Views
	No, the File System Capacity monitor is set to only allow 5 entries for exclusions or special cases. If you find that 5 is too limiting there are two options 1) Ensure you are using the * wildcard... By: uptime Support \| Date Created: 12-31-1969 \| Last Modified: 8-31-2011 \| Index: 300		2177

How many exclusions can the File System Capacity Monitor use?

Rating

Views

No, the File System Capacity monitor is set to only allow 5 entries for exclusions or special cases. If you find that 5 is too limiting there are two options 1) Ensure you are using the * wildcard...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 300

2177

File System Capacity Monitor Examples	Rating	Views
	Below are some common examples for use in the File System Capacity Service Monitor. 1 - Ignore a drive. Set one or more exclude patterns to the drive name Windows Example: "D:" Other: "/usr" 2 -... By: uptime Support \| Date Created: 12-31-1969 \| Last Modified: 8-31-2011 \| Index: 301		3216

File System Capacity Monitor Examples

Rating

Views

Below are some common examples for use in the File System Capacity Service Monitor. 1 - Ignore a drive. Set one or more exclude patterns to the drive name Windows Example: "D:" Other: "/usr" 2 -...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 301

3216

Tru64 agent does not ignore NFS file systems	Rating	Views
	On some versions of the Tru64 agent NFS file systems were not igrnored by default. To resolve this issue please update your agent (available on support.uptimesoftware.com) or make the following... By: uptime Support \| Date Created: 10-10-2009 \| Last Modified: 8-13-2011 \| Index: 409		1583

Tru64 agent does not ignore NFS file systems

Rating

Views

On some versions of the Tru64 agent NFS file systems were not igrnored by default. To resolve this issue please update your agent (available on support.uptimesoftware.com) or make the following...

By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 409

1583

Windows agent not showing file systems above 1.37 TB	Rating	Views
	Previous versions of the up.time Windows agent may not recognize file systems greater than 1.37TB. To resolve this issue, please update to the latest version of the Windows agent. By: uptime Support \| Date Created: 10-14-2009 \| Last Modified: 8-10-2011 \| Index: 428		1951

Windows agent not showing file systems above 1.37 TB

Rating

Views

Previous versions of the up.time Windows agent may not recognize file systems greater than 1.37TB. To resolve this issue, please update to the latest version of the Windows agent.

By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-10-2011 | Index: 428

1951

My Uptime IM

phperror.log file filled with "File does not exist" errors

Article Info

Options

Quick Links

Related Articles

Excluding drives in the File System Capacity monitor

How many exclusions can the File System Capacity Monitor use?

File System Capacity Monitor Examples

Tru64 agent does not ignore NFS file systems

Windows agent not showing file systems above 1.37 TB

User Comments

No comments have been posted.

Email:
Password: