2 Replies Latest reply on Jul 19, 2010 8:53 AM by Patrick Conway

    RHQ3.0.0 install postgres 8.4 - fails to create db's

    Patrick Conway Newbie

      Hi

       

      I'm trying to install the new release of RHQ 3.0.0

       

      I have created a new db in postgresql 8.4

       

      when I fill out the initial installer form   http://myserveraddress/installer/start.jsf

       

      I get an error when the installer tries to create tables

       

      Failed to save properties and fully deploy - RHQ Server will not function properly Cause: java.sql.SQLException:Failed to create table [RHQ_CONFIG_DEF] [ErrorCode=[0]; SQLState=[58P01]; Message=[ERROR: could not open segment 1 of relation base/157215/2661 (target block 118926606): No such file or directory]; Type=[org.postgresql.util.PSQLException]][SQLException=Failed to create table [RHQ_CONFIG_DEF] [ErrorCode=[0]; SQLState=[58P01]; Message=[ERROR: could not open segment 1 of relation base/157215/2661 (target block 118926606): No such file or directory]; Type=[org.postgresql.util.PSQLException]]] -> org.postgresql.util.PSQLException:ERROR: could not open segment 1 of relation base/157215/2661 (target block 118926606): No such file or directory[SQLException=ERROR: could not open segment 1 of relation base/157215/2661 (target block 118926606): No such file or directory]

       

      Full stack trace attached..above is the error presented on the web page

       

       

      ......../PostgreSQL/8.4/data/base/157215 # ls
      112        11452_vm   11462_fsm  11472      1247_fsm  1259_fsm  2328      2602_vm   2606_fsm  2609_fsm  2613      2617_fsm  2620_fsm  2657  2666  2679  2688  2702      2757  2838      3502      3602_fsm  3608      549
      113        11454      11462_vm   11472_fsm  1247_vm   1259_vm   2600      2603      2606_vm   2609_vm   2614      2617_vm   2620_vm   2658  2667  2680  2689  2703      2830  2838_fsm  3503      3602_vm   3609      pg_internal.init
      11447      11456      11464      11472_vm   1249      1417      2600_fsm  2603_fsm  2607      2610      2615      2618      2650      2659  2668  2681  2690  2704      2831  2838_vm   3600      3603      3712      PG_VERSION
      11447_fsm  11457      11466      11474      1249_fsm  1418      2600_vm   2603_vm   2607_fsm  2610_fsm  2615_fsm  2618_fsm  2651      2660  2669  2682  2691  2753      2832  2839      3600_fsm  3603_fsm  3764
      11447_vm   11457_fsm  11467      11476      1249_vm   157226    2601      2604      2607_vm   2610_vm   2615_vm   2618_vm   2652      2661  2670  2683  2692  2753_fsm  2833  2840      3600_vm   3603_vm   3764_fsm
      11449      11457_vm   11467_fsm  11477      1255      157231    2601_fsm  2605      2608      2611      2616      2619      2653      2662  2673  2684  2693  2753_vm   2834  2840_fsm  3601      3604      3764_vm
      11451      11459      11467_vm   11479      1255_fsm  157233    2601_vm   2605_fsm  2608_fsm  2612      2616_fsm  2619_fsm  2654      2663  2674  2685  2696  2754      2835  2840_vm   3601_fsm  3605      3766
      11452      11461      11469      11481      1255_vm   174       2602      2605_vm   2608_vm   2612_fsm  2616_vm   2619_vm   2655      2664  2675  2686  2699  2755      2836  2841      3601_vm   3606      3767
      11452_fsm  11462      11471      1247       1259      175       2602_fsm  2606      2609      2612_vm   2617      2620      2656      2665  2678  2687  2701  2756      2837  3501      3602      3607      548

       

       

      The file does exist, so I suspect a relative path issue maybe??

       

       

      I'm using CentOS 5.4

      Linux version 2.6.18-164.6.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Nov 3 16:12:36 EST 2009

       

      Any idea how I can resolve this issue?