TDI startup error: "Config or group name not specified"

[Karl Prinelle]

Hi,

I've built a docker container to run TDI but I'm hitting an error at startup.
It reads like the server has started (see below), but then bales out with the "Config or group name is not specified" error.

I'm a little stuck because I don't know where this error is coming from. Has anyone seen it before? I'm hoping that knowing what the error is will help work towards a solution.

I've got the pre-req's installed on this image so don't think that is the issue;
compat-libstdc++-33.x86_64
libXp.x86_64


The error;
CTGDKD024I Remote API successfully started on port:1099, bound to:'SessionFactory'. SSL and Client Authentication are enabled.

java.lang.Exception: CTGDIS196E Config or group name is not specified.
at com.ibm.di.server.Log.exception(Log.java:1192)

[Karl Prinelle]

I should have said that I'm running TDI 7.2 FP6. From reading a couple of other posts about FP8 I realise I could remove the compat package. In parallel I'll try to get hold of FP8 to see if that helps.
Still interested to hear if anyone knows what the error means though.....

[Franzw]

Hi Karl

Two things :
From what I know of the CTGDIS196E error message is normally triggered because some quoting is not correct and hence the command link the config is messed up.

Be aware that when you go to 7.2 FP8 your log4j is migrated to version 2 and your logging setup has to be migrated to reflect that - check the release notes carefully :-)

HTH
Regards
Franz Wolfhagen

[Karl Prinelle]

Thanks for that. I've moved to FP8 and removed the compat libs from the build but still have the same issue.
This is a fresh install of TDI and for now I'm running ibmdisrv with the solution directory in the installation directory so I was expecting all paths and quoting would be ok.
I'll turn on some debugging to see if I can find at least where the message is coming from. That should help lead to a fix.

Aside: In reality I'll volume mount the solution directory from S3 into the container to better integrate with our CI/CD pipelines. Right now I'm just trying to get TDI running in the container

[Eddie Hartman]

What does your startup commandline look like? I managed to spin up a TDI solution in a container a while back and am happy to have a look with you if you haven't sorted this out yet.

/Eddie

[Karl Prinelle]

On Sunday, 24 July 2022 at 13:57:48 UTC+1, eddieh...@gmail.com wrote:
> What does your startup commandline look like? I managed to spin up a TDI solution in a container a while back and am happy to have a look with you if you haven't sorted this out yet.
>
> /Eddie

Sorry - must have missed the notification. Got it working in the end. I think there was just something wrong in my docker setup. Works nicely now.