Backup results in an error code 142. This error is not in the manual.

Keywords

Error 142 BackupEDGE Unattended edge

Release

BackupEDGE releases prior to 01.01.02

Problem

Backup results in an error code 142. This error is not in the manual.

Cause

A combination of locking and timing issues with certain database applications can result in an error code 142 on a backup. This anomaly is most likely to occur when older Xenix binaries are used on a Unix system. In reality, signal 14 is sent to the process for the following reason. Versions of BackupEDGE (prior to 01.01.02)ran into difficulties with applications that used mandatory, versus advisory, types of locks. With mandatory locking, any program attempting to open a file, including tar and cpio, would hang.

BackupEDGE intelligently sets a wakeup call, which lets the process know whether or not it is hanging. When all is clear and there is no chance of hanging the process reading a file, the wakeup call is dismantled.

Dismantling the wakeup call occurs in several stages. Rare instances occur where a wakeup call 'squeeks' through when some mechanisms to handle it are dismantled, resulting in an error code 142.

Solution

BackupEDGE has been updated with logic that ensures that no wakeup call passes through until BackupEDGE is prepared to handle the call.

Back to the main index

Back to the MICROLITE Home Page

Copyright Notice