Socket error code table

Source: Internet
Author: User
Tags socket error connection reset types of functions

Socket ErrorCodeTable.

Socket error 0-directly send error

Socket error 10004-interrupted function call

Socket error 10013-Permission denied

Socket error 10014-bad address

Socket error 10022-invalid argument

Socket error 10024-Too enabled open files

Socket error 10035-resource temporarily unavailable

Socket error 10036-operation now in progress

Socket error 10037-operation already in progress

Socket error 10038-socket operation on Non-socket

Socket error 10039-destination address required

Socket error 10040-message too long

Socket error 10041-Protocol wrong type for socket

Socket error 10042-bad protocol option

Socket error 10043-protocol not supported

Socket error 10044-socket type not supported

Socket error 10045-operation not supported

Socket error 10046-protocol family not supported

Socket error 10047-address family not supported by protocol family

Socket error 10048-address already in use

Socket error 10049-cannot assign requested address

Socket error 10050-network is down

Socket error 10051-network is unreachable

Socket error 10052-network dropped connection on Reset

Socket error 10053-software caused connection abort

Socket error 10054-Connection reset by peer

Socket error 10055-no buffer space available

Socket error 10056-socket is already connected

Socket error 10057-socket is not connected

Socket error 10058-cannot send after socket Shutdown

Socket error 10060-connection timed out

Socket error 10061-connection refused

Socket error 10064-host is down

Socket error 10065-No route to host

Socket error 10067-Too processing processes

Socket error 10091-network subsystem is unavailable

Socket error 10092-Winsock. dll version out of range

Socket error 10093-successful wsastartup not yet completed MED

Socket error 10094-graceful shutdown in progress

Socket error 11001-host not found

Socket error 11002-non-authoritative host not found

Socket error 11003-this is a non-recoverable error

Socket error 11004-valid name, no data record of requested type

Wsaeaddrinuse (10048) address already in use

Wsaeconnaborted (10053) software caused connection abort

Wsaeconnrefused (10061) connection refused

Wsaeconnreset (10054) Connection reset by peer

Wsaedestaddrreq (10039) Destination Address required

Wsaehostunreach (10065) No route to host

Wsaemfile (10024) Too program open files

Wsaenetdown (10050) network is down

Wsaenetreset (10052) network dropped connection

Wsaenobufs (10055) No buffer space available

Wsaenetunreach (10051) network is unreachable

Wsaetimedout (10060) connection timed out

Wsahost_not_found (11001) Host not found

Wsasysnotready (10091) network sub-system is unavailable

Wsanotinitialised (10093) wsastartup () not completed MED

Wsano_data (11004) valid name, no data of that type

Wsano_rediscovery (11003) non-recoverable query Error

Wsatry_again (11002) Non-authoritative host found

Wsavernotsupported (10092) Wrong Winsock dll version

++ ++

Common socket error return code ()

Wsaeintr (10004) is called by the middleware's System

When the Winsock function in wsacancelblockingcall () is blocked, the blocking function will receive the Invalid Message "wsaeintr. It should be noted that when your program uses wsacancelblockingcall to block the implicit function, you must handle wsaeintr program messages for this blocking function. Otherwise, your program may have some unexpired program records.

In principle, all the scripts that can be implemented in the blocking form may generate this program.

Wsaebadf (10009) zookeeper Case Generation

In the Bock's socket interface, the case description and socket description are the same. Opening a socket can be considered as opening a case. The meaning of wsaebadf in the Bock socket interface refers to the socket description of the zookeeper, the socket description of this operator may be an unopened socket or a socket that is related to the operator.

In WinSock, there is a connected zookeeper generation called javaswsaenotsock, which is used to specify the socket description of zookeeper. Please refer to the wsaenotsock section.

Wsaeacces (10013) does not have this permission

For the bock socket interface, the cause of this attack is usually to open a case or socket that does not have the permission to open. For example, on UNIX, a general user cannot open a socket named sock_raw. This permission is generally granted to a Super User. If a general user attempts to open a socket named sock_raw, this warning message will be generated.

