ejabberd - Comments for "concerned that running wrong mySQL driver and or wrong schema for mod_offline_odbc" https://www.ejabberd.im/node/5632 en It works. The very last "mod" https://www.ejabberd.im/node/5632#comment-58826 <p>It works.</p> <p>The very last "mod" that I have yet to successfully move over is pub sub. That one throws an error, but I think that is my config'. All other modules are moved over to ODBC now.</p> <p>Thanks all. </p> <p>I'll go hang a shingle on our website that we are now "ejabbered experts for hire".</p> <p>Cheers.</p> <p>Jason<br /> S I P</p> Sat, 16 Jun 2012 18:42:50 +0000 anonymous@domain.tld comment 58826 at https://www.ejabberd.im This seems to have helped a https://www.ejabberd.im/node/5632#comment-58825 <p>This seems to have helped a lot. I hope these notes help someone else.</p> <p><noindex><a href="https://support.process-one.net/doc/display/MESSENGER/Using+relational+databases" title="https://support.process-one.net/doc/display/MESSENGER/Using+relational+databases" rel="nofollow" >https://support.process-one.net/doc/display/MESSENGER/Using+relational+d...</a></noindex></p> <p>Specifically, the "R13" set of files that I copied in to /usr/lib64/ejabberd/ebin/ The "R14" files did not work for me (ejabberd-2.1.11-1.el5 running on centOS 5.8 64bit). The "R14" files threw this error:</p> <p>Loading of /usr/lib64/ejabberd/ebin/mysql_conn.beam failed: badfile</p> <p>I now see connections to the mySQL database server.</p> <p>I am updating as I go. </p> <p>Now to get actual usable records to flow back-n-forth.</p> Sat, 16 Jun 2012 18:14:54 +0000 anonymous@domain.tld comment 58825 at https://www.ejabberd.im Thanks, Mike, but in this https://www.ejabberd.im/node/5632#comment-58823 <p>Thanks, Mike, but in this specific instance, I am confident that this is not related to mySQL permissions. I say that for a couple of reasons: we run a dedicated mySQL server in-house with many many dozens of DB's inside of it &amp; each is set-up in a similar way, with a dedicated connection account and privileges, and we did the same thing here for eJabber. And here is the big one, the error is "module could not be loaded". This thing is not even trying or attempting to touch the DB server yet. It can't even load the SQL module. Once the module is loaded, it will reach out to touch the DB and we will see what happens then. Right now, the module is our issue. </p> <p>Any one out there know how to get the SQL/mySQL/ODBC modules to load-up correctly at time of daemon start? </p> <p>Please.</p> <p>Thanks.</p> <p>Jason</p> Sat, 16 Jun 2012 16:28:25 +0000 anonymous@domain.tld comment 58823 at https://www.ejabberd.im Honestly, I don't know the https://www.ejabberd.im/node/5632#comment-58822 <p>Honestly, I don't know the "best practices" here, as I don't use ODBC. My usecase is limited to insite LDAP-based IM.</p> <p>But maybe this information is relevant. <noindex><a href="http://syslinux.ru/node/56" rel="nofollow" >This page</a></noindex> tells that there's a step that made that person to hit a wall: the ejabberd user in mysql needs to be granted rights to the database:</p> <p><code>mysql&gt;GRANT SELECT,INSERT,UPDATE,CREATE ON jabber.* TO&nbsp; ejabberd@localhost&nbsp; IDENTIFIED BY &quot;yourpassword&quot;;</code></p> <p>HTH</p> Fri, 15 Jun 2012 11:52:40 +0000 mikekaganski comment 58822 at https://www.ejabberd.im mikekaganski wrote: So you https://www.ejabberd.im/node/5632#comment-58819 <div class="quote-msg"> <div class="quote-author"><em>mikekaganski</em> wrote:</div> <p>So you use "MySQL in native mode instead of the ODBC generic mode"?</p> <p>What other modules are working OK with this mode?<br /> Or do you use native MySQL for mod_offline_odbc only? If so, what are the reasons to do so? Maybe it's practical to check the usual configuration first?</p></div> <p>Thanks, Mike. You know, now that you ask, I must admit that I do not exactly know those answers. If I mis-stated, I didn't mean to. I guess I ought to know for certain the answers to those questions before I go on. Can you kindly let me know how I would know one or the other? I can say this, all I have been doing in the "conf" file is playing with adding or removing "_odbc" to the end of the lines. I thought that that would in turn tell the daemon to see the ODBC configuration section, which in turn would be my database server configuration line, which in my case would be a dedicated mySQL server on our LAN. If I have misunderstand how that works, then I need to be put straight. :) </p> <p>Let me ask this, what is best practice here? native driver? or generic driver? or what? </p> <p>I need to add one very important piece of information here, this is installed on centOS 5.x from the repo' using yum (i.e.: rpm) and nothing else has changed *except* my dropping the above referenced files in to that directory and restarting the daemon. </p> <p>Thanks much.</p> <p>Jason</p> Fri, 15 Jun 2012 06:15:58 +0000 anonymous@domain.tld comment 58819 at https://www.ejabberd.im So you use "MySQL in native https://www.ejabberd.im/node/5632#comment-58817 <p>So you use "MySQL in native mode instead of the ODBC generic mode"?</p> <p>What other modules are working OK with this mode?<br /> Or do you use native MySQL for mod_offline_odbc only? If so, what are the reasons to do so? Maybe it's practical to check the usual configuration first?</p> Thu, 14 Jun 2012 22:14:53 +0000 mikekaganski comment 58817 at https://www.ejabberd.im