I have just set up an Ingres 10.1 installation on a FC11 Linux box.

The Ingres installation have any issues and Ingres starts up without any
issues. The iigcd and iigcn processes are running.

When I try to configure a vnode on another Linux server, or try to
connect from Windows with jdbc I can't connect to the installation.

netutil reports it is unable to establish a network connection and jdbc
reports no route to host.

I can ssh to this server and ping on it. The new server can ping on
other servers in its network as well.

If i run service --status-all | grep Ingres on a working Linux server it
reports all the Ingres services running. If I do this on the new Linux
server it doesn't report any Ingres services running.

If I do a lsof on the iigcn process it reports it is listening on the
same port as reported by ingprenv. lsof on the iigcd process reports it
is listening on 2 different ports, neither of which are the same as
iigcn - is this correct?

I don't know where to go from here and hoping someone else has seen this
and knows what the issue may be. I'm guessing this really not an Ingres
issue, but a network issue on the new server, but I don't have any idea
of what to look for at this point.

As an FYI, not to potentially confuse cause and effect with coincidence
- I initially set the new server up with DHCP enabled, did a bunch of
configuration (including Ingres), and then moved it to another network
using a static IP. The hostname didn't change between the two. In any
case I reinstalled Ingres to see if this may have had some effect.

Thanks

Dennis

Hello Dennis,

two questions:
1st: what is the result of this at your server site?
iigetres ii.`hostname`.gcc.*.tcp_ip.port
iigetres ii.`hostname`.gc.*.tcp_ip.port
ingprenv II_SHADOW_PWD

2nd: Which values you enter for vnode at your client site?
3rd: How does your url look when you try a JDBC connection?

Bilgihan


--
bilgihan

Hi,

Is it possible there's a firewall (eg iptables) on the FC11 host that's
blocking access to the ports?

You can see the port number the comsvr uses by looking in errlog.log,
eg:

IIGCC, 28131 , 00000000ffffffff]: Mon Nov 14 10:18:51 2011
E_GC2815_NTWK_OPEN Network open complete for protocol TCP_IP, port
II (21064).

The port number for the DAS isn't quite so easily identified from
errlog, you'll see something like:

IIGCD, 28152 , 0000000000000000]: Mon Nov 14 10:18:52 2011
E_GC4803_NTWK_OPEN Network open complete for protocol TCP_IP, port
II7.

As I'm only running 1 comsvr I know that's running on listen address
II0, so the port for II7 will be 21064 + 7 = 21071. lsof on the iigcd
process shows that port open.

I'm fairly sure I've seen a program that converts listen addresses to
port numbers before now, maybe someone will be able to provide a link.

G


--
geraintjones

An old KB doc 'Knowlege Base | Program to Convert the 2 Letter
Installation Code - 167025 - Actian'
(http://www.actian.com/kb/article/167025) indeed describes how to
convert listen addresses to port numbers.


--
mohsa01

Sounds like SELinux blocking the ports to me.


--
daryl.monge (AT) ingres (DOT) com
------------------------------------------------------------------------
daryl.monge (AT) ingres (DOT) com's Profile: http://community.actian.com/forum/member.php?userid=736
View this thread: http://community.actian.com/forum/sh...ad.php?t=14116

On 12/11/2011 6:15 PM, Dennis wrote:
Thanks for all of the responses.

It turns out it was iptables blocking Ingres services.

Although I couldn't find any log files (or don't know which ones to look
at) Ingres never complained and started all of its service processes.

I've had issues in the past where if selinux is enabled Ingres generally
won't install properly and as such won't start up properly.

The iptables issue is one I had forgotten about :-( In this case I
turned it off and that resolved the issue.

Thanks

Dennis

Off-topic, but still relevant - Fedora project dropped the "Core" from
the project's name in 2007 with the Fedora 7 release... So we should
refer to Fedora 11 as F11, not FC11.


--
dejan