[Olsr-dev] [OLSRd 0000047]: memory leak on one remote end of point to point link

[Henning Rogge]

Hi,

I did some tests with olsrd but I was unable to trigger any kind of
(non-static) memory leak... even when switching on/off an interface
every few seconds.

Any ideas what else could trigger the strange behavior on the node?

Henning

On Thu, Dec 4, 2014 at 9:55 AM, (spam-protected)
<(spam-protected)> wrote:
> That node is not initiating vpn connection.
>
> On Thu, Dec 4, 2014 at 9:20 AM, Jernej Kos <(spam-protected)> wrote:
>> Hello!
>>
>> Looks like a failed VPN connection, but this doesn't seem related to the
>> memory leak to me.
>>
>>
>> Jernej
>>
>> On 04. 12. 2014 09:15, (spam-protected) wrote:
>>> Today there was one event on aljmas-luka-link-02 node I couldn't ping
>>> that node. Here is what has occurred in the logs at that time:
>>>
>>> Thu Dec  4 08:30:01 2014 cron.info crond[797]: crond: USER root pid
>>> 5969 cmd /usr/sbin/run-crons 30
>>> Thu Dec  4 08:30:48 2014 daemon.warn td-client: Failed to send()
>>> control packet (errno=146)!
>>> Thu Dec  4 08:34:25 2014 daemon.warn td-client: Failed to send()
>>> control packet (errno=146)!
>>> Thu Dec  4 08:35:01 2014 cron.info crond[797]: crond: USER root pid
>>> 7742 cmd /usr/sbin/run-crons 5
>>>
>>> If you take a look at attached Smokeping screenshot this is exactly
>>> when node was unreachable.
>>>
>>> Any ideas?
>>>
>>> On Mon, Nov 24, 2014 at 4:40 PM, Henning Rogge <(spam-protected)> wrote:
>>>> On Mon, Nov 24, 2014 at 3:22 PM, (spam-protected)
>>>> <(spam-protected)> wrote:
>>>>> aljmas-luka-link-02 is client that is connected to aljmas-luka-link-01 (AP).
>>>>> there is no issue on eth0 ports, they are stable, so there is probably
>>>>> no issue with ethernet cable, only with wifi...
>>>>>
>>>>> (spam-protected):~# logread |grep down
>>>>> Mon Nov 17 00:04:19 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 00:14:06 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 00:17:00 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 00:29:39 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 00:42:17 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 00:55:10 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 01:47:32 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 01:55:48 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>> Mon Nov 17 02:13:01 2014 daemon.notice netifd: Network device 'wlan0'
>>>>> link is down
>>>>
>>>> One "interface down" every 15 minutes... that doesn't sound like the
>>>> source of the problem.
>>>>
>>>> Henning
>>