This could be a corrupted write-ahead log. During startup, MonetDB reads the write-ahead log that was left behind by the previous database run. The function log_read_string tries to read a string from the log and in order to do so, it first reads the length of the string, allocated memory for it, and then reads the string. This allocation failed, quite possibly because the size that was read was incorrect. Failures during the reading of the write-ahead log are fatal.
On 12/04/2019 11.37, Amit Ambekar wrote:
Hi, Log in merovingian.log below: 2019-04-12 14:56:50 ERR narrator[2802]: !ERROR: log_read_string: malloc failed 2019-04-12 14:56:50 ERR narrator[2802]: !mvc_init: unable to create system tables 2019-04-12 14:56:50 ERR narrator[2802]: Fatal error during initialization: 2019-04-12 14:56:50 ERR narrator[2802]: SQLException:SQLinit:42000!Catalogue initialization failed
*Warm Regards,*
*Amit Suryakant Ambekar*
/*Technology Associate*///
/* */
Office: Ist floor, Poddar Chambers, Mathruradas Mill Compound,
Lower Parel, Mumbai 400013 | Landline: +91 22 43470408
Cell: +91 7741823310 | Email: amit@g-square.in mailto:amit@g-square.in | Website: www.g-square.in http://www.g-square.in/
**
On Fri, 12 Apr 2019 at 14:29, Amit Ambekar <amit@g-square.in mailto:amit@g-square.in> wrote:
Hi, I am using MonetDB from last 2 years, but never faced such issue till now. I am not able to use database ,it is giving error as below: monetdbd: internal error while starting mserver database has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details' Regards, Amit Ambekar Data Engineer
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list