3 Replies Latest reply on Nov 15, 2016 6:39 AM by mattel

    FileMaker Cloud Crashed - No Notice

    mattel

      TLDR: don't change the default dhcp option set in your vpc.

       

      I'm running a filemaker cloud server as a test -- if it all goes well - we will put it into production with 100 users or so.

      The instance has been running since November 5th, and till now, not had any problems I was aware of.

      Today I tried to connect to it, and the website access is down, I tried accessing it from the local machine ip from another machine on the same vpc - no luck.  Connection refused.

      I can still ping the machine and I ssh'd into it.

      So my question is this, if the filemaker server process crashes, how do I setup an alert to reboot the instance?  Or at least send me an email. I expected something like this to be built into it automatically.

       

      Prior to posting this I did get it back up and running.  I had been working on creating some remote desktop servers to access this filemaker cloud server from (also in aws).  I created a new dhcp-option set that would use the dns servers of the domain.  Apparently that interferes with something that the filemaker cloud image is doing in registering itself with.  Additionally you made need to look at the /etc/resolv.conf and confirm that your server is not trying to add your local domain to the prefix instead of ec2-internal. 

       

      Everything is still not correct and I will likely end up relaunching this server.  Obviously there is still a lot of inflexibility built into this for those who otherwise would be deploying it into a mixed environment.

        • 1. Re: FileMaker Cloud Crashed - No Notice
          TSGal

          mattel:

           

          Thank you for your post.

           

          In the FileMaker Cloud console, check the Notifications in the upper right.  Are there any reports listed?  If so, then turn on email notifications.  See Knowledge Base Article #16178 for more information:

          Overview of notifications in FileMaker Cloud | FileMaker

           

          You can also reboot the instance from the FileMaker Cloud console by going to Configuration tab, clicking on System Configuration, and clicking Refresh to the right of the instance.

           

          TSGal

          FileMaker, Inc.

          • 2. Re: FileMaker Cloud Crashed - No Notice
            wimdecorte

            mattel wrote:

             

            So my question is this, if the filemaker server process crashes, how do I setup an alert to reboot the instance? Or at least send me an email. I expected something like this to be built into it automatically.

             

            It is actually built in (except for the email).  Unlike the on-premise regular FMS, the Cloud one has a 'robot administrator' that monitors FMS and brings it back to life where necessary.

             

            Sounds like your problem was not with that and that it was running all the time, just that you could not get to it?

            You can download the event log from the admin console, you may want to do that and see if it shows any relevant entries.

            • 3. Re: FileMaker Cloud Crashed - No Notice
              mattel

              I ended up destroying the instance and starting over.  Moving the data from the old volume to the new one.

              The problem was the fmhelper file wouldn't connect to the server that it wanted to "phone" home as it may be.

               

              My point was that the servers should be setup to detect if fmserver is running and restart the process independent of being able to ping back to some central server of filemaker-cloud.  Also that if they are going to require to use the amazon ec2 provided dns servers instead of your own - that should be documented.