We’ll give the upgrade new try tomorrow. I’ve had some good input from admins of other instances, which are also gonna help troubleshoot during/after the upgrade.
Also there are newer RC versions with fixed issues.
Be aware that might we need to rollback again, posts posted between the upgrade and the rollback will be lost.
We see a huge rise in new user signups (duh… it’s July 1st) which also stresses the server. Let’s hope the improvements in 0.18.1 will also help with that.
My lemmy server is also running the same versions are you are now. I was getting timeouts with lemmy.world federation so I recompiled lemmy_server with timeout changes:
diff --git a/crates/utils/src/lib.rs b/crates/utils/src/lib.rs index e5d07db2c..e2c592d82 100644 --- a/crates/utils/src/lib.rs +++ b/crates/utils/src/lib.rs @@ -18,7 +18,7 @@ use std::time::Duration; pub type ConnectionId = usize; -pub const REQWEST_TIMEOUT: Duration = Duration::from_secs(10); +pub const REQWEST_TIMEOUT: Duration = Duration::from_secs(13); #[macro_export] macro_rules! location_info { diff --git a/src/lib.rs b/src/lib.rs index cc77ca48f..45c621a7c 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -37,7 +37,7 @@ use tracing_subscriber::{filter::Targets, layer::SubscriberExt, Layer, Registry} use url::Url; /// Max timeout for http requests -pub(crate) const REQWEST_TIMEOUT: Duration = Duration::from_secs(10); +pub(crate) const REQWEST_TIMEOUT: Duration = Duration::from_secs(16); /// Placing the main function in lib.rs allows other crates to import it and embed Lemmy pub async fn start_lemmy_server() -> Result<(), LemmyError> {0.18.1 changed the limit to one hour. So, hopefully, this issue is soon solved for everyone :)