[Serusers] error starting ser daemon with persistency support - sr-users

Bogdan-Andrei IANCU

22 Jan 22 Jan

5:54 p.m.

Hi, increase the debug level in configuration file and you will see the line were the error lays in config script. Bogdan Ziying Sherwin wrote:

...

We are trying to compile ser 0.8.12 on Solaris 2.8 using gcc 3.3. The compilation and installation go smoothly until we tried to start the ser daemon with persistancy support. We followed the instructions listed on the website. First, we modified the MySQL configuration file to increase the maximun connections allowed. Second we restart the MySQL daemon. Third, we modified the ser_mysql.sh file to set the username, password and path properly and used it to create the MySQL tables. Then we modifid ser.cfg file and uncommented the following lines: loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/mysql.so" loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth.so" loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth_db.so" modparam("usrloc", "db_mode", 2) modparam("auth", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") uncommented and modified the following lines: if (!www_authorize("<our domain name>", "subscriber")) { www_challenge("<our domain name>", "0"); break; }; Finally, we tried to start the ser daemon by directly calling the binary "ser", and the got the following error message:

ser

ERROR: bad config file (1 errors) How can we find where the error is? All the modules listed in the configuration file are present in the directory. What else could go wrong? Thank you very much in advance. Ziying Sherwin _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

Vitali Nikolaev

6:21 p.m.

New subject: Re[2]: [Serusers] error starting ser daemon with persistency support

Hello Ziying, modparam("auth_db", "db_url","sql://ser:passwd@localhost/ser") modparam("usrloc", "db_url", "sql://ser:passwd@localhost/ser") Thursday, January 22, 2004, 11:17:20 AM, you wrote: ZS> Thank you very much for the help with the debug level. Now we can finally find ZS> where the problem is. It seems that it has something to do with the MySQL ZS> database access. We changed the username and password in both ser_mysql.sh ZS> and serctl. So we got the following error message from the ser debug output: ZS> 0(29503) connect_db(): Access denied for user: ZS> 'ser@localhost' (Using password: YES) ZS> 0(29503) db_init(): Error while trying to connect database ZS> 0(29503) mod_init(): Error while connecting database ZS> 0(29503) init_mod(): Error while initializing module usrloc ZS> ERROR: error while initializing modules ZS> We did not find any place to reset the password and username in the ser.cfg ZS> file, does that mean that those passwords and usernames are hard-coded into ZS> the C files? Which files should we change to reflect the password/username ZS> modification we made? ZS> Thanks again. ZS> Ziying Sherwin ZS> On Thu, 22 Jan 2004, Bogdan-Andrei IANCU wrote:

...

> Hi, > increase the debug level in configuration file and you will see the line > were the error lays in config script. > > Bogdan > > Ziying Sherwin wrote: > > >We are trying to compile ser 0.8.12 on Solaris 2.8 using gcc 3.3. The > >compilation and installation go smoothly until we tried to start the ser > >daemon with persistancy support. > > > >We followed the instructions listed on the website. First, we modified the > >MySQL configuration file to increase the maximun connections allowed. Second > >we restart the MySQL daemon. Third, we modified the ser_mysql.sh file to > >set the username, password and path properly and used it to create the MySQL > >tables. Then we modifid ser.cfg file and uncommented the following lines: > > > > loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/mysql.so" > > loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth.so" > > loadmodule > "/depot/package/ser_0.8.12/lib/ser/modules/auth_db.so" > > modparam("usrloc", "db_mode", 2) > > modparam("auth", "calculate_ha1", yes) > > modparam("auth_db", "password_column", "password") > > > >uncommented and modified the following lines: > > > > if (!www_authorize("<our domain name>", "subscriber")) { > > www_challenge("<our domain name>", "0"); > > break; > > }; > > > >Finally, we tried to start the ser daemon by directly calling the binary "ser", > >and the got the following error message: > > > > > > > >>ser > >> > >> > >ERROR: bad config file (1 errors) > > > >How can we find where the error is? All the modules listed in the configuration > >file are present in the directory. What else could go wrong? > > > >Thank you very much in advance. > > > >Ziying Sherwin > > > > > >_______________________________________________ > >Serusers mailing list > >serusers(a)lists.iptel.org > >http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > >

ZS> _______________________________________________ ZS> Serusers mailing list ZS> serusers(a)lists.iptel.org ZS> http://lists.iptel.org/mailman/listinfo/serusers -- Best regards, Vitali

Reply

Jan Janak

23 Jan 23 Jan

8:32 p.m.

New subject: Re[2]: [Serusers] error starting ser daemon with persistency support

Check the permissions of /tmp/ser_fifo. Jan. On 22-01 14:04, Ziying Sherwin wrote:

...

Thank you again for the help. We modified the ser.cfg file and made some progress. The ser server finally started, but when we monitor it using "serctl moni" we noticed the following messages: ... UsrLoc Stats Domain Registered Expired 'location' 0 0 ^V[cycle #: 15; if constant make sure server lives and fifo is on] Server: Sip EXpress router (0.8.12 (sparc64/solaris)) Now: Thu Jan 22 13:52:41 2004 Up Since: Thu Jan 22 13:41:38 2004 Up time: 663 [sec] Transaction Statistics Current: 70 (71 waiting) Total: 283 (0 local) Replied localy: 364 Completion status 6xx: 0, 5xx: 0, 4xx: 283, 3xx: 0,2xx: 0 Stateless Server Statistics 200: 0 202: 0 2xx: 0 300: 0 301: 0 302: 0 3xx: 0 400: 0 401: 0 403: 0 404: 0 407: 0 408: 0 483: 12 4xx: 0 500: 0 5xx: 0 6xx: 0 xxx: 0 failures: 7 ... Does that have anything to do with the message from the ser debug output: 0(0) DEBUG: setting SO_RCVBUF; set=65536,verify=65536 0(0) DEBUG: udp_init: trying SO_RCVBUF: 131072 0(0) DEBUG: setting SO_RCVBUF; set=131072,verify=131072 0(0) DEBUG: udp_init: trying SO_RCVBUF: 262144 0(0) DEBUG: setting SO_RCVBUF; set=262144,verify=262144 0(0) INFO: udp_init: SO_RCVBUF is finally 262144 0(0) WARNING: using only the first listen address (no fork) 1(686) DBG: open_uac_fifo: opening fifo... 1( 1(686) DEBUG: open_fifo_server: FIFO stat failed: Error 0 1(686) DEBUG: FIFO created @ /tmp/ser_fifo 1(686) DEBUG: fifo /tmp/ser_fifo opened, mode=432 686) DEBUG: init_mod_child (-1): tm Why does it fail to open the fifo? We also tried to test the ser by using a SIP user agent called "sip-communicator" (https://sip-communicator.dev.java.net/) which is a Java-base sip client. It does not contain a field in the configuration file to set the password. When we start the sip-communicator, it tried to register with our sip server, but failed to create a register transaction because our sip server is not responding. What happened to our sip server? Thanks again. Ziying Sherwin On Thu, 22 Jan 2004, Vitali Nikolaev wrote:

Hello Ziying, modparam("auth_db", "db_url","sql://ser:passwd@localhost/ser") modparam("usrloc", "db_url", "sql://ser:passwd@localhost/ser") Thursday, January 22, 2004, 11:17:20 AM, you wrote: ZS> Thank you very much for the help with the debug level. Now we can finally find ZS> where the problem is. It seems that it has something to do with the MySQL ZS> database access. We changed the username and password in both ser_mysql.sh ZS> and serctl. So we got the following error message from the ser debug output: ZS> 0(29503) connect_db(): Access denied for user: ZS> 'ser@localhost' (Using password: YES) ZS> 0(29503) db_init(): Error while trying to connect database ZS> 0(29503) mod_init(): Error while connecting database ZS> 0(29503) init_mod(): Error while initializing module usrloc ZS> ERROR: error while initializing modules ZS> We did not find any place to reset the password and username in the ser.cfg ZS> file, does that mean that those passwords and usernames are hard-coded into ZS> the C files? Which files should we change to reflect the password/username ZS> modification we made? ZS> Thanks again. ZS> Ziying Sherwin ZS> On Thu, 22 Jan 2004, Bogdan-Andrei IANCU wrote:

> Hi, > increase the debug level in configuration file and you will see the line > were the error lays in config script. > > Bogdan > > Ziying Sherwin wrote: > > >We are trying to compile ser 0.8.12 on Solaris 2.8 using gcc 3.3. The > >compilation and installation go smoothly until we tried to start the ser > >daemon with persistancy support. > > > >We followed the instructions listed on the website. First, we modified the > >MySQL configuration file to increase the maximun connections allowed. Second > >we restart the MySQL daemon. Third, we modified the ser_mysql.sh file to > >set the username, password and path properly and used it to create the MySQL > >tables. Then we modifid ser.cfg file and uncommented the following lines: > > > > loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/mysql.so" > > loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth.so" > > loadmodule > "/depot/package/ser_0.8.12/lib/ser/modules/auth_db.so" > > modparam("usrloc", "db_mode", 2) > > modparam("auth", "calculate_ha1", yes) > > modparam("auth_db", "password_column", "password") > > > >uncommented and modified the following lines: > > > > if (!www_authorize("<our domain name>", "subscriber")) { > > www_challenge("<our domain name>", "0"); > > break; > > }; > > > >Finally, we tried to start the ser daemon by directly calling the binary "ser", > >and the got the following error message: > > > > > > > >>ser > >> > >> > >ERROR: bad config file (1 errors) > > > >How can we find where the error is? All the modules listed in the configuration > >file are present in the directory. What else could go wrong? > > > >Thank you very much in advance. > > > >Ziying Sherwin > > > > > >_______________________________________________ > >Serusers mailing list > >serusers(a)lists.iptel.org > >http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > >

ZS> _______________________________________________ ZS> Serusers mailing list ZS> serusers(a)lists.iptel.org ZS> http://lists.iptel.org/mailman/listinfo/serusers -- Best regards, Vitali

_______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

Ziying Sherwin

23 Jan 23 Jan

5:55 p.m.

New subject: [Serusers] problem establishing conversation between two sip users

We are now running ser 0.8.12 daemon on Solaris 2.8 platform without persistency support. When we do the testing, we tried to establish a conversation between two X-lite 2.0 clients built on Mac OS X. After we started the X-lite, we configured it to use our sip server. The user can log into the sip server properly. However, when we tried to initiate a conversation from one X-lite to another, even though both of them are logged into the same host, they could not reach each other. The invitaion finally timed out. We also tried to initiate a conversation from X-lite to Windows messenger. It works fine, but we could not initiate a conversation from Windows Messenger to X-lite. Do anyone have similiar experience? Is there anyway to check sip users' activities on the ser side? How do we know whether there is communication between two users? We tried to use "serctl moni" to monitor the activity, but the log is long and confusing. Is there any documentatiion that we can refer to? Thanks in advance.

Reply