For the Winsock API interface, there are two types of functions for sending the response: Send () and sendto (). When sending data using send () or sendto (), the target address is set to a broadcast address, but no setsockopt () call is made () when so_broadcast is set, wsaeacces authentication failure occurs.

The host address of wsaefault (10014) zookeeper

The system displays the host address that uses the response. When calling the Winsock function, there are often metric data written in as a metric. This metric may point to a structure, such as the sockaddr_in structure, or point to a data area. When the program accidentally fails to import a metric that is not specified by the website administrator, the website wsaefault is generated. In addition, when the memory area to which the metric points is too small, this problem will also occur.

Wsaeinval (10022) numeric Regression

If an incorrect numeric value is returned to the Winsock function, wsaeinval is returned. If the number of records is the index of a component, an incorrect value is entered in the content of the component. For example, the number of how () records in the shutdown () function can only be 0, 1, or 2. If it is set to another number, this slow response occurs.

In the design of the program, the call between the function and the function usually has a certain sort order, such as failing to follow this sort order, this problem also exists. The following is an explicit description of each related function.

Function

Indicates the time when a producer occurs.

Accept ()

No successful call to listen () was made before the call to accept ()

BIND ()

You have successfully called the BIND () function, and the stocket name is specified.

Getstockname ()

No call to bind () function specified socket name success

Listen ()

The specified socket name already exists or the socket does not call BIND ().

Recv () and recvfrom ()

For datemedisocket, the socket does not call the BIND () function to specify the IP address, port, and encoding. For stream socket, the connector has not been created.

Send () and sendto ()

For datemedisocket, the socket does not call the BIND () function to specify the IP address, port, and encoding. For stream socket, the connector has not been created.

In principle, the values set by the number of all functions have a certain limit, or some specific values. These functions may generate this limit.

Too many opening cases in wsaemfile (10024)

The solution to the bock hole socket interface is to open a large number of cases, which exceeds the limit on the number of open cases. The opening of the case and the socket will be described in file descriptor in the bock socket. Winsock has a different case for socket. The meaning of wsaemfile in Winsock is to open too many sockets.

This program usually occurs when there are too many web programs in the same machine, so that too many sockets are opened. Another option that can be avoided is that the application does not have a socket that is normally not used, resulting in socket resource consumption.

Wsaewouldblock (10035) function in blocking

When the function of the current function is to return a result, the function is not completed. For example, the pseudo-set send () sends a piece of data to the terminal host in a non-blocking manner. When the pseudo-set function returns, the parameter wsaewouldblock is obtained, this means that the information cannot be sent completely in this send () call.

For the connect () function, this parameter indicates that the client host has not been successfully connected. The connection request is in progress. If setsockopt () function is used in your program to set the time limit with so_linger, this variable may appear when you call closesocket.

