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.
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
Web UI: error parsing log message #3694
Comments
This error shows anywhere logs are loaded in the web UI. |
Log file contents:
|
I got this in testing, but we weren't able to reproduce it because I stupidly deleted my log file. Ping @timmaxw |
Oh no. @mglukhovsky If possible please make a copy from the log file as well. |
@mglukhovsky Never mind, can reproduce with the data you posted above. |
The file_reverse_reader_t is giving us these two lines as one:
|
This goes away if I for example increase the I think this is not a new bug. When the error shows up, it's more visible in the new web UI with ReQL admin. Previously it seems like if a log entry was illegal, all log entries would simply appear as blank. Now we get a very visible ReQL error message. Re-assigning to @Tryneus since you were the last to work with the file. |
As a side note, I'd add that I had some serious weirdness going on when I was first trying to setup the cluster -- each server had very different port offsets given as command-line flags, but a few of them reported as connecting on the wrong intracluster port and showed up as ghost servers in the web UI and had to have their However, I think that was unrelated. I also couldn't reproduce this, so I chalked it up to gremlins. |
I also have the log file in Dropbox to share if we need it (but I think @danielmewes nailed it). This should go in a point release, but again, couldn't reproduce easily. |
Fix is up in review 2551, mostly just an off-by-one error. |
A query failed for log entries in the web UI:
The problem persists after refresh.
Running
r.db('rethinkdb').table('logs')
in the Data Explorer returns:The text was updated successfully, but these errors were encountered: