Opened 14 years ago
Closed 13 years ago
#59 closed task (invalid)
Problems on kahlua when postgres is started with an explicit port
Reported by: | Dimitar Misev | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | reladminif | Version: | |
Keywords: | Cc: | Peter Baumann | |
Complexity: | Medium |
Description (last modified by )
On kahlua the production PostgreSQL database is started on port 9000. However, after updating rasdaman, connection to postgres through libpq fails.
The relevant part from the server's log:
ENTER TransactionIf ONCE DatabaseIf getName() RASSERVICE begin(RASSERVICE, 1) ENTER DatabaseIf baseDBMSOpen() RASSERVICE ONCE Adminif getCurrentDatabaseIf() 0 ONCE Adminif setCurrentDatabaseIf(0x12d7820) 0 ENTER DatabaseIf connect() MIDDLE DatabaseIf Error: cannot obtain libpq connection . . . . . . . . Throwing Exception (SQLCODE=0): Throwing Exception (SQLCODE=0): ENTER DatabaseIf baseDBMSClose() ONCE Adminif getCurrentDatabaseIf() 0x12d7820 ONCE Adminif setCurrentDatabaseIf(0) 0x12d7820 ENTER DatabaseIf disconnect() EXIT DatabaseIf disconnect() SQLCODE=0 EXIT DatabaseIf baseDBMSClose() Error: exception 206: Serialisable exception r_Ebase_dbms: error in base DBMS. . . . . . . . LEAVE RnpRasDaManComm::decodeFragment, rasdaman exception caught: Serialisable exception r_Ebase_dbms: error in base DBMS. [2011-05-19 18:54:35]Error: request terminated: Serialisable exception r_Ebase_dbms: error in base DBMS. . . . . . . . rasdaman exception kind=35, errorno=206 Error in response: (35 206) Serialisable exception r_Ebase_dbms: error in base DBMS. . . . . . . . adjusted client ID from 0x0 to 0xffffffffabcdef01 [2011-05-19 18:54:35] request completed; request time=0.002s
For now the workaround is to start postgres at the default port, 5432.
Change History (2)
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.