Re: [sr-dev] Kamailio 3.1 testing - PGSQL initialisation problems - sr-dev

5 Oct 2010

Hello Daniel,

I have still corrected the initial request mail in June and explained
that the tables "acc" and "missed_calls" do not need any change. They
are / were working fine.

However, in a first quick try of testing the pre-release I found out
that the "not NULL" options in the relations "presentity" and
"pua" are
still wrong. They must be adapted manually for Kamailio being able to
insert an entry into the database.

I will follow up with deeper tests of the presence related stuff and
will send an updated message about what is working fine and what not.

regards,
Klaus Feichtinger

...
    Hello,

 I have reapplied part of Henning's patch to solve the non null
 terminated blobs causing issues with presence modules. Please give it
 at
  try as well and report if works fine.

  From the discussion done in June (the link you provided), I didn't
 get
 why acc and missed_calls need to allow null for id columns - they
 should
  be auto-incremented, being a sequence like in the other tables. Here
 is your initial email in that thread:
 http://lists.sip-router.org/pipermail/sr-dev/2010-June/007882.html

 If you can refresh what is still not working after last fixes, would
 be great.

 Thanks,
 Daniel

 On 9/30/10 10:19 AM, klaus.lists(a)inode.at wrote:
  Hello,

 I've heard your appeal to support testing the new pre-release 3.1 of
 kamailio. So I started with compiling and installing it. My focus is
 / was testing kamailio 3.1 with DB engine POSTGRESQL.

 However, my testing phase was stopped very early, because "kamdbctl
 create" was stopped by an error message related to creating the table
 "lcr". AFAIK the tables / table names have changed, because Juha has
 modified this module as discussed earlier in this list. Could this be
 the reason why kamdbctl stopped? It seems that the script still knows
 only the old relations within the DB.

 The error message looks as follows:

 voiceserver1:/usr/local/etc/kamailio# kamdbctl create
 INFO: creating database openser ...
 NOTICE:  CREATE TABLE will create implicit sequence "acc_id_seq" for
 serial column "acc.id"
 [...]
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 "dialplan_pkey" for table "dialplan"
 ERROR:  relation "lcr" does not exist
 ERROR:  relation "lcr" does not exist
 ERROR:  relation "lcr_id_seq" does not exist
 ERROR:  relation "lcr_id_seq" does not exist
 ERROR: Grant privileges to standard tables failed!

 I recommend CHECKING the initialisation script(s) for POSTGRESQL in
 general. Because in the previous release 3.0.3 the problem / error
 with wrong settings for column attributes especially for presence
 related tables  (as discussed in spring this year - see
 http://lists.sip-router.org/pipermail/sr-dev/2010-June/007896.html)
 is still present!

 regards,
 Klaus Feichtinger

 _______________________________________________
 sr-dev mailing list
 sr-dev(a)lists.sip-router.org
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev 
 --
 Daniel-Constantin Mierla
 http://www.asipto.com 