[Serusers] Mysql Connection Errors

[Nils Ohlmeier]

Maybe this old reply on a similar problem will be helpfull for you:
http://lists.iptel.org/pipermail/serusers/2003-March/000627.html

Regards
  Nils Ohlmeier

On Thursday 22 May 2003 00:04, Todd wrote:
> Ok..I have setup SER according to the guide on the iptel site.
> Here is a copy of what's in my ser.cfg
>
> _________________________________________
> #
> # $Id: ser.cfg,v 1.12 2002/10/21 02:40:06 jiri Exp $
> #
> # simple quick-start config script
> #
>
> # ----------- global configuration parameters ------------------------
>
> debug=3          # debug level (cmd line: -dddddddddd)
> fork=yes
> log_stderror=no	# (cmd line: -E)
> check_via=no	# (cmd. line: -v)
> dns=no           # (cmd. line: -r)
> rev_dns=no      # (cmd. line: -R)
> port=5060
> children=4
> fifo="/tmp/ser_fifo"
>
> # ------------------ module loading ----------------------------------
>
> # Uncomment this if you want to use SQL database
> loadmodule "//usr/lib/ser/modules/mysql.so"
>
> loadmodule "//usr/lib/ser/modules/sl.so"
> loadmodule "//usr/lib/ser/modules/tm.so"
> loadmodule "//usr/lib/ser/modules/rr.so"
> loadmodule "//usr/lib/ser/modules/maxfwd.so"
> loadmodule "//usr/lib/ser/modules/usrloc.so"
> loadmodule "//usr/lib/ser/modules/registrar.so"
>
> # Uncomment this if you want digest authentication
> # mysql.so must be loaded !
> loadmodule "//usr/lib/ser/modules/auth.so"
>
> # ----------------- setting module-specific parameters ---------------
>
> # -- usrloc params --
>
> #modparam("usrloc", "db_mode",   0)
>
> # Uncomment this if you want to use SQL database
> # for persistent storage and comment the previous line
> modparam("usrloc", "db_mode", 2)
>
> # -- auth params --
> # Uncomment if you are using auth module
> #
> #modparam("auth", "secret", "alsdkhglaksdhfkloiwr")
> modparam("auth", "calculate_ha1", yes)
> #
> # If you set "calculate_ha1" parameter to yes (which true in this
> config),
> # uncomment also the following parameter)
> #
> modparam("auth", "password_column", "password")
>
> # -------------------------  request routing logic -------------------
>
> # main routing logic
>
> route{
>
> 	# initial sanity checks -- messages with
> 	# max_forwars==0, or excessively long requests
> 	if (!mf_process_maxfwd_header("10")) {
> 		sl_send_reply("483","Too Many Hops");
> 		break;
> 	};
> 	if (len_gt( max_len )) {
> 		sl_send_reply("513", "Message too big");
> 		break;
> 	};
>
> 	# Do strict routing if pre-loaded route headers present
> 	rewriteFromRoute();
>
> 	# if the request is for other domain use UsrLoc
> 	# (in case, it does not work, use the following command
> 	# with proper names and addresses in it)
> 	if (uri=~"computergeeks.hopto.org") {
>
> 		if (method=="REGISTER") {
>
> # Uncomment this if you want to use digest authentication
> 			if (!www_authorize("computergeeks.hopto.org", "subscriber")) {
> 				www_challenge("computergeeks.hopto.org", "0");
> 				break;
> 			};
>
> 			save("location");
> 			break;
> 		};
>
> 		# native SIP destinations are handled using our USRLOC DB
> 		if (!lookup("location")) {
> 			sl_send_reply("404", "Not Found");
> 			break;
> 		};
> 	};
> 	# forward to current uri now
> 	if (!t_relay()) {
> 		sl_reply_error();
> 	};
>
> }
>
> _________________________________________________
>
>
> The modules are all where they say they are but when I try to start SER
> I get this in my messages log file
>
> May 21 18:58:45 computergeeks ser: ser startup succeeded
> May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: connect_db(): Can't
> connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
> (2)
> May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: db_init(): Error
> while trying to connect database
> May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: mod_init(): Error
> while connecting database
> May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: init_modules():
> Error while initializing module usrloc
>
>
> Can someone please tell me what I'm doing wrong?  I've searched all over
> the net for information on this...I'm sure it's something simple..but
> I'm overlooking it.
>
> If I disable the Mysql integration is works perfect, so I'm thinking it
> has something to do with the mysql.so module?!?
>
> Thanks
>
> Todd