Ошибка 10048 мта

думаю, что у вас просто закончились динамические порты в системе…..

ошибка (учитывая что изменение max_connection не помогает) формируется вовсе не из за mysql , а из-за невозможности винды предоставить нужное число портов.

WSAEADDRINUSE
(10048)
Address already in use.
Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn’t closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all — connectwill choose an unused port automatically.»

что в общем случае означает —

Address already in use (Адрес уже используется).
Обычно разрешено только одно использование адреса сокета (проткол/адрес IP/порт). Эта ошибка возникает, когда приложение пытается привязаться к сокету функцией bind(), но комбинация адрес IP/порт уже используется существующим сокетом, или сокет не был корректно закрыт, или продолжается процесс закрытия сокета. Для серверных приложений, требующих привязки нескольких сокетов к одному и тому же номеру порта следует использовать setsockopt(SO_REUSEADDR). Клиентские приложения обычно не используют bind() — функция connect() автоматически выбирает неиспользуемый порт.

В вашем случае, при возрастании числа запросов к базе, когда открывается и закрывается куча подключений к базе, то оти попросту не успевают закрыться. Обратите внимание, что речь идет не о том, чтобы не забыть закрыть подключение mysql, а о том, что ресурсы для НОВОГО подключения освободятся не сразу….

Если мне память не изменяет, то есть в реестре пара параметров, которые на это влияют.

один из них — TcpTimedWaitDelay. Этот параметр определяет интервал времени, в течение которого подключение находится в состоянии ожидания, прежде чем будет закрыто. Пока подключение находится в состоянии ожидания, пара сокетов не может быть использована повторно. А согласно RFC793, данное значение должно в два раза превышать максимальное время жизни пакета.
Если учесть что в Windows XP и Microsoft Windows Server 2003 значение по умолчанию было установлено на 120 секунд, то получается что целых 2 минуты система просто ждет никому не отдавая уже освободившийся ресурс.

ищем тут

Код: Выделить всё • Развернуть

HKLMSYSTEMCurrentControLSetServicesTcpipParametersTcpTimedWaitDelay

и уменьшаем значение.
если нет, то создаем
REG_DWORD – время в секундах , с допустимыми параметрами 30-300 (в десятичной системе)

и второй параметр это MaxUserPort
находится он в

Код: Выделить всё • Развернуть

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters

имеет тип DWORD и допустимые значения от десятичных 5000 (по умолчанию) до 65534

он определяет максимальный номер порта, который используется, когда программа запрашивает у системы доступный пользовательский порт.

в итоге изначально имеем в системе всего 5000-1024 = 3976 портов, доступных для приложений, да еще и повторно использовать их можно не чаще раза в 2 минуты…

отпишитесь, плиз, помогло написанное или нет ?

p.s. если параметра нет в реестре, то это не значит что он не используется, просто его значение принимается системой по умолчанию…..

по итогам размышлений над

http://bugs.mysql.com/bug.php?id=10498

и

http://bugs.mysql.com/bug.php?id=6580

• 

• Forum

• MMO Zone

• MMO and MMORPG Developments

• Ran Online

• Ran Online Help

• [SOLVED] bind Error. Error Code:10048

1. 07-08-12

   #1

   
   Member

   

   ---

   [SOLVED] bind Error. Error Code:10048
   

   i have this error in Login Server

   PHP Code:

   
Service Provider:CHINA

   CreateIoCompletionPort OK

   --------------- System Information -------------------Microsoft Windows XP

   Unknown Processor 3041 Mhz

   1 System Processor Detected

   ------------------------------------------------------1 Worker Thread

   1 st Worker Thread Create OK

   Server Update Thread Create OK

   WSASocket OK

   bind Error

   . Error Code:10048== Please wait until server stop 

   CloseAllClient

   Stop IOCP

   Stop Meessage Queue

   INFO

   :SQL_ATTR_CONNECTION_POOLING OK

   INFO

   :SQLAllocHandle OK

   Stop DataBase

   Stop CFG

   =======================================================Server Stop OK=======================================================INFO:SQL_ATTR_CONNECTION_POOLING OK

   INFO

   :SQLAllocHandle OK 



   ---

2. 

   ---

