Opened 8 years ago
Closed 6 years ago
#1576 closed defect (invalid)
rasj requires the remote hostname to be resolvable locally
| Reported by: | Dimitar Misev | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 9.7 |
| Component: | java | Version: | development |
| Keywords: | Cc: | Vlad Merticariu, Peter Baumann, Bang Pham Huu | |
| Complexity: | Medium |
Description (last modified by )
Suppose we have a server machine with hostname REMOTEHOST, accessible at REMOTEIP. rasdaman is configured on this machine so that in etc/rasmgr.conf each rasserver specifies -host REMOTEHOST.
Suppose on a different client machine we run rasj and want to connect to the remote server to execute some queries. As server we specify REMOTEIP for the rasj connection. The connection will fail, unless on this client machine we add an entry in the /etc/hosts like this:
REMOTEIP REMOTEHOST
The same seems to happen with rasql as well.
Change History (5)
comment:1 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 7 years ago
| Milestone: | 9.5 → Future |
|---|
comment:3 by , 7 years ago
| Milestone: | Future → 9.6 |
|---|
comment:4 by , 7 years ago
| Milestone: | 9.6 → 9.7 |
|---|
comment:5 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
It's a bad configuration in rasmgr.conf in this case, we should simply use -host REMOTEIP (rather than the hostname).
Note:
See TracTickets
for help on using tickets.
This needs more attention, it's an annoying problem.
For example we can't add RRasdaman to CRAN because we can't setup a test that executes against a rasdaman running on kahlua.