It is a better practice to use a noload option in
modules.conf. That way if and when you upgrade you wont need to remove them
again they will just continue to not load
Alex
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
PedroSent: Monday, November 21, 2005
Yeah - tried that. Here are 2 lines I have in my modules.conf file:
noload = pbx_realtime.so
noload = app_realtime.so
For some reason, I still get the following in my logs even after a restart of Asterisk.
Nov 21 13:17:08 ERROR[31192] res_config_mysql.c: MySQL RealTime: Failed
to connect
Check the mysql logs. I would suspect from this one of several things:
1.) the userid/password is incorrect.
on the db host use the command lin e mysql client like so:
mysql -h localhost -u asterisk user -p
you'll be prompted for a password. If that works, go to the next
Pedro wrote:
Yeah - tried that. Here are 2 lines I have in my modules.conf file:
noload = pbx_realtime.so
noload = app_realtime.so
For some reason, I still get the following in my logs even after a
restart of Asterisk.
Nov 21 13:17:08 ERROR[31192] res_config_mysql.c: MySQL RealTime:
Thanks Bruce - but the whole point I am trying to accomplish is that I
don't want to use Realtime and don't want asterisk to try to establish
the connection. Was just chatting in IRC about this and it seems
that Realtime may not be able to be truly disabled (not sure how
accurate that is, but that
Olle,
Yep - was actually replying to this as I got your message - I was
searching for modules that had realtime in the name (did not see the
res_config_mysql.so file). Setting the noload =
res_config_mysql.so in modules.conf took care of the issue I was having.
Thanks for your prompt response!