Kbase P65448: 793 and 794 messages after network connection breaks
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/03/2004 |
|
Status: Verified
FACT(s) (Environment):
SCO OpenServer 5.0.7
FACT(s) (Environment):
Progress 8.3E
SYMPTOM(s):
793 and 794 messages after network connection breaks
Select returned -1 , errno=19. (793)
Forcing shutdown, reason 15. (744)
CAUSE:
Given the context - a network connection being broken - these messages are two of a number that might appear. The behaviour they describe isn't a problem as such: the broker picks up on the select call failing and the database is - correctly - shutdown. It doesn't crash and there should be a 2248 appearing as well after the 793 and 744 -
Begin normal shutdown (2248)
The database is brought down to ensure the data integrity.
The reason 15 in the error 744 is a Progress-internal message code and indicates that a select statement failed. The description for the 793 is -
"The PROGRESS server suffered a serious network error that caused it to be unable to continue listening on the network. Try shutting down your database and restarting. Another situation could be that PROGRESS is trying to sleep for a short period and had a problem executing select() to perform the sleep. See errno.h for a description of the associated errno."
The errno 19 is from /usr/include/sys/errno.h -
#define ENODEV 19 No such device
This suggests that Progress was looking for something on the network but because of the network problem, couldn't find it. It is a symptom of whatever the network issue is at that site, and it is correct behaviour.
FIX:
From the Progress side, this is expected behaviour. However, the messages would suggest that there are network issues that require resolving.
Ensure also that the platform and Progress version are a supported configuration.