sct / overseerr

Request management and media discovery tool for the Plex ecosystem
https://overseerr.dev
MIT License
3.89k stars 449 forks source link

Error 500 on Logs retrieve #3752

Open TayZ3r opened 10 months ago

TayZ3r commented 10 months ago

Description

I get an error 500 when I try to access /settings/logs. 6Jzui5fh91

Version

1.33.2

Steps to Reproduce

  1. Log in with admin account
  2. Click on Settings
  3. Click on Logs

What I'm supposed to see : Logs What I actually have : Error 500

Screenshots

6Jzui5fh91

Logs

[error][Logs]: Something went wrong while retrieving logs {"errorMessage":"Unexpected token \u0000 in JSON at position 0"}

Platform

desktop

Device

PC

Operating System

Windows 11

Browser

Brave

Additional Context

No response

Code of Conduct

daurpam commented 9 months ago

I've got the same problem, after a sudden shutdown of server, the log has not retrieve by the web ui, but is it working on files and I can review the content.

2024-02-13T17:36:53.310Z [error][Logs]: Something went wrong while retrieving logs {"errorMessage":"Unexpected token \u0000 in JSON at position 0"}
2024-02-13T17:37:00.004Z [debug][Jobs]: Starting scheduled job: Download Sync
stale[bot] commented 6 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

drewstopherlee commented 1 month ago

Commenting in case anyone else runs into this issue. In my case, the Unexpected token error was caused by a corrupted log file. I stopped the container, deleted the overseerr.log file, and restarted the container and this resolved my issue. This comment here pointed me in the right direction.