Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value <Date> ~ bad lexical cast: source type value could not be interpreted as target

Server Version#: 1.24.5.5173

I am recently getting loads of warnings in my logs that follow this pattern:

Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '{{date}} ~ bad lexical cast: source type value could not be interpreted as target

What could be the problem?

These are the logs (5.7 MB)

3 Likes

Server Version#: 1.24.5.5173

Same here

Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2015-03-14' ~ bad lexical cast: source type value could not be interpreted as target
1 Like

Me three.

WARN - Caught exception trying to convert extra data attribute ‘originallyAvailableAt’ with type 1 and value ‘2018-03-14’ ~ bad lexical cast: source type value could not be interpreted as target

Same here

Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-10-22' ~ bad lexical cast: source type value could not be interpreted as target

I got the same…

Thank you for the logs – Written up and submitted

1 Like

Same here today.

Add me to the list as well…

Caught exception trying to convert extra data attribute ‘originallyAvailableAt’ with type 1 and value ‘2021-10-25’ ~ bad lexical cast: source type value could not be interpreted as target

Flooding the logs randomly

1 Like

At this point, we wait.

While waiting, can you summarize the impact the exceptions have to make sure I’ve caught everything?

1 Like

What is the Git Issue #? I would like to track its progress as this issue is affecting me as well…

Server Version#: 1.24.5.5173

Have the exact same issue, it appears to have broken hardware accelerated transcoding for me. I get the exact message 3 times, then “Transcode runner appears to have died.”

I ran into this issue last night when trying to play seemingly anything with subtitles.

This is just a warning log message. It doesn’t cause any issues except spamming the logs.

It will be corrected in a future update. If you have a specific issue please report what your specific issue is.

When I turn on verbose logs. This is the only error coming up when my stream crashes transcoding to a android tv.

3 Likes

Same for me. Only error I get when streaming to Android TV.

This log message is not related to that. Please create new post with your problem and post your logs there for both the Android client and PMS (and please disable Verbose logging before).

This error pops up for me when I try to download anything to my phone.

Any updates to this? It spams this several times before my transcoder crashes :confused:

This error makes it impossible for me to watch a file via Android app. If I remove the parameter from an episode (via Frontend), the playback works. However, I don’t want to remove this parameter from all files now…

plex

To reiterate. This log message is not the cause of any issues. If you have an issue, please create a forum thread explaining your specific issue and your server logs.

2 Likes