tubearchivist
/
docs
mirror of https://github.com/tubearchivist/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add more reactivate commands

This commit is contained in:
Simon 2023-09-02 12:17:48 +07:00
parent 4e2aca039b
commit af163d9c50
No known key found for this signature in database
GPG Key ID: 2C15AA5E89985DD4
1 changed files with 46 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
mkdocs/docs/advanced.md
View File

@ -9,19 +9,21 @@ description: Collection of advanced concepts and debug info.
A loose collection of advanced debug info, may or may not apply to you, only use this when you know what you are doing. Some of that functionality might get implemented in the future in the regular UI.
## Reactivate all Videos
As part of the metadata refresh task, Tube Archivist will mark videos as deactivated, if they are no longer available on YouTube. For some reasons, that might have deactivated videos that shouldn't have, for example if a video got reinstated after a copyright strike on YT. You can reactivate all videos in bulk, so the refresh task will check them again and deactivate the ones that are actually not available anymore.
## Reactivate documents
As part of the metadata refresh task, Tube Archivist will mark videos, channels and playlists as deactivated, if they are no longer available on YouTube. For some reasons, that might have deactivated something that shouldn't have, for example if a video got reinstated after a copyright strike on YT. You can reactivate all things in bulk, so the refresh task will check them again and deactivate the ones that are actually not available anymore.
Run this curl command from within the TA container:
Curl commands to run within the TA container.
Reactivate all videos:
```bash
curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
{
"query": {
"term": {
"active": {
"value": false
}
"active": {
"value": false
}
}
},
"script": {
@ -31,6 +33,44 @@ curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSW
}'
```
Reactivate all channels:
```bash
curl -XPOST "$ES_URL/ta_channel/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
{
"query": {
"term": {
"channel_active": {
"value": false
}
}
},
"script": {
"source": "ctx._source.channel_active = true",
"lang": "painless"
}
}'
```
Reactivate all playlists:
```bash
curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
{
"query": {
"term": {
"playlist_active": {
"value": false
}
}
},
"script": {
"source": "ctx._source.playlist_active = true",
"lang": "painless"
}
}'
```
## Corrupted ES index reset
After a hard reset of your server or any other hardware failure you might experience data corruption. ES can be particularly unhappy about that, especially if the reset happens during actively writing to disk. It's very likely that only your `/indices` folder got corrupted, as that is where the regular read/writes happen. Luckily you have your [snapshots](settings.md#snapshots) set up.