Sierra 5391-02, 5391-01 Potential Problems with Event Logging File Problems, Space Problems

Page 24

T12017-Sentry_LANServer_Users_Manual

Page 24 of 59

5.9.3.Potential Problems with Event Logging

5.9.3.1.File Problems

Events are written to file on the LANServer’s flash disk. When the events page is viewed the file is read from the flash disk. Errors could occur with the file. These are reported on the error screen.

Produced when viewing events page

WEB:#19 Err. Reading event record file.

WEB:#20 Err. Bad file pos.

WEB:#21 Err. Opening event record file.

Produced when storing events

WEB:#31 Err. Cant open %s for append.

WEB:#32 Err. Event write failed.

WEB:#33 Err. Cant open %s for append

WEB:#34 Err. Cant open %s for read.

WEB:#35 Err. Event write failed.

Where %s is equal to ‘events.dat’ or ‘events~.dat’

5.9.3.2.Space Problems

There is a limited amount of space on the flash disk. Event logging is not permitted to completely fill the free space – a minimum amount of free space is maintained.

If this threshold (currently set at 100k Bytes) is reached then event file maintenance is performed. If after the maintenance, the available space is still below the threshold then event logging is automatically disabled and the LANServer prints a message to the error screen.

5.9.3.3.Limited number of event records

The LANServer will only store a maximum (currently 400) event records. If this threshold is reached then event file maintenance is performed.

5.9.3.4.Event File Maintenance

This procedure is executed by the LANServer when there is too little space to write new event records or when the maximum number of event records has been exceeded.

The procedure is as follows:

If an event record is older than 1 day (current setting) then the record is discarded.

If after they have been removed then if there are more than 350 records (current setting) then only the 350 most recent events are retained.

If there is still too little space or two many records, the events.dat file is removed and all events are lost. If this happens then this message “WEB:#38 Err No space for Sentry Logging” Is printed in the error log.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-2269 Toll_Free: 888-509-1970 email: support@fieldserver.com

Image 24
Contents Sentry LANServer Applicability & EffectivityTable of Contents LED1 Features Product Description GeneralOperation Sentry Firmware Version ConnectionsModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start LANServer Terminology Quick StartBrowser Security Settings Setting Browser Security Settings for ActiveX controlsActiveX Controls and Security T12017-SentryLANServerUsersManual Customize the settings Setting the Browser Privacy Settings for Cookies Cookies and Browser SecuritySpecify the WebServer IP address and then click Allow T12017-SentryLANServerUsersManual Interpreting Zone Buttons T12017-SentryLANServerUsersManual Interpreting Sentry-Sensor Controls Interpreting Sentry -Combo Controls Interpreting Sentry Alarms Understanding the Alarm Table Colors Acknowledging AlarmsClick Retry to clear the dialog Interpreting Sentry Events Event Report TypesPage What happens if Event Logging is disabled? Understanding the EventsEvents Page and the Date / Time Potential Problems with Event Logging File Problems Space ProblemsEvent File Maintenance Limited number of event recordsManaging Sentry Events Uploading Potential Problems with an Upload How Event Time Stamps are reported Manual uploadInterpreting the Sentry Face Plate LED Current sensor number Gas Concentration for current sensor Sensor ActiveX Not Installed One User at a TimeLANServer Driver Ver .05f Required Description How the Control OperatesBackup File Contents Problems with Calibration Backup ControlInterpreting Analog, Text and LED controls Analog Controls Text ControlsLED Controls Using the LANServer to allow customers to upload files Appendix 1.3. Page login.htm not found Appendix 1.2. Objects report ‘Not Found’Appendix 1.6. Buttons Display in White Appendix 1.7. Cookie LengthAppendix 1.9. LANServer Configuration LED 40159,8 40977,8 40985,8Appendix 2. LANServer Error Messages FYIWEB#13 Err Not enough Space for alarm WEB#15 FYI ASO Max Limited to %d Web#68 FYI. Http Appendix 3. WinSock Error Messages Wsaeconnreset WsaenetresetWsaeafnosupport WsaealreadyWsaefault WsaedestaddrreqWsaehostdown WsaehostunreachWsaeisconn WsaemfileWsaemsgsize WsaenetdownWsaenotconn WsaenotsockWsaeopnotsupp WsaepfnosupportWsaeshutdown WsaesocktnosupportSockraw WsaetimedoutWsainvalidparameter WsainvalidproctableWsainvalidprovider WsaioincompleteWsanotinitialised WsanodataWsanorecovery HostsWsaproviderfailedinit WsasyscallfailureWINSOCK.DLL WsavernotsupportedWsaediscon WsaoperationabortedAppendix 4. FieldServer ActiveX Controls Appendix 4.1. Ana1 Appendix 4.2. LED1Appendix 4.3. Char1 Appendix 4.4. Limitations and Supported Environments Appendix 5. General Appendix 5.1 .1 Browser Caching This page Intentionally Left Blank