Hello gurus,

Update to Ingres version 9.1.1 (linux x64) and patch 13273 appears to have been successful on 4 servers.
Except that the data access server doesn't start on some servers. It's OK on two, but not on two others.
I'm not even sure that it's really needed, but want to be on the safe side.

I haven't been able to figure out why it won't start.
The error log says:

..
..
..
delta ::[57984 IIGCC, 12738 , 00000000ffffffff]: Mon Apr 13 12:18:22 2009 E_GC2006_STARTUP Communication Server normal startup: server rev. level II 9.1.
delta ::[41437 IIGCN, 12576 , 0000000000000004]: Mon Apr 13 12:18:23 2009 E_GC0153_GCN_SRV_STARTUP Server Registration: class DASVR, address 46631
delta ::[46631 IIGCD, 12757 , 0000000000000000]: Mon Apr 13 12:18:23 2009 E_GC4805_NTWK_RQST_FAIL Network request 'OPEN' failed with error 0x0001FE02.
delta ::[46631 IIGCD, 12757 , 0000000000000000]: Mon Apr 13 12:18:23 2009 E_GC4806_NTWK_INIT_FAIL Network initialization failure: all protocol opens failed.
delta ::[41437 IIGCN, 12576 , 0000000000000004]: Mon Apr 13 12:18:23 2009 E_GC0155_GCN_SRV_FAILURE Registered server failure: class DASVR, address 46631

Can any one suggest a solution please? or where I should be looking?

Bob Borbiro.

Hi Bob,



Are you trying to start the DAS server with the same port than the JDBC
server on both these installations?

The DAS server cannot start with the same JDBC server port (default
address II7).

There is no reason to start both a JDBC and a DAS server: The DAS
server includes all the JDBC functionalities.

If so: The recommendation is to set the JDBC server with a startup count
to 0, using cbf.



Note:

If for any reason you want to start both, then the listen address for
one must be changed in CBF before startup.

And then, check the Firewall:

To do that, look at the file "/etc/sysconfig/iptables".

You should see a line similar to

" -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport
46631 -j ACCEPT"

If you changed one of the listen addresses (JDBC or DAS server) to start
both of them, just duplicate the existing line in the file and change
the port you want open.

Then restart the iptables service: "service iptables restart".



Bonus:

IP version 4:

To be on the safe side, if IPv6 support is not needed, I suggest to set
the Ingres variable II_TCPIP_VERSION to 4.

This forces the usage of the IPv4-only protocol. The command is: "
ingsetenv II_TCPIP_VERSION 4"



HTH,

Uncle JL





From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Ballpoint
Sent: lundi 13 avril 2009 04:44
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] IIGCD doesn't start after update to 9.1.1



Hello gurus,



Update to Ingres version 9.1.1 (linux x64) and patch 13273 appears to
have been successful on 4 servers.

Except that the data access server doesn't start on some servers. It's
OK on two, but not on two others.

I'm not even sure that it's really needed, but want to be on the safe
side.



I haven't been able to figure out why it won't start.

The error log says:



..

..

..

delta ::[57984 IIGCC, 12738 , 00000000ffffffff]:
Mon Apr 13 12:18:22 2009 E_GC2006_STARTUP Communication Server
normal startup: server rev. level II 9.1.
delta ::[41437 IIGCN, 12576 , 0000000000000004]:
Mon Apr 13 12:18:23 2009 E_GC0153_GCN_SRV_STARTUP Server
Registration: class DASVR, address 46631
delta ::[46631 IIGCD, 12757 , 0000000000000000]:
Mon Apr 13 12:18:23 2009 E_GC4805_NTWK_RQST_FAIL Network request
'OPEN' failed with error 0x0001FE02.
delta ::[46631 IIGCD, 12757 , 0000000000000000]:
Mon Apr 13 12:18:23 2009 E_GC4806_NTWK_INIT_FAIL Network
initialization failure: all protocol opens failed.
delta ::[41437 IIGCN, 12576 , 0000000000000004]:
Mon Apr 13 12:18:23 2009 E_GC0155_GCN_SRV_FAILURE Registered
server failure: class DASVR, address 46631

Can any one suggest a solution please? or where I should be looking?



Bob Borbiro.