<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 26, 2014 at 2:55 PM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Thu, Jun 26, 2014 at 2:25 PM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">After upgrading to FS commit af0ded1 (2014/03/18), freeswitch_licence_server it not working properly.<div>
It starts, but without outputting the expected</div><div> XX channels of G.729A<br><div><br></div><div>
So it is alive</div><div><div><br></div><div>[root@garam ~]# ps -e|grep fre</div><div> 2021 ? 00:58:24 freeswitch</div><div> 5777 ? 00:00:00 freeswitch_lice</div></div><div><br></div><div>but i get this from fs_cli:</div>
<div><br></div><div><div>[root@garam ~]# bancmd fs_cli<br></div><div>...</div><div>freeswitch@192.168.88.58@internal> g729_info</div><div>Can't contact licence server.</div></div><div><br></div><div>However, this only happens in one host. On another host i get this:</div>
<div><br></div><div><div>Scanning /etc/freeswitch/XXXXXXXXXXXXXXXXXXXX.conf for licences</div><div>Purchase code XXXXXXXXXXXXXXXXXXXX</div><div>20 channels of G.729A</div><div><br></div></div></div><div>and it works fine.</div>
<div><br></div><div>But since on the failed host freeswitch_licence_server doesn't output any error message, I don't know what would be the problem.</div><div><br></div><div>Any tips on how to investigate this?</div>
</div></blockquote><div><br></div></div></div><div>For completeness, we also upgraded the OS from CentOS 5.4 to CentOS 6.5 but we didn't change NICs etc (although in this host we have bond interfaces over the eth interfaces and we don't have those in the OK host).</div>
</div></div></div></blockquote><div><br></div><div>I Think I know what happened.</div><div>In the new host the eth interfaces were switched (eth0 is using the MAC address that was previously set to eth1 and vice-versa).</div>
<div>There is no error message indicating this but it is probably the reason. I will check.</div></div><br></div></div>