search

pulsejet / memories

Fast, modern and advanced photo management suite. Runs as a Nextcloud app.
https://memories.gallery
GNU Affero General Public License v3.0
3.13k stars 82 forks source link

State of the automatic indexing: Indexing has not been run yet since installation #941

Closed PolishTanker closed 6 months ago

PolishTanker commented 10 months ago

Describe the bug

After installation, I can't force automatic indexation to work. Or to be more clear, to hide below monits. I don't have any information in the logs, even on debug level. Manual indexing from occ is working. Installation of nextcloud (nginx) don't have any problems and cron is working, nextcloud files have proper permissions.

To Reproduce Steps to reproduce the behavior:

Install memories on bellow versions of soft and nginx.

Screenshots image

Platform:

Additional context Add any other context about the problem here.

pulsejet commented 10 months ago

cron is working

Are you sure? This just indicates the internal cron memories job isn't running.

PolishTanker commented 10 months ago

Nextcloud says so, there is no errors from cron. Passwords for example gives signs of life after cron jobs.

Screenshot_20231124_233339_Samsung Internet Screenshot_20231124_233158_Samsung Internet

pulsejet commented 10 months ago

Okay,

  1. Any errors in the cron? You could try running cron.php manually
  2. Does the jobs table contain the Memories jobs. Something like 
    SELECT * FROM oc_jobs WHERE class LIKE '%Memories%'
  3. What about the appconfig 
    SELECT * FROM oc_appconfig WHERE appid LIKE 'memories'
PolishTanker commented 10 months ago

Manual cron execution from cli is executed without errors.

Screenshot_20231125_000621_Termux

pulsejet commented 10 months ago

That's interesting. Looks like the job did start ~12 hours ago but never completed.

  1. What kind of environment is this? If docker, how are you running the cron job
  2. Did you get this output before or after you manually ran cron?
PolishTanker commented 10 months ago

It is rasbian (debian 11), it is not dockered. Cron job is running from crontab in the same way the official documentation shows. What is weird I rebooted system twice and this output must be there since first run after installation.

pulsejet commented 10 months ago

Did you get this output before or after you manually ran cron?

I meant, did you run the sql commands before or after the manual cron run

PolishTanker commented 10 months ago

After

PolishTanker commented 10 months ago

I don't understand, after night it started working. All day it didn't work, and now it is. I cleared cash not once on various web browsers.

image

pulsejet commented 10 months ago

I'm guessing there simply were too many things competing for cron time.