Hai Kalaiarasi,

On 10 Jan 2020, at 07:08, Kalaiarasi Gowtham 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 Date: Thu, 9 Jan 2020 at 19:25 Subject: Re: users-list Digest, Vol 89, Issue 2 To:

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, 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 To: Communication channel for MonetDB users , ALEX OSSIPOV 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="", 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