On 24-05-2007 18:04:17 +0200, Stefan Manegold wrote:

Venks,

the error message says is all: http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/MonetDB.tar.gz is currently not accessible. I guess, Fabian will fix this as soon as he's back online.

Actually, I'm waiting for testweb to put back the files that used to be there, such that it works again...

On 25-05-2007 09:34:16 +0200, Stefan Manegold wrote:

On Fri, May 25, 2007 at 09:17:24AM +0200, Fabian Groffen wrote:

...

On 24-05-2007 18:04:17 +0200, Stefan Manegold wrote:

...

Venks,

the error message says is all: http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/MonetDB.tar.gz is currently not accessible. I guess, Fabian will fix this as soon as he's back online.

Actually, I'm waiting for testweb to put back the files that used to be there, such that it works again...

Which files? And where? I'm not aware the testing did/does put files into http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/ ...

All files in http://monetdb.cwi.nl/testing/projects/monetdb/Current/.DailyBuilds./0_lates...

are back (should have been since yesterday morning)

Then it should work, as my "files" are just symlinks to the latests ones. Nothing more.

Hi Venks,

On 25-05-2007 10:00:27 -0400, Venks wrote:

I used the install script this morning and it worked.

But, I am unable to connect from any other client except server. I updated the .conf file and also I am setting mapi_open = true explicitly while starting the server with "monetdb".

I believe this issue was reported by Colin earlier but I didn't see any solution.

This wasn't not an issue with earlier MonetDB installed 10 days ago. In fact, I didn't set anything for "mapi_open" and everything worked fine. With the new build this is an issue.

I believe we see this same thing happening in the connection test, where a "connection refused" error is returned.

I hope we can find the cause soon.

Venks wrote:

I used the install script this morning and it worked.

But, I am unable to connect from any other client except server. I updated the .conf file and also I am setting mapi_open = true explicitly while starting the server with "monetdb".

I believe this issue was reported by Colin earlier but I didn't see any solution.

This wasn't not an issue with earlier MonetDB installed 10 days ago.

Thanks! This at least indicates the direction to look for the problem. Assuming you are using M5/SQL, there was a change in the src/modules/mal/mserver.mx module to align with the policy of M4/SQL to test for mapi_open property to access/deny connections.

Fabian,Sjoerd could either of you check that patch -------------------------------------------- diff -r1.84 -r1.85 604a605,606

  int accept_any=1;
  char *env;

616a619,623

  env = GDKgetenv("mapi_port");
  if(env){
          accept_any= (int) atol(env);
  }

646a654,658

@- Set server port and allow network connections from any workstation. Bind the socket to the server port. @c

651,652c663,666 < /* FIXME: this should be configurable via the config file */ < server.sin_addr.s_addr = INADDR_ANY; ---

          if (accept_any)
                  server.sin_addr.s_addr = htonl(INADDR_ANY);
          else
                  server.sin_addr.s_addr = htonl(INADDR_LOOPBACK);

mk@gio::~/monet5/package/MonetDB5/src/modules/mal> -----------------------------------------------

In fact, I didn't set anything for "mapi_open" and everything worked fine. With the new build this is an issue.

As we connect to MonetDB using JDBC client, we can't use MonetDB without this issue being resolved.

Please look into this ASAP.

Thanks,

On 5/25/07, Fabian Groffen Fabian.Groffen@cwi.nl wrote:

...

On 25-05-2007 09:34:16 +0200, Stefan Manegold wrote:

...

On Fri, May 25, 2007 at 09:17:24AM +0200, Fabian Groffen wrote:

...

On 24-05-2007 18:04:17 +0200, Stefan Manegold wrote:

...

Venks,

the error message says is all: http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/MonetDB.tar.gz is currently not accessible. I guess, Fabian will fix this as soon as he's back online.

Actually, I'm waiting for testweb to put back the files that used to be there, such that it works again...

Which files? And where? I'm not aware the testing did/does put files into http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/ ...

All files in http://monetdb.cwi.nl/testing/projects/monetdb/Current/.DailyBuilds./0_lates...

are back (should have been since yesterday morning)

Then it should work, as my "files" are just symlinks to the latests ones. Nothing more.

---

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

---

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

On 05/25/2007 09:18 PM, Fabian wrote:

On 25-05-2007 21:14:48 +0200, Martin Kersten wrote:

...

Thanks! This at least indicates the direction to look for the problem. Assuming you are using M5/SQL, there was a change in the src/modules/mal/mserver.mx module to align with the policy of M4/SQL to test for mapi_open property to access/deny connections.

Fabian,Sjoerd could either of you check that patch

Yeah, it was faulty, and always allowing connections, ignoring the mapi_open property. This has been fixed now, so it defaults to local connections only. The effect of this is that you have to set mapi_open to true to get the previous behaviour.

...

---

diff -r1.84 -r1.85 604a605,606

...

  int accept_any=1;
  char *env;

616a619,623

...

  env = GDKgetenv("mapi_port");
  if(env){
          accept_any= (int) atol(env);
  }

646a654,658

...

@- Set server port and allow network connections from any workstation. Bind the socket to the server port. @c

651,652c663,666 < /* FIXME: this should be configurable via the config file */

< server.sin_addr.s_addr = INADDR_ANY;

...

          if (accept_any)
                  server.sin_addr.s_addr = htonl(INADDR_ANY);
          else
                  server.sin_addr.s_addr = htonl(INADDR_LOOPBACK);

mk@gio::~/monet5/package/MonetDB5/src/modules/mal>

---

This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

It seems to me that the fix is wrong. It looks at mapi_port, not mapi_open to decide whether to open up the connection.