For non-synchronous web interfaces (wsaasyncgetxxxxbyyyyy (), wsaewouldblock metadata is obtained, indicating that the network resources to be queried cannot be obtained currently. This is usually a temporary response, and the application may call the same function later.

Wsaeinss SS (10036) has a blocking effect. The function is being processed.

For each process or thread, Winsock only allows "one" blocking operation. If the blocked function is calling the Winsock function, the function returns the invalid function of wsaeinprogress.

This operation also generates a function that requires a long period of time, such as connect (). There is a kind of sentiment like this: when the line is "non-blocking" Connect () two times, caused by non-blocking connect (), the first call was sent back to wsaewouldblock when there were too many requests. At this time, the operation is not completed yet, and the second connect () call will get the progress of wsaeinprogress.

Our suggestion is to add wsaisblocking () to determine whether there is a blocking function in the response to a possible response call. If so, we may need to cancel the blocking form in progress or cancel what we want to do.

Wsaealready (10037) function completed

This parameter means that there is a big difference between the Berk socket interface and the Winsock function solution. In WinSock, wsaealready indicates: "The non-synchronization event you want to cancel has been canceled !", That is, when you call wsacancelasyncrequest () Cancel to cancel a non-synchronous event, the event has been canceled.

The socket of wsaenotsock (10038) is invalid.

Generally, the Winsock function uses a socket to describe the sub-account data, then, wsaenotsock was obtained. In principle, as long as the socket is used to describe the sub-accounts, all the functions may generate wsaenosock statistics.

Wsaedestaddrreq (10039) requires the peer address

When you want to send data to the receiver, you must specify the peer address (and port, etc.) to send data to the receiver. Verify to check whether your application is correctly filled in with the sockaddr structure when you call connect () or sendto.

Wsaemsgsize (10040) is too long, so the region cannot accommodate it.

The reason for this issue is that the response information is too large and the region cannot accommodate it, the region here may be the region specified by the user or used within the system. There are four types of writing that will generate this example:

Function

Indicates the time when a producer occurs.

Recv (), recvform ()

When receiving data using datav socket, if the region length specified by Recv () and recvform () is smaller than that specified by the received data, after this time, the long datatime will be reported and the function wsaemsgsize will be used.

Send (), sendto ()

When using datax socket to send data, if the data sent is larger than the maximum length of datax that Winsock can handle, send () and sendto () sending back the message "wsaemsgsiz"

Watermark stereotypes of wsaeprototype (10041) zookeeper

The reason for the production is that when a socket () call is performed, a fixed sequence parameter that is not supported by Winsock is specified. In this example, you cannot use steam socket (sock_stream) SET protocol (ippro_udp) based on UDP protocol ). Stream socket does not support UDP protocol setting. If you really want to renew your subscription, the program deliberately calls socket (): hsock = socket (af_inet, sock_stream, ipproto_udp); you will find that, the socket () function call will receive the wsaeprotonosupport response. This operation is not correct, so we should obtain the wsaeprototype parameter. Wsaeprototype indicates that the parameter setting of the parameter is specified, and the specified parameter must be supported by the address family (the parameter family), but it is not applicable to the socket type. In the preceding example, UDP protocol must belong to the af_inet address family, but it cannot be used on stream socket (sock_stream socket. Wsaeprotonosupport indicates that the specified parameter is not supported by the specified parameter family, which means that wsaeprototype indicates inbound.

In fact, the difference between wsaeprototype and wsaeprotonosupport is very small. When developing a web program, these two types of website programs both represent the same category of website, which is determined to specify the category.

In short, you can never publish the wsaeprototype parameter.

Selection of wsaenoprotoopt (10042) zookeeper)

This operator mainly applies to getsockopt () and setsockopt. These two functions can be used to set different options based on numbers. There are more or less restrictions on each option. For example, some options can only be used in stream socket, while some can only be used in datax socket. If these restrictions are reversed, the attack will occur. See the following table:

So_dontlinger

So_keepalive

So_linger

So_oobinline

Tcp_nodelay

Datainsocket (sock_dgram) does not support these options

So_debug

So_dontroute

So_rcvbuf

So_sndbuf

Tcp_nodelay

Some vendors do not support the selection of the Winsock TCP/IP core.

So_acceptconn

So_error

So_type

These selections are only applicable to the getsockopt () function and cannot be used as the setsockopt () function.

Quota not supported by wsaeprotonosupport (10043)

Winsock depends on the core and does not support the specified sequence. For example, when you use the socket () function, the second vertex is specified as sock_stream, and the third vertex is specified as ipproto_icmp () the call will receive the parameter wsaeprotonosupport. Winsock 1. Version 1 does not support ICMP resolution. Therefore, when you call socket () to specify ICMP resolution, a response is generated. In fact, this is not the case for the production of wsaeprotonpsupport protocol. We can see wsaeprototype.

Socket types not supported by wsaesocktnosupport (10044)

Currently, the Winsock version does not support socket types specified by the function. For example, the fully developed Winsock Specification Core does not support the socket type sock_raw. When you call the socket () function, if the address family selects af_inet (pf_inet) and the socket type does not select sock_raw, this response will be generated.

The WinSock programming core developed by some vendors not only supports the specifications of WinSock 1.1, but also provides many different functions. We suggest that you consider compatibility with other environments if you need to use these functions during the development process.

The socket type is not supported by the function of wsaeopnotsupp (10045 ).

