Home › Forums › Installation › Service not starting
Tagged: Openiam Installation
- This topic has 16 replies, 2 voices, and was last updated 11 months, 1 week ago by
JK.
-
AuthorPosts
-
June 1, 2021 at 4:30 am #2150
JK
ParticipantDear Team
i installed OpenIAM on Centos 7 with
16GB Ram
200GB HDD and 4 cpuAfter 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 11 months, 3 weeks ago by
JK.
Attachments:
You must be logged in to view attached files.June 2, 2021 at 5:58 am #2156suneet_shah
KeymasterHi 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 stopJune 2, 2021 at 6:09 am #2158JK
ParticipantDear 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.June 2, 2021 at 6:09 am #2160JK
ParticipantTried to manually start the service but still getting same error
June 2, 2021 at 7:58 pm #2161suneet_shah
KeymasterHi 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?
June 2, 2021 at 9:34 pm #2162JK
ParticipantDear Sunnet,
I manually run the below commands for all the Openiam services and still warning error. waitied for 24 hours and still same errorsystemctl enable openiam-esb
systemctl start openiam-esbwhen running manually for workflow I am getting the below error
[root@iam-nonprod ~]# systemctl start workflow
Failed to start workflow.service: Unit not foundAttachments:
You must be logged in to view attached files.June 3, 2021 at 2:15 am #2164JK
ParticipantDear Suneet,
The system is online now. All the services are started…But default login password not taking
Username: sysadmin
Password: passwd00After trying 3 times now getting account locked out error.
I am using different password for Root
June 3, 2021 at 2:06 pm #2165suneet_shah
KeymasterHi 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-dockerThe last two digits are zeros.
Can you check the esb logs to see if there any errors being thrown?
June 10, 2021 at 1:38 am #2194JK
ParticipantDear 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: 200GBafter 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.June 10, 2021 at 3:45 am #2198JK
ParticipantStill Services are in warning state….
June 12, 2021 at 9:15 pm #2216JK
ParticipantAny idea?
June 13, 2021 at 4:54 am #2217JK
Participant3 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 11 months, 2 weeks ago by
JK.
June 13, 2021 at 1:47 pm #2219suneet_shah
KeymasterYou 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?
June 14, 2021 at 10:33 pm #2225JK
ParticipantDear 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 : 5672Via web browser i can able to login to RabbotMQ using port number 15672
June 14, 2021 at 11:01 pm #2226JK
ParticipantDear 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 ” -
This topic was modified 11 months, 3 weeks ago by
-
AuthorPosts
- You must be logged in to reply to this topic.