Cisco Prime NCS Install

Unanswered Question
Aug 15th, 2011

Hi,

I am trying to play around with NCS.

I have ESXi box (4.1 and 5) and have tried using both ver 1.0 and 1.1 of the appliance.

The error i get on boot up is

Failure during Network Control System startup. Check launchout.log for details

How can i check that logfie?

I have this problem too.
2 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
ajaparih Wed, 08/24/2011 - 03:46

do u have the required space & memory--if after installation its giving this error then that might be the case.

craig.eyre Tue, 11/22/2011 - 06:49

Ben,

Any luck with your failure to start? We are seeing the same issue right now and cannot figure it out.

Thanks

Craig

Ben_Skinner_2 Tue, 11/22/2011 - 07:20

Yep, my VM was not up to spec, gave it more ram and cpu and it was happy once again

craig.eyre Tue, 11/22/2011 - 07:26

Thanks Ben,

Can you tell me what your specs are for your VM? I tried installing it on a dual processor, 4GB ram, 100GB vm with 4.1 esxi+

Thanks again,

Craig

Ben_Skinner_2 Tue, 11/22/2011 - 07:29

I kind of went over kill on it and gave it 52 gig of ram and 8 cores.

i woud say its the ram, it didnt like my orginal 8gb ram and dual core

cslack1313 Wed, 02/01/2012 - 13:21

Is there another fix for this issue? I have more then the required amount of RAM and CPU, 12GB RAM and 4 CPUs in an ESXi 4.1 environment.. Still get the error "Failure during Network Control System startup. check launchout.log for details"

Also how do you check that log file?

Thomas Boettcher Tue, 02/14/2012 - 04:29

Hi,

same problem here.

after problems during upgrade from ncs 1.0 to 1.1 the system (VA) does not start anymore. Where can we check the mentioned "launchout.log" file?

Thanks for any help.

craig.eyre Tue, 02/14/2012 - 08:49

Hey All,

Of course I forgot to write it down or wrote it down in the wrong spot :>)

If I remember correctly my issue was the command I used to import my data from the WCS into the NCS. I missed the ending of the command but still looked as though the import worked but it didn't and I got the same error failure during startup.

If I find the exact command I will post it.

Craig

Thomas Boettcher Thu, 02/16/2012 - 03:25

hi,

after all I found the command

"copy logs "

It generates a file "ADElogs.tar.gz" which also does not(!) contain a "launchout.log". :-(

By now, our NCS is unstartable. Our Supporter is going to rehost the NCS License to a new VA.

With this expierience I can recommend to take snapshots from the VA especially before trying to upgrade.

good luck everyone else.

Thomas Boettcher Fri, 02/17/2012 - 05:42

hi,

to whom it may concern:

"backup-logs NCS repository "

produces an tar.gz-archive wherein the launchout.log can be found.

hope that helps someone.

fgunawan Tue, 04/24/2012 - 23:16

Have you check that maybe it is the symptom of this caveat: CSCto13373?

The "ncs start" command on a running NCS reports an incorrect message.

Symptom: The "ncs start" command on an already running NCS reports an incorrect message.

Conditions: NCS 1.0.2.29

Workaround: If NCS is already running and if you enter the command "ncs start", it would report the following message. ncs-lab/admin# ncs start Starting Network Control System... This may take a few minutes... Health Monitor is already running. Failure during Network Control System startup. Check launchout.log for details. ncs-lab/admin#

From :

http://www.cisco.com/en/US/docs/wireless/ncs/1.1/release/notes/NCS_RN1.1.html

thefranmanatt Tue, 09/04/2012 - 17:52

you can't use the copy command, you have to use the backup command

example "backup-logs mybackup repository myrepository"

You can also download them from the web gui under the logging, once it is up.

choikyujin Mon, 01/07/2013 - 05:23

I tried Prime Infrastructure 1.2 which has NCS 1.2.0.103. (I tried 1.2.1.012, it shows same an issue)

I got same error like below.

riwakefi Mon, 01/28/2013 - 14:42

NCS Error -->  "Failure during Network Control System startup.  Check launchout.log for details." 

Checking in launchout.log, it says

"Start failed. Initiating shutdown. Please check logs/Startup.log"

There is no logs/Startup.log in the backup-logs dump.

mkilic Fri, 06/21/2013 - 02:20

I have same error.

Failure during Network Control System startup.  Check launchout.log for details.

rafael.libanio.sp Mon, 07/01/2013 - 10:48

Dear,

follows this procedure to be performed. I tested it and it worked.

=================================================================

1.> Please try these commands then try to start
 
the ncs:
 
ncs stop ( 3 times)
reload.
 
ncs status ( email me the o/p)
 
2.> If the #1 does not helps  please run 
 
ncs cleanup
 
3> Note: If the above does not help, and only if *** this is new install ***, it might
be ok to re-init the DB ( use your own judgement )
 
Note: NCS DB you will loose previous data when you re-init. but if this DB corrupt issue
may help.
 
the ncs:
 
ncs stop
 
ncs db reinitdb
 
ncs start

=================================================================

Hugs.

Craiglebutt_2 Thu, 10/10/2013 - 01:07

Hi

Did you problem heve get sorted?  I'm having the same issue, looked at launchlog, which says check startup.log which seems to be da."startup.log"

I've found some errors, but can't find anywhere to check these against.

anyone have any ideas, don't realy want to reonotdb.

cheers

relder@hoho.org Fri, 12/13/2013 - 13:17

Just happened to me.  I am running version 1.3.0.20.

I already did a NCS CLEANUP, and it finished sucesfully, but unable to start it.  It looks like I have enough space..

I have 30,293,413,888 byes available.  So i don't think it is a disk space issue.  The device was working good till today.

Thanks!

Edit - I did reboot it as well.  Nothing.

Actions

Login or Register to take actions

This Discussion

Posted August 15, 2011 at 6:52 AM
Stats:
Replies:18 Avg. Rating:
Views:9061 Votes:2
Shares:0
Tags: No tags.

Discussions Leaderboard