Hi Itregistrations:
The lines depicted are not actual "debugs" as if something had been turned on, they're actually messages thrown to the console by the Linux daemon whose name is "debugd" or debug daemon, that's watching what's going on as the Prime Infrastructure service starts up. They're not helpful at all in diagnosing a problem, but they will stay on screen a long, long time while the service is in the process of starting. Once it does completely start, a login prompt should appear.
What is helpful is connecting to an SSH session, checking the output of "ncs status" to know which of the listed services are running or stopped.
Also, a set of logs generated by running the command "backup-logs repository " is helpful. Logs always help, particularly the hm-0-0.log file that tells what the "mother hen" Health Monitor service encounters as it tries to start up all the subservices. Depending on which subservice is having trouble, the log of that subservice would be the next source of help. For example, if Health Monitor tells the database server to start, but the database server doesn't, one would want to check the dbadmin-0-0.log to see why the database server disobeyed Health Monitor.
