Ingres Installation

[Rich Ford]

I just installed 11.2 on SuSe

express_install.sh -licdir /ingres/license -interactive -no32bit

but got this error at the end:

redirecting to systemctl start ingresII.service
Failed to start ingresII.service: Unit ingresII.service not found.

Is there a fix for this?

Rich

[Paul Mason]

Hi Rich,

This is an error trying to start the Ingres service. It gets installed as part of the installation.

If you don't care about starting Ingres as a service then it's not a show stopper. If you do then you can install it manually (see below)

A few questions:

What version of Suse is this?

Was this the rpm saveset or the ingbuild one?

Was it an upgrade?

Check whether you have the file $II_SYSTEM/ingres/files/rcfiles/ingresII.service. If you do you can manually install it with:

mksystemd -i

as root.

If you still have the output of the install terminal session it would be interesting to see if there are any errors relating to systemd.

Thanks
Paul

_______________________________________________
Info-ingres mailing list
Info-...@lists.planetingres.org
https://lists.planetingres.org/mailman/listinfo/info-ingres

[Rich Ford]

1) OS version is 15.2
2) Not sure of the distinction between saveset or inbuild.
I downloaded from Actian:
actianx-11.1.0-100-com-linux-rpm-x86_64-15692
3) New installation

Thanks,
Rich

[Rich Ford]

Yes it's ingbuild called from running express_install.sh.
install/ingbuild

[Paul Mason]

You mentioned the rpm saveset -

actianx-11.1.0-100-com-linux-rpm-x86_64-15692

that doesn't use ingbuild, that would be the other saveset -

actianx-11.1.0-100-com-linux-ingbuild-x86_64-15692

I asked because the way things are done is slightly different.

Did you find the service file in $II_SYSTEM/ingres/files/rcfiles?

During the installation (either type) the service file first gets created and then gets installed. Your original error implies it was not installed but it would be interesting to know whether it failed getting created or just installed. That's why I asked about having the output from the terminal when you installed.

As I said before you should be able to install the service manually if you want it. A fix may be needed to the install process but you probably don't want to re-install Actian X just to get the service working.

When I get the time I'll try the install on Suse 15.2 myself and see if I can reproduce it. If you want to pursue this then you may want to open a Support issue.

Regards

[Rich Ford]

I checked but there is no ingresII.service file.

[Paul Mason]

Hi Rich,

First I must apologise. I misread this as you trying to install 11.2 not 11.1, despite the fact you clearly mentioned 11.1.

In 11.1 we are still using so-called "sysv" style service scripts. These are ones that get created in /etc/rc.d. Most modern Linux distros use systemd instead and provide compatibility scripts to make sysv scripts appear as if they were systemd services. However in the case of OpenSuSE 15 and SLES 15 a part of this compatibility layer is not installed by default.

So in order to fix this you would need to install "insserv-compat" i.e. something like:

sudo zypper install insserv-compat

This then would allow the installing of the 11.1 sysv service scripts. Since you probably already installed the instance itself OK and don't want to re-install just to fix it you can install it manually:

$ source /opt/Actian/IngresII/.ingIIsh # or whatever your instance env script is
$ mkrc # this generates the scripts, specific to your instance
$ sudo -s
$ source /opt/Actian/IngresII/.ingIIsh
$ mkrc -i

We added full systemd support in 11.2 which uses mksystemd instead of mkrc (although you can still use sysv if you really want). So apologies because a lot of my previous comments refer to that.

This is a known problem and there was supposed to be a fix and/or note in the readme. However the "fix" will be the installer warning you that you need to install insserv-compat. I'll chase that up.

Regards
Paul

[Rich Ford]

Good information. I have this configured now.

Rich

[Rich Ford]

I made the changes and rebooted the server but now getting this error:

accessdb
E_LC0001 GCA protocol service (GCA_REQUEST) failure.
Internal service status E_GCfe05 -- Unable to make outgoing connection.
- Please check that the remote server (localhost/127.0.0.1) is correct
and that the port (44819) you are trying to connect to is open and
allowed through the firewall.
connect() failed with operating system error 107 (Transport endpoint is
not connected).

E_LQ0001 Failed to connect to DBMS session.

E_IC0061 Error starting INGRES.
Error '000094D4' occurred when Accessdb/Catalogdb tried to connect to
the database. The preceding error messages should explain what type of
error occurred. If not, then report this problem to your Site Technical
Contact.

Rich

[Rich Ford]

Please ignore.
User error on my part.

Rich

[Roy Hann]

Rich Ford wrote:

> On Monday, 6 December 2021 at 08:39:20 UTC-8, Rich Ford wrote:

[snip]

> I made the changes and rebooted the server but now getting this error:
>
> accessdb
> E_LC0001 GCA protocol service (GCA_REQUEST) failure.
> Internal service status E_GCfe05 -- Unable to make outgoing connection.
> - Please check that the remote server (localhost/127.0.0.1) is correct
> and that the port (44819) you are trying to connect to is open and
> allowed through the firewall.
> connect() failed with operating system error 107 (Transport endpoint is
> not connected).
>
> E_LQ0001 Failed to connect to DBMS session.
>
> E_IC0061 Error starting INGRES.
> Error '000094D4' occurred when Accessdb/Catalogdb tried to connect to
> the database. The preceding error messages should explain what type of
> error occurred. If not, then report this problem to your Site Technical
> Contact.

What do you get from running

iinamu show servers

If it shows 44819 the name server is confused.

Roy

[Rich Ford]

iinamu show servers
RMCMD * 36669
STAR * 36965
DASVR * 46677
COMSVR * 43781
INGRES * 37469 (sole server)
IUSVR * 37585
IINMSVR * 33501