Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle server=1 logs #4

Open
rcowham opened this issue Dec 31, 2019 · 2 comments
Open

Handle server=1 logs #4

rcowham opened this issue Dec 31, 2019 · 2 comments

Comments

@rcowham
Copy link
Contributor

rcowham commented Dec 31, 2019

Such logs do not have a completed record. Needs to be detected and handled appropriately.
@rcowham
Copy link
Contributor Author

rcowham commented Mar 22, 2021 •
edited
Loading

Note there is better handling of these - there will be a panic and an appropriate error message hopefully.
Not sure what else to do at this point.

rmmeta.log: 36.7 MB/598.1 MB 6% estimated finish 11:45:07, 15m18s remaining...
rmmeta.log: 36.7 MB/598.1 MB 6% estimated finish 11:45:23, 15m34s remaining...
panic: ERROR: max running command limit (20000) exceeded. Does this server log have completion records configured (configurable server=3)?

goroutine 8 [running]:
github.com/rcowham/go-libp4dlog.(*P4dFileParser).LogParser.func4(0xc0000ff800, 0x9e6160, 0xc0000b91c0)
/go/src/github.com/rcowham/go-libp4dlog/p4dlog.go:1421 +0x2b9
created by github.com/rcowham/go-libp4dlog.(*P4dFileParser).LogParser
/go/src/github.com/rcowham/go-libp4dlog/p4dlog.go:1407 +0x174

@rcowham
Copy link
Contributor Author

rcowham commented May 16, 2024

Note that log2sql has a flag to help with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rcowham