Hi stelgenkamp ,

Make sure ndsd is up and running, you can check ndsd.service

Related to the UMC login issue can you run the UMC health script and check all the UMC dependencies are fulfilled,  you can run - "umcServiceHealth -a"

You can provide/check the logs in /var/opt/novell/log/umc/apps/umc-server/* for umc-related errors or info logs

Did not know the UMC had its own health script.

running the command gave 2 errors :

- umcConfig Object is missing in the tree

- Table "report" is not present in DB ; Create the missing table by running umcservicehealth -dautofix

Now the Table error is fixed. But the UMC object is still missing, re-run the YAST OES task, and reconfigured the UMC,

but still shows as missing.

i don't known this command umcServiceHealth -a

But i have the problem that after each reboot from this oes24.1.1 server, i must reconfigure umc with the command "yast umc", that i can login in the umc console.

Since long time (4 month) a case is open for this at the support portal, also many others without help

I run this command on my server and this give 6 errors:

1. ERROR: DB "umc" is not present in postgres.

2. ERROR: Table "umc_login_sessions" is not present in DB.

3. ERROR: Table "action" is not present in DB.

4. ERROR: Table "tree" is not present in DB.

5. ERROR: Table "user_profile" is not present in DB.

6. ERROR: Table "report" is not present in DB.

DB Check 6 Issue Found

DB Check 1 Warning Found

On a other oes24.1.1 server, i don't have to reconfigure umc after reboot this command found

Service Check 2 Issue Found

EdirApi Check 2 Issue Found

1. postgresql.service is inactive
ERROR: postgresql is in inactive state. Make sure service is up and running by e  

2. ERROR: edirapi-container is not running

nc: connect to 192.168.13.96 port 9010 (tcp) failed: Connection refused
ERROR: edirapi port 192.168.13.96:9010 is not opened in firewall

why is this command not known from the support?

hope that this solved now my trouble by rebooting the server!

Thank for publishing this possibility!

Check out this KB item : portal.microfocus.com/.../KM000013619

Changed /etc/sysconfig/novell/umc SERVICE_CONFIGURED to "no",so the UMC configuration will do a full reconfiguration

Did a full reconfiguration. Now it reports an error with the LDAP connection ldap_sasl_bind(SIMPLE)  can't contact LDAP server.

To be continued.

this hat solved my trouble!
Thanks

Hi Greiner Claude ,

If you are on OES 24.1.1 and facing db and other umc configuration-related issues.

can you do a cleanup of UMC and reconfigure UMC? you can follow  Re-configuration/Cleanup of UMC on OES 

Let me know this resolve the issue or not

Hi stelgenkamp 

umcHealth script will do ldapsearch to get the the object details, if that is giving error.

You can check through identity console or imanager  that cn=umcConfig,cn=Security obect is created and it has umcJwkUrl entry set with value

Once object is created and no db issue is found, you can proceed with login.

Let me know if this helps

Hi Gaurav, i don't work with identity console! What is the latest version? 1.7.2 What is the best installation on a oes24.1.1 server (docker or standalone linux or workstation on windows?

I don't have any experience with IC! I work with the latest imanager version 3.2.6

But i could solved my trouble with this:

Changed /etc/sysconfig/novell/umc SERVICE_CONFIGURED to "no", so the UMC configuration will do a full reconfiguration with yast umc

After this, umcServiceHealth -a don't have any trouble!

But i had hear, that this can be recome by next server reboot, i must take a look for this!

Same steps in imanager -

• Delete the umcConfig Object under Security in iManager
• Then Goto Schema Role and Task > Select Delete Class > Delete umcConfig class
• Then Select Delete Attribute > Delete umcJwkUrl and umcOspJwkUrl
• Set SERVICE_CONFIGURED="no" in /etc/sysconfig/novell/umc
• Retry UMC Configuration by running > yast2 umc