[ic] No error message: 'connect failed'

Marco m.mescoli at omnib.it
Sun Nov 15 12:58:01 UTC 2009

Gert van der Spoel ha scritto:
>> -----Original Message-----
>> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
>> users-bounces at icdevgroup.org] On Behalf Of Marco
>> Sent: Sunday, November 15, 2009 2:18 AM
>> To: interchange-users at icdevgroup.org
>> Subject: [ic] No error message: 'connect failed'
>> 2 twins servers with 2 twins catalog
>> 1) develop server:
>> 	ubuntu, kernel 2.6.24-25, threaded perl 5.8.8, ic 5.6.2
>> 2) production server
>> 	ubuntu, kernel 2.6.24-19, threaded perl 5.8.8, ic 5.6.2
>> 1) Develop server:
>> If i put down external mysql db and load error catching page ic give me
>> immediatly this error:
>> [15/novembre/2009:00:33:44 +2500] elcat - table 'permessi_bk' failed:
>> table permessi_bk connect failed -- unknown error. Driver 'mysql'
>> installed?
>> :-) Well i can catch the db error.
>> 2) Production server:
>> If i put down external mysql db and load ic error catching page do not
>> give me any error (catalogue error.log) and the catching page give the
>> same results but only after about five minutes.
>> :-O Problem for me too much time to catch the error.
>> Compared without any indication
>>   interchange.cfg,
>>   catalog.cfg,
>>   variable.txt
>> Any ideas ?
>> Great thanks in advance :-)
> Different firewall rules on dev/prod to connect to the external database?
> CU,
> Gert
Solved ! :-)
Thanks Gert as you say: different rules on firewall.

All the hosts dev/prod and 'remote' mysql servers are in LAN and i 
excluded firewall problems because when the mysqlds are up all goes well 
in dev/prod but ... mysqld lives behind an XP firewall.

When mysql server is up XP open 3306 port and all goes well. When mysql 
server is down XP close 3306 port and the clients who try to connect are 
not immediatly rejected but must wait for timeout.

XP Mysqld down, LAN connection test with mysql clients:

1) XP 3306 open only when mysqld is up: default for XP firewall
ERROR 2003 (HY000): Can't connect to MySQL server on '' (110)
(3 minutes late)

2) XP 3006 force opended
ERROR 2003 (HY000): Can't connect to MySQL server on '' (111)

Force opening input port 3306 in XP firewall will solve this so mysql 
clients gets soon its "connect failed"


More information about the interchange-users mailing list