Changes between Version 29 and Version 30 of FAQ


Ignore:
Timestamp:
Sep 2, 2009, 7:27:54 AM (15 years ago)
Author:
Peter Baumann
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • FAQ

    v29 v30  
    3030   A: Make sure you use the proper compiler version. GNU folks have a relaxed view on backwards compatibility even with minor release changes, and we have experienced such problems indeed.
    3131
    32  * '''Q: When running the script "create_db.sh", I get the following cryptic error message:'''
    33       {{{ Creating base RASBASE...Warning/error in AdminIf Connect: }}}
     32 * '''Q: When running the script "create_db.sh", I get the following cryptic error message: ''Creating base RASBASE...Warning/error in AdminIf Connect: SQLSTATE: 08001 SQLCODE: -402'' '''
    3433
    35       {{{ SQLSTATE: 08001 SQLCODE: -402}}}
     34   A: There are several possible reasons:
     35      '''Execution permissions.''' Run the script as the user owning the postgresql processes. Use '''only''' that user for further work with rasdaman. If you use Ubuntu and installed postgres with apt-get, then you should probably login as user '''postgres'''. (The postgres db does not allow full access to rasdaman tools, because they do not run under the administrative user that launched the db server process.)
    3636
    37    A: Please login as the user owning the postgresql processes, and run the same command. Use '''only''' that user for further work with rasdaman. If you use Ubuntu and installed postgres with apt-get, then you should probably login as user '''postgres'''. ( The problem is that the postgres db does not allow full access to rasdaman tools, because they do not run under the administrative user that launched the db server process. )
     37      '''Blocked incoming connections.''' Another cause of the problem might be that postgres does not allow incoming connections. If you have Postgres v8 or more recent, modify file "postgresl.conf" and set (uncomment) the option
    3838
    39    A: Another cause of the problem might be that postgres does not allow incoming connections. If you have Postgres v8 or more recent, please modify file "postgresl.conf", and set (uncomment) the option
    40      {{{ listen_addresses = 'localhost' }}}
    41 If you have Postgres v7, please set (uncomment) the following option:
    42      {{{ tcpip_socket = true }}}
     39      {{{ listen_addresses = 'localhost' }}}
     40
     41      '''TCP-IP connection.''' If you have Postgres v7, set (uncomment) the following option:
     42
     43      {{{ tcpip_socket = true }}}