Hello

Thank you David Loh and Henning

I reviewed your instructions and did the next:

First I did the David's instructions, I just comment the lines 376 and 377 of the openser.cfg and the result was:

I don't get error message: Feb 27 01:05:53 [7788] CRITICAL:core:yyerror: parse error in config file, line 376, column 2-6: syntax error Feb 27 01:05:53 [7788] CRITICAL:core:yyerror: parse error in config file, line 376, column 2-6: Feb 27 01:05:53 [7788] ERROR:core:main: bad config file (2 errors)

but when i try to monitoring the system with command /usr/local/sbin/openserctl moni I got the message: ERROR: Error opening OpenSER's FIFO /tmp/openser_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")' in your config ERROR: and also have loaded the mi_fifo module.

I have attached the complete starting trace in starting_trace1.txt and the openser1.cfg

Then I tried with Henning's instructions, I changed my current openser.cfgfor the openser.cfg that I donwloaded from http://devel.openser.org/svn/branches/1.3/etc/openser.cfg and changed the properties to work with postgres but the result was same that when I followed the David's instructions.

so, I returned to the initial openser.cfg file and sow that the lines 154 and 155 of --usrloc params-- session were commented #modparam("usrloc", "db_url", # "mysql://openser:openserrw@192.168.1.3/openser_1_3")

equals that 163 and 164 of --uth_db params-- session #modparam("auth_db", "db_url", # "mysql://openser:openserrw@192.168.1.3/openser_1_3")

then I uncommented that lines and changed mysql for pgsql, 192.168.1.3 for 192.168.1.1 because it is the static ip of my pc and openser_1_3 for openser because it is the name of the database create in postgres

the new lines were: modparam("usrloc", "db_url", "pgsql://openser:openserrw@192.168.1.1/openser")

equals that 163 and 164 of --uth_db params-- session modparam("auth_db", "db_url", "psql://openser:openserrw@192.168.1.1/openser")

I was run again the openser and the result was starting_trace2.txt and the config file used was openser2.cfg

As you can see there are some error asociate with the postgres module: ERROR:core:bind_dbmod: module pgsql does not export db_use_table function Feb 28 22:58:23 [5979] ERROR:usrloc:mod_init: failed to bind database module Feb 28 22:58:23 [5979] ERROR:core:init_mod: failed to initialize module usrloc Feb 28 22:58:23 [5979] ERROR:core:main: error while initializing modules Feb 28 22:58:23 [5979] DBG:xlog:destroy: destroy module...

I don't know if it are the errors that Henning said in his response that will be fixed in new release of openser 1.3.1

Thanks a lot for you time

Regards, Mauricio Viveros

2008/2/28, David Loh davidloh@vyke.com:

Hi there, from the error log it doesn't look like postgres or openser 1.3fault, but your configuration file.

Line 376 was the line with "exit", since you have comment out the whole route[2], why leave the "exit" and close parenthesis there?

You can try to comment out line 376 and 377 then start the openser, hopes this solve your question.

Regards, David Loh

Mauricio Viveros wrote:

Hello

My name is Mauricio Viveros, I'm a Colombian programmer. I'm implementing VoIP system in a little company, so I'm installed OPENSER with POSTGRES module but when I try to run openser I get dis error message:

Feb 27 01:05:53 [7788] DBG:core:find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/local/lib/openser/modules/] Feb 27 01:05:53 [7788] CRITICAL:core:yyerror: parse error in config file, line 376, column 2-6: syntax error Feb 27 01:05:53 [7788] CRITICAL:core:yyerror: parse error in config file, line 376, column 2-6: Feb 27 01:05:53 [7788] ERROR:core:main: bad config file (2 errors)

to see all trace, see the attached file openser_error_message.txt I attached too the config files: openser.cfg y openserctlrc

I hope that you can help me with this problem. Thank you very much.

Mauricio Viveros Programmer Cali-Colombia

---

---

Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

On Friday 29 February 2008, Mauricio Viveros wrote:

[..] Then I tried with Henning's instructions, I changed my current openser.cfgfor the openser.cfg that I donwloaded from http://devel.openser.org/svn/branches/1.3/etc/openser.cfg and changed the properties to work with postgres but the result was same that when I followed the David's instructions.

so, I returned to the initial openser.cfg file and sow that the lines 154 and 155 of --usrloc params-- session were commented

then I uncommented that lines and changed mysql for pgsql, 192.168.1.3 for 192.168.1.1 because it is the static ip of my pc and openser_1_3 for openser because it is the name of the database create in postgres

the new lines were: modparam("usrloc", "db_url", "pgsql://openser:openserrw@192.168.1.1/openser")

equals that 163 and 164 of --uth_db params-- session modparam("auth_db", "db_url", "psql://openser:openserrw@192.168.1.1/openser")

Hi Mauricio,

the correct driver name is 'postgres', not 'psql' or 'pgsql'. The error message that you've got because of this problem is somewhat misleading.

http://www.openser.org/dokuwiki/doku.php/troubleshooting:faq#qerrorcorebind_...

Cheers,

Henning