Problems with starting up On-Premise Application Node

mkorneliussen
Tera Contributor

‎03-04-2025 04:43 AM - edited ‎03-04-2025 04:51 AM

Im having trouble starting up my first application node on Washington DC Patch 6 and RHEL8.10.

 

When I'm starting up the systemctl service it starts up and runs for 1 minute and then shuts down.

 

I have the correct SELinux permissions and servicenow owns the files in /glide/nodes. I have also turned off FIPS.

 

Has anyone seen this error before?

 

Thanks in advance for help 🙂

 

mkorneliussen_0-1741092680241.png

 

0 Helpfuls
  • 545 Views
3 REPLIES 3

Dr Atul G- LNG
Tera Patron
Tera Patron

‎03-04-2025 04:50 AM

Hi @mkorneliussen 

 

Best to log now support case with team.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************
0 Helpfuls

Bert_c1
Kilo Patron

‎03-04-2025 07:31 AM - edited ‎03-04-2025 07:35 AM

The Support team do not have access to self-hosted instances. See the following for related documentation:

 

guide-to-installing-servicenow-on-premise

 

A PDF containing much the same info: self-hosted-software-guide.pdf

 

Found using google search, Good luck.

satyavrataanand
Tera Contributor

4 weeks ago

Hi MK,

 

Did you manage to get the resolution? Would you like to share any details to us?

0 Helpfuls