cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
31578
Views
82
Helpful
6
Replies

respawning too fast disabled for 5 minutes Cisco FMC

faiqmahdi
Level 1
Level 1

Hello Team 

 

Cisco FMC Version: 

Cisco_Firepower_Management_Center_Virtual_VMware-6.2.3-83.tar.gz

 

VMware ESXi Version:

6.5.0 Update 1 (Build 5969303)

 

We are trying to install Cisco FMC but we receive the attached error after successful installation and implementation 

 

Has anyone encountered this problem? any resolution? 

 

 

1 Accepted Solution

Accepted Solutions

jimholla
Cisco Employee
Cisco Employee

Symptoms:

One of the following error messages are seen on the console of VMware FMC/FTD/NGIPS running on ESXI 6 and 6.5.

“INIT:  Id  "s1" respawning too fast:  disabled for 5 minutes”

or

“INIT:  Id  "ftd1" respawning too fast:  disabled for 5 minutes”

 

Fix:

  1. Edit the settings of the virtual device in VSphere while powered off.
  2. Select “Serial Port” from the “New device” drop down and click add.
  3. Select “Use physical serial port”
  4. Uncheck the “Connect At Power On” checkbox.
  5. Click OK to save settings.

View solution in original post

6 Replies 6

jimholla
Cisco Employee
Cisco Employee

Symptoms:

One of the following error messages are seen on the console of VMware FMC/FTD/NGIPS running on ESXI 6 and 6.5.

“INIT:  Id  "s1" respawning too fast:  disabled for 5 minutes”

or

“INIT:  Id  "ftd1" respawning too fast:  disabled for 5 minutes”

 

Fix:

  1. Edit the settings of the virtual device in VSphere while powered off.
  2. Select “Serial Port” from the “New device” drop down and click add.
  3. Select “Use physical serial port”
  4. Uncheck the “Connect At Power On” checkbox.
  5. Click OK to save settings.

Thank you very much for your support the suggested solution worked perfectly.  FMC is working perfectly since morning without any issue otherwise, it starts giving the error after the installation.  

Although FMC is working fine I get an error in VM settings page: 


The configured guest OS (Other 2.6.x Linux (64-bit)) for this virtual machine does not match the guest that is currently running (Other 3.x or later Linux (64-bit)). You should specify the correct guest OS to allow for guest-specific optimizations.

 

is this something I need to worry? I am also attaching the screenshot for your reference. 

 

Regards

 

If you map the serial port to the physical serial port the VMware DRS and vMotion will stop working for the specified VM. So I'll keep the message and have VMware vMotion working.

Since the Physical Serial Port is not actually connected to the VM by the fourth step;

4.Uncheck the “Connect At Power On” checkbox.

vMotion and DRS are not affected for the VM. I've performed the Accepted fix in this article and verified that I can still freely move the VM from ESXi Host to Host without any issues.

Same thing happened to me going from 6.2.x > 6.3.0 - FMC on VMware ESX 6.5u1

 

Add the serial port > uncheck connect > power on vm.

Still occurred on 7.2.2:
- workaround: vi /etc/inittab --> (as >expert --> root#) find line: #s1:2345:respawn:/sbin/agetty -L 9600 ttyS0 vt100
#... and SET DISABLED !
Maybe will be overwritten by next update.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: