#mastodonserveroperators — Public Fediverse posts

While my Mastodon server moves its cache into object storage, I’m effectively browsing in text-only mode. Time to see how many people use #AltText.

#MastodonServerOperators #MastodonAdmins #SelfHosted #sysadmin

While my Mastodon server moves its cache into object storage, I’m effectively browsing in text-only mode. Time to see how many people use #AltText.

#MastodonServerOperators #MastodonAdmins #SelfHosted #sysadmin

While my Mastodon server moves its cache into object storage, I’m effectively browsing in text-only mode. Time to see how many people use #AltText.

#MastodonServerOperators #MastodonAdmins #SelfHosted #sysadmin

While my Mastodon server moves its cache into object storage, I’m effectively browsing in text-only mode. Time to see how many people use #AltText.

#MastodonServerOperators #MastodonAdmins #SelfHosted #sysadmin

While my Mastodon server moves its cache into object storage, I’m effectively browsing in text-only mode. Time to see how many people use #AltText.

#MastodonServerOperators #MastodonAdmins #SelfHosted #sysadmin

UPDATE: I solved the problem! The heap size was so low that Elasticsearch was crashing due to low memory. But, raising it made the OOM killer reap it.

Instead, I used the oldest trick in the book. I have my hosting provider's 512 MB swap disk, but I added a 512 MB swap file, too. That got Elasticsearch to run and stay running.

It'd still consume all of the CPU, until I added `CPUSchedulingPriority=idle` to the systemd service file. Now, it runs peacefully in the background!

Let's go! :mastodon: :linux: #MastodonAdmins #MastodonServerOperators #SelfHosted

UPDATE: I solved the problem! The heap size was so low that Elasticsearch was crashing due to low memory. But, raising it made the OOM killer reap it.

Instead, I used the oldest trick in the book. I have my hosting provider's 512 MB swap disk, but I added a 512 MB swap file, too. That got Elasticsearch to run and stay running.

It'd still consume all of the CPU, until I added `CPUSchedulingPriority=idle` to the systemd service file. Now, it runs peacefully in the background!

Let's go! :mastodon: :linux: #MastodonAdmins #MastodonServerOperators #SelfHosted

UPDATE: I solved the problem! The heap size was so low that Elasticsearch was crashing due to low memory. But, raising it made the OOM killer reap it.

Instead, I used the oldest trick in the book. I have my hosting provider's 512 MB swap disk, but I added a 512 MB swap file, too. That got Elasticsearch to run and stay running.

It'd still consume all of the CPU, until I added `CPUSchedulingPriority=idle` to the systemd service file. Now, it runs peacefully in the background!

Let's go! :mastodon: :linux: #MastodonAdmins #MastodonServerOperators #SelfHosted

UPDATE: I solved the problem! The heap size was so low that Elasticsearch was crashing due to low memory. But, raising it made the OOM killer reap it.

Instead, I used the oldest trick in the book. I have my hosting provider's 512 MB swap disk, but I added a 512 MB swap file, too. That got Elasticsearch to run and stay running.

It'd still consume all of the CPU, until I added `CPUSchedulingPriority=idle` to the systemd service file. Now, it runs peacefully in the background!

Let's go! :mastodon: :linux: #MastodonAdmins #MastodonServerOperators #SelfHosted

UPDATE: I solved the problem! The heap size was so low that Elasticsearch was crashing due to low memory. But, raising it made the OOM killer reap it.

Instead, I used the oldest trick in the book. I have my hosting provider's 512 MB swap disk, but I added a 512 MB swap file, too. That got Elasticsearch to run and stay running.

It'd still consume all of the CPU, until I added `CPUSchedulingPriority=idle` to the systemd service file. Now, it runs peacefully in the background!

Let's go! :mastodon: :linux: #MastodonAdmins #MastodonServerOperators #SelfHosted

Is there any way to run Mastodon on a single-core low-memory server? I set it up on a cheap $5/month host to try it out, and I like it.

However, I’ve had to disable ElasticSearch, and it’s still prone to expected hangs (while performing maintenance) and unexpected hangs (like when a relay sends over a bunch of posts). It’s not bad, but it could be better.

Can Mastodon (without Docker) be run on a single vCPU and 1 GB of memory? Or, do I need to stop being a cheapskate and fork over an extra $6/month for another core and more memory?

#MastodonAdmins #MastodonServerOperators #selfhosted #sysadmin

Is there any way to run Mastodon on a single-core low-memory server? I set it up on a cheap $5/month host to try it out, and I like it.

However, I’ve had to disable ElasticSearch, and it’s still prone to expected hangs (while performing maintenance) and unexpected hangs (like when a relay sends over a bunch of posts). It’s not bad, but it could be better.

Can Mastodon (without Docker) be run on a single vCPU and 1 GB of memory? Or, do I need to stop being a cheapskate and fork over an extra $6/month for another core and more memory?

#MastodonAdmins #MastodonServerOperators #selfhosted #sysadmin

Is there any way to run Mastodon on a single-core low-memory server? I set it up on a cheap $5/month host to try it out, and I like it.

However, I’ve had to disable ElasticSearch, and it’s still prone to expected hangs (while performing maintenance) and unexpected hangs (like when a relay sends over a bunch of posts). It’s not bad, but it could be better.

Can Mastodon (without Docker) be run on a single vCPU and 1 GB of memory? Or, do I need to stop being a cheapskate and fork over an extra $6/month for another core and more memory?

#MastodonAdmins #MastodonServerOperators #selfhosted #sysadmin

Is there any way to run Mastodon on a single-core low-memory server? I set it up on a cheap $5/month host to try it out, and I like it.

However, I’ve had to disable ElasticSearch, and it’s still prone to expected hangs (while performing maintenance) and unexpected hangs (like when a relay sends over a bunch of posts). It’s not bad, but it could be better.

Can Mastodon (without Docker) be run on a single vCPU and 1 GB of memory? Or, do I need to stop being a cheapskate and fork over an extra $6/month for another core and more memory?

#MastodonAdmins #MastodonServerOperators #selfhosted #sysadmin

Is there any way to run Mastodon on a single-core low-memory server? I set it up on a cheap $5/month host to try it out, and I like it.

However, I’ve had to disable ElasticSearch, and it’s still prone to expected hangs (while performing maintenance) and unexpected hangs (like when a relay sends over a bunch of posts). It’s not bad, but it could be better.

Can Mastodon (without Docker) be run on a single vCPU and 1 GB of memory? Or, do I need to stop being a cheapskate and fork over an extra $6/month for another core and more memory?

#MastodonAdmins #MastodonServerOperators #selfhosted #sysadmin

I just set up my own #selfhosted Mastodon instance. Often times, I’ll sit down and try to do something on my desktop, and be greeted with “Oops! Something went wrong!” with zero explanation as to what this something is that went wrong.

The browser dev tools say something like “type I is undefined.” The officials docs say to check `journalctl` but my failed actions don’t log anything.

If I use #IceCubesApp on my iPhone, everything is flawless. Sometimes if I come back to my computer later, it just works.

I’m not sure how to even begin troubleshooting “Oops!” Is there a way to make Mastodon give *real* error messages?

EDIT: It’s DNS. It’s always DNS.

#MastodonOwners #MastodonServerOperators #MastodonInstanceOperators #sysadmin

I just set up my own #selfhosted Mastodon instance. Often times, I’ll sit down and try to do something on my desktop, and be greeted with “Oops! Something went wrong!” with zero explanation as to what this something is that went wrong.

The browser dev tools say something like “type I is undefined.” The officials docs say to check `journalctl` but my failed actions don’t log anything.

If I use #IceCubesApp on my iPhone, everything is flawless. Sometimes if I come back to my computer later, it just works.

I’m not sure how to even begin troubleshooting “Oops!” Is there a way to make Mastodon give *real* error messages?

EDIT: It’s DNS. It’s always DNS.

#MastodonOwners #MastodonServerOperators #MastodonInstanceOperators #sysadmin

I just set up my own #selfhosted Mastodon instance. Often times, I’ll sit down and try to do something on my desktop, and be greeted with “Oops! Something went wrong!” with zero explanation as to what this something is that went wrong.

The browser dev tools say something like “type I is undefined.” The officials docs say to check `journalctl` but my failed actions don’t log anything.

If I use #IceCubesApp on my iPhone, everything is flawless. Sometimes if I come back to my computer later, it just works.

I’m not sure how to even begin troubleshooting “Oops!” Is there a way to make Mastodon give *real* error messages?

EDIT: It’s DNS. It’s always DNS.

#MastodonOwners #MastodonServerOperators #MastodonInstanceOperators #sysadmin

I just set up my own #selfhosted Mastodon instance. Often times, I’ll sit down and try to do something on my desktop, and be greeted with “Oops! Something went wrong!” with zero explanation as to what this something is that went wrong.

The browser dev tools say something like “type I is undefined.” The officials docs say to check `journalctl` but my failed actions don’t log anything.

If I use #IceCubesApp on my iPhone, everything is flawless. Sometimes if I come back to my computer later, it just works.

I’m not sure how to even begin troubleshooting “Oops!” Is there a way to make Mastodon give *real* error messages?

EDIT: It’s DNS. It’s always DNS.

#MastodonOwners #MastodonServerOperators #MastodonInstanceOperators #sysadmin

I just set up my own #selfhosted Mastodon instance. Often times, I’ll sit down and try to do something on my desktop, and be greeted with “Oops! Something went wrong!” with zero explanation as to what this something is that went wrong.

The browser dev tools say something like “type I is undefined.” The officials docs say to check `journalctl` but my failed actions don’t log anything.

If I use #IceCubesApp on my iPhone, everything is flawless. Sometimes if I come back to my computer later, it just works.

I’m not sure how to even begin troubleshooting “Oops!” Is there a way to make Mastodon give *real* error messages?

EDIT: It’s DNS. It’s always DNS.

#MastodonOwners #MastodonServerOperators #MastodonInstanceOperators #sysadmin