Summary:	ASTERISK-23485: Asterisk suddenly stops writing data to astdb
Reporter:	Nikolay (tensor)	Labels:
Date Opened:	2014-03-14 02:41:02	Date Closed:	2014-05-02 10:23:57
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	11.6.0	Frequency of Occurrence
Related Issues:
Environment:	hardware: 2 CPU xeon E5649, 36GB RAM, CentOS release 6.2 (Final), kernel 2.6.32-220.13.1.el6.x86_64, asterisk version is 11.6-cert1	Attachments:
Description:	We've encountered the following issue. Asterisk stops writing to astdb.sqlite3 after a while until reboot (problem may start from a few hours to a few days of uptime). But log file astdb.sqlite3-journal is created with every DB change. The problem only occurs on highload PBXs, but it usualy begins when astdb is not under high load. The only non-typical setting associated with astdb is astdb path: astdbdir => / var / lib / asterisk / astdb
Comments:	By: Rusty Newton (rnewton) 2014-03-17 09:27:21.658-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks! By: Rusty Newton (rnewton) 2014-03-17 09:33:31.295-0500 You've told us a problem exists, but we can't do much about it unless you can tell us how to reproduce the issue, or provide information with which we can investigate the issue. Please read through the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] Specifically provide at least a full log showing the time at which the issue occurs. [Instructions are here|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] Please check the log before attaching it to the issue to verify it has DEBUG and VERBOSE message types. By: Nikolay (tensor) 2014-03-19 01:40:53.072-0500 1. I run asterisk and look at astdb. At first DB updates, and still updates, and then stops updating (mtime stops changing). Then I restart Asterisk and see that sequence of queues has changed (in comparison with Asterisk-before-restart). 2 . Accordingly, I expect astdb to contain up-to-date information. 3 . As I've already mentioned, I'm faced with the fact that the new data is not written to the database, although the 'database show' command shows current information. There are no any errors in logs. I don't know how to reproduce the problem. Also, I don't understand what kind of debug can help you deal with the situation. part of fullog https://drive.google.com/file/d/0BzOB_far0-7dVWxoaTFKZko4RkE/edit?usp=sharing illustration http://s018.radikal.ru/i515/1403/70/4ae5de827f97.png By: Nikolay (tensor) 2014-03-26 06:27:50.123-0500 The information about queues is available through 'queue show' command. However, this information occasionally stops syncing with is astdb.sqlite (file is not modified for a long time). May be you can tell me if there are any instruments to sync data directly with astdb. By: Matt Jordan (mjordan) 2014-04-17 09:59:25.742-0500 Without any additional information, it will be hard for any developer to determine what is occurring here. Please provide a script or some mechanism that reproduces the problem in a simulated environment. Without that, we'll be highly unlikely to be able to determine what might be causing your problem. By: Rusty Newton (rnewton) 2014-05-02 10:27:48.074-0500 [~skillx] If you can provide reproduction steps or if others can reproduce the issue, then we'll re-open the issue. Until then there doesn't appear to be anything we can do to investigate it. If someone comes up with ideas then we'll reopen. Feel free to contact a bug marshal in irc.freenode.net #asterisk-bugs to request the issue to be reopened at that time.