RARE user and assistance email list

[Alexander Gall <>]

On Wed, 24 Aug 2022 17:49:02 +0200, mc36 <> said:

> nono! please please dont take it personally!

I don't, don't worry :)  I just didn't understand what the problem
was.

> nothing specifial, not the first and not the last bug, i get reports weekly 
> soo....
> and basically it was me as usual too, i just simply fucket it up again:
> https://github.com/rare-freertr/freeRtr/blob/master/src/net/freertr/serv/servP4langConn.java#L265
> but for now, i'm happy with the issue because at least we see who hit the 
> issue, until you push a new release...

I left the upgrade running yesterday before leaving the office and it
actually did finish despite the horrible connectivity. GVA0001 now has
the latest rare-nix release installed with freertr commit c6d49f. I
hope this has fixed the issue.

-- 
Alex


> On 8/24/22 17:44,  wrote:
>> On Wed, 24 Aug 2022 17:25:52 +0200, mc36 <> said:
>> 
>>> yes it is
>>> i already got 3 such messages...
>>> the message is just a consequence, but there are signs: getNextDynVrf
>>> i already have a patch but i decided apply it later
>> 
>>> so the best i can do is to kick off the dataplane if it does not sends me 
>>> the supported vrf range
>>> so if i apply the patch now, you'll still have a dead dataplane...
>>> so for now, as it sends me a traceback, at least i can notify you all...
>> 
>> Ok, it is finally dawning on me what you mean :) This is specific to
>> GVA0001. I didn't catch that until now. I thought it was a generic
>> thing about the rare-nix repo.
>> 
>> That host has a version of rare-nix installed with a slightly older
>> version of the forwarder and somebody has used "flash update" to
>> overwrite rtr.jar in the package, which is not reversible (yes,
>> everyone, please don't do that).
>> 
>> Frederic has actually tried to fix this with the
>> release-manager. However, the management network is currently so bad
>> at that location that this fails with a timeout (400kbps max and
>> probably tons of loss, virtually unusable). He has reached out the
>> GEANT NOC but no result yet AFAIK.
>>