After a fresh emerge install of firebird I tried to start it but firebird gives me me this: buttercup root # /etc/init.d/firebird start * Starting Firebird server... check $FIREBIRD/firebird.log file for errors can not start server [ ok ] This is my firebird log: buttercup root # tail -f /opt/firebird/firebird.log buttercup (Server) Fri Jan 14 01:53:43 2005 SERVER/process_packet: connection rejected for firebird buttercup (Server) Fri Jan 14 01:53:43 2005 SERVER/process_packet: connection rejected for firebird buttercup (Server) Fri Jan 14 01:53:43 2005 SERVER/process_packet: connection rejected for firebird My firebird actually runs like a charm. I can gsec and isql on it: buttercup root # ps aux | grep fb firebird 6933 0.0 0.5 3720 1488 pts/0 S 01:53 0:00 /opt/firebird/bin/fbguard -f firebird 6934 0.0 1.1 10276 2960 ? S 01:53 0:00 /opt/firebird/bin/fbserver firebird 6935 0.0 1.1 10276 2960 ? S 01:53 0:00 /opt/firebird/bin/fbserver firebird 6938 0.0 1.1 10276 2960 ? S 01:53 0:00 /opt/firebird/bin/fbserver firebird 6940 0.0 1.1 10276 2960 ? S 01:53 0:00 /opt/firebird/bin/fbserver
Did you executed `ebuild /usr/portage/dev-db/firebird/firebird-1.5.1.ebuild config` ?
no, I did not run `ebuild /usr/portage/dev-db/firebird/firebird-1.5.1.ebuild config`. Should I ? one more thing I did miss out the top portion of the /opt/firebird/firebird.log. The log starts like this:- buttercup (Client) Fri Jan 14 18:00:27 2005 INET/inet_error: connect errno = 111 buttercup (Client) Fri Jan 14 18:00:28 2005 /opt/firebird/bin/fbguard: guardian starting bin/fbserver buttercup (Server) Fri Jan 14 18:00:29 2005 SERVER/process_packet: connection rejected for firebird buttercup (Server) Fri Jan 14 18:00:29 2005 SERVER/process_packet: connection rejected for firebird buttercup (Server) Fri Jan 14 18:00:29 2005 SERVER/process_packet: connection rejected for firebird buttercup (Server) Fri Jan 14 18:00:31 2005 SERVER/process_packet: connection rejected for firebird . . . .
I did the ebuild as you told me. The firebird starts ok now but the firebird.log still gives me the 111 error? buttercup root # > /opt/firebird/firebird.log buttercup root # /etc/init.d/firebird start * Starting Firebird server... server has been successfully started [ ok ] buttercup root # cat /opt/firebird/firebird.log buttercup (Client) Fri Jan 14 19:22:11 2005 INET/inet_error: connect errno = 111 buttercup (Client) Fri Jan 14 19:22:11 2005 /opt/firebird/bin/fbguard: guardian starting bin/fbserver buttercup root # ps aux | grep fb firebird 10906 0.0 0.5 3720 1488 pts/0 S 19:22 0:00 /opt/firebird/bin/fbguard -f firebird 10907 0.0 1.1 8228 3000 ? S 19:22 0:00 /opt/firebird/bin/fbserver firebird 10908 0.0 1.1 8228 3000 ? S 19:22 0:00 /opt/firebird/bin/fbserver firebird 10911 0.0 1.1 8228 3000 ? S 19:22 0:00 /opt/firebird/bin/fbserver root 10916 0.0 0.1 1376 440 pts/0 S+ 19:23 0:00 grep fb buttercup root #
but firebird works nice or not?
I guess the firebird runs fine. I can do execute basic mysql. Do you know what cause the inet error number 111 ? Here is screenshot:- buttercup root # /opt/firebird/bin/isql /opt/firebird/example/employee.fdb Database: /opt/firebird/example/employee.fdb SQL> show tables; COUNTRY CUSTOMER DEPARTMENT EMPLOYEE EMPLOYEE_PROJECT JOB PHONE_LIST PROJECT PROJ_DEPT_BUDGET SALARY_HISTORY SALES SQL> select * from country; COUNTRY CURRENCY =============== ========== USA Dollar England Pound Canada CdnDlr Switzerland SFranc Japan Yen Italy Lira France FFranc Germany D-Mark Australia ADollar Hong Kong HKDollar Netherlands Guilder Belgium BFranc Austria Schilling Fiji FDollar SQL> quit CON> ; buttercup root # tail -f /opt/firebird/firebird.log buttercup (Client) Tue Jan 18 07:46:29 2005 INET/inet_error: connect errno = 111 buttercup (Client) Tue Jan 18 07:46:29 2005 /opt/firebird/bin/fbguard: guardian starting bin/fbserver
I've never see that error and documentation doesn't mantion it at all.
What documentation are you talking about? Anyway I post this problem to firebird-support list and I get this answer From: Helen Borrie <helebor@t...> Date: Tue Jan 18, 2005 1:58 pm Subject: Re: [firebird-support] Should I worry about INET/inet_error ? ADVERTISEMENT At 12:42 AM 18/01/2005 +0000, you wrote: >When ever I start my super server firebird 1.5 at my gentoo I got this >error in my firebird.log. > >INET/inet_error: connect errno = 111 > >What does this tell me? What can I do to fix this? They are TCP/IP errors. Firebird doesn't know why they are happening - it only reports them. They are useful if you are observing problems at the same time that Firebird *does* know about.
OK, i searched in C include files, firebird docs placed in firebird.sf.net, manuals and didn't found anything about this error number
I'm going to leave this as resoleved since it's turns out not to halt the db. I received an e-mail saying this:- I hope this help! (From http://community.borland.com/article/0,1410,27663,00.html) INET/inet_error: connect errno = 111 - by Borland Developer Support Staff Abstract: Why the error "INET/inet_error: connect errno = 111" is entered in the interbase.log file. Question: When I execute -start command with IBMGR the server(SuperServer) successfully starts but in the interbase.log file this message appears: INET/inet_error: connect errno = 111 Answer: After you execute the start command IBMGR immediately tries to connect to isc4.gdb. This happens before the server is ready to accept connections so it generates the error, "INET/inet_error: connect errno = 111". IBMGR will try again to connect to isc4.gdb and the usually the server is ready to accept connections so the next entry in the log will probably be, "/opt/interbase/bin/ibguard: guardian starting bin/ibserver" indicating that the server has been successfully started.
