```
19:58 <vlorentz> we have a revision 00a867beb2ad8e203f242e9843d2e88de0856cda
19:58 <vlorentz> which was obviously created by the CRAN loader, from its content
19:59 <vlorentz> and the origin should be https://cran.r-project.org/package=mljar
19:59 <vlorentz> but that origin doesn't exist
19:59 <vlorentz> additionally, the revision is referenced by a snapshot (f7ce27eb87dc82e02b6178db3c9d9dbc9fa055d6) which isn't reference by any visit status
19:59 <vlorentz> I could understand an orphan snapshot, but not the missing origin
20:01 <vlorentz> any idea what happened?
20:01 <vlorentz> the revision was created on 2020-01-09T13:14:43.438615+00:00, btw
20:02 <+olasd> one could fish out the cran_loader worker logs for that date, see what happened
20:03 <+olasd> (using kibana)
20:03 <+olasd> but for such old logs you'd need to reopen the elasticsearch indexes first
```
but I can't access the logs.
I opened the index, but Kibana doesn't see it. (and it's half unusable anyway, T2534), and ES doesn't return any document when searching in the index:
```
$ curl "esnode1.internal.softwareheritage.org:9200/swh_workers-2020.01.09/_search" -X GET -H "Content-Type: application/json" -d '{"query": {"match_all": {}}}'
{"took":0,"timed_out":false,"_shards":{"total":0,"successful":0,"skipped":0,"failed":0},"hits":{"total":{"value":0,"relation":"eq"},"max_score":0.0,"hits":[]}}
```