14 Replies Latest reply on Dec 27, 2012 1:20 PM by mark.stuller

    FileMaker Server Advanced Crashed

    mihalych_2012

      Process: fmserverd [178]

      Path: /Library/FileMaker Server/Database Server/bin/fmserverd

      Identifier: fmserverd

      Version: ??? (???)

      Code Type: X86 (Native)

      Parent Process: launchd [1]

       

      Date/Time: 2012-12-26 10:53:01.486 +0300

      OS Version: Mac OS X 10.6.8 (10K549)

      Report Version: 6

       

      Exception Type: EXC_BAD_ACCESS (SIGBUS)

      Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004

      Crashed Thread: 32

       

       

      Thread 32 Crashed:

      0 ...ilemaker.dbengine.framework 0x005521ab Draco::DBQueryProgram::LocalProjection(Draco::DBFileUser const*, Draco::DBCursor const&, short, std::vector<Draco::DBFieldSpec, std::allocator<Draco::DBFieldSpec> > const&, std::vector<Draco::DBJoinFieldInfo, std::allocator<Draco::DBJoinFieldInfo> > const&, Draco::HBPosition&, Draco::HBAbstractKey const&) + 427

      1 ...ilemaker.dbengine.framework 0x00549644 Draco::DBQuery::PerformJoin(Draco::DBRelatedSet&, Draco::DBTableAlias const&, Draco::DBTableAlias const&) + 4772

      2 ...ilemaker.dbengine.framework 0x0054a326 Draco::DBQuery::PerformJoin(Draco::DBRelatedSet&) + 646

      3 ...ilemaker.dbengine.framework 0x005650a8 Draco::DBRelatedSet::Setup(Draco::DBSortSpec const*, Draco::DBCalcFormula const*, bool) + 904

      4 ...ilemaker.dbengine.framework 0x005659ce Draco::DBRelatedSetPtr::Reset(Draco::DBCursor const&, Draco::HBSerialKey<(unsigned char)5> const&, Draco::DBSortSpec const*, Draco::DBCalcFormula const*, short) + 1166

      5 ...ilemaker.dbengine.framework 0x0049ea60 Draco::DBRecordCursor::GetData(Draco::DBData&, Draco::DBFieldSpec const&, Draco::DBField const&, unsigned long, unsigned short) const + 848

      6 ...ilemaker.dbengine.framework 0x0046655c Draco::DBCalcSolver::SolveField(unsigned short const&, bool&, bool&, unsigned short) + 508

      7 ...ilemaker.dbengine.framework 0x0047bb55 Draco::DBCalcSolver::SolvePolish(Draco::DBDataArg&, unsigned short) + 8885

      8 ...ilemaker.dbengine.framework 0x00430f4f Draco::DBCalcFormula::Solve(Draco::DBData&, Draco::DBCursor const*, Draco::DBCursor const*, Draco::DBData const*, Draco::DBFieldSpec const*, Draco::DBField const*, unsigned short) const + 751

      9 ...ilemaker.dbengine.framework 0x0043112c Draco::DBCalcFormula::Solve(Draco::DBData&, Draco::DBCursor const&, Draco::DBFieldSpec const&, Draco::DBField const&, Draco::DBCursor const*) const + 76

      10 ...ilemaker.dbengine.framework 0x00495129 Draco::DBRecordCursor::GetCalculatedData(Draco::DBData&, Draco::DBFieldSpec const&, Draco::DBField const&) const + 457

      11 ...ilemaker.dbengine.framework 0x0049ef3e Draco::DBRecordCursor::GetData(Draco::DBData&, Draco::DBFieldSpec const&, Draco::DBField const&, unsigned long, unsigned short) const + 2094

      12 ...ilemaker.dbengine.framework 0x005511f5 Draco::DBQueryProgram::LocalProjectRow(Draco::DBCursor const&, short, std::vector<Draco::DBFieldSpec, std::allocator<Draco::DBFieldSpec> > const&, std::vector<Draco::DBJoinFieldInfo, std::allocator<Draco::DBJoinFieldInfo> > const&, std::vector<Draco::DBField*, std::allocator<Draco::DBField*> > const&, Draco::DBData&, Draco::HBPosition&, Draco::HBSerialKey<(unsigned char)9> const&) + 725

      13 ...ilemaker.dbengine.framework 0x00551813 Draco::DBQueryProgram::LocalProjection(Draco::DBFileUser const*, std::vector<Draco::DBFieldSpec, std::allocator<Draco::DBFieldSpec> > const&, std::vector<Draco::DBJoinFieldInfo, std::allocator<Draco::DBJoinFieldInfo> > const&, Draco::HBSerialKey<(unsigned char)5> const&, Draco::DBRidList const&, Draco::HBPosition&, Draco::HBAbstractKey const&) + 563

      14 ...ilemaker.dbengine.framework 0x00551e84 Draco::DBQueryProgram::Projection(Draco::DBSession*, Draco::HBPosition&) + 1044

      15 ...ilemaker.dbengine.framework 0x00559b3e Draco::DBQueryProgram::Execute(Draco::DBSession*) + 2926

      16 ...ilemaker.dbengine.framework 0x0055a41a Draco::DBRemoteQueryProgram::PerformOperation() + 202

      17 ...ilemaker.dbengine.framework 0x003fb3cc Draco::RCUploadDownload::Perform() + 316

      18 ...ilemaker.dbengine.framework 0x00411fb2 Draco::RCNetworkStack::DispatchTransaction(Draco::RCConnection*, unsigned long, void*, unsigned long) + 498

      19 ...ilemaker.dbengine.framework 0x00412dac RPO_i::Perform(unsigned long, unsigned long, OctetSeq&, OctetSeq_out) + 188

      20 ...ilemaker.dbengine.framework 0x003fe021 _0RL_lcfn_E7F0BDFD3D523DDE_70000000(omniCallDescriptor*, omniServant*) + 145

      21 ...ilemaker.omniorb4.framework 0x010cb745 omniCallHandle::upcall(omniServant*, omniCallDescriptor&) + 165

      22 ...ilemaker.dbengine.framework 0x003ff8a5 _impl_RPO::_dispatch(omniCallHandle&) + 245

      23 ...ilemaker.omniorb4.framework 0x011a936f omni::omniOrbPOA::dispatch(omniCallHandle&, omniLocalIdentity*) + 643

      24 ...ilemaker.omniorb4.framework 0x011877eb omniLocalIdentity::dispatch(omniCallHandle&) + 109

      25 ...ilemaker.omniorb4.framework 0x01122791 omni::GIOP_S::handleRequest() + 307

      26 ...ilemaker.omniorb4.framework 0x01122e4b omni::GIOP_S::dispatcher() + 229

      27 ...ilemaker.omniorb4.framework 0x0113c9f2 omni::giopWorker::real_execute() + 1406

      28 ...ilemaker.omniorb4.framework 0x0113caaa omni::giopWorker::execute() + 50

      29 ...ilemaker.omniorb4.framework 0x01141f28 omniAsyncWorker::real_run() + 334

      30 ...ilemaker.dbengine.framework 0x00401c06 threadCreateInterceptor(omni::omniInterceptors::createThread_T::info_T&) + 22

      31 ...ilemaker.omniorb4.framework 0x01142134 omniAsyncWorker::run(void*) + 50

      32 ...ilemaker.omniorb4.framework 0x011bad0e omni_thread_wrapper + 160

      33 libSystem.B.dylib 0x9455f259 _pthread_start + 345

      34 libSystem.B.dylib 0x9455f0de thread_start + 34

        • 1. Re: FileMaker Server Advanced Crashed
          taylorsharpe

          I see you are running Mac OS X 10.6.8.  What version of FMS is this?  11?  12?  What else was going on?  Are you using IWP, CWP, ODBC?  Did this happen recently after a storm or power outage?  After it crashes, does it come back up or stay crashed?

           

          While we can give some suggestions, I find the best solution is to export your schedules/groups and then reinstall FMS.  It is the most likely thing to solving something like this. 

           

          BUT BEFORE doing anything, please backup your databases <grin>. 

           

          If you're going to reinstall FMS, you might even consider upgrading your OS from 10.6.8.  Yes, I don't like the Lion or Mountain Lion Server Admin's as well, but that is the direction things are going.  And if you are on a pre-FMS 12 server, you might consider upgrading to 12.  Just remember all of your clients have to be upgraded too. 

           

          As for the long strong of crash code above, that will only be useful to a FileMaker systems engineer.  I don't think us developers on Technet would ever be able to decipher the crash code.  But you will note that the first few lines talk about a Draco database and a join error, so it may have to do with a corrupted relationship or corrupted index causing the join to fail.  You might try a Recover on the Draco database as a suggestion. 

          • 2. Re: FileMaker Server Advanced Crashed
            SBerger

            As far as I know "Draco" is the name of FileMaker database engine.

            How can you recover it?

            • 3. Re: FileMaker Server Advanced Crashed
              taylorsharpe

              Download the File from Server or get a copy from the Server's backups folder.  Just don't copy a live open file from the server.  Put it in your documents folder or desktop.  Open FileMaker, go up to FILE and pull down to the last entry, RECOVER.  Navigate the menu to select the database and it will create a recovered version from the corrupted file.  It usually does a pretty good job.  Some people will tell you that this is just to export data from the new file and that once corrupt, you should never use a recovered file.  That is a very conservative approach and I've found most recovered files work just fine.  But pay close attention to them to make sure some corruption did not pass on to the recovered file. 

              • 4. Re: FileMaker Server Advanced Crashed
                mihalych_2012

                We use Filemaker Server 11 ADV. Also we use IWP and ODBC. We have produced the following: Replace the hard drive on the server, replaced the memory, reinstalled Filemaker Server. However, an error from time to time continue to occur. Can cause incorrect operation of a computer or some other external influence?

                • 5. Re: FileMaker Server Advanced Crashed
                  taylorsharpe

                  My only suggestion may be reinstalling the OS and making sure you are using a RAID drive to eliminate bad data bits.  Replacing the OS will reinstall Apache and PHP to make sure they are not corrupt.  Are there any other applications or services running?  Eliminating them would be a good way to trouble shoot and make sure this is a FileMaker only issue.  How much memory does the machine have? 

                  • 6. Re: FileMaker Server Advanced Crashed
                    mihalych_2012

                    Yes, yesterday before reinstalling Filemaker Server we format the hard drive, reinstall the operating system. Other tasks (except for Filemaker Server) on this computer is not being addressed. Memory - 8 GB. We use RAID drive.

                    • 7. Re: FileMaker Server Advanced Crashed
                      taylorsharpe

                      Well, it could be some strange hardware issue, but it seems like you've removed the most obvious hardware issues. 

                       

                      I would still suspect a possible OS problem and would probably try reinstalling the OS.  Or maybe just download and update it to 10.7.  I don't think FMS 11 is certified for 10.8, so I would not upgrade to Mountain Lion.  But Lion (10.7) would get the latest OS software for FMS 11v4. 

                       

                      Do you have any Server Side Plugins?  Have you tried running the server without those plugins if you have them?

                      • 8. Re: FileMaker Server Advanced Crashed
                        mihalych_2012

                        Yes, Filemaker Server 11 is certified to version 10.7. Plugins for Filemaker Server we have not loaded.

                        Can external users Filemaker Server somehow influence the system?

                        • 9. Re: FileMaker Server Advanced Crashed
                          taylorsharpe

                          I would not be worried about external FileMaker client connections.  But some FMP client connections could be maybe as old as FMP 7 and those may have a number of issues opening a FMS 11 database even though they can.  I would be more interested in whether you are having external ODBC connections.  They need to have the latest FileMaker ODBC driver on their system.  Also, you could have problems having the FileMaker Server connect to other databases via ODBC and you have to make sure to have a current Actual Technologies Server license ODBC driver.  To test if there are ODBC issues, turn off ODBC connections in the Admin Console and see if your problems go away. 

                           

                          I still would first do a system re-install before playing around with ODBC or IWP issues. 

                          • 10. Re: FileMaker Server Advanced Crashed
                            mihalych_2012

                            That was the question on the topic:

                            one of the databases on Filemaker Server is 8 GB and the amount of available memory about 7.4 GB (excluding the area of the operating system).

                            Can the Database Server fails because excess of the amount the database on the amount of RAM?

                            • 11. Re: FileMaker Server Advanced Crashed
                              SBerger

                              Maybe you did not pay close attention to what I wrote :

                               

                                 "Draco" is not a hosted file - it is the name of FileMaker Database Engine. Not a file, it's their internal name for the DB engine.

                              • 12. Re: FileMaker Server Advanced Crashed
                                gdurniak

                                File Size is limited only by Disk space

                                 

                                but anything is possible

                                 

                                We had a case once where the Motherboard was bad ...

                                 

                                greg

                                 

                                 

                                > one of the databases on Filemaker Server is 8 GB and the amount of available memory about 7.4 GB ...Can the Database Server fails because excess of the amount the database on the amount of RAM?

                                 

                                > Replace the hard drive on the server, replaced the memory, reinstalled Filemaker Server. However, an error from time to time continue to occur. Can cause incorrect operation of a computer or some other external influence?

                                • 13. Re: FileMaker Server Advanced Crashed
                                  taylorsharpe

                                  I'm betting the database became that big due to a large number of container fields/records.  If so, life will be much better when you upgrade to 12 and externally store those container fields.  But, no, RAM won't be the limiting factor other than it will work as slow as molasis if you don't have much RAM. 

                                  • 14. Re: FileMaker Server Advanced Crashed
                                    mark.stuller

                                    We have had FMSA 11.0.4.404 crash when (sorry guys!) ODBC and server-side plugins (written in Java) have conflicted. I do want to state that this may NOT be what's causing your problem however.

                                     

                                    Our solution was to move the Java-based plugin to a FMSA that did not need ODBC and removing ODBC connections from that FMSA. Removing the source of the conflict if effect.

                                     

                                    hth, Mark