The function of the function does not support the current socket type. For example, the accept () and listen () functions can only be applied to the forward socket (stream socket), that is, the stream socket. For the Recv (), recvform (), send (), and sendto () functions, MSG_OOB can only be used for sockets connected to the forward direction.

Default families not supported by wsaepfnosupport (10046)

Currently, the Winsock tuning core does not support the specified tuning family. This example is very similar to wsaeafnosupport. Currently, this example is replaced by wsaeafnosupport. Users can refer to the description section of wsaeafnosupport.

Address families not supported by wsaeafnosupport (10047)

The specified address family is not supported by the specified sequence. For the socket () function, the cause of writing is the number of function compute records. For the number of functions in the sockaddr ending structure, the cause of the initial occurrence is that the network does not support the sockaddr structure (sin_family members) the specified address family.

The wsaeaddrinuse (10048) address has been specified.

The specified "Address" is in use. The address here refers to the socket name, which consists of three parts: fixed, port, and IP address. The reason for this issue is that when the application program uses the BIND () function to specify the port, the port has been used by other applications. This scenario occurs when two server programs with the same quality (specifying the same socket name) are written on the same host, the second program will get this warning message because the first program attempts to use a port first.

It is also common to say that when writing a client program, BIND () is used to specify the socket port, which is usually generated in this example. Instead of using bind () to specify the socket port, you cannot determine whether the specified port is in use when the program is running. Usually, BIND () is rarely called in the client program. Generally, the client program allows the system to select an appropriate port for you.

In addition, application programs can use the so_reuseaddr option of setsockopt (), allowing ports to be reused, but we do not want to do this. This may cause the core of TCP/IP to be stuck in the application.

Wsaeaddrnotavail (10049) cannot specify an address

Zookeeper is usually generated by specifying the address that the machine should not have. The address here consists of three parts: Network Setting, port, and IP address.

When you call BIND () in the bock sockets interface, if the specified IP address is not the address that the local machine should have, this problem occurs. When you call the connect () or sendto () function, if the sin_port in the sockaddr_in structure is set to "0 ", this will also lead to this issue (eaddrnotavail transaction on unxi ).

For the Winsock function, the time when the machine was generated is similar to the bock socket function. Both BIND () and connect () will cause such a problem.

For the Winsock function, the time when the machine was generated is similar to the bock socket function. Both BIND () and connect () will cause such a problem. The rules in Winsock 1.1 do not mention that the BIND () function will send messages to wsaeaddrnotavail zookeeper, but the result of our response, BIND () it will also cause such a problem.

Wsaenetdown (10050) outbound traffic

The following figure shows a problem with the development of the web system. This is a serious problem. This will cause all Winsock correspondence calls to fail. If your Winsock function generates a token, you should check your web card, Web card drivers, and your Winsock program to determine the core.

Wsaenetunreach (10051) cannot access the specified network.

In the bock sockets interface, this parameter indicates that the method cannot be used to obtain the signature from the peer network. In Winsock 1. In the 1 Clause, wsaenetunreach is connected to ethostunreach in the Bock socket interface.

Wsaenetreset (10052) has been reset

The peer's primary machine leaves and then restarts. The response is obtained when the caller calls the local host machine and the token is related. For the setsockopt () function, the cause of this release is that the worker sets so_keepalive to a timeout connection.

Zookeeper in wsaeconnaborted (10053)

After the slave node is established, when the TCP/IP address determines that the core does not resend the data, and all the data is resending, the TCP/IP listener will be connected to the listener. At this time, the application will receive the packet "wsaconnaborted.

Wsaeconnreset (10054) has been reset by the peer

The reason has been blocked by the opposite system. TCP/IP depends on the core. If a problem occurs when a stream socket response occurs, it indicates a reset). At this time, the equation will obtain the response information of the wsaeconnreset.

The wsaenobufs (10055) region is too small

The Winsock core cannot be configured with sufficient memory partitions, and cannot be used to program the program. The development of this website is related to the entire Windows system. If the entire Windows system has few available resources, there will be fewer programs that can be used at the same time. It may also be because the "bad" application program has been released, and there is no normal usage or administrative data source (such as a memory ). Or some applications may not be properly related to the system resource.

Wsaeisconn (10056) socket has been connected

