As some of you probably have noticed I have been trying to deal with some server issues that have built up over the years as a result of it being left unattended, (due to personal tragedy), now that I have the time.
I have most of them wrapped up and only one is outstanding; sometimes my server will trap; Trap 000e; Sockets.
It doesn't happen often, but contrary to that, it did so twice yesterday which probably means that it is increasing in frequency. But whether that is true or not, I have to deal with it.
The problem with traps generated by TCP/IP socket I thought had been permanently deal with by IBM with their last TCP/IP update. As a result of that one seldom reads anything about it anymore.
Has anyone here experienced such issues and if so, have any pointers on where to look?
My guess would be crappy NIC drivers, but I need to have more to go on before spending money on something that may not solve the problem.
Thank-you.
Having managed for years the Mensys webservers (I have not seen these boxes for close to 5 years) you can have TRAPS in the different protocol drivers for different reasons. Some of our servers where up for weeks, but...
1) Changing the settings on the network static with any driver switches is not recommended.
2) What type of software are you running ? Like what web browser are you running and what version of the software ?
Do you load PHP ? Do you load Wordpress website for example.
3) In inetcfg.ini make certain that
keepalive 300 7800 0 7800 KeepAlive (sec) is set to 300 and not 7800.
4) The exhaustation of TCP/IP stack resources can be contributed to many issue's which you slowy need to sort out.
A) Are you having DDOS attacks on your server ?
B) Are web crawlers (Search engines) drowning the server in requests.
C) Keep an eye on netstats -s it shows the open sockets. They should close after some time so IP stack resources are given back to the system.
Also some software I have seen on OS/2 has the tendency to not release TCP/IP sockets. Again at a faster rate exhausting the system.
This certainly has nothing todo with bad NIC drivers. Its purely a matter of tuning your server and confuring the server software correctly.
Roderick Klein