Содержание
- What are those 100XX errors in firebird.log?
- iBase.ru Forum
- Win 7
- Win 7
What are those 100XX errors in firebird.log?
These are the network errors as reported by Windows. Here’s a list for your convenience (with explanations):
ERROR_SERVICE_CANNOT_ACCEPT_CTRL
(1061)
The service cannot accept control messages at this time.
WSAEACCES
(10013)
Permission denied.
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).
Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEADDRINUSE
(10048)
Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port) is 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 was not 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, connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
WSAEADDRNOTAVAIL
(10049)
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0).
WSAEAFNOSUPPORT
(10047)
Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
WSAEALREADY
(10037)
Operation already in progress.
An operation was attempted on a nonblocking socket with an operation already in progress, that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.
WSAECONNABORTED
(10053)
Software caused connection abort.
An established connection was aborted by the software in your host machine, possibly due to a data transmission time-out or protocol error.
WSAECONNREFUSED
(10061)
Connection refused.
No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host, that is, one with no server application running.
WSAECONNRESET
(10054)
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
WSAEDESTADDRREQ
(10039)
Destination address required.
A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.
WSAEFAULT
(10014)
Bad address.
The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a SOCKADDR structure, is smaller than the sizeof(SOCKADDR).
WSAEHOSTDOWN
(10064)
Host is down.
A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH
(10065)
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAEINPROGRESS
(10036)
Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation, per- task or thread, to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.
WSAEINTR
(10004)
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEINVAL
(10022)
Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket, for instance, calling accept on a socket that is not listening.
WSAEISCONN
(10056)
Socket is already connected.
A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
WSAEMFILE
(10024)
Too many open files.
Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEMSGSIZE
(10040)
Message too long.
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.
WSAENETDOWN
(10050)
Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
WSAENETRESET
(10052)
Network dropped connection on reset.
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAENETUNREACH
(10051)
Network is unreachable.
A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENOBUFS
(10055)
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
WSAENOPROTOOPT
(10042)
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAENOTCONN
(10057)
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error, for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAENOTSOCK
(10038)
Socket operation on nonsocket.
An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
WSAEOPNOTSUPP
(10045)
Operation not supported.
The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT
(10046)
Protocol family not supported.
The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.
WSAEPROCLIM
(10067)
Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached.
WSAEPROTONOSUPPORT
(10043)
Protocol not supported.
The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAEPROTOTYPE
(10041)
Protocol wrong type for socket.
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
WSAESHUTDOWN
(10058)
Cannot send after socket shutdown.
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.
WSAESOCKTNOSUPPORT
(10044)
Socket type not supported.
The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.
WSAETIMEDOUT
(10060)
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
WSATYPE_NOT_FOUND
(10109)
Class type not found.
The specified class was not found.
WSAEWOULDBLOCK
(10035)
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
WSAHOST_NOT_FOUND
(11001)
Host not found.
No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
WSANOTINITIALISED
(10093)
Successful WSAStartup not yet performed.
Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.
WSANO_DATA
(11004)
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record, indicating the host itself exists, but is not directly reachable.
WSANO_RECOVERY
(11003)
This is a nonrecoverable error.
This indicates some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.
WSASYSNOTREADY
(10091)
Network subsystem is unavailable.
This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:
That the appropriate Windows Sockets DLL file is in the current path.
That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.
The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
WSATRY_AGAIN
(11002)
Nonauthoritative host not found.
This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.
WSAVERNOTSUPPORTED
(10092)
Winsock.dll version out of range.
The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.
WSAEDISCON
(10101)
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
Источник
iBase.ru Forum
Форум по InterBase, Firebird и Yaffil
- Темы без ответов
- Активные темы
- Поиск
- Наша команда
Win 7
Win 7
Сообщение warlock000 » 07 июн 2011, 12:07
Доброе время суток, собственно сам саж: есть сетка, на всех компах этой сети стоит Windows 7 проф, на одном из компов стоит fbserver версии 1,5,6,5026, также на сервере стоит 4G модем который раздает интернет по стеки через общее подключение, локалка собсна с этим АЙПМ 192,168,137,1 всё бы хорошо но из вне нет коннекта к серверу, в бренд маузере созданы исключения на порты 3050/3051 (также добавлен сам файл сервера в исключения) последний добавил на всякий случай (так как из софтины увидил что оный слушается на том порту) локально сервер запускается и работает отлично но из он виснет при коннекте сервера, пробывал перенастроить сетку и для эксперемента сделал соеденение через свич двух компов из сетки с IP 192,168,0,1 тоже безрезультатно (думал может запарка из за двух сеток но как показал эксперемент это нетак) уже 4й день помогите
ADMIN (Client) Tue Jun 07 09:27:04 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Tue Jun 07 09:27:25 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Tue Jun 07 09:32:31 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
REMOTE INTERFACE/gds__detach: Unsuccesful detach from database.
Uncommitted work may have been lost
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Mon Jun 06 09:46:43 2011
INET/inet_error: connect errno = 10060
ADMIN (Server) Mon Jun 06 11:48:47 2011
Shutting down the Firebird service with 4 active connection(s) to 3 database(s)
*** (Client) Mon Jun 06 17:44:21 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:48 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:51 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:54 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:57 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:37:34 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:37:57 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:38:08 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:38:11 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:45:01 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:45:24 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:45:27 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:45:30 2011
INET/inet_error: connect errno = 10061
Источник
Firebird log file (firebid.log) can contain a lot of various messages, here you can find the list of most frequent of them, with the explanation of the error.
INET/inet_error: read errno = 10054
Short: Software caused connection abort.
The disconnect of the client from the server. If error text contains with (Client), it means that the client application lost its connection to the server and wrote down this fact to the log.
If error text contains (Server), it means that server lost the connection to the client and reported it to the firebird.log.
The usual reason of 10054 error is an unstable connection, for example, weak Wi-Fi.
Also, it is possible to see this error if a client application doesn’t explicitly close the database connection, i.e., there is no explicit command like «MyDB.Active:=false» on closing the software.
INET/inet_error: read errno = 104
Short: Software caused connection abort.
The same as 10054, but on Linux.
WNET/wnet_error: ReadFile end-of-file errno = 109
In short: Software caused connection abort.
The same as 10054, but this error occurs when client application uses the WNET connection path to the Firebird server instance on Windows, something like this:
\serverpathdatabase.fdb
This is not recommended, better use TCP/IP connections for network connections (in the format server:pathdatabase.fdb or, on Firebird 3, inet://servername:pathdatabase.fdb), and XNET for local connections (local path on 2.5 and xnet://pathdatabase.fdb).
Consider to disable WNET connections, look here how to disable connection protocols for Firebird on Windows.
INET/inet_error: send errno = 10053 (on Windows)
or INET/inet_error: send errno = 103 (on Linux)
Also means broken connection, but WinSock error is 10053.
INET/inet_error: connect errno = 10060 (Windows)
or INET/inet_error: connect errno = 10061 (Windows)
In short: 10061 — Connection refused, 10060 — Connection timed out
In general, this error means that it is not possible to establish a connection between the server and client application.
In case of this error with (Client), It means that the client application tried to connect to Firebird through network connection string, but failed, either Firebird server is not running, or access closed by a firewall.
More details about common Winsock errors is here.
|
|
|
|
информация о разделе
 |
Данный раздел предназначается исключительно для обсуждения вопросов использования языка запросов SQL. Обсуждение общих вопросов, связанных с тематикой баз данных — обсуждаем в разделе «Базы данных: общие вопросы». Убедительная просьба — соблюдать «Правила форума» и не пренебрегать «Правильным оформлением своих тем». Прежде, чем создавать тему, имеет смысл заглянуть в раздел «Базы данных: FAQ», возможно там уже есть ответ. |
Удаленное соединение к БД на FireBird
, не происходит
- Подписаться на тему
- Сообщить другу
- Скачать/распечатать тему
|
|
|
|
Рейтинг (т): 0 |
Доброе время суток. |
Full Member
|
vladimir74 |
|
|
никаких проблем не разу не видел, а какая ошибка вылетает (и какое подключение) ? |
 jack128 |
|
|
Цитата Лисенок @ 10.10.07, 12:18 хотя файл gdb виден по сети. а нафиг ты его расшарила? FB — это клиент-сервер, так что файл базы в сети расшаривать не нужно. Цитата Лисенок @ 10.10.07, 12:18 Как только не пыталась прописать путь к файлу…
фотмат такое(для tcp/ip соединения) например если база лежит в папке C:MyBasesBase.fdb и IP этой машины 192.168.0.46 то в параметрах соединения ты должна прописать 192.168.0.46:C:MyBasesBase.fdb Добавлено 10.10.07, 12:51 |
|
A.I. |
|
|
Добрый кот
Рейтинг (т): 29 |
несколько смутило расширение файла. Я бы рекомендовал все-таки перегнать в родной формат fdb. |
|
vladimir74 |
|
|
A.I. |
jack128 |
|
|
хинт: FB глубоко плюёт на расширение файла. хоть rar’ом его обзовите. |
|
londinium |
|
|
Junior
Рейтинг (т): нет |
открыть на файерволе порт, на котором висит FireBird (по умочанию 3050) |
|
Лисенок |
|
|
Рейтинг (т): 0 |
Спасибо все за помощь. |
|
Romkin |
|
|
Для event должны быть открыты все порты |
|
A.I. |
|
|
Добрый кот
Рейтинг (т): 29 |
jack128, хинт защитан. |
|
LordMadman |
|
|
Junior
Рейтинг (т): нет |
Пишет ошибку ‘connection rejected by remote interface’. Сервер FB2.0, конект через localhost/TCP |
|
Romkin |
|
|
Некрофил! Файрволу объясни, что тебе хочется. |
|
LordMadman |
|
|
Junior
Рейтинг (т): нет |
Цитата Romkin @ 27.04.08, 11:23 Некрофил! Файрволу объясни, что тебе хочется.
Их нихт!!! Усё выключено! В логах FB пишет INET/inet_error: connect errno = 10061 Сообщение отредактировано: LordMadman — 27.04.08, 16:14 |
|
Romkin |
|
|
61 — значит, нет сервера БД на этом порту. (Вроде 60 — это компьютера нет Добавлено 28.04.08, 09:04 |
)0 пользователей читают эту тему (0 гостей и 0 скрытых пользователей)
0 пользователей:
- Предыдущая тема
- Базы данных: SQL
- Следующая тема
[ Script execution time: 0,0919 ] [ 15 queries used ] [ Generated: 9.02.23, 18:48 GMT ]
Доброе время суток, собственно сам саж: есть сетка, на всех компах этой сети стоит Windows 7 проф, на одном из компов стоит fbserver версии 1,5,6,5026, также на сервере стоит 4G модем который раздает интернет по стеки через общее подключение, локалка собсна с этим АЙПМ 192,168,137,1 всё бы хорошо но из вне нет коннекта к серверу, в бренд маузере созданы исключения на порты 3050/3051 (также добавлен сам файл сервера в исключения) последний добавил на всякий случай (так как из софтины увидил что оный слушается на том порту) локально сервер запускается и работает отлично но из он виснет при коннекте сервера, пробывал перенастроить сетку и для эксперемента сделал соеденение через свич двух компов из сетки с IP 192,168,0,1 тоже безрезультатно (думал может запарка из за двух сеток но как показал эксперемент это нетак) уже 4й день помогите 
Логи сервера
ADMIN (Client) Tue Jun 07 09:27:04 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Tue Jun 07 09:27:25 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Tue Jun 07 09:32:31 2011
WNET/wnet_error: CreateFile errno = 53
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
REMOTE INTERFACE/gds__detach: Unsuccesful detach from database.
Uncommitted work may have been lost
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Thu Jun 02 11:30:44 2011
INET/inet_error: send errno = 10054
ADMIN (Client) Mon Jun 06 09:46:43 2011
INET/inet_error: connect errno = 10060
ADMIN (Server) Mon Jun 06 11:48:47 2011
Shutting down the Firebird service with 4 active connection(s) to 3 database(s)
Логи клиента:
*** (Client) Mon Jun 06 17:44:21 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:48 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:51 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:54 2011
INET/inet_error: connect errno = 10061
*** (Client) Mon Jun 06 17:55:57 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:37:34 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:37:57 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:38:08 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:38:11 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:45:01 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:45:24 2011
INET/inet_error: connect errno = 10060
*** (Client) Tue Jun 07 09:45:27 2011
INET/inet_error: connect errno = 10061
*** (Client) Tue Jun 07 09:45:30 2011
INET/inet_error: connect errno = 10061
Written by Embarcadero USA on Sunday, 23 July 2000 Posted in DATA
Problem:
Received error 10061 connection refused
Solution:
INET errors are TCP/IP error codes. A listing of these types of error can
be found in (winsock.h) for C/C++ or (winsock.pas) if using Pascal. There
are a variety of reasons why the system could return this message. Listed
below are some steps to discern what could be causing this error and how
to fix it.
Steps to resolve / things to check with regard to this issue:
1. If the server machine had local interbase on it before the server
version was installed, you may benefit by uninstalling local
interbase before attempting to install the server version of
interbase. Users have reported difficulty when they did not
uninstall old versions of local interbase before installing
the server version. If you have data in a database, please
back it up before doing the uninstall/reinstall process.
2. Verify the InterBase server is started on the machine that you
are trying to connect to.
3. Make sure that you have this entry in your services file on the
client and the server.
gds_db 3050/tcp
4. Another possibility is the licensing may be incorrect.
Make sure that you have the proper license string on the
server side for a server version of InterBase -- not local
InterBase.
5. Make sure that you have the the servername and ip address
correct in the hosts file of the client.
6. Finally, double check the machine name and path in the
connect string on the client.
Article originally contributed by Borland Staff
Tags:
Deployment
InterBase
Error
connection
Inet
10061
Check out more tips and tricks in this development video:
No iframes