I seem to be having a problem with the recently added section of Tautulli. This recently started and was not a problem during my initial install so I’m not sure what caused this to happen. I checked the FAQ and didn’t see anything there and I’m running Python 2.7.17 so I’m good there. Anyone out there run into the same problem and find the solution or does anyone have any thoughts or suggestions as to what may be causing this? This has continued through the last 2 Tautulli updates and I’m running Plex 1.18.3.2156. The only thing I’ve changed is the default image for the newsletter and that works fine as it sends out weekly updates on what I added to my server. I attached an image to this post showing the error I’m getting.
You corrupted your recently_added.html file. Not the HTML file used for newsletters, but the HTML file used for the homepage. They both have the same filename, but are located in different folders.
1 Like
Ok I will check it tonight. Thank You!
This did it. I guess I accidentally changed that file when I fixed the email logo and messed it all up. Thank you!
So now that Python 2 is “officially” no longer supported, what is Tautulli’s plan towards Python 3?
2 Likes
I would like to remind everyone to be courteous to others.
Thank you
2 Likes
Honestly, i don’t use reddit. Someone asking both there and here might actually educate those like me who don’t know about reddit having a place for Plex or Tautulli.
I come to this thread for answers, as I would expect 'Plex forums" to have answers for a product used with Plex.
I’ll go ahead and ask again, has the answer to dev plans for Python 3 been answered already? (Even if on Reddit - what was the answer?)
Thanks.
2 Likes
I will not waste my time responding to the same person asking the same question 3 times in different locations. Seeing someone ask the same question in multiple places is seriously really annoying, especially without even waiting for a response where they posted first. It should be common courtesy to have some patience when asking for support. We are only a few people who spend our own free time to provide support; we don’t have to provide any support at all, but we do it because we want to help. Our response time is usually within 24 hours, so if you do not receive a response after that time, then and only then would it be appropriate to ask again. The priority of our responses is Discord, Reddit, then Plex Forums.
Also, if we don’t even acknowledge that the question has already been asked an answered elsewhere, then it gives the impression that we are ignoring support questions. Since you, @JamminR, don’t visit our subreddit, if we just left it without answering, to you it would seem like we just ignored his question. Having @Samwiseg0 respond, and even provide a link to the answer, allows you and anyone else that comes to this forum thread to find a link to the answer.
@Samwiseg0 is part of my support team and if he didn’t respond here first, I would have given the exact same response. I have seen the private messages from @ChuckPa to @Samwiseg0 regarding the issue above and his attitude is seriously making me consider removing the Plex Forums for any Tautulli support. This has nothing to do with us trying to moderate the Plex Forums, but it is a Tuatulli support issue and how I wish to deal with my own support. I don’t want to remove the Plex Forums for support, but if we are not welcome here then I will take it elsewhere.
@ChuckPa, if you think anyone is trying to micro-moderate this thread, then please look at comments #1221 and #1238.
As for Python 3, I commented here on Reddit.
https://www.reddit.com/r/Tautulli/comments/do4p67/tautulli_on_python_3/
I do not discuss road maps.
1 Like
“the response time is usually within 24 hours”
only if you consider a year 24 hours. i’ve been through the forums and thread after thread after thread after thread after thread not answered. i can see why someone might go a bit overboard and create multiple threads in multiple sections. as for the member posting both at reddit and here, this is their business not yours.
I do not see any post history from your account so I have no idea what question you asked. I think you may have confused Plex support with Tautulli support.
It is my business because they are asking me a question about my software.
Actually rather there is one site that has support for something or a thousand sites that provide support for something it IS the posters choice if they want to create the same thread / post at more then one of those sites. that is not open to debate. Now when the poster creates multiple threads on the same site about the same item then that is a problem. As for confusing Tautulli support for Plex support simply NO since this thread is for Tuatulli support. As for having history here that’s a nonissue.
@SwiftPanda16
I seem to have struck, or added to the pressure, of a nerve here.
At the time, not my intent.
I simply stated what I felt about the conversation at hand, and appreciated that a person might ask in both places so I too can be educated with an answer, even if/when it’s a link back to the first location originally asked.
If one is going to operate multiple support locations, overlap is expected.
That being said, tautulli.com has 4 support links. There is no other indication you prefer to support in that order.
I now understand your preference. Personal opinion. Noted.
However, Discord may be great for live communication, it’s flat search absolutely sucks for finding/linking to previous answers. I understand the idea of using DIscord, as I too am part of a community and support server, but, we often link back to answers on our forum because it’s easier to search/find previous answers.
As for delays in answers, this … is the … fourth … time … I’ve asked in over a year, and not once have you or another team member answered, even with a “i don’t discuss road map” until the fourth.
And I must say, how very Plex-like of you.
I understand this isn’t your day job. (nor is my dev project community that I help support)
I love the product you have created in your limited hobby time. Sweat/blood poured into it.
It’s a good thing it’s free, because as with Plex, the seeming attitude towards the people that want to use it seem a bit over the top right now.
I’ve stopped helping others in the Plex forums due to the overall direction they’ve gone as a company.
I guess I’ll stop visiting this thread too.
I’ll be one less person to support, and you won’t have to be concerned with me attempting to help others either, perhaps for that rare occasion I may give incorrect links back to the FAQ.
That should help you out some.
You’re welcome.
1 Like
Coming back to this because I happened to have a whole bunch of core dumps created in my Tautulli config folder that were taking up a couple hundred gigs. I started looking at trying to look at the core dumps but was not able to due to gdb not having the debug symbols so I couldn’t really get any good information. And I don’t believe it’s system related based on some new information I found (I also tried on my test server and got the same result of signal -11).
All that, said, in my research to try and figure out how to actually get that information (unsuccessful) I came across this post, Alpine and Python Docker Debug Solutions | Rookout, which I found relevant as the person used Alpine Linux for the base image and also using Python. Basically, this quote is the relevant part:
So based on that, I think this issue is actually related to the docker container and underlying image that is used. The status -11 is probably happening because of the low memory allocation and therefore it’s very easy for the allocated memory to run out therefore causing Python to try and access an illegal memory location.
Furthermore, I did some additional tests. Both the official and Linuxserver.io use Alpine Linux as the base image. I tested using another container (bmoorman) which uses Ubuntu Bionic as the base and I ran multiple tests and the scripts all successfully ran, leading me back to the conclusion that this is a container issue relating to the above link and an issue with the version of Alpine Linux being used.
-Shark2k
Interesting find. Although we have seen the same segmentation fault error -11 from users who are not using the Docker container.
Regardless, we have already been testing a new Docker container using the Python base image instead of Alpine Linux. I do not have a release date for the updated container.
That’s good to hear you are testing a new Docker container using the Python base image instead of Alpine Linux. Would be great if that new container can help resolve the issue.
I do want to add, I mentioned this to the LinuxServer.io team and the person pointed out that what I linked to had already been implemented 2 years ago (I don’t use Github so I overlooked that). However, that doesn’t mean that the increase in allocation they gave was enough in the Alpine base. And as I mentioned I did run multiple consecutive tests that kicked off a script using bmoorman’s containter with Ubuntu Bionic as the base (had to be at least 15 in a row maybe more) and I didn’t get the segmentation fault error -11. It would be interesting to know what those users that received it that are not using the Docker container are running on.
Anyway, thanks for the reply. I feel that at this point I’m at a standstill until maybe you getting that updated container out (with no ETA as you said). I’d use bmoorman’s container but the logs weren’t updating from the web browser properly (the actual log file was updating correctly so I was able to run a tail -f on it to get the updates, but going to view logs wouldn’t refresh at all). I did use that on a test environment so maybe something was off there.
Anyway, thanks again (sorry for the long winded reply).
-Shark2k
Not able to get my log to work - just stopped working on Feb 1. Any ideas? I can add more of the log if requested.
2020-02-12 12:03:51 - ERROR :: Thread-3 : Tautulli Database :: Fatal Error executing INSERT INTO sessions (stream_video_codec, transcode_width, stream_video_resolution, video_height, stream_video_width, friendly_name, year, subtitle_codec, height, stream_bitrate, player, optimized_version, parent_rating_key, audio_codec, parent_title, duration, session_key, subtitles, rating_key, transcode_video_codec, transcode_key, optimized_version_title, stream_audio_channels, user_id, thumb, title, bitrate, live, quality_profile, synced_version, transcode_audio_channels, video_decision, platform, state, transcode_height, transcode_container, transcode_hw_decoding, stream_video_framerate, media_type, video_resolution, grandparent_rating_key, stream_audio_decision, stream_container, transcode_audio_codec, product, audio_channels, view_offset, optimized_version_profile, section_id, stream_container_decision, aspect_ratio, full_title, user, raw_stream_info, audio_decision, transcode_decision, container, video_width, ip_address, grandparent_thumb, video_framerate, transcode_hw_encoding, stream_video_decision, transcode_protocol, media_index, stream_video_height, stream_subtitle_decision, video_bitrate, synced_version_profile, original_title, stream_video_bitrate, session_id, live_uuid, stream_subtitle_codec, stopped, parent_thumb, stream_audio_codec, stream_audio_bitrate, grandparent_title, video_codec, parent_media_index, machine_id, width, audio_bitrate, session_key, rating_key) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) :: database disk image is malformed
2020-02-12 12:03:51 - ERROR :: Thread-3 : Tautulli WebSocket :: Failed to process session data: database disk image is malformed.
2020-02-12 12:03:51 - ERROR :: Thread-2 : Tautulli Database :: Fatal Error executing SELECT * FROM sessions :: database disk image is malformed
2020-02-12 12:03:51 - ERROR :: Thread-2 : Tautulli NotificationHandler :: Notification thread exception: database disk image is malformed
Traceback (most recent call last):
File “C:\Tautulli\plexpy\notification_handler.py”, line 60, in process_queue
add_notifier_each(**params)
File “C:\Tautulli\plexpy\notification_handler.py”, line 104, in add_notifier_each
**kwargs)
File “C:\Tautulli\plexpy\notification_handler.py”, line 515, in build_media_notify_params
sessions = ap.get_sessions()
File “C:\Tautulli\plexpy\activity_processor.py”, line 457, in get_sessions
sessions = self.db.select(query, args)
File “C:\Tautulli\plexpy\database.py”, line 165, in select
sql_results = self.action(query, args).fetchall()
File “C:\Tautulli\plexpy\database.py”, line 144, in action
sql_result = c.execute(query, args)
DatabaseError: database disk image is malformed
2020-02-12 12:04:02 - DEBUG :: Thread-3 : Tautulli ActivityHandler :: Session 123 started by user 17039341 (nobel.lanette@gmail.com) with ratingKey 69753 (Frozen II).
2020-02-12 12:04:02 - ERROR :: Thread-3 : Tautulli Database :: Fatal Error executing INSERT INTO sessions (stream_video_codec, transcode_width, stream_video_resolution, video_height, stream_video_width, friendly_name, year, subtitle_codec, height, stream_bitrate, player, optimized_version, parent_rating_key, audio_codec, parent_title, duration, session_key, subtitles, rating_key, transcode_video_codec, transcode_key, optimized_version_title, stream_audio_channels, user_id, thumb, title, bitrate, live, quality_profile, synced_version, transcode_audio_channels, video_decision, platform, state, transcode_height, transcode_container, transcode_hw_decoding, stream_video_framerate, media_type, video_resolution, grandparent_rating_key, stream_audio_decision, stream_container, transcode_audio_codec, product, audio_channels, view_offset, optimized_version_profile, section_id, stream_container_decision, aspect_ratio, full_title, user, raw_stream_info, audio_decision, transcode_decision, container, video_width, ip_address, grandparent_thumb, video_framerate, transcode_hw_encoding, stream_video_decision, transcode_protocol, media_index, stream_video_height, stream_subtitle_decision, video_bitrate, synced_version_profile, original_title, stream_video_bitrate, session_id, live_uuid, stream_subtitle_codec, stopped, parent_thumb, stream_audio_codec, stream_audio_bitrate, grandparent_title, video_codec, parent_media_index, machine_id, width, audio_bitrate, session_key, rating_key) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) :: database disk image is malformed
2020-02-12 12:04:02 - ERROR :: Thread-3 : Tautulli WebSocket :: Failed to process session data: database disk image is malformed.
2020-02-12 12:04:02 - ERROR :: Thread-1 : Tautulli Database :: Fatal Error executing SELECT * FROM sessions :: database disk image is malformed
2020-02-12 12:04:02 - ERROR :: Thread-1 : Tautulli NotificationHandler :: Notification thread exception: database disk image is malformed
Traceback (most recent call last):
File “C:\Tautulli\plexpy\notification_handler.py”, line 60, in process_queue
add_notifier_each(**params)
File “C:\Tautulli\plexpy\notification_handler.py”, line 104, in add_notifier_each
**kwargs)
File “C:\Tautulli\plexpy\notification_handler.py”, line 515, in build_media_notify_params
sessions = ap.get_sessions()
File “C:\Tautulli\plexpy\activity_processor.py”, line 457, in get_sessions
sessions = self.db.select(query, args)
File “C:\Tautulli\plexpy\database.py”, line 165, in select
sql_results = self.action(query, args).fetchall()
File “C:\Tautulli\plexpy\database.py”, line 144, in action
sql_result = c.execute(query, args)
DatabaseError: database disk image is malformed
2020-02-12 12:04:12 - DEBUG :: Thread-3 : Tautulli ActivityHandler :: Session 123 started by user 17039341 (nobel.lanette@gmail.com) with ratingKey 69753 (Frozen II).
2020-02-12 12:04:12 - ERROR :: Thread-3 : Tautulli Database :: Fatal Error executing INSERT INTO sessions (stream_video_codec, transcode_width, stream_video_resolution, video_height, stream_video_width, friendly_name, year, subtitle_codec, height, stream_bitrate, player, optimized_version, parent_rating_key, audio_codec, parent_title, duration, session_key, subtitles, rating_key, transcode_video_codec, transcode_key, optimized_version_title, stream_audio_channels, user_id, thumb, title, bitrate, live, quality_profile, synced_version, transcode_audio_channels, video_decision, platform, state, transcode_height, transcode_container, transcode_hw_decoding, stream_video_framerate, media_type, video_resolution, grandparent_rating_key, stream_audio_decision, stream_container, transcode_audio_codec, product, audio_channels, view_offset, optimized_version_profile, section_id, stream_container_decision, aspect_ratio, full_title, user, raw_stream_info, audio_decision, transcode_decision, container, video_width, ip_address, grandparent_thumb, video_framerate, transcode_hw_encoding, stream_video_decision, transcode_protocol, media_index, stream_video_height, stream_subtitle_decision, video_bitrate, synced_version_profile, original_title, stream_video_bitrate, session_id, live_uuid, stream_subtitle_codec, stopped, parent_thumb, stream_audio_codec, stream_audio_bitrate, grandparent_title, video_codec, parent_media_index, machine_id, width, audio_bitrate, session_key, rating_key) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) :: database disk image is malformed
2020-02-12 12:04:12 - ERROR :: Thread-3 : Tautulli WebSocket :: Failed to process session data: database disk image is malformed.
2020-02-12 12:04:12 - ERROR :: Thread-2 : Tautulli Database :: Fatal Error executing SELECT * FROM sessions :: database disk image is malformed
2020-02-12 12:04:12 - ERROR :: Thread-2 : Tautulli NotificationHandler :: Notification thread exception: database disk image is malformed
Traceback (most recent call last):
File “C:\Tautulli\plexpy\notification_handler.py”, line 60, in process_queue
add_notifier_each(**params)
File “C:\Tautulli\plexpy\notification_handler.py”, line 104, in add_notifier_each
**kwargs)
File “C:\Tautulli\plexpy\notification_handler.py”, line 515, in build_media_notify_params
sessions = ap.get_sessions()
File “C:\Tautulli\plexpy\activity_processor.py”, line 457, in get_sessions
sessions = self.db.select(query, args)
Unable to retrieve data for get_activity: ‘studio’
Traceback (most recent call last):
File “/usr/local/share/Tautulli/plexpy/webserve.py”, line 5147, in get_activity
result = pms_connect.get_current_activity()
File “/usr/local/share/Tautulli/plexpy/pmsconnect.py”, line 1499, in get_current_activity
session_output = self.get_session_each(session_)
File “/usr/local/share/Tautulli/plexpy/pmsconnect.py”, line 1889, in get_session_each
metadata_details = self.get_metadata_details(rating_key=rating_key, cache_key=session_key)
File “/usr/local/share/Tautulli/plexpy/pmsconnect.py”, line 859, in get_metadata_details
‘studio’: show_details[‘studio’],
KeyError: ‘studio’
getting this error when i try watching live tv, how can i fix
All of suden I have problems with notification on my Iphone.
It was working ok, but now If I have two playing movies on diffrent users, notifications on Iphone keeps on coming. I can’ turn it off.
If I play only one movie, everything is ok.
What can be wrong, I didn’t change anything ? Thank you.
