romm icon indicating copy to clipboard operation
romm copied to clipboard

[Bug] Scan not adding new roms?

Open karl0ss opened this issue 9 months ago • 8 comments

RomM version 3.1.0

Describe the bug Upgraded from working 2.x install, Have added some new games, but nothing was found during the cron scan, manually kicked off a scan in the ui, but nothing seems to scan in, also doesn't appear to be anything in the logs related to it

To Reproduce Steps to reproduce the behavior: Try to scan new roms for platform Never finishes and just keeps scanning

Expected behavior Scan in new roms?

Screenshots image

Desktop (please complete the following information): Offical Docker Image

Smartphone (please complete the following information): Chrome on Windows 11

karl0ss avatar May 08 '24 07:05 karl0ss

Chome debug console seems to be spamed with image

karl0ss avatar May 08 '24 07:05 karl0ss

Hi! can you post the container logs?

zurdi15 avatar May 08 '24 07:05 zurdi15

How can i force the logs? i just wiped all the logs from my logs folder, restarted and did the process again, but it hasn't written anything to the log files?

karl0ss avatar May 08 '24 09:05 karl0ss

portainerlogs.txt

Ive attached the portainer logs from the restart/process

karl0ss avatar May 08 '24 09:05 karl0ss

could you share the logs when you perform a scan?

zurdi15 avatar May 08 '24 09:05 zurdi15

I have performed a scan during the period of the logs.....

I will try again and see if I can capture anything else....

This has been working fine - image

karl0ss avatar May 08 '24 10:05 karl0ss

Oh damn sorry, you are totally right, i'm totally blidn. There are the scan socket petitions but with a status code 400. Can you try cleaning cache/cookies and try to scan again? Seems like something could be got stuck from the 2.x version

zurdi15 avatar May 08 '24 10:05 zurdi15

I had an issue recently where scanning was starting but never finishing (it just kept scanning but never finding anything). I shut down RomM, deleted the redis backup file "dump.rdb", then restarted RomM, and this solved the problem.

WalterSchirmacher avatar May 14 '24 00:05 WalterSchirmacher

Nginx proxy manager wasn't set to allow web sockets, having enabled that, all is working..

karl0ss avatar May 19 '24 15:05 karl0ss