Sadly IC still not usable in OES environment. 

Docker and IC are running in the installations. However, there is one problem: a few steps need to be carried out each time after a restart.


A question for those who have problems with the UMC and IC:
in /var/log/messeages

is there something similar to this?

2025-01-29T15:45:45.218460+01:00 oesserver systemd[1]: Starting edirapi container...
2025-01-29T15:45:45.233810+01:00 oesserver docker[30437]: Error response from daemon: No such container: edirapi-container

and

2025-01-29T15:44:12.547307+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:12+01:00 ] : info : TreeResolutionService::getAllTrees:Entered method in service to get tree names
2025-01-29T15:44:24.086712+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LocalStrategy::validate:Entered local strategy login method
2025-01-29T15:44:24.086972+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapAuthenticationService::authenticate:Entered the method
2025-01-29T15:44:24.087881+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapProxyService::login:Entered Ldap Proxy service login method with dn = cn=OESCommonProxy_oesserver,ou=adm,o=myou
2025-01-29T15:44:24.109683+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapProxyService::login:Proxy login failed
2025-01-29T15:44:24.109832+01:00 oesserver bash[7970]:  HttpException: Exception while executing edir API login: connect ECONNREFUSED my-ip:9010
2025-01-29T15:44:24.109924+01:00 oesserver bash[7970]:     at t.edirLogin (/opt/novell/umc/apps/umc-server/main.js:1:14912)
2025-01-29T15:44:24.110030+01:00 oesserver bash[7970]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-01-29T15:44:24.110114+01:00 oesserver bash[7970]:     at async LdapProxyService.login (/opt/novell/umc/apps/umc-server/main.js:1:37075)
2025-01-29T15:44:24.110212+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29497)
2025-01-29T15:44:24.110307+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.authenticate (/opt/novell/umc/apps/umc-server/main.js:1:29225)
2025-01-29T15:44:24.110387+01:00 oesserver bash[7970]:     at async LocalStrategy.callback [as _verify] (/opt/novell/umc/apps/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:11:44)
2025-01-29T15:44:24.110495+01:00 oesserver bash[7970]: In start readCommonProxyCreds
2025-01-29T15:44:24.239746+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : info : LdapProxyService::login:Entered Ldap Proxy service login method with dn = cn=OESCommonProxy_oesserver,ou=adm,o=myou
2025-01-29T15:44:24.251055+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapProxyService::login:Proxy login failed
2025-01-29T15:44:24.251141+01:00 oesserver bash[7970]:  HttpException: Exception while executing edir API login: connect ECONNREFUSED my-ip:9010
2025-01-29T15:44:24.251180+01:00 oesserver bash[7970]:     at t.edirLogin (/opt/novell/umc/apps/umc-server/main.js:1:14912)
2025-01-29T15:44:24.251216+01:00 oesserver bash[7970]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-01-29T15:44:24.251258+01:00 oesserver bash[7970]:     at async LdapProxyService.login (/opt/novell/umc/apps/umc-server/main.js:1:37075)
2025-01-29T15:44:24.251292+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29497)
2025-01-29T15:44:24.251324+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.tryUserLoginUsingUsername (/opt/novell/umc/apps/umc-server/main.js:1:29957)
2025-01-29T15:44:24.251357+01:00 oesserver bash[7970]:     at async LdapAuthenticationService.authenticate (/opt/novell/umc/apps/umc-server/main.js:1:29225)
2025-01-29T15:44:24.251389+01:00 oesserver bash[7970]:     at async LocalStrategy.callback [as _verify] (/opt/novell/umc/apps/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:11:44)
2025-01-29T15:44:24.251435+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : LdapAuthenticationService::tryUserLoginUsingUsername:Exception while login with edir credential
2025-01-29T15:44:24.251481+01:00 oesserver bash[7970]:  undefined
2025-01-29T15:44:24.257168+01:00 oesserver bash[7970]: [ 2025-01-29T15:44:24+01:00 ] : error : Exception thrown: {"response":"Exception while login with edir credential","status":401,"message":"Exception while login with edir credential","na
me":"HttpException"}

Please do not comment on what is not yet possible. I just want to know if there are similar entries in the logs.

I have found other things that should be discussed elsewhere. What I can say here is about iManager and OES services that are buggy or based on deprecated configurations at startup. Otherwise I can say that the dev team has done a good job here. Thanks to the Dev Team. I will try to give the dev team my results with your feedback to get a solution.

Greetings George

Hi George,

Yes, we see the missing edirapi container errors after upgrading from 24.4 to 25.1 on our test server. This is our first foray into trying to install umc and we've just about managed to be able to log in to it but it doesn't seem to be very "useful" maybe because of the missing components from the install.

Mark.

Hi George,

Yes, we see the missing edirapi container errors after upgrading from 24.4 to 25.1 on our test server. This is our first foray into trying to install umc and we've just about managed to be able to log in to it but it doesn't seem to be very "useful" maybe because of the missing components from the install.

Mark.

There is a workaround in the installations I maintain for the situation where UMC or IC cause problems.

Girish (OT) has written a lot about UMC troubleshooting in the forum and has given well-founded presentations in webinars.

The umcServiceHealth tool is the key to this. In the case above, an error is displayed during the Docker check for the IC container is displayed.

If there are no other errors, run systemctl stop docker-ic.service and then restart with systemctl start docker-ic.service. Use the umcServiceHealth tool again to see possible further errors. In the IC console you have to log in with CN=user,o=ou.

Unfortunately, I don't have much time in the next few days to look into the topic in depth.