BPSTATS2(1)

πŸ“¦ version 3.2.1, in ubuntu jammy

✨ bpstats2 β€” the stats girlie πŸ’…

okay bestie, listen up: bpstats2 is a Bundle Protocol (BP) processing statistics query utility β€” but the way it works is via bundles. yes, bundles. it's giving "I ask nicely and the numbers come to me" energy and honestly? iconic.


🌸 SYNOPSIS 🌸

bpstats2 sourceEID [default destEID] [ct]

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea. bpstats2 creates bundles that are literally stuffed with the current values of all BP processing statistics accumulators. no cap. and it makes these bundles when one of these two things happens:

  • an interrogation bundle is delivered to sourceEID β€” the contents of that bundle get discarded (we don't read them, we don't care, the format is irrelevant, periodt), a brand new statistics bundle is generated, and it's sent straight back to the source of the interrogation bundle. the vibe of the interrogation bundle literally does not matter. 🫢
  • a SIGUSR1 signal is delivered to the bpstats2 application β€” a new statistics bundle gets generated and sent to default destEID. it's giving main character energy, one signal and the stats are out the door. ✨

πŸ’– EXIT STATUS πŸ’–

  • "0" β€” bpstats2 has terminated. any problems encountered during operation will be noted in the ion.log log file. (she's fine, she's just logging πŸ“)
  • "1" β€” bpstats2 failed to start up or receive bundles. go diagnose the issue reported in the ion.log file and try again, bestie. 😭

✨ OPTIONS ✨

  • [ct] β€” if the string "ct" is appended as the last argument, then statistics bundles will be sent with custody transfer requested. that's it, that's the whole option list. one option. she's lowkey minimalist and I respect it. πŸ’…

πŸŽ€ FILES πŸŽ€

No configuration files are needed. not a single one. she's self-sufficient, she's thriving. 🌈


πŸ’œ ENVIRONMENT πŸ’œ

No environment variables apply. nope, none, zero, nada. ✨


πŸ”₯ DIAGNOSTICS πŸ”₯

these are the diagnostics that may be issued to the ion.log log file. buckle up, there's a few:

  • bpstats2 can't bp_attach(). β€” bpadmin has not yet initialized BP operations. (she's knocking on the door and nobody's home πŸšͺ)
  • bpstats2 can't open own endpoint. β€” another BP application has opened that endpoint. close it and try again. (endpoint is taken, it's giving "seat's saved" energy 😀)
  • No space for ZCO extent. β€” ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
  • Can't create ZCO extent. β€” ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
  • bpstats2 can't send stats bundle. β€” Bundle Protocol service to the remote endpoint has been stopped. πŸ’€
  • Can't send stats: bad dest EID (dest EID) β€” the destination EID printed is an invalid destination EID. the destination EID may be specified in default destEID or the source EID of the interrogation bundle. make sure default destEID is an EID that is valid for ION, and that the interrogator is a source EID that is also a valid destination EID. and note this one closely: "dtn:none" is not a valid destination EID, but it is a valid source EID. iykyk. πŸ™ˆ

🌟 NOTES 🌟

a very simple interrogator is bpchat, which can repeatedly interrogate bpstats2 by just striking the enter key. yes bestie, enter key spam is a valid interrogation strategy. obsessed. βŒ¨οΈπŸ’–


😭 BUGS 😭

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>. she's not perfect, she's just trying her best. 🫢


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie!! πŸŽ€ this manual was served up by perl v5.24.1 on 2016-07-07, and it lives in the BP executables section of the manual. slay, stay hydrated, and always read your ion.log. πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from