cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
657
Views
1
Helpful
5
Replies

FMC "mongo terminated unexpected" notification and it be disk full

hi

i use FMC 6.4.0.4 (vm ) for 2 FTD Cluster (6.2.3) afew days ago i took some alarm in fmc "mongo terminated unexpected " and i recognized it be create file every 5 minutes in /var/opt/lamplighter/data/journal/ that cause my FMC disk be full . at last these files cause my FMC disk be full and i cannot login to fmc . and i have to remove these logs with CLI every day so that disk will be not full. if you have any solution for solving that please tell me . if not , i thinnk i have to move to my last clone of FMC .

1-i have a clone of this FMC but it is for 5 month ago and it is not diffrent with this FMC version insted of some Access control rules and some SRU/VDB update , can i use it ? i mean i turn off this FMC and turn on that ?

2-in this FMC i have backup (system > tools >backup) and take export config file (system > tools > export ) ... if i use my old FMC (Clone ) can i use these backup (export and configuration)  configuration ? i have many rules in my Access Control Policy that After changing FMC , they should not change do you have the better solution for my problem ?

thanks

1 Accepted Solution

Accepted Solutions

You can export your ACP from the failing FMC and import into the clone if they are the same FMC version.

View solution in original post

5 Replies 5

marce1000
VIP
VIP

 

      - Check content of /var/log/mongodb/mongod.log

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

thanks marce , but i didnt  have mongodb directory  in /var/log .

Marvin Rhoads
Hall of Fame
Hall of Fame

You can only restore an old FMC backup onto a system with the same version and VDB. If you meet those requirements, you should be able to use the clone.

In the longer term you should really plan to get on to a current supported version. You are running many releases behind what is current and supported.

you are right
i must switch to high version of FTD and FMC . unfortunately we didnt have higher version of ESXI . after upgrade them we will switch to current supported version of FTD
i dont sure of old clone vdb version , what happen if i start old clone with diffrent vdb version ?
if i will start old clone (FMC) , how i restore my ACP policy ( because i had many new rules after clone and i have exported ACPs of latest FMC ) ? can i import from system > tools > import , is it true ?

You can export your ACP from the failing FMC and import into the clone if they are the same FMC version.

Review Cisco Networking for a $25 gift card