loadmodule order is significant. I don't think I ever realized that<br>
before. So, Bogdan's original question as to whether cassandra was loaded<br>
or not is the answer to my problem. After changing the order of the<br>
loadmodule statements Opensips loads just fine.<br>
<br>
Thank you both for responding and thank you Vlad for the sample. Seeing it<br>
caused me to question if load order could be the problem.<br>
<br>
Richard<br>
<br>
<br>
On Wed, Mar 19, 2014 at 12:19 PM, vladpaiu <notifications@github.com> wrote:<br>
<br>
> Hello,<br>
><br>
> Which version of OpenSIPS are you using ? Latest trunk ?<br>
> I just ran a quick test against trunk :<br>
><br>
> loadmodule "cachedb_cassandra.so"<br>
> loadmodule "dialog.so"<br>
> modparam("dialog","cachedb_url","cassandra://127.0.0.1:9160/A_B_C")<br>
><br>
> and connections was good :<br>
><br>
> Mar 19 17:58:11 [4455] INFO:dialog:mod_init: Dialog module - initializing<br>
> Mar 19 17:58:11 [4455] INFO:cachedb_cassandra:cassandra_init_connection:<br>
> Keyspace = [A]. ColumnFamily = [B]. CounterFamily = [C]<br>
><br>
> Can you help in replicating this ?<br>
><br>
> Best Regards,<br>
> Vlad<br>
><br>
> --<br>
> Reply to this email directly or view it on GitHub<https://github.com/OpenSIPS/opensips/issues/179#issuecomment-38071603><br>
> .<br>
>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/OpenSIPS/opensips/issues/179#issuecomment-38084426'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxMDg3MDc0MSwiZGF0YSI6eyJpZCI6Mjc3NzA5MzV9fQ==--3ab10efa1a8127df2924d91866e5eae60350c14b.gif' height='1' width='1'></p>