From mellow.drifter at gmail.com  Sun Oct 20 13:31:55 2019
From: mellow.drifter at gmail.com (Darren O'Connor)
Date: Sun, 20 Oct 2019 09:31:55 -0400
Subject: [RPKI] Routinator memory usage
Message-ID: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>

Hi all.

I recently set up routinator to serve some bird2 instances. It is mentioned
that it was designed to be lean and use less than 1GB of RAM. However this
still seems like quite a lot.

Right now my current instance is using 556.7MB. Bird2 itself is using
1.2GB, but this instance has full IPv4 and IPv6 BGP tables from 10 peers.
So I'd expect that kind of usage.

On the other hand, half a gig used for 96k IPv4 roas and 16k IPv6 roas
seems high. What kind of memory usage do you think we'll see when 50% of
each table is signed?

Thanks
Darren (@mellowdrifter)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191020/6769c24a/attachment.htm>

From mellow.drifter at gmail.com  Sun Oct 20 17:11:30 2019
From: mellow.drifter at gmail.com (Darren O'Connor)
Date: Sun, 20 Oct 2019 13:11:30 -0400
Subject: [RPKI] Routinator memory usage
In-Reply-To: <303f8b3e7a4d6031aec6037f6e0a6bcd.squirrel@webmail.prolocation.net>
References: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
 <303f8b3e7a4d6031aec6037f6e0a6bcd.squirrel@webmail.prolocation.net>
Message-ID: <CAGTohBFXR6WEMRCCfuA7qnR37Zi3Y-p745MjmdsraQehTEoinw@mail.gmail.com>

Even stranger is that I have two instances on two identical servers. One is
550MB and the second is using 657MB. I'm not sure why.

On Sun, 20 Oct 2019, 13:08 Paul Hoogsteder, <paul at meanie.nl> wrote:

> That seems excessive. My routinator uses 116/139M at the moment. That's on
> Raspbian so not completely comparable but I guess most datastructures will
> be comparable in size.
>
> Paul.
>
> > Hi all.
> >
> > I recently set up routinator to serve some bird2 instances. It is
> > mentioned
> > that it was designed to be lean and use less than 1GB of RAM. However
> this
> > still seems like quite a lot.
> >
> > Right now my current instance is using 556.7MB. Bird2 itself is using
> > 1.2GB, but this instance has full IPv4 and IPv6 BGP tables from 10 peers.
> > So I'd expect that kind of usage.
> >
> > On the other hand, half a gig used for 96k IPv4 roas and 16k IPv6 roas
> > seems high. What kind of memory usage do you think we'll see when 50% of
> > each table is signed?
> >
> > Thanks
> > Darren (@mellowdrifter)
> > --
> > RPKI mailing list
> > RPKI at nlnetlabs.nl
> > https://www.nlnetlabs.nl/mailman/listinfo/rpki
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191020/3eea7dee/attachment.htm>

From paul at meanie.nl  Sun Oct 20 17:08:14 2019
From: paul at meanie.nl (Paul Hoogsteder)
Date: Sun, 20 Oct 2019 19:08:14 +0200
Subject: [RPKI] Routinator memory usage
In-Reply-To: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
References: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
Message-ID: <303f8b3e7a4d6031aec6037f6e0a6bcd.squirrel@webmail.prolocation.net>

That seems excessive. My routinator uses 116/139M at the moment. That's on
Raspbian so not completely comparable but I guess most datastructures will
be comparable in size.

Paul.

> Hi all.
>
> I recently set up routinator to serve some bird2 instances. It is
> mentioned
> that it was designed to be lean and use less than 1GB of RAM. However this
> still seems like quite a lot.
>
> Right now my current instance is using 556.7MB. Bird2 itself is using
> 1.2GB, but this instance has full IPv4 and IPv6 BGP tables from 10 peers.
> So I'd expect that kind of usage.
>
> On the other hand, half a gig used for 96k IPv4 roas and 16k IPv6 roas
> seems high. What kind of memory usage do you think we'll see when 50% of
> each table is signed?
>
> Thanks
> Darren (@mellowdrifter)
> --
> RPKI mailing list
> RPKI at nlnetlabs.nl
> https://www.nlnetlabs.nl/mailman/listinfo/rpki
>




From martin at nlnetlabs.nl  Mon Oct 21 09:37:50 2019
From: martin at nlnetlabs.nl (Martin Hoffmann)
Date: Mon, 21 Oct 2019 11:37:50 +0200
Subject: [RPKI] Routinator memory usage
In-Reply-To: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
References: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
Message-ID: <20191021113750.2dce2e80@glaurung.nlnetlabs.nl>

Hi Darren,

Darren O'Connor wrote:
> 
> I recently set up routinator to serve some bird2 instances. It is
> mentioned that it was designed to be lean and use less than 1GB of
> RAM. However this still seems like quite a lot.

It is, indeed. So far, we haven?t looked much at resource usage but
focused on getting all the features implemented and see the internal
architecture stabilize a bit. There?s one more significant change I
want to make (right now, trust anchors are processed in parallel which
I want to change to publication points because of APNIC, which already
has four and thus slows everything down). After that, I think we are on
the home stretch and can start looking at optimising resource usage.

I suspect that currently we are optimizing for speed over memory
consumption. For instance, we save on memory allocations by keeping
bigger objects around for longer. We?ll have try out different options
and see how they influence performance and resource usage.

Which is to say, we definitely have some work to do.

Kind regards,
Martin


From martin at nlnetlabs.nl  Mon Oct 21 09:40:30 2019
From: martin at nlnetlabs.nl (Martin Hoffmann)
Date: Mon, 21 Oct 2019 11:40:30 +0200
Subject: [RPKI] Routinator memory usage
In-Reply-To: <CAGTohBFXR6WEMRCCfuA7qnR37Zi3Y-p745MjmdsraQehTEoinw@mail.gmail.com>
References: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
 <303f8b3e7a4d6031aec6037f6e0a6bcd.squirrel@webmail.prolocation.net>
 <CAGTohBFXR6WEMRCCfuA7qnR37Zi3Y-p745MjmdsraQehTEoinw@mail.gmail.com>
Message-ID: <20191021114030.09e23c1a@glaurung.nlnetlabs.nl>

Darren O'Connor wrote:
> On Sun, 20 Oct 2019, 13:08 Paul Hoogsteder, <paul at meanie.nl> wrote:
> 
> > That seems excessive. My routinator uses 116/139M at the moment.
> > That's on Raspbian so not completely comparable but I guess most
> > datastructures will be comparable in size.
>
> Even stranger is that I have two instances on two identical servers.
> One is 550MB and the second is using 657MB. I'm not sure why.

It looks like memory consumption is tied to the number of validation
threads which defaults to the number of CPUs (or cores, rather). Paul?s
Pi probably has just one -- if I run Routinator with
--validation-threads 1, I get to a similar number.

Are you perhaps using VMs or somesuch with different number of cores
allocated?

Kind regards,
Martin


From mellow.drifter at gmail.com  Mon Oct 21 13:38:22 2019
From: mellow.drifter at gmail.com (Darren O'Connor)
Date: Mon, 21 Oct 2019 09:38:22 -0400
Subject: [RPKI] Routinator memory usage
In-Reply-To: <20191021114030.09e23c1a@glaurung.nlnetlabs.nl>
References: <CAGTohBEB_AEV56GKE0zqWRYWoa4fQxLmqCea+TFhYUqMb=3g9w@mail.gmail.com>
 <303f8b3e7a4d6031aec6037f6e0a6bcd.squirrel@webmail.prolocation.net>
 <CAGTohBFXR6WEMRCCfuA7qnR37Zi3Y-p745MjmdsraQehTEoinw@mail.gmail.com>
 <20191021114030.09e23c1a@glaurung.nlnetlabs.nl>
Message-ID: <CAGTohBHbJ0OO=zD5Ce3EJ+TxDQL6QGtns4x0eEiPfaHHspBGww@mail.gmail.com>

Heya.

Hope, both are VMs yes, but they are provisioned identically. Looking a bit
deeper each server is using a slightly different 'version' of the CPU:

cat /proc/cpuinfo | grep mode
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz

 cat /proc/cpuinfo  | grep mode
model           : 63
model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
model           : 63
model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz

One thing I notice is that on the server using more memory right now, it
has more logs about rsync timeouts:

? routinator.service - Routinator 3000
   Loaded: loaded (/etc/systemd/system/routinator.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2019-10-19 21:59:07 EDT; 1 day 11h ago
     Docs: man:routinator(1)
 Main PID: 27905 (routinator)
    Tasks: 8 (limit: 4626)
   Memory: 747.3M
   CGroup: /system.slice/routinator.service
           ??27905 /root/.cargo/bin/routinator server --rtr 127.0.0.1:3323

Oct 21 09:10:35 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with
status exit code: 35
Oct 21 09:10:35 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync
error: timeout waiting for daemon connectio
Oct 21 09:20:53 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with
status exit code: 35
Oct 21 09:20:53 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync
error: timeout waiting for daemon connectio
Oct 21 09:21:10 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap:
failed with status exit code: 35
Oct 21 09:21:10 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap:
rsync error: timeout waiting for da
Oct 21 09:31:35 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap:
failed with status exit code: 35
Oct 21 09:31:35 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap:
rsync error: timeout waiting for da
Oct 21 09:31:48 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with
status exit code: 35
Oct 21 09:31:48 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync
error: timeout waiting for daemon connection


? routinator.service - Routinator 3000
   Loaded: loaded (/etc/systemd/system/routinator.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sun 2019-10-20 17:47:29 EDT; 15h ago
 Main PID: 23658 (routinator)
    Tasks: 8 (limit: 4626)
   Memory: 645.9M
   CGroup: /system.slice/routinator.service
           ??23658 /root/.cargo/bin/routinator server --rtr 127.0.0.1:3323

Oct 20 20:57:14 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: failed with status exit code: 3
Oct 20 20:57:14 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: rsync error: timeout waiting fo
Oct 20 21:07:43 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: failed with status exit code: 3
Oct 20 21:07:43 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: rsync error: timeout waiting fo
Oct 20 21:18:12 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: failed with status exit code: 3
Oct 20 21:18:12 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: rsync error: timeout waiting fo
Oct 20 21:28:55 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: failed with status exit code: 3
Oct 20 21:28:55 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: rsync error: timeout waiting fo
Oct 20 21:39:24 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: failed with status exit code: 3
Oct 20 21:39:24 bgp1 rpki-routinator[23658]: rsync://
rpki.afrinic.net/repository: rsync error: timeout waiting fo


I might be completely wrong here, but maybe the memory is increasing each
time there is a timeout?

Thanks
Darren

On Mon, 21 Oct 2019 at 05:40, Martin Hoffmann <martin at nlnetlabs.nl> wrote:

> Darren O'Connor wrote:
> > On Sun, 20 Oct 2019, 13:08 Paul Hoogsteder, <paul at meanie.nl> wrote:
> >
> > > That seems excessive. My routinator uses 116/139M at the moment.
> > > That's on Raspbian so not completely comparable but I guess most
> > > datastructures will be comparable in size.
> >
> > Even stranger is that I have two instances on two identical servers.
> > One is 550MB and the second is using 657MB. I'm not sure why.
>
> It looks like memory consumption is tied to the number of validation
> threads which defaults to the number of CPUs (or cores, rather). Paul?s
> Pi probably has just one -- if I run Routinator with
> --validation-threads 1, I get to a similar number.
>
> Are you perhaps using VMs or somesuch with different number of cores
> allocated?
>
> Kind regards,
> Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191021/cdcfdc8f/attachment.htm>

From muhammadyasirshamim at gmail.com  Tue Oct 22 11:52:37 2019
From: muhammadyasirshamim at gmail.com (Muhammad Yasir Shamim)
Date: Tue, 22 Oct 2019 16:52:37 +0500
Subject: [RPKI] Fwd:  Routinator memory usage
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
Message-ID: <042173F4-86D6-449B-A650-3E304616C362@gmail.com>


> Hi 
> 
> I am getting an error while establishing a session between with Routinator.
> 
> routinator server --rtr 124.29.243.110:3323 --refresh=300       -------------------------------------> 124.29.243.110:3323  is the routinator server IP.
> Failed to bind RTR listener 124.29.243.110:3323: Address already in use (os error 98)
> 
> I am using Juniper, 
> 
> autonomous-system 9541;
> validation {
>     group rpki {
>         session 124.29.243.110 {
>             refresh-time 30;
>             port 3323;
>             local-address 124.29.246.101;
> 
> show validation session    
> Session                                  State   Flaps     Uptime #IPv4/IPv6 records
> 124.29.243.110                           Connect     0            0/0
> 
> ---------- Forwarded message ---------
> From: Muhammad Yasir Shamim <muhammadyasirshamim at gmail.com>
> Date: Tue, Oct 22, 2019 at 4:46 PM
> Subject: Re: [RPKI] Routinator memory usage
> To: Darren O'Connor <mellow.drifter at gmail.com>
> 
> 
> Hi 
> 
> I am getting an error while establishing a session between with Routinator.
> 
> routinator server --rtr 124.29.243.110:3323 --refresh=300       -------------------------------------> 124.29.243.110:3323  is the routinator server IP.
> Failed to bind RTR listener 124.29.243.110:3323: Address already in use (os error 98)
> 
> I am using Juniper, 
> 
> autonomous-system 9541;
> validation {
>     group rpki {
>         session 124.29.243.110 {
>             refresh-time 30;
>             port 3323;
>             local-address 124.29.246.101;
> 
> show validation session     
> Session                                  State   Flaps     Uptime #IPv4/IPv6 records
> 124.29.243.110                           Connect     0            0/0
> 
> 
> 	Virus-free. www.avast.com
> 
>> On Mon, Oct 21, 2019 at 6:40 PM Darren O'Connor <mellow.drifter at gmail.com> wrote:
>> Heya.
>> 
>> Hope, both are VMs yes, but they are provisioned identically. Looking a bit deeper each server is using a slightly different 'version' of the CPU:
>> 
>> cat /proc/cpuinfo | grep mode
>> model           : 45
>> model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
>> model           : 45
>> model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
>> 
>>  cat /proc/cpuinfo  | grep mode
>> model           : 63
>> model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
>> model           : 63
>> model name      : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
>> 
>> One thing I notice is that on the server using more memory right now, it has more logs about rsync timeouts:
>> 
>> ? routinator.service - Routinator 3000
>>    Loaded: loaded (/etc/systemd/system/routinator.service; enabled; vendor preset: enabled)
>>    Active: active (running) since Sat 2019-10-19 21:59:07 EDT; 1 day 11h ago
>>      Docs: man:routinator(1)
>>  Main PID: 27905 (routinator)
>>     Tasks: 8 (limit: 4626)
>>    Memory: 747.3M
>>    CGroup: /system.slice/routinator.service
>>            ??27905 /root/.cargo/bin/routinator server --rtr 127.0.0.1:3323
>> 
>> Oct 21 09:10:35 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with status exit code: 35
>> Oct 21 09:10:35 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync error: timeout waiting for daemon connectio
>> Oct 21 09:20:53 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with status exit code: 35
>> Oct 21 09:20:53 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync error: timeout waiting for daemon connectio
>> Oct 21 09:21:10 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap: failed with status exit code: 35
>> Oct 21 09:21:10 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap: rsync error: timeout waiting for da
>> Oct 21 09:31:35 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap: failed with status exit code: 35
>> Oct 21 09:31:35 bgp2 routinator[27905]: rsync://rpki-repository.nic.ad.jp/ap: rsync error: timeout waiting for da
>> Oct 21 09:31:48 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: failed with status exit code: 35
>> Oct 21 09:31:48 bgp2 routinator[27905]: rsync://ca.rg.net/rpki: rsync error: timeout waiting for daemon connection
>> 
>> 
>> ? routinator.service - Routinator 3000
>>    Loaded: loaded (/etc/systemd/system/routinator.service; enabled; vendor preset: enabled)
>>    Active: active (running) since Sun 2019-10-20 17:47:29 EDT; 15h ago
>>  Main PID: 23658 (routinator)
>>     Tasks: 8 (limit: 4626)
>>    Memory: 645.9M
>>    CGroup: /system.slice/routinator.service
>>            ??23658 /root/.cargo/bin/routinator server --rtr 127.0.0.1:3323
>> 
>> Oct 20 20:57:14 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: failed with status exit code: 3
>> Oct 20 20:57:14 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: rsync error: timeout waiting fo
>> Oct 20 21:07:43 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: failed with status exit code: 3
>> Oct 20 21:07:43 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: rsync error: timeout waiting fo
>> Oct 20 21:18:12 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: failed with status exit code: 3
>> Oct 20 21:18:12 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: rsync error: timeout waiting fo
>> Oct 20 21:28:55 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: failed with status exit code: 3
>> Oct 20 21:28:55 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: rsync error: timeout waiting fo
>> Oct 20 21:39:24 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: failed with status exit code: 3
>> Oct 20 21:39:24 bgp1 rpki-routinator[23658]: rsync://rpki.afrinic.net/repository: rsync error: timeout waiting fo
>> 
>> 
>> I might be completely wrong here, but maybe the memory is increasing each time there is a timeout?
>> 
>> Thanks
>> Darren
>> 
>>> On Mon, 21 Oct 2019 at 05:40, Martin Hoffmann <martin at nlnetlabs.nl> wrote:
>>> Darren O'Connor wrote:
>>> > On Sun, 20 Oct 2019, 13:08 Paul Hoogsteder, <paul at meanie.nl> wrote:
>>> > 
>>> > > That seems excessive. My routinator uses 116/139M at the moment.
>>> > > That's on Raspbian so not completely comparable but I guess most
>>> > > datastructures will be comparable in size.
>>> >
>>> > Even stranger is that I have two instances on two identical servers.
>>> > One is 550MB and the second is using 657MB. I'm not sure why.
>>> 
>>> It looks like memory consumption is tied to the number of validation
>>> threads which defaults to the number of CPUs (or cores, rather). Paul?s
>>> Pi probably has just one -- if I run Routinator with
>>> --validation-threads 1, I get to a similar number.
>>> 
>>> Are you perhaps using VMs or somesuch with different number of cores
>>> allocated?
>>> 
>>> Kind regards,
>>> Martin
>> -- 
>> RPKI mailing list
>> RPKI at nlnetlabs.nl
>> https://www.nlnetlabs.nl/mailman/listinfo/rpki
> 
> 
> -- 
> Cheers
> Yasir
> 
> 	Virus-free. www.avast.com
> 
> 
> -- 
> Cheers
> Yasir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191022/a298a05b/attachment.htm>

From martin at nlnetlabs.nl  Tue Oct 22 12:24:02 2019
From: martin at nlnetlabs.nl (Martin Hoffmann)
Date: Tue, 22 Oct 2019 14:24:02 +0200
Subject: [RPKI] Fwd:  Routinator memory usage
In-Reply-To: <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
 <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
Message-ID: <20191022142402.0b080535@glaurung.nlnetlabs.nl>

Hi,

Muhammad Yasir Shamim wrote:
> > 
> > I am getting an error while establishing a session between with
> > Routinator.
> > 
> > routinator server --rtr 124.29.243.110:3323 --refresh=300
> > -------------------------------------> 124.29.243.110:3323  is the
> > routinator server IP. Failed to bind RTR listener
> > 124.29.243.110:3323: Address already in use (os error 98)

This typically means that there is already something on your machine
listening on that port. You can find out the process ID of that by
running "netstat -lntp" as root.

HTH and kind regards,
Martin


From muhammadyasirshamim at gmail.com  Tue Oct 22 21:11:14 2019
From: muhammadyasirshamim at gmail.com (Muhammad Yasir Shamim)
Date: Wed, 23 Oct 2019 02:11:14 +0500
Subject: [RPKI] Fwd: Routinator memory usage
In-Reply-To: <20191022142402.0b080535@glaurung.nlnetlabs.nl>
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
 <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
 <20191022142402.0b080535@glaurung.nlnetlabs.nl>
Message-ID: <CALmbqArFWJA=fqzm9w0HHRMj9bW++bd78KVBi+=JLGO6zHh_Cw@mail.gmail.com>

Hi Martin

I verify it and nothing have been listening on that port, only the server
IP is listening the DNS queries on port 53. Due to limited access I
wouldn't be able to share the output. What are the other possibilities of
having an os error 98.

Regards
Yasir

On Tue, Oct 22, 2019 at 5:24 PM Martin Hoffmann <martin at nlnetlabs.nl> wrote:

> Hi,
>
> Muhammad Yasir Shamim wrote:
> > >
> > > I am getting an error while establishing a session between with
> > > Routinator.
> > >
> > > routinator server --rtr 124.29.243.110:3323 --refresh=300
> > > -------------------------------------> 124.29.243.110:3323  is the
> > > routinator server IP. Failed to bind RTR listener
> > > 124.29.243.110:3323: Address already in use (os error 98)
>
> This typically means that there is already something on your machine
> listening on that port. You can find out the process ID of that by
> running "netstat -lntp" as root.
>
> HTH and kind regards,
> Martin
>


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191023/80013faf/attachment.htm>

From muhammadyasirshamim at gmail.com  Wed Oct 23 06:19:03 2019
From: muhammadyasirshamim at gmail.com (Muhammad Yasir Shamim)
Date: Wed, 23 Oct 2019 11:19:03 +0500
Subject: [RPKI] Fwd: Routinator memory usage
In-Reply-To: <CALmbqArFWJA=fqzm9w0HHRMj9bW++bd78KVBi+=JLGO6zHh_Cw@mail.gmail.com>
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
 <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
 <20191022142402.0b080535@glaurung.nlnetlabs.nl>
 <CALmbqArFWJA=fqzm9w0HHRMj9bW++bd78KVBi+=JLGO6zHh_Cw@mail.gmail.com>
Message-ID: <CALmbqAqffJTVwDcgsSjC4u=9dwOVwfB2_LEDqisYGaUjE2mCOw@mail.gmail.com>

Hi

On Junos its showing in connect state.

validation {
    group rpki {
        session 124.29.243.110 {
            refresh-time 30;
            port 3323;

show validation session
Session                                  State   Flaps     Uptime
#IPv4/IPv6 records
124.29.243.110                           Connect     0            0/0

whereas on the server it is listening on on port 3323.

tcp        0      0 124.29.243.110:3323     0.0.0.0:*               LISTEN
     -

Please assist.

Regards
Yasir

On Wed, Oct 23, 2019 at 2:11 AM Muhammad Yasir Shamim <
muhammadyasirshamim at gmail.com> wrote:

> Hi Martin
>
> I verify it and nothing have been listening on that port, only the server
> IP is listening the DNS queries on port 53. Due to limited access I
> wouldn't be able to share the output. What are the other possibilities of
> having an os error 98.
>
> Regards
> Yasir
>
> On Tue, Oct 22, 2019 at 5:24 PM Martin Hoffmann <martin at nlnetlabs.nl>
> wrote:
>
>> Hi,
>>
>> Muhammad Yasir Shamim wrote:
>> > >
>> > > I am getting an error while establishing a session between with
>> > > Routinator.
>> > >
>> > > routinator server --rtr 124.29.243.110:3323 --refresh=300
>> > > -------------------------------------> 124.29.243.110:3323  is the
>> > > routinator server IP. Failed to bind RTR listener
>> > > 124.29.243.110:3323: Address already in use (os error 98)
>>
>> This typically means that there is already something on your machine
>> listening on that port. You can find out the process ID of that by
>> running "netstat -lntp" as root.
>>
>> HTH and kind regards,
>> Martin
>>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> <#m_-3477448137726928605_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191023/75b0724d/attachment.htm>

From martin at nlnetlabs.nl  Wed Oct 23 12:01:02 2019
From: martin at nlnetlabs.nl (Martin Hoffmann)
Date: Wed, 23 Oct 2019 14:01:02 +0200
Subject: [RPKI] Fwd: Routinator memory usage
In-Reply-To: <CALmbqAqffJTVwDcgsSjC4u=9dwOVwfB2_LEDqisYGaUjE2mCOw@mail.gmail.com>
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
 <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
 <20191022142402.0b080535@glaurung.nlnetlabs.nl>
 <CALmbqArFWJA=fqzm9w0HHRMj9bW++bd78KVBi+=JLGO6zHh_Cw@mail.gmail.com>
 <CALmbqAqffJTVwDcgsSjC4u=9dwOVwfB2_LEDqisYGaUjE2mCOw@mail.gmail.com>
Message-ID: <20191023140102.48b3149d@glaurung.nlnetlabs.nl>

Hi Yasir,

this looks like everything is working as expected? Router is connected
and Routinator is listening on 3323?

Kind regards,
Martin

Muhammad Yasir Shamim wrote:
> Hi
> 
> On Junos its showing in connect state.
> 
> validation {
>     group rpki {
>         session 124.29.243.110 {
>             refresh-time 30;
>             port 3323;
> 
> show validation session
> Session                                  State   Flaps     Uptime
> #IPv4/IPv6 records
> 124.29.243.110                           Connect     0            0/0
> 
> whereas on the server it is listening on on port 3323.
> 
> tcp        0      0 124.29.243.110:3323     0.0.0.0:*
> LISTEN -
> 
> Please assist.
> 
> Regards
> Yasir
> 
> On Wed, Oct 23, 2019 at 2:11 AM Muhammad Yasir Shamim <
> muhammadyasirshamim at gmail.com> wrote:  
> 
> > Hi Martin
> >
> > I verify it and nothing have been listening on that port, only the
> > server IP is listening the DNS queries on port 53. Due to limited
> > access I wouldn't be able to share the output. What are the other
> > possibilities of having an os error 98.
> >
> > Regards
> > Yasir
> >
> > On Tue, Oct 22, 2019 at 5:24 PM Martin Hoffmann
> > <martin at nlnetlabs.nl> wrote:
> >  
> >> Hi,
> >>
> >> Muhammad Yasir Shamim wrote:  
> >> > >
> >> > > I am getting an error while establishing a session between with
> >> > > Routinator.
> >> > >
> >> > > routinator server --rtr 124.29.243.110:3323 --refresh=300  
> >> > > -------------------------------------> 124.29.243.110:3323  is
> >> > > the routinator server IP. Failed to bind RTR listener
> >> > > 124.29.243.110:3323: Address already in use (os error 98)  
> >>
> >> This typically means that there is already something on your
> >> machine listening on that port. You can find out the process ID of
> >> that by running "netstat -lntp" as root.
> >>
> >> HTH and kind regards,
> >> Martin
> >>  
> >
> >
> >
> > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
> > Virus-free. www.avast.com
> > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> > <#m_-3477448137726928605_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >  



From stavros.konstantaras at ams-ix.net  Wed Oct 23 12:11:20 2019
From: stavros.konstantaras at ams-ix.net (Stavros Konstantaras)
Date: Wed, 23 Oct 2019 14:11:20 +0200
Subject: [RPKI] Fwd: Routinator memory usage
In-Reply-To: <20191023140102.48b3149d@glaurung.nlnetlabs.nl>
References: <CALmbqArrq+9JYc9qyqKvcSC9zCU-sCsPzcNv_NNXU5aszYi=KA@mail.gmail.com>
 <042173F4-86D6-449B-A650-3E304616C362@gmail.com>
 <20191022142402.0b080535@glaurung.nlnetlabs.nl>
 <CALmbqArFWJA=fqzm9w0HHRMj9bW++bd78KVBi+=JLGO6zHh_Cw@mail.gmail.com>
 <CALmbqAqffJTVwDcgsSjC4u=9dwOVwfB2_LEDqisYGaUjE2mCOw@mail.gmail.com>
 <20191023140102.48b3149d@glaurung.nlnetlabs.nl>
Message-ID: <A9F8B69D-B1B9-440F-92B0-82FA374EACB7@ams-ix.net>

Hi Martin,

For Junos the state should be ?UP? and show the uptime of the connection instead of ?connect.

@Yasir, can you check on your Juniper router the ACL of your management interface to see if you allow the IP + port of your Routinator instance ? If that looks good, can you check your iptables config on your Routinator?s server for any misconfiguration? 


Best regards,

Stavros Konstantaras | NOC Engineer | AMS-IX 
M +31 (0) 620 89 51 04 | T +31 20 305 8999
ams-ix.net

> On 23 Oct 2019, at 14:01, Martin Hoffmann <martin at nlnetlabs.nl> wrote:
> 
> Hi Yasir,
> 
> this looks like everything is working as expected? Router is connected
> and Routinator is listening on 3323?
> 
> Kind regards,
> Martin
> 
> Muhammad Yasir Shamim wrote:
>> Hi
>> 
>> On Junos its showing in connect state.
>> 
>> validation {
>>    group rpki {
>>        session 124.29.243.110 {
>>            refresh-time 30;
>>            port 3323;
>> 
>> show validation session
>> Session                                  State   Flaps     Uptime
>> #IPv4/IPv6 records
>> 124.29.243.110                           Connect     0            0/0
>> 
>> whereas on the server it is listening on on port 3323.
>> 
>> tcp        0      0 124.29.243.110:3323     0.0.0.0:*
>> LISTEN -
>> 
>> Please assist.
>> 
>> Regards
>> Yasir
>> 
>> On Wed, Oct 23, 2019 at 2:11 AM Muhammad Yasir Shamim <
>> muhammadyasirshamim at gmail.com> wrote:  
>> 
>>> Hi Martin
>>> 
>>> I verify it and nothing have been listening on that port, only the
>>> server IP is listening the DNS queries on port 53. Due to limited
>>> access I wouldn't be able to share the output. What are the other
>>> possibilities of having an os error 98.
>>> 
>>> Regards
>>> Yasir
>>> 
>>> On Tue, Oct 22, 2019 at 5:24 PM Martin Hoffmann
>>> <martin at nlnetlabs.nl> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Muhammad Yasir Shamim wrote:  
>>>>>> 
>>>>>> I am getting an error while establishing a session between with
>>>>>> Routinator.
>>>>>> 
>>>>>> routinator server --rtr 124.29.243.110:3323 --refresh=300  
>>>>>> -------------------------------------> 124.29.243.110:3323  is
>>>>>> the routinator server IP. Failed to bind RTR listener
>>>>>> 124.29.243.110:3323: Address already in use (os error 98)  
>>>> 
>>>> This typically means that there is already something on your
>>>> machine listening on that port. You can find out the process ID of
>>>> that by running "netstat -lntp" as root.
>>>> 
>>>> HTH and kind regards,
>>>> Martin
>>>> 
>>> 
>>> 
>>> 
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>>
>>> Virus-free. www.avast.com <http://www.avast.com/>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>>
>>> <#m_-3477448137726928605_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> 
> 
> -- 
> RPKI mailing list
> RPKI at nlnetlabs.nl <mailto:RPKI at nlnetlabs.nl>
> https://www.nlnetlabs.nl/mailman/listinfo/rpki <https://www.nlnetlabs.nl/mailman/listinfo/rpki>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191023/1e0ec356/attachment.htm>