Fatal Postgres Connect Error

RE : Fatal Postgres Connect Error

soleadd13 — 2011-07-08T05:00:47+02:00

Are you particular you don't have anymore trouble collectively with your databases ?!? Moreover, you need to replace the JDBC driver granted from the installer over the appropriate just one corresponding collectively with your databases version.

invalid link : url=http://www.discountdvdsets18.com/goods-512Aladdin+The+Return+Of+Jafar+DVD+%28Disney%29-FREE+SHIPPING.html(Illegal character in scheme name at index 3: url=http://www.discountdvdsets18.com/goods-512Aladdin+The+Return+Of+Jafar+DVD+%28Disney%29-FREE+SHIPPING.html)Aladdin The Return Of Jafar DVD! url !,invalid link : url=http://www.discountdvdsets18.com/goods-510Being+Human+Seasons+1-3+DVD+Boxset-FREE+SHIPPING.html(Illegal character in scheme name at index 3: url=http://www.discountdvdsets18.com/goods-510Being+Human+Seasons+1-3+DVD+Boxset-FREE+SHIPPING.html)Being Human Seasons DVD! url !

RE : Fatal Postgres Connect Error

Sebastien Jourdain — 2009-01-14T14:38:06+01:00

Thanks for your feed back, and I'm sorry that I didn't manage to solve your problem...

LibreSource work normally well on Linux, Mac OSX and Windows.

Anyway, I'm happy that you manage to make it work.

Regards,

Seb

RE : Fatal Postgres Connect Error

moriger — 2009-01-13T16:38:51+01:00

Hi Sebastien,

We tried installing on a Windows machine and we were up and running right away. Thanks for your help and efforts!

RE : Fatal Postgres Connect Error

moriger — 2009-01-06T21:12:40+01:00

Hi Sebastien, The postgres installation is a standard linux installation using three yum packages. However I think I am going to try and do a potentially faster work-around and install this on a Windows 2008 Server

RE : Fatal Postgres Connect Error

Sebastien Jourdain — 2008-12-31T18:25:59+01:00

In fact, its the same, my table came from the origine of LS… That's why my index has not the same name… So nothing strange appear to me.

Could you tell me more about the way you've installed Postgres ?

RE : Fatal Postgres Connect Error

moriger — 2008-12-31T18:00:08+01:00

Just FYI public.profileresource_ has no tuples.

RE : Fatal Postgres Connect Error

moriger — 2008-12-31T17:58:03+01:00

Sorry last post was working strangely

Table "public.profileresource_"
     Column     |              Type              | Modifiers accountstatus_ | integer                        |
 email_         | character varying              |
 jabberid_      | character varying              |
 lastlogintime_ | timestamp(3) without time zone |
 id_            | character varying              | not null
 infos_         | bytea                          |
 onlinestatus_  | integer                        |
 fullname_      | character varying              |
Indexes:
    "profileresource__pkey" PRIMARY KEY, btree (id_)

RE : Fatal Postgres Connect Error

moriger — 2008-12-31T17:56:36+01:00

Mine is similar but not the same

Table "public.profileresource_"
     Column     |              Type              | Modifiers
----------------+--------------------------------+-----------
 accountstatus_ | integer                        |
 email_         | character varying              |
 jabberid_      | character varying              |
 lastlogintime_ | timestamp(3) without time zone |
 id_            | character varying              | not null
 infos_         | bytea                          |
 onlinestatus_  | integer                        |
 fullname_      | character varying              |
Indexes:
    "profileresource__pkey" PRIMARY KEY, btree (id_)

RE : Fatal Postgres Connect Error

Sebastien Jourdain — 2008-12-31T17:39:39+01:00

It might be jonas which don't initialize properly the table that manage Profile beans...

And I don't see why. Errors occurs before the initial bootstrap due to the initial empty state, but not the one you've got that prevent LS from starting.

Have you got the same table definition ?

psql libresource
\d profileresource_

Table "public.profileresource_"
     Column     |              Type              | Modifiers 
----------------+--------------------------------+-----------
 id_            | character varying              | not null
 fullname_      | character varying              | 
 email_         | character varying              | 
 jabberid_      | character varying              | 
 infos_         | bytea                          | 
 onlinestatus_  | integer                        | 
 lastlogintime_ | timestamp(3) without time zone | 
 accountstatus_ | integer                        | 
Indexes:
    "courgette_users__pkey" PRIMARY KEY, btree (id_)

RE : Fatal Postgres Connect Error

moriger — 2008-12-31T17:23:23+01:00

Hi Sebastien,

For each of the URLs you listed I received the same error output as before. It complains of org.libresource.membership.MembershipServiceException: Error in getProfile : Error in systemGetProfile : The pk fields has not been initialized the ejbCreate method of the bean Node org.libresource.membership.ejb.MembershipServiceBean.getProfile(MembershipServiceBean.java:922)

Does this mean that a primary key field does not exist in the database? Or that the Java Bean is not initializing the variable? Or something else?