I have a linux machine that runs 50 instances of the same 50Mb database.
cmd for each looks like this:
With NN starting at 01 up to 50
These databases are presently all just idling. No workload. But between 2-5 hours, a random one would just stop running. Upon inspecting the /var/log folder in my Ubuntu server, I came across the following in the apport.log file:
Any idea what could cause this, or where I should start looking?
What is the maximum number of databases I can run on a single machine?
I don't want to run a single server with multiple databases as each should listen on a different port.
This is indicating that the database server process (pid 2985) received a signal 6 (SIGABRT). SQL Anywhere will typically issue a SIGABRT during a database assertion. (See KBA 1958942 - Error: "Assertion failed: 123456" / SQLCODE -301 "Internal Database Error" - Handling an Assertion Failure)
Just to confirm the scenario: so for two hours, the database server was running, checkpointing, etc. and then crashed with no message in the console log (
Typically when SQL Anywhere crashes, we have a signal handler that attempts to write out a core file to the current working directory of the database server (using the default
Under these situations to generate a core file you must either:
In this case (Ubuntu),
For more information about SQL Anywhere and core files, and to understand which files we will need to collect in technical support to analyze the core files for more information, see the following KBAs: