- My View
This happened to me today.
I just submitted the startup script again and it seemed to just check for the existing tables, instead of recreating them. I'm on a lab machine so I just gave it a try.
I had also configured the run levels.
I don't think there is workaround as your node is not coming up. Try check application server log and find out what cause the node not coming up. I expect some errors or exception in application server log can help to narrow down the scope of troubleshooting.
I encountered the same thing during a self-hosed install of ServiceNow, and also here, running the ./startup.sh works as a workaround. The application server logs does not point me in any direction either.
The installation guide even says "Reboot the server to ensure that all services activate automatically." But it does not give any tips with regards to what to do when the services do not start…
Any suggestions for a permanent fix? Is it considered bad practice to add startup.sh to the Linux server startup file?
We must have the same version of the installation guide. haha
I had to give up trying to config the run levels after a couple days. But hope to come back to it.
I think adding startup.sh to the Linux server startup file should be fine. I was going to give that a try as well. When I get back to it.