Bugs item #2808233, was opened at 2009-06-18 08:31
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2808233&group_id=129076
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Query Execution
Group: Sedna (current)
Status: Open
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Daniela Tura (dtura)
Assigned to: Ivan Shcheklein (shcheklein)
Summary: sedna crashes
Initial Comment:
SEDNA version is 3.1.175
System: Linux 2.6.28-11-server x86_64
Log files: here attached, the fatal error starts at line 3021
We have been using sedna db for two years now and we have experimented that
sometimes it crashes and we need to restart the governor.
With the previous version, sometimes the db was corrupted and we needed to
restore a backup.
Now we have upgraded to 3.1.175 and the problem still occurs, but at least it
seems that we only need to restart (automatically) the governor (the db is not
corrupted)
We tried to detect the specific situation/query that causes the crash, but we
haven't found a recurring one, so we decided to post this bug, attaching the
log file containing the error.
Our application is written in .NET 2.0 and we have built our own wrapper
(managed c++ extensions) to your C API, so we dont' expect the error to be in
our code.
The system is currently deployed in a production enviroment and sometimes it
crashes more times in a day, so it would be very useful to us to have a reply
as soon as possible.
Kind regards
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2009-06-22 08:51
Message:
Thank you very much for your soon reply, we have just increased the number
of semaphores, we will observe the behaviour of the database for some days
and we'll let you know.
----------------------------------------------------------------------
Comment By: Ivan Shcheklein (shcheklein)
Date: 2009-06-18 09:03
Message:
Concerning exactly this crash. According to the event logs, Sedna wasn't
able to allocate semaphore (Cannot create
SM_TO_VMM_CALLBACK_SEM1_BASE_STR). It seems that the reason is your OS
configuration.
Try to extend some of the default kernel parameter settings. It's quite
simple. For example, here are instructions on how to modify the kernel.sem
and how to keep them set after a reboot:
* Log on as a user with root authority
* Open up /etc/sysctl.conf in a text editor and add entries:
kernel.sem="250 64000 32 256". Last number (SEMMSL) means system wide
maximum of semaphore sets, first (SEMMNI) defines maximum number of
semaphores per set, second defines total number of semaphores and usually
must be equal SEMMSL*SEMMNI. Note! se_gov + se_sm processes take apprx. 20
semaphore sets and each se_trn (session) process takes 3 semaphores at
least.
* Enter the sysctl -p command to load in sysctl settings from
/etc/sysctl.conf.
* Enter the ipcs -l to view the updated kernel parameters in sysctl.
Feel free to close this bug report if it works for you.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2808233&group_id=129076
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
