-
Notifications
You must be signed in to change notification settings - Fork 3
Log view stops working #145
Comments
I honestly have no idea. I put your log file into my Tautulli and it works perfectly fine. |
Maybe an extension you have in your browser? When you have the issue do you see the same problem in an incognito window? |
@samwiseg00 - 98% sure not an extension. I just tried Firefox safe mode on the PMS machine. Same issue, Does the server thread error for jquery in the tautulli log not help any to know what to look for? Since it only happens after a few days, I theorize it's Plex adding something to the log that jquery doesn't like Also, using google for that error, I found a similar fetching rows error with History tab that never seemed to get resolved with PlexPy. |
FYI - just updated Tautulli - log still won't load. |
4k limit still not fixed in code maybe? |
Does erasing lines from the end of the log file eventually get back to it working in the UI? (i.e. keep erasing lines from the end until it works again and that would identify which line in the logs is causing the issue.) Are you using any of the log level filters, search, table sorting, or changing pages? Maybe some combination of these actions causes it to break. |
Apologies for late reply, non-Plex-related-life has been busy. EDIT - NOT using any sort/search terms. Simply load the logs page and nothing shows after amount of time due to event (time, something in logs, unknown) |
Ok, I'm totally lost as to how to re-create this issue. Edit - you can see in the end few lines that even Tautulli is adding the JS error to the log. |
I still have no idea. I really think it's some issue on your system. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Please do not post unrelated support issues in a bug report. This has literally been answered in every support channel. Github Issues are not a support channel. https://github.com/Tautulli/Tautulli-Wiki/wiki/Asking-for-Support |
Version:
Windows 10 (10.0.17134)Version v2.1.25
Branch:
beta
Commit hash:
56a91de2c4ff0fdd8fbdff4dd7d7677bd16a4b28
Operating system:
Python version:
2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:25:58) [MSC v.1500 64 bit (AMD64)]
What you did?
Attempted to view Tautulli log using Tautulli while logged in as admin
What happened?
No results, and a jquery error was added to the tautulli log
2018-11-27 17:15:08 - ERROR :: CP Server Thread-14 : WebUI :: /logs : TypeError: 'createCaption' called on an object that does not implement interface HTMLTableElement.. (jquery-2.1.4.min.js:4)
What you expected?
the Tautulli log to display instead of the page area below the header row remaining blank.
How can we reproduce your issue?
If I stop Tautulli, delete the log, then restart Tautulli, the view capability will work until whatever is causing it to break occurs again.
I've tried viewing from multiple machines and multiple browsers with same results.
Unsure how to produce as I do not fully understand what is breaking the ability.
Perhaps one could try viewing my log (attached and linked) using their own Tautulli with same version as mine.
Current log attached, and linked to, was viewable as late as 11/26 in late evening. 1900 hours?
I do not remember the exact time I viewed the night of 11/26.
On 11/27, at 17:15, I attempted to view the log, and the screen was blank.
Restarting Tautulli doesn't fix the issue. I have to delete the log file.
What are your (relevant) settings?
I do not run a proxy.
I have non-standard ports forwarded on my router straight to my Win10 machine for Tautulli and PMS.
A Let'sEncrypt certificate and key is used/loaded by Tautulli.
Both PMS and Tautulli run on same machine.
Link to logs:
https://gist.github.com/JamminR/c5da85247af2d5d6b224ffd983bfb838
tautulli.log
This issue has occurred somewhat frequently since at least September.
Someone else in the Plex forums whose PMS was injecting odd characters into plex API log also had a similar issue. https://forums.plex.tv/t/tautulli-monitor-your-plex-media-server/225242/946?u=jamminr
Even if this were a "Plex is outputting bad characters issue", the log view capability should be able to ignore, reformat, or behave in a way so as to not prevent viewing of additional Tautulli log entry lines.
I tested adding the "broken" tuatulli.log file to my PMS logs directory, then attempting to view in WebTools. It allowed me to view with no apparent issues.
The text was updated successfully, but these errors were encountered: