Service not starting

[JK]

Dear Team

i installed OpenIAM on Centos 7 with
16GB Ram
200GB HDD and 4 cpu

After installation when I am trying to start the openiam service I am getting the below error.

“service openiam start”
“Failed to start openiam.service: Unit not found”

MariaDB services are up and running.and installation completed without any errors.

• This topic was modified 2 months ago by JK.

Attachments:

You must be logged in to view attached files.

[suneet_shah]

Hi Jayesh,

Are you following the documentation here? https://docs.openiam.com/docs-4.2.0.7/installation/1-rpm-installation/1-singlenode

Please use the openiam-cli instead of the “service” to start the application.
You will first need to do:

openiam-cli init

then you can use
openiam-cli status
openiam-cli start
openiam-cli stop

[JK]

Dear Suneet,

I followed the document and re-installed the OpenIAM with Centos 7.9 and getting the below error after installation

Attachments:

You must be logged in to view attached files.

[JK]

Tried to manually start the service but still getting same error

[suneet_shah]

Hi Jayesh,

How did you try manually? Please use the scripts which have been provided.

for the containers which are showing a warning, how long did you wait? It should take about 12-15 min depending on your environment for it to start up.

Also, did you increase your system resources as noted in the other message?

[JK]

Dear Sunnet,
I manually run the below commands for all the Openiam services and still warning error. waitied for 24 hours and still same error

systemctl enable openiam-esb
systemctl start openiam-esb

when running manually for workflow I am getting the below error

[root@iam-nonprod ~]# systemctl start workflow
Failed to start workflow.service: Unit not found

Attachments:

You must be logged in to view attached files.

[JK]

Dear Suneet,

The system is online now. All the services are started…But default login password not taking

Username: sysadmin
Password: passwd00

After trying 3 times now getting account locked out error.

I am using different password for Root

[suneet_shah]

Hi Jayesh,

You can find details to unlock the account here
https://docs.openiam.com/docs-4.2.0.7/installation/2-docker-installation/3-faq-docker

The last two digits are zeros.

Can you check the esb logs to see if there any errors being thrown?

[JK]

Dear Suneet,

We reinstalled the Openiam with

OS: EL8 – OpenIAM Identity and Access Manager CE via RPM 4.2.07 RHEL 8.x/CentOS 8.x
RAM: 32GB
CPU: 8
HDD: 200GB

after successful installation we waited for more than 1 hour for the service up.But still the same warning we are getting.

Openiam Status report Thu Jun 10 12:36:06 +04 2021
[WARNING] – openiam-esb – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[WARNING] – workflow – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[WARNING] – groovy-manager – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[WARNING] – idm – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[OK] – reconciliation – Service working. Application status: [ DOWN ]
[WARNING] – email-manager – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[WARNING] – auth-manager – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[OK] – synchronization – Service working. Application status: [ UP ]
[OK] – device-manager – Service working. Application status: [ UP ]
[OK] – openiam-ui – Service working. Application status: [ 500 ]
[root@iam-nonprod ~]#

Attachments:

You must be logged in to view attached files.

[JK]

Still Services are in warning state….

[JK]

Any idea?

[JK]

3 days completed Still service in warning state. What will be the issue??..

Openiam Status report Sun Jun 13 15:52:17 +04 2021
[WARNING] – openiam-esb – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[OK] – workflow – Service working. Application status: [ UP ]
[OK] – groovy-manager – Service working. Application status: [ UP ]
[WARNING] – idm – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[OK] – reconciliation – Service working. Application status: [ UP ]
[WARNING] – email-manager – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[WARNING] – auth-manager – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes
[OK] – synchronization – Service working. Application status: [ UP ]
[OK] – device-manager – Service working. Application status: [ UP ]
parse error: Invalid numeric literal at line 1, column 10
[WARNING] – openiam-ui – Service working, but Application status: [ DOWN ]. Probably it’s still starting. Please check again in few minutes

• This reply was modified 1 month, 2 weeks ago by JK.

[suneet_shah]

You shouldnt have to wait 1 hour for the services to come up. Normal time is between 10-15 min depending on the environment. The screenshot ofthe services not does not help. Can you post your logs form the ESB? Can you check if the RabbitMQ, Redis and Elasticsearch are running?

[JK]

Dear Suneet,

After reinstalling openiam with RHEL8 this service issue has been resolved.

But when we are trying to configure AD connector using below details its unable to connect

Connector name : AD connector
RabbitMQ host: FQDN of Openiam server
Username: openiam
password: default
Port : 5672

Via web browser i can able to login to RabbotMQ using port number 15672

[JK]

Dear Sunnet,

Ignore the previous post..

After successful installation of AD connector (Connection testing also completed successfully) when i am checking the managed systems its showing
“AD Powershell Managed System No active connectors found ”

[Author]

Posts