check

lsof -i:5432
COMMAND    PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
postgres 15191 postgres    6u  IPv4  97870      0t0  TCP *:postgresql (LISTEN)

and

python3 umc-config.py get_config

Hi BM2EC ,

We have tested this and did not see the issue during release time.

DB Name is calculated and read from the prod.env from umc and populated on the yast screen. The name is not active so the DB name can not be changed.

Can I get the y2logs for further debugging so we can help resolve the issue?

Can you provide me the email ID so I can contact you and get the logs for debugging?

Regards,

Gaurav

Hi Gaurav,

is there a documentation which parts are needed to have umc and identityconsole running on OES24.4? (Repos; Pattern, Packets, docker-images, ...) and how there are started?

I have a fresh installed OES24.4. it seems that there UMC and identityconsole are setup and running. But I have some upgraded hosts (OES23.4 -> OES24.4 via offline in place upgrade) were the whole UMC/identityconsole is struggling.

And how is the naming of the components? It looks like sometimes there is a edirapi wich uses port 9010, but at the other hand identityconsole uses this port.

Is there a sketch how this components works together?

Hello BM2EC, hello Gurav,

when migrating to OES 24.4 I have similar problems as owed here in the post. In the docs / readme and webcast there are possible solutions or to-do's on what to do.

One thing I have observed is that although there was no IC Console on the source systems that UMC starts after a migration but the IC does not allow login. Here, too, there are instructions from OT that do not provide a solution. My analysis of the docker showed that certificates cannot be loaded because paths in the start scripts for UMC / IC may be incomplete

My analysis

/opt/novell/umc/scripts # python3.6 umc-config.py get_config

 docker exec -it identityconsole-oes sh

umcServiceHealth with appropriate parameters or fix

then later reconfigure with /opt/novell/umc/scripts/ic-configure.sh

but first please delete the docker container regarding IC

What also always helps me is docker inspect container id

The IC can also be “hooked” back into the UMC at a later date

here once with error because container exists.

./ic-configure.sh
identityconsole.tar.gz
edirapi.conf
edirapi_osp.conf
osp.tar.gz
Identityconsole_Bundle_License.txt
osp-edirapi-silent.properties
Loaded image: identityconsole:1.8.0.0000
Error response from daemon: Conflict. The container name “/identityconsole-oes” is already in use by container “b5f05b42d6c3c2a868937634494202fd45ac2865d946c072d2899c0d8c523269”. You have to remove (or rename) that container to be able to reuse that name.
Successfully copied 6.66kB to identityconsole-oes:/etc/opt/novell/eDirAPI/cert/keys.pfx
Successfully copied 3.58kB to identityconsole-oes:/etc/opt/novell/eDirAPI/cert/SSCert.pem
Successfully copied 2.05kB to identityconsole-oes:/etc/opt/novell/eDirAPI/conf/edirapi.conf
identityconsole-oes
Warning: ALREADY_ENABLED: 9010:tcpsuccess

there is something else I don't understand

pluto:/ # docker image list
REPOSITORY TAG IMAGE ID CREATED SIZE
identityconsole 1.8.0.0000 fe20f909a5ea 5 months ago 380MB
edirapi 1.7.0.0000 eda50e33af60 19 months ago 225MB
edirapi 1.5.0.0000 50a96d0ab987 2 years ago 476MB

After the migration, the “old” docker image for the UMC remains. I cannot yet say to what extent this is an issue.

One thing I have seen directly in psql that the remote db connection from another OES sometimes fails. Again, just the first observation please.

Unfortunately, I don't have the time to get to the bottom of the issue, but I would find the problem.

George

George