3. 07-08-12

   #2

   
   Account Upgraded | Title Enabled!

   

   ---

   Re: Someone help me
   

   Check you IP adress in CFG.Make sure you use a valid IP adress and already written down in the CFG.

   ---

4. 07-08-12

   #3

   
   Member

   

   ---

   Re: Someone help me
   

   I check my ip but nothing wrong…

   please chck sir

   ---

5. 08-08-12

   #4

   Re: Someone help me
   

   @0103:

   did you check your database Setting in Sql ? and odbc?

   check and recheck your settings again maybe you have a mistake or you forgot to setup something!!

   and if you running the servers make sure Hamachi is Power ON/Online And not Close

   Last edited by Men In White; 08-08-12 at 12:37 AM.

   ---

6. 08-08-12

   #5

   
   Member

   

   ---

   Re: Someone help me
   

   I have already Solved Sir..Thanks again.. Thread Closed

   ---

7. 08-08-12

   #6

   Re: Someone help me
   

   @mod : Close This Thread Immidiately
   Reason: Problem of 0103 Already Solved!

   ---

8. 10-08-12

   #7

   
   Account Upgraded | Title Enabled!

   

   ---

   Re: Someone help me
   

   Please post here how you solve your problem so that other people can refer to this thread if they got the same problem.

   ---

9. 10-08-12

   #8

   
   Member

   

   ---

   Re: Someone help me
   

   I Download other serverfiles that’s compatible in my Client..

   Thanks Again

   /Thread Close

   ---

10. 16-08-12

    #9

    Re: Someone help me
    

    

    Note: Please message me if you have any request for this thread.

    ---

Advertisement

SQL server error 10048 occurs while starting the SQL server.

Here at Bobcares, we have seen several causes for this error while troubleshooting SQL issues as part of our Server Management Services for SQL database users, web hosts, and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

What causes SQL server error 10048 to occur?

Now let’s see what causes this error to occur. Port 1433 is a standard port number for SQL Server.

However, in some cases, the TCP port where the SQL server is listening is already used by another service or process.

These changes lead to the 10048 error. For instance, the error appears as:

How we resolve SQL server error 10048?

Now let’s dig into the solution part of this error. Here are some of the solutions that our Support Engineers follow to fix this error.

Find the process which is using that port and stop that process.

We run the below command in the command prompt to check the TCP ports which are in use. This also displays the name of the application which is using it.

netstat -a -b

Here, we find the application which is using TCP port 1433 and change that application to use a different port number.

Change port of SQL Server to a port that is not used by any other process.

We follow the below steps to change the port of the SQL server.

1. Initially, we open the SQL Server Configuration Manager. For that, we click on Start >> Programs >> Microsoft SQL Server 2005 >> Configuration Tools >> SQL Server Configuration Manager.
2. A Dropdown is available under the SQL Server 2005 Network Configuration and then we select the instance.
3. Here we right-click on TCP/IP and select Properties option.
4. Then we select the IP Addresses Tab to change to an open port.
5. Finally, we restart the SQL SERVER to fix this error.

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, SQL server error 10048 occurs when the TCP port where SQL server must run is used by other processes. Today, we saw how our Support Engineers fix this error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

• Remove From My Forums

• Question

