This is weird.

Earlier today I moved the directory containing II_SYSTEM (/opt) to a
new drive. Afterwards I was able to start Ingres just fine except for
DAS, which wouldn't start. It throws E_GC4805 and E_GC4806 errors.

I didn't need it for what I was doing so I just set the startup count to
zero. A few minutes ago I moved everthing back to where it was
originally and just for a laugh I restored the starup count to 1. And
now DAS starts.

Why would DAS (alone) care which drive it lives on?

II 10.0.0 (a64.lnx/483)NPTL

--
Roy

UK Ingres User Association Conference 2010 will be on Tuesday June 8 2010
Go to http://www.iua.org.uk/join to get on the mailing list.

Hi Roy,
This error is generally caused when both JDBC and DAS are configured at
the same port (listen address).
However, since this is Ingres 10, that possibility rules out.
One thing that comes to mind is probably the listen sockets for the DAS
TCP port were still lying around after ingstop and thus, the DAS server
didn’t restart. Once the keepalive (or similar on Linux) function
removed the stray sockets, i.e. when the listen sockets were gone, the
DAS server got restartd successfully.
Thanks,
Divya


--
Divya

Ingres Forums wrote:

Yes, a classic problem.

That's a possibility. I've rebooted so many times today I can't recall
for sure if I did one after moving II_SYSTEM. I shall be moving it
again shortly, so I'll keep you posted.

--
Roy

UK Ingres User Association Conference 2010 will be on Tuesday June 8 2010
Go to http://www.iua.org.uk/join to get on the mailing list.

Roy,

I called HP Support on this, and they say you should buy a new blade server
and a SAN if you want to move /opt. Actually, you need 3 for redundancy.

Cheers,

Mike Leo


On Feb 26, 2010, at 2:19 PM, Roy Hann wrote:

Mike Leo wrote:

Really? About 20 years ago they'd have told me to keep using it like
it is and I'd get used to it.

My, how times change.

--
Roy

UK Ingres User Association Conference 2010 will be on Tuesday June 8 2010
Go to http://www.iua.org.uk/join to get on the mailing list.

Hi Roy,

I don't quite see a problem with starting the DAS server when II_SYSTEM
is relocated... The GC errors that you are seeing indicate that network
initialization errors by the DAS server and thus preventing it from
starting successfully.

Is it possible to attach the errlog.log before and after the II_SYSTEM
relocation? What about the Communication server (iigcc)? Does it come up
fine after relocation? I seem to only have more questions about the
Ingres configuration than answers for you.....

Regards,
Usha


--
rajus01

Roy Hann wrote:

It seems that Divya was correct. It was probably just a port left open.
I'd stopped and started that installation about 20 times that morning,
but it chose to leave a port open the one time I moved a file system.
Sod's law I guess.

I've moved the file systems around five or six times without incident
now.

--
Roy

UK Ingres User Association Conference 2010 will be on Tuesday June 8 2010
Go to http://www.iua.org.uk/join to get on the mailing list.