Web functions usually have a certain order of calls. Some function calls can no longer be called after successful calls. Otherwise, a response is generated. When the listener is established, the client program calls () successfully, while the server program calls accept () successfully. At this time, if the client calls the connect () function again, the wsaeisconn response is returned, indicating that the socket is already connected. If the client calls the listen () function, the response is displayed, indicating that the function should not be called at this time. For the server program, if the socket is already connected to a remote connection, and the program calls the connect () function, it will also get the parameter "wsaeisconn.

The above scheme occurs on stream socket, because stream socket will establish a scheme. For datax socket, multiple successful connect () calls are allowed (for datdgram socket, the purpose of the call connect () function is not to establish a Failover ). The reason why dataphin socket sends this token is that, in the sendto () function, when sendto () is called to send dataphin, if the peer address is set to inaddr_any ("0.0.0.0 ") when port is set to 0 (in the addr_in structure), wsaeisconn is generated.

Wsaenotconn (10057) socket has not been switched over

Web functions usually have a certain order of calls. Some functions must call a successful function before calling. The reason for the development of wsaenotconn is very clear, that is, before the establishment of the connection, you may obtain information from the access peer or send information to the expected peer, wsaenetconn will be generated.

For example, for stream socket, if you call send () Publish messages to send data or call Recv () resume to obtain data before the connection is established, this response will be generated, telling you that the socket has not yet established a response. If you call the getpeername () function to obtain the socket of the access peer, this response is also displayed. For the setsockopt () function, if so_keepalive is set but the listener is connected to a running container, wsaenetconn is also displayed.

The beginner may not check whether or not he calls the connected () function after calling the connect () function, so that he does not know whether the connection has been established.

Wsaeshudown (10058) socket has been closed

This temporary response means that there is no way to send data, because the socket has been closed by the shutdown () function. When you use Shutdown () to shut down the socket, the TCP/IP setting of WinSock will be related to the sending or receiving function of the socket. Note that this parameter will only appear in stream socket.

Wsaw.manyrefs (10059) has too many references, and resources are consumed.

In UNIX operating systems, the solution refers to the system's core resource consumption. However, in the rules of WinSock 1.1, no function is used to generate this function.

Wsaetimedout (10060) Timeout over time (timeout)

When the program uses connect () to connect to a terminal host, the host has never responded. After a while, the TCP/IP determines that the core will return the Response Message of the Connect () function wsaetimedout. The cause of this attack may be the problem with the system of the terminal host to which the program is connected, or the host does not exist. There is also a possible cause: the local machine's network system has a problem, which means that the local host cannot communicate with the local host. Check the settings of your network system to see what is inappropriate, such as the settings of the gateway, in the host s table, the host name and network address are subject to snapshots.

Wsaeconnrefused (10061) Reject

The response request is rejected by the opposite machine, and cannot be connected with the other party. This problem does not occur in the network system. Instead, the server program of the server rejects the access requirements of the client program, or there is no such server program. When the TCP/IP core receives a response request, check whether the port listened to by a server program in the system is exactly the port to be accessed by this program. If the server program does not exist, the TCP/IP core returns a wsaeconnrefused to the equation.

There are several reasons for this issue. The user may attempt to connect to the zookeeper master or the zookeeper port, or the host and port may be the opposite, but the server program does not. Check whether the sockaddr_in structure in the program has been filled in? The IP addresses and ports in sockaddr_in are arranged in the hierarchical order of network bits.

Too many symbolic links in wsaeloop (10062)

In a UNIX operating system, this parameter indicates a symbolic link that has been used for many tests ).

Wsaenametoolong (10063) was too long

In the UNIX operating system, this parameter indicates that the path name (including the case name) to be opened is too long.

Wsaehostdown (10064) Peer host

In the solution of the Baike sockets interface, the cause of this attack is that the master machine is down or the system is faulty.

Wsaehostunreach (10065) cannot access the host of the peer

In the bock socket interface, this parameter indicates that the attacker cannot obtain the token from the peer host. In terms of WinSock, there is a similar kind of attention generation, which can be used to explain the concept of wsaenetunreach.

Wsaeproclim (10067) Too processing processes.

A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. wsastartup () may fail with this error if the limit has been reached.

The wsasysnotready (10091) master machine network has not been completed yet

The Network System of the local host machine has not been able to operate normally. If this problem occurs, check whether Winsock. dll (or wsock32.dll Of the 32-bit meta version) exists? Is the path of this shard correct?

Wsavernotsupported (10092) does not support Winsock. dll versions because the specified Winsock version is not supported by the current Winsock version when the wsastartup () function is called. If this problem occurs, the attacker needs to determine the Winsock version in the local Windows system and the version that can be supported by this version. Generally, a new version can support the Winsock of the new version at the same time. It is recommended that you use the new Winsock version.

Wsanotinitialised (10093) has not completed the wsastartup ()

The application did not call wsastartup () or call wsastartup. The application must successfully call wsastartup () to use Winsock. dll. Otherwise, this vulnerability may occur.

Wsaediscon (10101) graceful shutdown in progress.

Returned by wsarecv (), wsarecvfrom () to indicate the remote party has initiated a graceful shutdown sequence.

Wsatype_not_found (10109) class type not found

The specified class was not found.

Wsahost_not_found (11001) has passed the verification and the host cannot be found.

When you use the Web interface to find the information of the host, and the host does not exist, this website will be generated. The method of searching for the network host information is usually to first find the host name list of the local host machine. If the host name cannot be found, you can find it through the DNS, if it cannot be found, it is usually returned to the response type.

When such a problem occurs, check whether there is a problem with the host name resolution settings of the local host. What is more likely to happen to users is the DNS settings, and whether or not to set up the DNS server that hosts them. If the DNS server is correct, check whether the DNS server is running. You can ping this program to see if the DNS server is running. If the program is not pinged, you can resolve a fixed host, check whether the DNS server is running properly.

Wsatry_again (11002) cannot find the network resource, but it is not verified

This is a temporary token. It tells you that you cannot find the network resources you want. You can try again.

Wsano_recovery (11003) unrecoverable commandid

The reason for checking the Host Name Is that Domain Name System (DNS) caused by the generated sequence. These domain names include DNS formerr, refused, noibd, and other domain names. Please refer to documents related to the website domain name indexing system of rfc1035.

The reason for this vulnerability is that the information for storing web resources cannot be found. This information is usually stored on the host machine, such as services and protocol.

The wsano_data (11004) Name token is valid but cannot be found.

The query token format is correct, but no such information exists. This is usually a temporary token, which may be found on different Web Resources servers.

Wsaproviderfailedinit (OS dependent) unable to initialize a service provider.

Either a service provider's dll cocould not be loaded (loadlibrary () failed) or the provider's wspstartup/nspstartup function failed.

Wsasyscallfailure (OS dependent) system call failure ..

Returned when a system call that shocould never fail does. For example, if a call to waitformultipleobjects () fails or one of the Registry APIs fails trying to manipulate

Protocol/namespace catalogs.

Wsa_invalid_handle (OS dependent) Specified event object handle is invalid.

An application attempts to use an event object, but the specified handle is not valid.

Wsa_invalid_parameter (OS dependent) one or more parameters are invalid.

An application used a Winsock function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters.

Wsainvalidproctable (OS dependent) invalid procedure table from service provider.

A service provider returned a bogus proc table to ws2_32.dll. (usually caused by one or more of the function pointers being null .)

Wsainvalidprovider (OS dependent) invalid service provider version number.

A service provider returned a version number other than 2.2.

Wsa_io_incomplete (OS dependent) overlapped I/O event object not in signaled state.

The application has tried to determine the status of an overlapped operation which is not yet completed. applications that use wsagetoverlappedresult () (with the fwait flag set to false) in a polling mode to determine when an overlapped operation has completed will get this error code until the operation is complete.

Wsa_io_pending (OS dependent) Overlapped operations will complete later.

The application has initiated an overlapped operation which cannot be completed immediately. A completion indication will be given at a later time when the operation has been completed.

Wsa_not_enough_memory (OS dependent) Insufficient memory available.

An application used a Winsock function which directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources.7

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.