Giter Club home page Giter Club logo

Comments (3)

gconnell avatar gconnell commented on May 15, 2024

That's not lovely :)

Could you try running stenographer with flag --v=10 and, when you run the query, paste the logs it generates in here?

from stenographer.

jasonish avatar jasonish commented on May 15, 2024

Ok, started a long running ping and with expanded out after and before parameters I know I have an echo/reply for every second in the time range I'm testing for.

Command:
stenoread 'icmp and after 2016-02-12T19:00:00Z and before 2016-02-12T19:02:00Z'

In this case I didn't get any packets returned. The output is attached as 190000-190200.txt. If I change the after time to 18:59, then I do get some packets in the 13:00:20 -> 13:01:19 range. That output is attached as 185900-190200.txt
185900-190200.txt
190000-190200.txt

.

from stenographer.

gconnell avatar gconnell commented on May 15, 2024

Okay, so making that into timestamps:
2016-02-12T19:00:00Z -> 1455303600 unix secs
2016-02-12T19:02:00Z -> 1455303720 unix secs

Looking at 190000-190200.txt, here's the files that are processed (just the ones close to the range, just thread 0):
"/tmp/stenographer720013252/PKT0/1455303017142474"
"/tmp/stenographer720013252/PKT0/1455303078263457"
"/tmp/stenographer720013252/PKT0/1455303257367202"
"/tmp/stenographer720013252/PKT0/1455303319266933"
"/tmp/stenographer720013252/PKT0/1455303380526130"
"/tmp/stenographer720013252/PKT0/1455303560343195"
"/tmp/stenographer720013252/PKT0/1455303621976087"
"/tmp/stenographer720013252/PKT0/1455303803269305"
"/tmp/stenographer720013252/PKT0/1455303864590381"
"/tmp/stenographer720013252/PKT0/1455303925700711"

Of these files we skip due to the time range (again, just those near the range, just thread 0):
"/tmp/stenographer720013252/IDX0/1455303017142474"
"/tmp/stenographer720013252/IDX0/1455303078263457"
"/tmp/stenographer720013252/IDX0/1455303257367202"
"/tmp/stenographer720013252/IDX0/1455303319266933"
"/tmp/stenographer720013252/IDX0/1455303380526130"
"/tmp/stenographer720013252/IDX0/1455303560343195" SHOULD HAVE PROCESSED
"/tmp/stenographer720013252/IDX0/1455303621976087" SHOULD HAVE PROCESSED
"/tmp/stenographer720013252/IDX0/1455303803269305"
"/tmp/stenographer720013252/IDX0/1455303864590381"
"/tmp/stenographer720013252/IDX0/1455303925700711"

Hmm, I'm somewhat stumped, but I'll look through some code.

from stenographer.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.