Hai Kalaiarasi,
On 10 Jan 2020, at 07:08, Kalaiarasi Gowtham <kalaiarasigowthamcivil@gmail.com> wrote:
Hi Jenni,
Appreciate your time Jennie, for clarity, we had installed Monetdb using the steps shared in my earlier email and were actively using the database for our evaluation.
Apologies, I misunderstood your first email on this topic. It looked like the problem occurred the first time you started MonetDB after installation, but with your subsequent information, it’s clear that there is nothing wrong with your installation (process).
We faced the aforesaid issue when the server crashed due to an outage and was started again. I would be happy to hear from you if there were anything that would help us correct our installation steps.
“outage” is a crucial word here. Can you provide us some more information?
* What exactly was the outage?
* Do you run MonetDB on bare-metal hardware or a virtual environment? (In any case, please make sure that your (guest/host) OSs are configured in such a way that when MonetDB instruct the OS to flush data, the data is *really* written on disk at the locations where they are supposed to be, instead of letting the OS or disk report that they have written the data while they didn’t.)
* Can you please send us the outputs of these commands:
ls -Al /<path-to-your-dbfarm>/<dbname>
cat /<path-to-your-dbfarm>/<dbname>/.scen
* Can you send us the complete merovingian.log file?
The MonetDB daemon checks if all expected scenarios are denoted in the .scen file of each database. You can get the error "database <dbname> did not initialise the sql scenario”, if the “sql” scenario is not found in the .scen file => until several years ago, it was possible to install MonetDB kernel without the SQL layer, so this error often means that the SQL lib. wasn’t properly installed => so I was surprised that you got this error. Now that you mentioned an outage, it could be that your database has been corrupted because of that…
Regards,
Jennie
---------- Forwarded message ---------
From: Kalaiarasi Gowtham <kalaiarasigowthamcivil@gmail.com>
Date: Thu, 9 Jan 2020 at 19:25
Subject: Re: users-list Digest, Vol 89, Issue 2
To: <users-list@monetdb.org>
Hi Jenni,
Please, find the below steps I have followed to install monetdb
Installation of MonetDB in CentOS 7
Installing dependencies
# yum update
# yum install python autoconf automake libtool bison openssl openssl-devel gettext-devel git
# git clone https://github.com/MonetDB/MonetDB.git
# cd /MonetDB
# ./bootstrap
# cd ..
# mkdir testdir
# cd testdir
To enable py3integration python version 3 should be installed
# yum install centos-release-scl
# yum install rh-python36
# scl enable rh-python36 bash
check python version
# python -V
then
# ../MonetDB/configure –enable-py3integration=yes
# make
# make install
Thanks and regards,
Kalai
On Wed, 8 Jan 2020 at 16:31, <users-list-request@monetdb.org> wrote:
Send users-list mailing list submissions to
users-list@monetdb.org
To subscribe or unsubscribe via the World Wide Web, visit
https://www.monetdb.org/mailman/listinfo/users-list
or, via email, send a message with subject or body 'help' to
users-list-request@monetdb.org
You can reach the person managing the list at
users-list-owner@monetdb.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users-list digest..."
Today's Topics:
1. Re: pymonetdb issue (ferreira)
2. Re: Monetdb (Ying Zhang)
----------------------------------------------------------------------
Message: 1
Date: Tue, 7 Jan 2020 17:22:59 +0000
From: ferreira <pedro.ferreira@monetdbsolutions.com>
To: Communication channel for MonetDB users <users-list@monetdb.org>,
ALEX OSSIPOV <alexo15@comcast.net>
Subject: Re: pymonetdb issue
Message-ID:
<0e74a920-b2ad-2993-b1dc-fcd7a49105bb@monetdbsolutions.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hello Alex,
I just looked at pymonetdb source code and indeed it does not support
IPv6 yet. I'm going to create an issue to request for it. The reason is
because in the past, the MAPI protocol (which MonetDB uses for socket
connections) didn't support IPv6, so the clients (Python, Ruby, JDBC,
etc.) never had to implemented them. However they can now add this option.
Best regards,
Pedro
On 12/22/19 5:30 AM, ALEX OSSIPOV wrote:
> Hi All
> I installed pymonetdb v 1.2.1 and trying to connect to remote
> server?MonetDB v11.35.3 (Nov2019) listening on IPV6 only. I have got
> next error in python client:
> >>> mapi_connection.connect(hostname="<server_name>", port=xxxxx,
> username="monetdb", password="monetdb", database="demo",
> language="sql", unix_socket=None, connect_timeout=-1)
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/local/lib/python3.7/site-packages/pymonetdb/mapi.py", line
> 143, in connect
> self.socket.connect((hostname, port))
> socket.gaierror: [Errno -2] Name or service not known
> >>>
> My pc client is also using ipv6 to connect to MonetDB server. I also
> have jdbc connection that works fine.
> Question:
> Does it mean pymonetdb does not support ipv6 only environment?
> What would be the reason if it has nothing to do with protocol?
>
> Thanks
> Alex
>
>
> _______________________________________________
> users-list mailing list
> users-list@monetdb.org
> https://www.monetdb.org/mailman/listinfo/users-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.monetdb.org/pipermail/users-list/attachments/20200107/fb2103eb/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 7 Jan 2020 22:03:08 +0100
From: Ying Zhang <Y.Zhang@cwi.nl>
To: Communication channel for MonetDB users <users-list@monetdb.org>
Subject: Re: Monetdb
Message-ID: <5A710256-AB9A-4583-B4EF-31C7F0564918@cwi.nl>
Content-Type: text/plain; charset=utf-8
> On 3 Jan 2020, at 10:36, Kalaiarasi Gowtham <kalaiarasigowthamcivil@gmail.com> wrote:
>
> Hi,
> Currently, we are trying to start the database created in monetdb using the following command
> monetdb start <dbname>
> monetdbd: internal error while starting mserver 'database <dbname> did not initialise the sql scenario', please refer to the logs
>
> Getting logs as follows
>
> [root@localhost mydbfarm]# tail -f merovingian.log
> 2020-01-03 16:03:14 MSG merovingian[13157]: database <dbname> has shut down
> 2020-01-03 16:03:14 ERR control[13157]: !monetdbd: an internal error has occurred 'database <dbname> did not initialise the sql scenario'
> 2020-01-03 16:03:18 ERR merovingian[13157]: client error: database <dbname> did not initialise the sql scenario
> 2020-01-03 16:03:18 MSG merovingian[13157]: database <dbname> (13263) has exited with exit status 0
Hai Kalai,
I?m not sure, but this feels like MonetDB wasn?t properly installed? How did you install it?
Regards,
Jennie
>
>
> Please,help us to solve this issue.
>
>
> Thanks
> Kalai
> _______________________________________________
> users-list mailing list
> users-list@monetdb.org
> https://www.monetdb.org/mailman/listinfo/users-list
------------------------------
Subject: Digest Footer
_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list
------------------------------
End of users-list Digest, Vol 89, Issue 2
*****************************************
_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list