You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have recent setup ABS about a week ago. I have added 108 podcasts from my Podcast Addict {android} application onto the server. In the latest episodes, all them are from when I added the podcast to the application even though I know more episodes have been released because they release an episode everyweek. An example is EconTalk. Looking at the podcase there are episodes available, and they will download if I do it manually. Attached is some screenshots. Additionally, I notice there is error app. Here is the error -
FATAL
[Server] Unhandled rejection: SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse () at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map () promise: Promise { SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse () at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map () }
What did you expect to happen?
I expect that podcasts will be downloaded on the schedule for the individual podcast.
Steps to reproduce the issue
1
Audiobookshelf version
v2.17.5
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
FATAL
[Server] Unhandled rejection: SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse (<anonymous>) at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map (<anonymous>) promise: Promise { <rejected> SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse (<anonymous>) at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map (<anonymous>) }
Additional Notes
No response
The text was updated successfully, but these errors were encountered:
Update. I notice that one my podcast "2.5 Admins", I could not get into. When I did, I would a socket error "Socket Failed to Connect". After some conversation it was discovered selecting that podcast was causing ABS to crash and then reboot. The RSS feed for that podcast is https://2.5admins.com/feed/.
What happened?
I have recent setup ABS about a week ago. I have added 108 podcasts from my Podcast Addict {android} application onto the server. In the latest episodes, all them are from when I added the podcast to the application even though I know more episodes have been released because they release an episode everyweek. An example is EconTalk. Looking at the podcase there are episodes available, and they will download if I do it manually. Attached is some screenshots. Additionally, I notice there is error app. Here is the error -
FATAL
[Server] Unhandled rejection: SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse () at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map () promise: Promise { SyntaxError: Bad control character in string literal in JSON at position 33 at JSON.parse () at parse (/node_modules/sequelize/lib/dialects/sqlite/data-types.js:34:19) at Query.applyParsers (/node_modules/sequelize/lib/dialects/sqlite/query.js:289:14) at /node_modules/sequelize/lib/dialects/sqlite/query.js:112:80 at /node_modules/lodash/lodash.js:13469:38 at /node_modules/lodash/lodash.js:4967:15 at baseForOwn (/node_modules/lodash/lodash.js:3032:24) at Function.mapValues (/node_modules/lodash/lodash.js:13468:7) at /node_modules/sequelize/lib/dialects/sqlite/query.js:93:18 at Array.map () }
What did you expect to happen?
I expect that podcasts will be downloaded on the schedule for the individual podcast.
Steps to reproduce the issue
1
Audiobookshelf version
v2.17.5
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
The text was updated successfully, but these errors were encountered: