Difference between revisions of "Seon Core list of possible log entries"

Revision as of 13:31, 16 May 2007 (view source) Admin (talk | contribs) (→‎<code>reveived signed EERP from partner invalid in field EERPDSN: raw content is '...'</code>) ← Older edit		Revision as of 13:32, 16 May 2007 (view source) Admin (talk | contribs) (→‎<code>reveived signed EERP from partner invalid in field EERPDATE: raw content is '...'</code>) Newer edit →
Line 86:		Line 86:
	=== <code>reveived signed EERP from partner invalid in field EERPDATE: raw content is '...'</code> ===		=== <code>reveived signed EERP from partner invalid in field EERPDATE: raw content is '...'</code> ===
		+	During verification of a signed OFTP2 EERP, the signed value of the EERP contains a different value than the unsigned one. The raw content of the signed value is contained in this message. The field is EERPDATE, which is the virtual file datestamp (format: YYYYMMDDCCCC, i.e. 200705160001).
		+	The EERP is not archived, as it is not valid.
		+
	=== <code>reveived signed EERP from partner invalid in field EERPTIME: raw content is '...'</code> ===		=== <code>reveived signed EERP from partner invalid in field EERPTIME: raw content is '...'</code> ===
	=== <code>reveived signed EERP from partner invalid in field EERPDEST: raw content is '...'</code> ===		=== <code>reveived signed EERP from partner invalid in field EERPDEST: raw content is '...'</code> ===

---

Revision as of 13:32, 16 May 2007

This list of possible log entries (both receive, send and system logs) gives you an overview of all logs that could appear and what they mean in detail.

The messages are listed in no special order. It's possible that this list doesn't contain all messages that can arise!

send log

unknown type of connectivity for entry ...

All sending processes try to obtain the medium of that partner from the configured partner table (see Seon Core configuration#Partner table parameters). If no numeric value can be resolved to a configured medium, this message is logged. The misleading value is contained in this message.

sending of file '...' aka '..' aborted: partner has asked for an invalid restart position of ... kB while we offered ... kB

OFTP offers a restart mechanism for file transfers. In this errornous case, the remote side wants to use a bigger restart position than Seon (as sender) proposed to use. According to chapter 5.3.4 - "SFPA - Start File Positive Answer" of RFC 2204, the restart position given by the remote (receiving) side must be equal or lower than the sender proposed.

sending of file '...' aka '...' aborted: partner has asked for an invalid restart position

OFTP offers a restart mechanism for file transfers. In this errornous case, the remote side wants to use a bigger restart position than Seon (as sender) proposed to use. According to chapter 5.3.4 - "SFPA - Start File Positive Answer" of RFC 2204, the restart position given by the remote (receiving) side must be equal or lower than the sender proposed. In difference to the above message, this one appears AFTER the calculation of amount of credits to be sent in case of using the send acceleration.

restarting file transfer at position ... kB

The file transfer begins at the documented position (not at the beginning of the file).

sending of file '...' aka '...' aborted by user at position ... kB of ... kB

During transfer of the file, a user interrupted the transfer by sending the process a signal so the transfer and connection will be aborted.

sending of file '...' aka '...' aborted at position ... kB of ... kB: send queue entry removed

As a "last option", Seon supports the deletion of send queue entries and recognizing in the active transfer process that "his" entry is removed during transfer. In this case, during updating the progress information, the send process checks the existance of the send queue entry. If not existant, the process aborts the file transfer and adds this message to the send logs.

sending of file '...' aka '...' failed at position ... kB of ... kB

A network or ISDN connection problem causes the physical or logical connection to be closed, causing this error message. The problem itself is logged in another message.

all send queue entries for this partner have been blocked because of connection problems

If connection problems to a partner exist (like physical line problem, wrong credentials, wrong SFID etc.), after the maximum send tries of a send queue entry ALL entries for that partner are blocked in order to save connection costs.

a send queue entry for this partner has been blocked because of sending problems

If a partners refuses the receipt of this specific file and the maximum send try count is reached, this file entry is blocked. All other file entries in the send queue remain in its original state.

Error creating connection BIO

For SSL/TLS secured TCP/IP connections, an internal handler is needed which is called "BIO". This "BIO" is not available here.

Error connecting to remote machine

When connecting to a remote partner via SSL/TLS over TCP/IP and the remote system doesn't answer, this message is logged.

Error connecting SSL object

An error occured during the SSL/TLS handshake with the remote partner.

openSSL error: peer certificate: ...

An error occured during the check of validity of the remote (partner's) SSL/TLS certificate. The error message (from openSSL) is printed out in this log entry.

OFTP ERROR: ESID received during filetransfer (normal termination)

During receiving a file, the remote side wants to close the OFTP connection unexpectedly. In this case, no error code was given by the remote side.

OFTP ERROR: ESID received during filetransfer (reason: ...)

During receiving a file, the remote side wants to close the OFTP connection unexpectedly. In this casean error code was given by the remote side and the textual interpretation is listed in the message.

error in verifying data ...

The verification process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in signing data ...

The signing process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in decrypting data

The decrypting process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in encrypting data

The encrypting process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in compressing data

The compression process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in decompressing data

The decompression process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

error in hashing data

The hashing process of OFTP2 data failed. The used command, returncode and output is appended in the log message.

Hashing is normally done internally only (called in Seon itself when a file is successfully received).

error in compressing signed data

The compression process of OFTP2 signed data failed. The used command, returncode and output is appended in the log message.

error in extracting certificate from automatic certificate delivery

During automatic certificate exchange of OFTP2, the remote certificate is extracted from a CMS package (a special file). During the extraction, an error occured.

reveived signed EERP from partner invalid: verification command returned with code ...

During verification of a signed OFTP2 EERP (end-to-end-response, something like a file confirmation), the OFTP2 internal signature verification process returned with a returncode which was not zero (the actual value is added to this message).

reveived signed EERP from partner invalid in field EERPDSN: raw content is '...'

During verification of a signed OFTP2 EERP, the signed value of the EERP contains a different value than the unsigned one. The raw content of the signed value is contained in this message. The field is EERPDSN, which is the virtual filename. The EERP is not archived, as it is not valid.

reveived signed EERP from partner invalid in field EERPDATE: raw content is '...'

During verification of a signed OFTP2 EERP, the signed value of the EERP contains a different value than the unsigned one. The raw content of the signed value is contained in this message. The field is EERPDATE, which is the virtual file datestamp (format: YYYYMMDDCCCC, i.e. 200705160001). The EERP is not archived, as it is not valid.

reveived signed EERP from partner invalid in field EERPTIME: raw content is '...'

reveived signed EERP from partner invalid in field EERPDEST: raw content is '...'

reveived signed EERP from partner invalid in field EERPORIG: raw content is '...'

reveived signed EERP from partner invalid in field EERPHSH: raw content is '...'

reveived signed EERP from partner invalid: could not execute verification command

reveived signed NERP from partner invalid: verification command returned with code ...

reveived signed NERP from partner invalid in field NERPDSN: raw content is '...'

reveived signed NERP from partner invalid in field NERPDATE: raw content is '...'

reveived signed NERP from partner invalid in field NERPTIME: raw content is '...'

reveived signed NERP from partner invalid in field NERPDEST: raw content is '...'

reveived signed NERP from partner invalid in field NERPORIG: raw content is '...'

reveived signed NERP from partner invalid in field NERPCREA: raw content is '...'

reveived signed NERP from partner invalid in field NERPHSH: raw content is '...'

reveived signed NERP from partner invalid: could not execute verification command

RemoteCAPI error: invalid authentification. Check environment variables CAPI_USER and CAPI_PASSWD

ISDN CAPI error 0x.... while connecting to partner: ....

ISDN CAPI error: no free line available on brick (... controller(s) checked)

connection aborted by user

OFTP ERROR: handled credit count is zero

OFTP ERROR: handled buffer size is zero

OFTP NERP ...: remote problem with virtual file '...': ...

OFTP SFNA ...: sending file '...' (aka '...') failed: ...

ODETTE EFNA ...: ...

ODETTE DISCONNECT ERROR ...: ...

partner acknowledges receipt of virtual file '...'

OFTP2 session aborted: secure authentification required, no SECD message received by partner

OFTP2 session aborted: secure authentification required (by ourself), no SECD message received by partner

session aborted: invalid challange ('...' != '...')

session aborted: invalid challange (returncode of verifying command was not 0)

session aborted: secure authentification required (by ourself), no AURP message received by partner

rejected receive of file: invalid virtual filename '...'

ISDN ERROR: disconnect

successful poll to partner

unsuccessful poll to partner

beginning transfer of file '...' (aka '...')

sending file '...' (aka '...') failed: unable to open file

correct transfer of file '...' (aka '...') @ ... kB/s

incorrect transfer of file '...' (aka '...'): ... (@ ... kB/s)

error connecting to partner: '...' (address: '...')

OFTP error: no SSRM received

wrong remote password (transmitted: '...', Seon database value: '...')

wrong remote SSID (transmitted: '...', Seon database value: '...')

OFTP protocol error: command contained invalid data

OFTP2 ERROR: secure authentification needed, but partner doesn't support this feature. Either set flag 'OFTPv2 allow unsecure authentification' in basic configuration or inform partner.

OFTP2 is not supported in this version of Seon. Please upgrade Seon and get a new license.

receive log

restarting file transfer at position ... kB

receiving of file '...' aka '...' aborted by user at position ... kB of (approx.) ... kB

receiving of file '...' aka '...' aborted at position ... kB of (approx.) ... kB: receive queue entry removed

OFTP ERROR: ESID received during filetransfer (normal termination)

OFTP ERROR: ESID received during filetransfer (reason: ...)

OFTP ERROR: no valid OFTP header found during file transfer (but character '...')

unsuccessful connect try from ISDN number '...'

unsuccessful connect try from IP '...'

error in verifying data ...

error in signing data ...

error in decrypting data

error in encrypting data

error in compressing data

error in decompressing data

error in hashing data

error in compressing signed data

error in signing data

error in verifying data

error in extracting certificate from automatic certificate delivery

malformed remote certificate request: message was not signed, it was compressed or signed EERP request was given

fulfilled remote remote certificate request by adding my local public certificate to the send queue

something went wrong during remote certificate request

successfully read in automatic certificate delivery

successfully handled incoming file '...' (file was ...)

Error loading CA file and/or directory

Error setting default CA file and/or directory

Error loading certificate from file '...': not in PEM format, file does not exist or invalid password supplied.

Error loading certificate from file '...': not in PEM format or invalid password supplied.

Error setting cipher list (no valid ciphers)

beginning transfer of file '...' (aka '...')

NETWORK ERROR: disconnecting during transfer of file '...' at ... kB of (approx.) ... kB

correct transfer of file '...' (description: '...') @ ... kB/s

correct transfer of file '...' @ ... kB/s

rejected receive of file: invalid virtual filename '...'

no space for file '...' (... kB) left on filesystem '...'

file '...' already exists

wrong local SFID (database value: '...', transmitted: '...')

wrong originator SFID (transmitted: '...', database value: '...')

session aborted: secure authentification required (by ourself), no AURP message received by partner

rejected receive of file: invalid virtual filename '...'

wrong remote SFID (transmitted: '...', no entry found for combination with SSID, password and SFID)

partner acknowledges receipt of virtual file '...'

OFTP protocol error: command contained invalid data

wrong remote password (is: '...', should be: '...')

partner unknown for SSID '...' and password '...'

OFTP ERROR: handled credit count is zero

OFTP ERROR: handled buffer size is zero

OFTP error: no valid SSID received

system log

If no partner could be found for a specific receive or send log message, or if the message is that generic, the entry will be put into the system log.

Remote CAPI timed out (possible reboot of device). Aborting session.

As a feature request, a reboot of hangup of a RemoteCAPI device is now logged in the systems log for each active transfer. So, a possible reboot of a Brick during the transfer of multiple files results into multiple (the amount of open transfers) system log entries.

license invalid

Hopefully speaks for itself: the license or its content is invalid. Please obtain a valid license.