• Hello.  I am experiencing the issue with SQL Server 2005 service not able to start when TCP/IP is enabled.  I have researched this issue extensively and what I come up with are fixes for checkpoints on clustered instances.  ISSUE: I am running
  a machine with XP Pro and not Server 2003, so I CANNOT have clustered instances.  ALL the fixes out there refer to commands such as «cluster res» which do not exist in Win XP Pro.  Here is the error log which looks exactly like everyone
  else’s (when they are dealing with clusters on Server 2003).  Can anyone shed ANY light on how to deal with this on a Win XP machine?  I’m going totally crazy here.  I can get the local server to load by disabling TCP/IP in SSCM.  VIA does
  not need to be disabled, just TCP/IP.   Of course you know this issue came up when I attempted to change the Listen Port / IP address.  I was starting and restarting and stopping and starting the SQL service in order to apply changes within
  SSCM and must have attempted to apply a change while the SQL server wasn’t running.  Thank you in advance for any help.  FYI, I attempted to run the GUI clusterrecovery.com but it failed miserably.  The «browse» function gave me an
  ActiveX error and I couldn’t locate my Cluster because I don’t think I have one.   Please, someone, any one… HELP.

  2013-01-21 10:56:42.12 Server      Microsoft SQL Server 2005 — 9.00.5000.00 (Intel X86)

      Dec 10 2010 10:56:29
      Copyright (c) 1988-2005 Microsoft Corporation
      Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 3)

  2013-01-21 10:56:42.23 Server      (c) 2005 Microsoft Corporation.
  2013-01-21 10:56:42.25 Server      All rights reserved.
  2013-01-21 10:56:42.26 Server      Server process ID is 4280.
  2013-01-21 10:56:42.28 Server      Authentication mode is MIXED.
  2013-01-21 10:56:42.29 Server      Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG’.
  2013-01-21 10:56:42.32 Server      This instance of SQL Server last reported using a process ID of 5292 at 1/21/2013 10:53:24 AM (local) 1/21/2013 5:53:24 PM (UTC). This is an informational message only; no user action is required.
  2013-01-21 10:56:42.37 Server      Registry startup parameters:
  2013-01-21 10:56:42.39 Server           -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
  2013-01-21 10:56:42.42 Server           -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
  2013-01-21 10:56:42.45 Server           -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
  2013-01-21 10:56:42.48 Server      Command Line Startup Parameters:
  2013-01-21 10:56:42.50 Server           -s advisorsassist
  2013-01-21 10:56:42.53 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
  2013-01-21 10:56:42.56 Server      Detected 2 CPUs. This is an informational message; no user action is required.
  2013-01-21 10:56:43.23 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
  2013-01-21 10:56:43.29 Server      Database mirroring has been enabled on this instance of SQL Server.
  2013-01-21 10:56:43.32 spid5s      Starting up database ‘master’.
  2013-01-21 10:56:43.46 spid5s      1 transactions rolled forward in database ‘master’ (1). This is an informational message only. No user action is required.
  2013-01-21 10:56:43.51 spid5s      0 transactions rolled back in database ‘master’ (1). This is an informational message only. No user action is required.
  2013-01-21 10:56:43.54 spid5s      Recovery is writing a checkpoint in database ‘master’ (1). This is an informational message only. No user action is required.
  2013-01-21 10:56:43.67 spid5s      SQL Trace ID 1 was started by login «sa».
  2013-01-21 10:56:43.68 spid5s      Starting up database ‘mssqlsystemresource’.
  2013-01-21 10:56:43.74 spid5s      The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
  2013-01-21 10:56:43.96 spid8s      Starting up database ‘model’.
  2013-01-21 10:56:43.96 Server      Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
  2013-01-21 10:56:43.98 spid5s      Server name is ‘LOWELLADVISORSASSIST’. This is an informational message only. No user action is required.
  2013-01-21 10:56:44.12 spid8s      Clearing tempdb database.
  2013-01-21 10:56:44.28 spid8s      Starting up database ‘tempdb’.
  2013-01-21 10:56:44.43 spid11s     The Service Broker protocol transport is disabled or not configured.
  2013-01-21 10:56:44.46 spid11s     The Database Mirroring protocol transport is disabled or not configured.
  2013-01-21 10:56:44.54 spid11s     Service Broker manager has started.
  2013-01-21 10:56:44.57 Server      A self-generated certificate was successfully loaded for encryption.
  2013-01-21 10:56:44.62 Server      Server is listening on [ ‘any’ <ipv4> 3136].
  2013-01-21 10:56:44.64 Server      Error: 26023, Severity: 16, State: 1.
  2013-01-21 10:56:44.64 Server      Server TCP provider failed to listen on [ ‘any’ <ipv4> 3136]. Tcp port is already in use.
  2013-01-21 10:56:44.68 Server      Error: 17182, Severity: 16, State: 1.
  2013-01-21 10:56:44.68 Server      TDSSNIClient initialization failed with error 0x2740, status code 0xa.
  2013-01-21 10:56:44.73 Server      Error: 17182, Severity: 16, State: 1.
  2013-01-21 10:56:44.73 Server      TDSSNIClient initialization failed with error 0x2740, status code 0x1.
  2013-01-21 10:56:44.78 Server      Error: 17826, Severity: 18, State: 3.
  2013-01-21 10:56:44.78 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
  2013-01-21 10:56:44.84 Server      Error: 17120, Severity: 16, State: 1.
  2013-01-21 10:56:44.84 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.