Operator.LOG

[Vallentin, Manfred]

Hi,
i become on my System the following Message when a TCPIP User connected to the System:
"Message from user INTERnet on KALVRA
INTERnet ACP Error Status = %SYSTEM-F-LINKABORT"
My Question:
What it this for an Error?
How can remove /disable this Message?

Thanks for your help

[Mobeen_1]

Vellentin,
Look at this, its from OpenVMS ask the wizard

The Question is:



What would cause an OpenVMS error 'SYSTEM-F-LINKABORT network parnet aborted
logical link' when DECnetting to another node to run a process there? What
fixes are recommended?



--------------------------------------------------------------------------------

The Answer is :



Check the contents of the log file typically created on the remote
node, as a start. If this was a SET HOST (CTERM) session, check
for sufficient process quotas and system resources (pool, etc) on
the originating and destination node, and check for any error messages
reported prior to the link disconnection -- insufficient process quotas
and insufficient system resources can cause problems with network
links, and can also prevent the display of error messages. Also
check the DECnet error counts for any specific indications.

--

LINKABORT, network partner aborted logical link

Facility: SYSTEM, System Services

Explanation: The remote process disconnected the logical link either
because the process exited prematurely or because it is the
normal way for the process to disconnect the link.

User Action: Check to see if the node is reachable, then retry.



rgds
Mobeen

[Mobeen_1]

Vallentin,
The following information may also help you

Connection Dies With SYSTEM-F-LINKABORT

Question:
My THRUWAY connection is dying. The NETSERVER.LOG has a SYSTEM-F-LINKABORT error in it.

Answer:
Possibly the REQUEST PACKETS are being exhausted on one of the nodes. Try the following:

1) Create the THRUway connection.

2) From another session issue a MONITOR POOL command. This will invoke the VMS MONITOR utility to monitor the SRPs, IRPs and LRPs.

3) Run the application using the THRUway disk and watch and see if any of the packets are getting exhausted (decreasing to zero).

If this is the case then you will need to adjust some SYSGEN parameters. The SYSGEN parameters to increase would be SRPCOUNT, IRPCOUNT or LRPCOUNT respectively. Consult the SYSGEN manual for more info on this. Unfortunately these SYSGEN parameters are not dynamic, so if you change these you will need to reboot the node.


Let me know if you have any specific questions

rgds
Mobeen

[Willem Grooters]

Manfred,

It can be quite normal - depending on what't on the other side. Normally it is that either side has disconnected (normally, 'the other side', but it may happen on the 'own side' as well.

It's quite worthwhile to find out what's on the other side that aborts the connection. As Mobeen stated: it can be a normal (but undesirable) behaviour. Since it's INETACP that signalles it, it's some requestor of a service on your machine. If this program is locally built, I would urge the programmer to change the program to close the connection the PROPER way, not brute force way. It will eliminate these messages from you opreator log and leave the REAL problems. If you purchased the program, and have a support contract, I would urge the supplier to do likewise. Otherwise, you _could_ disable NETWORK logging but then you would loose the real problems as well.

[Martin P.J. Zinser]

Hello Manfred,

a number of the answers here did refer to DECnet problems. Just for clarification, you do experience this problem with IP, don't you? Is there any more context to the message? This can be pretty much anything from network problems to misdesigned applications to uneducated users hitting the x in the upper right hand corner of a PC window to close an apllication.

Greetings, Martin

[Willem Grooters]

Manfred,

Perhaps another source of information - if the _receiving_ process died off: Check accounting...