New Issue

HTTP 502 errors after moving instance to a new server #738

Closed

opened by busshimoe · 4 comments

busshimoe commented (Migrated from github.com)

I recently had to reinstall my server running my Plume instance. I restored the database from backup and reinstalled Plume from source. All of this worked, until I published a new post, at which point Plume started throwing HTTP 502 errors. Trying to refill the search index (which I guessed might be part of the problem) gives the following error.

$ plm search refill
Configuration read from /home/plume/Plume/.env
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Search(IndexOpeningError)', src/libcore/result.rs:997:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Plume version: commit 458baf5f78
Operating system: Ubuntu 18.04.3 LTS x86_64

I recently had to reinstall my server running my Plume instance. I restored the database from backup and reinstalled Plume from source. All of this worked, until I published a new post, at which point Plume started throwing HTTP 502 errors. Trying to refill the search index (which I guessed might be part of the problem) gives the following error. ``` $ plm search refill Configuration read from /home/plume/Plume/.env thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Search(IndexOpeningError)', src/libcore/result.rs:997:5 note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace. ```  - **Plume version:** commit 458baf5f78daec1b823e0bbd17eaa96c23ae92f8 - **Operating system:** Ubuntu 18.04.3 LTS x86_64

elegaanz commented (Migrated from github.com)

Try to stop Plume, then do plm search unlock and plm search refill and finally restart Plume. It may help.

Try to stop Plume, then do `plm search unlock` and `plm search refill` and finally restart Plume. It may help.

busshimoe commented (Migrated from github.com)

Same issue. I think the root issue is probably something else, but I'm not sure what it could be.

elegaanz commented (Migrated from github.com)

Try to delete the search index directory, and recreate it with plm search init.

Try to delete the search index directory, and recreate it with `plm search init`.

busshimoe commented (Migrated from github.com)

OK wow, that worked, thank you!

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.

Labels Milestones

HTTP 502 errors after moving instance to a new server #738