Ok that makes sense. When I restarted OpenSER the table location got populated.
Should I file a bug report regarding the incorrect structure of the subscriber and location dbtext tables?
- Daryl
On 3/20/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
On 03/20/07 20:31, Daryl Sanders wrote:
I noticed the "NULL value not allows" errors for field 0 and field 2. In my location table file "field 0" = id(int) and "field 2" = domain(str).
I tried to correct the errors by adding ",null" to the column type for each of these columns. This resulted the errors going away, however no new rows are added to the dbtext location table file when a phone registers.
The dbtext tables are in memory only. They are flushed back to harddrive when openser is stopped.
Cheers, Daniel
- Daryl
On 3/20/07, Daryl Sanders daryl.sanders@gmail.com wrote:
With debug=9, I did not see any errors when starting OpenSER, however I do get the following error when a phone tries to register.
2(27383) DBT:dbt_table_check_row: NULL value not allowed - field 0 2(27383) DBT:db_insert: cannot insert the new row!! 2(27383) DBT:db_insert: make clean! 2(27383) db_insert_ucontact(): Error while inserting contact 2(27383) ERROR:usrloc:insert_ucontact: failed to insert in database 2(27383) build_contact(): Created Contact HF: Contact: sip:1000@x.x.x.x:5060;expires=300
- Daryl
On 3/20/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
seems that some column is missing in location table. Can you start openser in higher debug mode and see the output. Should give you
more hints.
Cheers, Daniel
On 03/20/07 19:32, Daryl Sanders wrote:
When the issue is completely solved I will certainly do that. At this point I still get the following error, even with the presumably correct columns. But at least OpenSER starts now.
2(26689) db_insert_ucontact(): Error while inserting contact 2(26689) ERROR:usrloc:insert_ucontact: failed to insert in
database
This error occurs when a phone tries to register.
- Daryl
On 3/20/07, Ovidiu Sas sip.nslu@gmail.com wrote:
Then pls. create a patch and upload the patch to the traker:
diff -Naur textdb.sh.old textdb.sh.new
Regards, Ovidiu Sas
On 3/20/07, Daryl Sanders daryl.sanders@gmail.com wrote: > One correction to my previous post... > > When using method 2 (textdb.sh) to create dbtext tables, the > subscriber table format appears broken. I was able to correct
this
> issue by using the following columns. > > phplib_id(str) username(str) domain(str) password(str) > first_name(str,null) last_name(str,null) phone(str,null) > email_address(str) datetime_created(int,null) > datetime_modified(int,null) confirmation(str,null) flag(str,null) > sendnotification(str,null) greeting(str,null) ha1(str) ha1b(str) > allow_find(str) timezone(str,null) rpid(str,null) domn(int,null) > uuid(str,null) > > - Daryl > > > On 3/20/07, Daryl Sanders daryl.sanders@gmail.com wrote: > > When using db_mode=1,2 or 3 I get the following error when
starting
> > OpenSER 1.2 using dbtext as the usrloc DB. > > > > 1(23052) preload_udomain(): Error while doing db_query > > 1(23052) ERROR:ul:child_init(1): Error while preloading domain 'location' > > 1(23052) ERROR:init_mod_child: Error while initializing module usrloc, rank 1 > > > > I am wondering if their may be a problem with the columns in
the
> > location table file. > > > > I tried two different methods of creating the initial table
files...
> > > > 1.) sc.dbtext dbtext /usr/local/etc/openser/dbtext/ > > 2.) textdb.sh create /usr/local/etc/openser/dbtext/ > > > > The first method has problems with the version file that I
tried to
> > repair by trying to mimic the mysql table structure. > > > > The second method seems to work ok with the exception of the
error I
> > mentioned above when starting OpenSER. > > > > Any help would be greatly appreciated! > > > > Thanks, > > Daryl > > > > _______________________________________________ > Users mailing list > Users@openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users