[Monetdb-developers] Can't start the database after build
Hi,
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
monetdbd start monetdb-farm/ monetdb create demo created database in maintenance mode: demo mark@mark-desktop:~$ monetdb start demo starting database 'demo'... FAILED
start: starting 'demo' failed: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
and not much more in the log
2011-10-10 19:12:38 MSG control[4544]: (local): created database 'demo' 2011-10-10 19:12:48 MSG control[4544]: (local): served status list 2011-10-10 19:12:48 MSG merovingian[4544]: startup of database under maintenance 'demo' forced 2011-10-10 19:12:48 MSG merovingian[4544]: starting database 'demo', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0) 2011-10-10 19:12:48 MSG demo[4553]: arguments: /usr/local/bin/mserver5 --set gdk_dbfarm=/home/mark/monetdb-farm --dbname=demo --set merovingian_uri=mapi:monetdb://mark-desktop:50000/demo --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/mark/monetdb-farm/demo/.mapi.sock --set monet_vault_key=/home/mark/monetdb-farm/demo/.vaultkey --set max_clients=64 --set monet_daemon=yes 2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV 2011-10-10 19:12:48 ERR control[4544]: (local): failed to fork mserver: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
Thank you. Sincerely, Mark
Hi Mark,
On 10-10-2011 19:17:47 -0500, Mark Kerzner wrote:
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
What is the platform you're on? The default branch is in a bad state, where some platforms seem to have segfaulting mservers during startup (like in your case), see: http://monetdb.cwi.nl/testweb/web/status.php?serial=42010:81eb00c2f449&o...
At this moment, I think you're (much) better off using the current release branch, Aug2011.
2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV
Thanks for your feedback, Fabian Groffen
On 10/11/2011 08:53 AM, Fabian Groffen wrote:
Hi Mark,
On 10-10-2011 19:17:47 -0500, Mark Kerzner wrote:
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
What is the platform you're on? The default branch is in a bad state, where some platforms seem to have segfaulting mservers during startup (like in your case), see: http://monetdb.cwi.nl/testweb/web/status.php?serial=42010:81eb00c2f449&o...
At this moment, I think you're (much) better off using the current release branch, Aug2011.
But that one does not contain my patch for the string-attach. That need then to be backported. (most importantly mserver5/sql.mx)
2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV
Thanks for your feedback, Fabian Groffen
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On Tue, Oct 11, 2011 at 10:06:03AM +0200, Martin Kersten wrote:
On 10/11/2011 08:53 AM, Fabian Groffen wrote:
Hi Mark,
On 10-10-2011 19:17:47 -0500, Mark Kerzner wrote:
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
What is the platform you're on? The default branch is in a bad state, where some platforms seem to have segfaulting mservers during startup (like in your case), see: http://monetdb.cwi.nl/testweb/web/status.php?serial=42010:81eb00c2f449&o...
At this moment, I think you're (much) better off using the current release branch, Aug2011.
But that one does not contain my patch for the string-attach. That need then to be backported. (most importantly mserver5/sql.mx)
I'd prefer to fix the default (where/why does it segfault?), rather than back-porting a new feature to a release branch.
Fabian's comment it genrerally true an should be read as " Unless you really need cutting-edge (and thus possibly immature & instable) features that are only available in the latest development version, you are (always) better off with using the latest stable release (branch). "
Of course, everyone using a Mercurial checkout can locally back-port changeset that implement new features from the development trunk (default branch) to the latest release branch --- no guarantees, though that they fit, compile, work correctly, there ...
Stefan
2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV
Thanks for your feedback, Fabian Groffen
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On 11-10-2011 10:22:10 +0200, Stefan Manegold wrote:
At this moment, I think you're (much) better off using the current release branch, Aug2011.
But that one does not contain my patch for the string-attach. That need then to be backported. (most importantly mserver5/sql.mx)
I'd prefer to fix the default (where/why does it segfault?), rather than back-porting a new feature to a release branch.
I completely concur with Stefan here. The default branch is segfaulting for way too long already now.
I just committed a fix that may well solve this crash.
On 2011-10-11 02:17, Mark Kerzner wrote:
Hi,
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
monetdbd start monetdb-farm/ monetdb create demo created database in maintenance mode: demo mark@mark-desktop:~$ monetdb start demo starting database 'demo'... FAILED
start: starting 'demo' failed: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
and not much more in the log
2011-10-10 19:12:38 MSG control[4544]: (local): created database 'demo' 2011-10-10 19:12:48 MSG control[4544]: (local): served status list 2011-10-10 19:12:48 MSG merovingian[4544]: startup of database under maintenance 'demo' forced 2011-10-10 19:12:48 MSG merovingian[4544]: starting database 'demo', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0) 2011-10-10 19:12:48 MSG demo[4553]: arguments: /usr/local/bin/mserver5 --set gdk_dbfarm=/home/mark/monetdb-farm --dbname=demo --set merovingian_uri=mapi:monetdb://mark-desktop:50000/demo --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/mark/monetdb-farm/demo/.mapi.sock --set monet_vault_key=/home/mark/monetdb-farm/demo/.vaultkey --set max_clients=64 --set monet_daemon=yes 2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV 2011-10-10 19:12:48 ERR control[4544]: (local): failed to fork mserver: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
Thank you. Sincerely, Mark
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
Sjoerd,
that indeed fixed it!
Thank you, Mark
On Tue, Oct 11, 2011 at 5:51 AM, Sjoerd Mullender sjoerd@acm.org wrote:
I just committed a fix that may well solve this crash.
On 2011-10-11 02:17, Mark Kerzner wrote:
Hi,
I've built the latest code from Mercurial repository, and I cannot get any database to start. I am doing everything locally, so this sequence of commands invariably results in the db crashing:
monetdbd start monetdb-farm/ monetdb create demo created database in maintenance mode: demo mark@mark-desktop:~$ monetdb start demo starting database 'demo'... FAILED
start: starting 'demo' failed: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for
details
and not much more in the log
2011-10-10 19:12:38 MSG control[4544]: (local): created database 'demo' 2011-10-10 19:12:48 MSG control[4544]: (local): served status list 2011-10-10 19:12:48 MSG merovingian[4544]: startup of database under maintenance 'demo' forced 2011-10-10 19:12:48 MSG merovingian[4544]: starting database 'demo', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0) 2011-10-10 19:12:48 MSG demo[4553]: arguments: /usr/local/bin/mserver5 --set gdk_dbfarm=/home/mark/monetdb-farm --dbname=demo --set merovingian_uri=mapi:monetdb://mark-desktop:50000/demo --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/mark/monetdb-farm/demo/.mapi.sock --set monet_vault_key=/home/mark/monetdb-farm/demo/.vaultkey --set max_clients=64 --set monet_daemon=yes 2011-10-10 19:12:48 MSG merovingian[4544]: database 'demo' (4553) was killed by signal SIGSEGV 2011-10-10 19:12:48 ERR control[4544]: (local): failed to fork mserver: database 'demo' has crashed after starting, manual intervention needed, check monetdbd's logfile for details
Thank you. Sincerely, Mark
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Sjoerd Mullender
All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
participants (5)
-
Fabian Groffen -
Mark Kerzner -
Martin Kersten -
Sjoerd Mullender -
Stefan Manegold