[OpenSIPS-Users] Need Help on integrating opensips with mysql on remote machine

[ram]

are you able to login to remote mysql server from opensips box ?

On Sun, Jan 17, 2010 at 5:50 AM, Alok Kushwaha <alok.cs04 at gmail.com> wrote:

>
> Hi! ram
> thanks for reply.
>
> yes , i have set this option. like -
> "mysql://user:db_password@remote_db_ip_address/opensips"
>
>
>  ram-2-3 wrote:
> >
> > have you set this option in the config
> >
> > "*mysql*://user:db_password at remote_db_ip_address/opensips"
> >
> >
> > On Mon, Jan 11, 2010 at 12:15 PM, Alok Kushwaha <alok.cs04 at gmail.com>
> > wrote:
> >
> >> Hi! All,
> >> I am using opensips 1.5 and installed using source. my DB server (mysql)
> >> is
> >> running on a remote machine. I have enabled the remote access and
> granted
> >> the proper privileges.
> >>
> >> I started the opensips with " service opensips start " but  it stopped
> in
> >> 2
> >> minutes.
> >> and follwing error message is logged - (in /var/log/message)
> >>
> >> Jan 11 07:01:15 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.11
> >> Jan 11 07:01:35 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.12
> >> Jan 11 07:01:55 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.13
> >> Jan 11 07:02:15 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.14
> >> Jan 11 07:02:35 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.15
> >> Jan 11 07:02:56 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.11
> >> Jan 11 07:03:16 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.12
> >> Jan 11 07:03:36 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.13
> >> Jan 11 07:03:56 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.14
> >> Jan 11 07:04:16 localhost opensips: WARNING:core:fix_socket_list: could
> >> not
> >> rev. resolve 200.200.100.15
> >> Jan 11 07:04:16 localhost opensips: INFO:core:init_tcp: using epoll_lt
> as
> >> the TCP io watch method (auto detected)
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> NOTICE:core:main:
> >> version: opensips 1.5.0-notls (i386/linux)
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> INFO:core:main:
> >> using 32 Mb shared memory
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> INFO:core:main:
> >> using 1 Mb private memory per process
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> NOTICE:signaling:mod_init: initializing module ...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:sl:mod_init:
> >> Initializing StateLess engine
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:tm:mod_init:
> >> TM - initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:maxfwd:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:usrloc:ul_init_locks: locks array size 512
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:registrar:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:textops:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:xlog:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:acc:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:auth:mod_init: initializing...
> >> Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:auth_db:mod_init: initializing...
> >> Jan 11 07:04:36 localhost /usr/local/sbin/opensips[4645]:
> >> INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4645]:last message
> >> repeated 5 times
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]:
> >> ERROR:db_mysql:db_mysql_new_connection: driver error(2003): Can't
> connect
> >> to
> >> MySQL server on '200.200.100.22' (4)
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]:
> >> ERROR:core:db_do_init: could not add connection to the pool
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]:
> >> ERROR:auth_db:child_init: unable to connect to the database
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]:
> >> ERROR:core:init_mod_child: failed to initializing module auth_db, rank
> 17
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]:
> >> ERROR:core:main_loop: init_child failed for UDP listener
> >> Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4665]:
> >> ERROR:db_mysql:db_mysql_new_connection: driver error(2003): Can't
> connect
> >> to
> >> MySQL server on '200.200.100.22' (4)
> >>
> >>
> >>
> >> for me it's look like some problem in core module. but i don't where to
> >> find it.
> >> please tell me why it's stopped.
> >> any help is appreciated.
> >> thanks in advance.
> >>
> >> --
> >> Regards,
> >> Alok Kushwaha
> >>
> >>
> >>
> >> "always be the reason of someones happiness."
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >>
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/Need-Help-on-integrating-opensips-with-mysql-on-remote-machine-tp4287536p4408184.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
>  Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100117/80ba6773/attachment-0001.htm