#154 Duplicate ACS signalled for ipn:1.0...

[Pat Cappelaere]

While testing bpcp, I encountered a flurry of errors in the ion.log

[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.10 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 241 of bp/library/acs/acsappend.c, Found existing custody signal (SUCCESS,0)
[2021/02/11-15:24:48] at line 419 of bp/library/acs/acsappend.c, Duplicate ACS signalled for ipn:1.0, ignored.
[2021/02/11-15:24:48] [2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,10,0,0) in bidHash to destroy
[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.11 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 244 of bp/library/acs/acstx.c, Couldn't find ACS signal (success, 0)
[2021/02/11-15:24:48] at line 247 of bp/library/acs/acsappend.c, Making new custody signal for (SUCCESS,0)
[2021/02/11-15:24:48] at line 326 of bp/library/acs/acsappend.c, SACK: to ipn:1.0, 90376(1)
[2021/02/11-15:24:48] at line 467 of bp/library/acs/acstx.c, Serialized a new ACS to ipn:1.0 that is 6 long (old: 0)
[2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,11,0,0) in bidHash to destroy
[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.12 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 241 of bp/library/acs/acsappend.c, Found existing custody signal (SUCCESS,0)
[2021/02/11-15:24:48] at line 326 of bp/library/acs/acsappend.c, SACK: to ipn:1.0, 90376(1) +90378(1)
[2021/02/11-15:24:48] at line 467 of bp/library/acs/acstx.c, Serialized a new ACS to ipn:1.0 that is 8 long (old: 6)
[2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,12,0,0) in bidHash to destroy

This is really flooding the log file.....
How do I clear that kind of error?
Thanks,
Pat.

[Scott Burleigh]

These bogus ACS error messages are annoying but apparently harmless, so they will most likely not receive immediate attention since we are now focusing on BPv7. For now, I would suggest that you simply disable custody transfer when you run bpcp (use the "-C" option); it's not needed if you're using reliable convergence-layer protocols under Bundle Protocol.

Scott

From: Pat Cappelaere cappelaere@users.sourceforge.net
Sent: Thursday, February 11, 2021 8:23 AM
To: Ticket #154: Duplicate ACS signalled for ipn:1.0... 154@bugs.ion-dtn.p.re.sourceforge.net
Subject: [EXTERNAL] [ion-dtn:bugs] #154 Duplicate ACS signalled for ipn:1.0...

---

[bugs:#154]https://urldefense.us/v3/__https:/sourceforge.net/p/ion-dtn/bugs/154/__;!!PvBDto6Hs4WbVuu7!dXLJ4UdopPHGg08ydhkeT8Dnmc-9L0ODx8StCxkFUjuSbp9GOJSWOVxGpTtpCbvUlMHHfm8RAJc$ Duplicate ACS signalled for ipn:1.0...

Status: open
Group: 3.7.0
Created: Thu Feb 11, 2021 04:23 PM UTC by Pat Cappelaere
Last Updated: Thu Feb 11, 2021 04:23 PM UTC
Owner: nobody

While testing bpcp, I encountered a flurry of errors in the ion.log

[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.10 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 241 of bp/library/acs/acsappend.c, Found existing custody signal (SUCCESS,0)
[2021/02/11-15:24:48] at line 419 of bp/library/acs/acsappend.c, Duplicate ACS signalled for ipn:1.0, ignored.
[2021/02/11-15:24:48] [2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,10,0,0) in bidHash to destroy
[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.11 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 244 of bp/library/acs/acstx.c, Couldn't find ACS signal (success, 0)
[2021/02/11-15:24:48] at line 247 of bp/library/acs/acsappend.c, Making new custody signal for (SUCCESS,0)
[2021/02/11-15:24:48] at line 326 of bp/library/acs/acsappend.c, SACK: to ipn:1.0, 90376(1)
[2021/02/11-15:24:48] at line 467 of bp/library/acs/acstx.c, Serialized a new ACS to ipn:1.0 that is 6 long (old: 0)
[2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,11,0,0) in bidHash to destroy
[2021/02/11-15:24:48] at line 362 of bp/library/acs/acsappend.c, SACK: ipn:1.64,666372285.12 (reason: 0, current custodian: ipn:1.0)
[2021/02/11-15:24:48] at line 241 of bp/library/acs/acsappend.c, Found existing custody signal (SUCCESS,0)
[2021/02/11-15:24:48] at line 326 of bp/library/acs/acsappend.c, SACK: to ipn:1.0, 90376(1) +90378(1)
[2021/02/11-15:24:48] at line 467 of bp/library/acs/acstx.c, Serialized a new ACS to ipn:1.0 that is 8 long (old: 6)
[2021/02/11-15:24:48] at line 205 of bp/library/acs/acsid.c, Couldn't find (ipn:1.64,666372285,12,0,0) in bidHash to destroy

This is really flooding the log file.....
How do I clear that kind of error?
Thanks,
Pat.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ion-dtn/bugs/154/https://urldefense.us/v3/__https:/sourceforge.net/p/ion-dtn/bugs/154/__;!!PvBDto6Hs4WbVuu7!dXLJ4UdopPHGg08ydhkeT8Dnmc-9L0ODx8StCxkFUjuSbp9GOJSWOVxGpTtpCbvUlMHHfm8RAJc$

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/https://urldefense.us/v3/__https:/sourceforge.net/auth/subscriptions/__;!!PvBDto6Hs4WbVuu7!dXLJ4UdopPHGg08ydhkeT8Dnmc-9L0ODx8StCxkFUjuSbp9GOJSWOVxGpTtpCbvUlMHHRBs8lK0$