Skip to main content

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure”

I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps.

  • Remove all relevant namespace files from data-file route path..
  • Now repair mongo instance using mongod process.
    • mongod --repair ////////// execute command from bin folder path
  •  Then start server using mongd process, if started server successfully then ..
    • mongod  ////////// execute command from bin folder path
  • Restore last backups as normal process.
  • Now check database by connecting mongo shell.
Thanks for reading, 
Please comment your experience if you faced and also share knowledge if you have better steps to resolve...


https://www.facebook.com/pages/Sql-DBAcoin/523110684456757 

Comments

  1. Anonymous17 July 2015 at 03:07

    Nice

    ReplyDelete
  2. Anonymous19 December 2015 at 21:37

    Remove all relevant namespace files from data-file route path--how remove name space file from data directory .can you please tell . presently i struck with the same issue .

    thanks

    ReplyDelete
    Replies
    1. Suman kumar 22 December 2015 at 20:42

      hi remove the lock file manually from route path re-start the mongod instance.

      Delete
  3. Kayal28 March 2019 at 00:26

    This blog provides many kinds of ideas, This is very helpful for my development and Thank you!!!
    Tableau Training in Chennai
    Tableau Course in Chennai
    Embedded System Course Chennai
    Linux Training in Chennai
    Social Media Marketing Courses in Chennai
    Pega Training in Chennai
    Excel Training in Chennai
    Tableau Training in Chennai
    Tableau Course in Chennai

    ReplyDelete
  4. GIEC Global - Best Migration Agent Melbourne & Education Consultant in Melbourne, Australia4 July 2021 at 23:14

    It's a great blog, I really liked it and will love to read your upcoming blogs.
    Thank you.
    GIEC Global ( Best Migration Agency Melbourne & Canada)
    https://giecglobal.com.au/

    ReplyDelete

Post a Comment

Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...
34 comments
Read more

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription 
29 comments
Read more

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.
28 comments
Read more