1# Socket Error Codes 2 3> **NOTE** 4> 5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md). 6 7## 2301001 Operation Not Allowed 8 9**Error Message** 10 11Operation not permitted. 12 13**Description** 14 15This error code is reported if an operation is not allowed. 16 17**Cause** 18 19The operation is illegal. 20 21**Procedure** 22 23Check the operation procedure. 24 25## 2301002 File Not Exist 26 27**Error Message** 28 29No such file or directory. 30 31**Description** 32 33This error code is reported if the requested file does not exist. 34 35**Cause** 36 37The requested file does not exist. 38 39**Procedure** 40 41Check the file name or file path. 42 43## 2301003 Process Not Exist 44 45**Error Message** 46 47No such process. 48 49**Description** 50 51This error code is reported if a process does not exist. 52 53**Cause** 54 55The process does not exist. 56 57**Procedure** 58 59Check the process information. 60 61## 2301004 System Call Interrupted 62 63**Error Message** 64 65Interrupted system call. 66 67**Description** 68 69This error code is reported if the system call is interrupted. 70 71**Cause** 72 73The system call is interrupted. 74 75**Procedure** 76 77Rectify system call errors. 78 79**Description of TCP/UDP error codes:** 80> Mapping format of other TCP/UDP Socket error codes: 2301000 + Linux kernel error code (errno). For details, see Linux kernel error codes. 81 82## 2300002 System Internal Error 83 84**Error Message** 85 86System internal error. 87 88**Description** 89 90This error code is reported if a system internal error occurs. 91 92**Cause** 93 941. The memory is abnormal. 95 962. A null pointer is present. 97 98**Procedure** 99 1001. Check whether the memory space is sufficient. If not, clear the memory and try again. 101 1022. Check whether the system is normal. If not, try again later or restart the device. 103 104## 2301206 Failed to Connect to the Proxy Server via SOCKS5 105 106**Error Message** 107 108Socks5 failed to connect to the proxy server. 109 110**Description** 111 112This error code is reported if a SOCKS5 client fails to connect to the proxy server. 113 114**Cause** 115 116The proxy server address is incorrect. 117 118**Procedure** 119 120Check whether the proxy server address is correct. 121 122## 2301207 Invalid User Name or Password for SOCKS5 Authentication 123 124**Error Message** 125 126Socks5 username or password is invalid. 127 128**Description** 129 130This error code is reported if the user name or password is invalid when the SOCKS5 client uses the password authentication mode. 131 132**Cause** 133 134The user name or password is incorrect. 135 136**Procedure** 137 138Check whether the user name and password are correct. 139 140## 2301208 Failed to Connect to the Remote Server via SOCKS5 141 142**Error Message** 143 144Socks5 failed to connect to the remote server. 145 146**Description** 147 148This error code is reported if a SOCKS5 proxy fails to connect to the remote server. 149 150**Cause** 151 152The network of the remote server is faulty. 153 154**Procedure** 155 156Check the network status of the remote server. 157 158## 2301209 Authentication Mode Negotiation Failed for SOCKS5 159 160**Error Message** 161 162Socks5 failed to negotiate the authentication method. 163 164**Description** 165 166This error code is reported if a SOCKS5 client fails to negotiate the authentication mode with the proxy server. 167 168**Cause** 169 170The proxy server does not support the authentication mode provided by the SOCKS5 client. 171 172**Procedure** 173 174Check whether the proxy server supports the authentication mode provided by the SOCKS5 client. 175 176## 2301210 Failed to Send Messages via SOCKS5 177 178**Error Message** 179 180Socks5 failed to send the message. 181 182**Description** 183 184This error code is reported if a SOCKS5 client fails to send messages due to a system call error. 185 186**Cause** 187 188This problem is usually caused by memory overflows and invalid parameters. Check the log for Linux kernel errors. 189 190**Procedure** 191 192Create a socket and initiate a connection again. 193 194## 2301211 Failed to Receive Messages via SOCKS5 195 196**Error Message** 197 198Socks5 failed to receive the message. 199 200**Description** 201 202This error code is reported if a SOCKS5 client fails to receive messages due to a system call error. 203 204**Cause** 205 206Errors such as memory overflow and invalid parameter have occurred. Check the log for Linux kernel errors. 207 208**Procedure** 209 210Create a socket and initiate a connection again. 211 212## 2301212 Failed to Serialize Messages for SOCKS5 213 214**Error Message** 215 216Socks5 serialization error. 217 218**Description** 219 220This error code is reported if message fails to be serialized for a SOCKS5 client. 221 222**Cause** 223 224The user name or password is too long, or the address and protocol type of the proxy server and the remote server do not match. 225 226**Procedure** 227 228Check whether the user name and password exceed the length limit and whether the addresses and protocol types of the proxy server and remote server match. 229 230## 2301213 Failed to Deserialize Messages for SOCKS5 231 232**Error Message** 233 234Socks5 deserialization error. 235 236**Description** 237 238This error code is reported if message fails to be deserialized for a SOCKS5 client. 239 240**Cause** 241 242The length of the response packets sent by the server does not comply with the protocol. 243 244**Procedure** 245 246Check the response data packets of the server. 247 248## 2303104 System Call Interrupted 249 250**Error Message** 251 252Interrupted system call. 253 254**Description** 255 256This error code is reported if the system call is interrupted. 257 258**Cause** 259 260Calling the **connect** function may result in a long blocking time. In such a case, the system generates an interrupt signal and returns an **EINTR** error. 261 262**Procedure** 263 264Call the **connect** function to try network connection again. 265 266## 2303109 Error File Number 267 268**Error Message** 269 270Bad file number. 271 272**Description** 273 274This error code is reported if an operation is performed on a locally closed socket. 275 276**Cause** 277 278The socket FD may be closed. 279 280**Procedure** 281 282Check whether the socket is closed unexpectedly. 283 284## 2303111 Requested Resource Temporarily Unavailable 285 286**Error Message** 287 288Resource temporarily unavailable. Try again. 289 290**Description** 291 292This error code is reported if the requested system resource is temporarily unavailable. 293 294**Cause** 295 296The system resources are in use. 297 298**Procedure** 299 300Try again later. 301 302## 2303188 Socket Operations on Non-Sockets 303 304**Error Message** 305 306Not a socket. 307 308**Description** 309 310This error code is reported if a socket descriptor is not specified for the **socket** parameter. 311 312**Cause** 313 314A socket descriptor is not specified for the **socket** parameter. 315 316**Procedure** 317 318Check whether the descriptor is correctly obtained. 319 320## 2303191 Incorrect Socket Protocol Type 321 322**Error Message** 323 324Incorrect socket protocol type. 325 326**Description** 327 328This error code is reported if the type of the specified socket protocol is incorrect. 329 330**Cause** 331 332The **socket** function is called with an unsupported socket protocol type. 333For example, the protocol type cannot be set to **SOCK_STREAM socket** for the the Internet UDP protocol. 334 335**Procedure** 336 337Check whether the socket protocol type is correct. 338 339## 2303198 Network Address Already In Use 340 341**Error Message** 342 343Address already in use. 344 345**Description** 346 347This error code is reported if a network address has been used. 348 349**Cause** 350 351The probable cause can be any of the following: The application attempts to bind a socket to an IP address/port that has been used for an existing socket. The socket is not properly closed. The socket is still being closed. 352 353**Procedure** 354 355Try another network address. 356 357## 2303199 Failed to Assign the Requested Address 358 359**Error Message** 360 361Address not available. 362 363**Description** 364 365This error code is reported if the requested address is invalid in its context. 366 367**Cause** 368 369The remote address or port is invalid for the remote server. 370 371**Procedure** 372 373Check whether the address or port is correct. 374 375## 2303200 Network Disabled 376 377**Error Message** 378 379Network is down. 380 381**Description** 382 383The network is disabled. 384 385**Cause** 386 387The network service is not started or has been stopped. 388 389**Procedure** 390 391Check the network connection. 392 393## 2303210 Connection Timeout 394 395**Error Message** 396 397Connection timed out. 398 399**Description** 400 401This error code is reported if the connection to the remote server cannot be set up for a long time. 402 403**Cause** 404 405It is probable that a server breakdown has occurred. 406 407**Procedure** 408 409Contact the peer end to rectify the fault. 410 411## 2303501 Null SSL 412 413**Error Message** 414 415SSL is null. 416 417**Description** 418 419This error code is reported if the SSL is null. 420 421**Cause** 422 423The returned error information is null when an internal function fails to be executed. 424 425**Procedure** 426 427Call the function again. 428 429## 2303502 TLS Reading Error 430 431**Error Message** 432 433An error occurred when reading data on the TLS socket. 434 435**Description** 436 437This error code is reported if an error occurs while reading data on the TLS socket. 438 439**Cause** 440 441The underlying socket is blocked. 442 443**Procedure** 444 445Perform data receiving again. 446 447## 2303503 TLS Writing Error 448 449**Error Message** 450 451An error occurred when writing data on the TLS socket. 452 453**Description** 454 455This error code is reported if an error occurs while writing data on the TLS socket. 456 457**Cause** 458 459When the send buffer is full, the underlying socket sends an **EWOUDLBLOCK** error, which means that the server does not read the data sent from the client. 460 461**Procedure** 462 463Rectify the fault on the server side. 464 465## 2303504 x509 Failed to Look Up the x509 Certificate 466 467**Error Message** 468 469An error occurred when verifying the X.509 certificate. 470 471**Description** 472 473An error occurred when verifying the x509 certificate. 474 475**Cause** 476 477The local certificate does not match the server certificate. 478 479**Procedure** 480 481Check whether the local CA matches the server certificate. 482 483## 2303505 TLS System Call Error 484 485**Error Message** 486 487An error occurred in the TLS system call. 488 489**Description** 490 491This error code is reported if the TLS system call fails because of fatal I/O errors. 492 493**Cause** 494 495Network communication fails because of network faults. 496 497**Procedure** 498 499For details, see the Linux kernel error codes (errno). 500 501## 2303506 Failed to Close TLS Connections 502 503**Error Message** 504 505Failed to close the TLS connection. 506 507**Description** 508 509This error code is reported if the TLS/SSL connection to be closed has been disabled. 510 511**Cause** 512 513The TLS/SSL connection to be closed has been disabled. 514 515**Procedure** 516 517Initiate a new TLS/SSL connection. 518