Notices by disroot (disroot@social.weho.st), page 2

???? Server upgrade ????

Tonight we are planning long awaited infrastructure upgrade on #disroot.

We are going to deploy new database server as well as upgrade file storage capacity.

We hope to be able to do all that at once, with minimal downtime possible. However disroot platform might be offline for even few hours.

If you see stuff being down, dont panic, keep your fingers crossed, drink a cup of hot coffee for us, have a good sleep or get some fresh air.

https://state.disroot.org/incident/93

@colegota
Damn.

Fixed.

Preparing hardware upgrade for Disroot.
New database server on the way:
Dell R610
6*512GB SSD's
88 GB RAM

▪️ Disroot total Blackout ▪️

Today Disroot's server had a bit of a tumble. Due to little mistake, our main server became a total zombie. There was no way for us to bring it back to life other then driving 70km to the data-center to manually restart it. Server was down at 14:45 and back up at 16:05.

We're very sorry...

????????????????????????
Because of stupidity of one of the admins, our main server is down.
We need to drive to the datacenter to kickstart it.
We should be back in 2h

Sorry for the fuckup folks!

@izaro

@demoakracia @mass92
Thats why we've created https://howto.disroot.org its not complete but slowly getting there. Thanks to amazing work of some of the users its being translated to many languages (also spanish).

Within next two /three weeks we are planning major update where we’re going to deploy a dedicated SSD based bare metal server for databases only. This should improve the performance and hopefully such issues with matrix will not occur anymore. We were hoping matrix will go easy on us until then, but looks like it was rather wishful thinking.

Hope you guys understand and live through this little turbulence for a bit longer without throwing your keyboards outside the window.
???? ???? ???? ???? ????

FYI Things are back to normal.

# Disroot Performance issue
Due to what we believe unintentional abuse of cloud service from one of the users, our server was brought to it's knees. We have identified the issue and applied a fix. However it will take some good few hours for everything to calm down and get back to normal.

We're sorry for inconvenience

#disroot

We hope you are all enjoying the last days of 2017 and are ready to take on what comes next year. These last months have been really encouraging for us with all the positive feedback we've been getting, the increase of support and of course the impressive contribution of translations. We are now ready to introduce the couple of extra feature we've been promising for some time...
read more on our blog: https://disroot.org/en/blog/happy-new-year

Hey peeps. Aparently someone made an account on twitter https://mobile.twitter.com/DisrootOrg which is not owned by us. Can someone with twitter account contact this account, tell them to contact us asap, and remove this account please?

We are trying to provide alternatives for a reason, and dont do tritter for a reason!!!!

Unexpected Server reboot

Most probably due to issue caused by out of memory scenario on one of the virtual containers, our main server has restarted, which caused a downtime of about 15 min. (booting the server, restarting all containers etc).

We will keep an eye on this as it might indicate hardware failure.
#disroot

https://state.disroot.org/incident/66

Nextcloud has just been updated to version 12.04.

Webmail autologin is back! \o/
You will need to put the password one more time.

#disroot #nextcloud

Update:

Thanks to clever engineers who think out of the box in the DataCenter and the fact we have redundant power on our servers (two power suppliers), guys figured a way to keep our servers alive while doing their maintenance work.

So looks like there won’t be a need for downtime.

Due to maintenance work on the Rack in the dataCenter where our servers are located, Disroot will be down for approximately 30 min.
This is totally not dependent on us, as the work done by DataCenter staff requires the power to be off in the entire rack.

We hope this will be a smooth operation and we'll be back online in no time!
#disroot
https://state.disroot.org/incident/63

DIsroot Platform reboot

(4.12.2017 - 2:00 - Amsterdam Localtime)

Due to some security updates we need to restart the host servers. This means all services will be down for no longer then 5 minutes.
#disroot
https://state.disroot.org/incident/62

Just finished a mumble meetup with community around https://elbinario.net/
It was very cool to meet and talk with some of the disrooters out there and similar minded people. @elbinario

@elmau @elbinario
We use captcha to prevent bots creating thousands of accounts, reserving the usernames that could be used otherwise.

We use re-captcha because thats the only captcha supported by user creation system we use in disroot.

Belive me we are ashamed of it, but until now it was the only way. However we are experimenting with a workaround now which will (if successful) eliminate re-captcha from our systems.

@elmau @juansantiago

**UPDATE:**
Google search results are back. Looks like we've been experiencing some abuse activity last days, which caused google to reject our queries.

We will work in coming days on implementing mechanisms (rate limits etc) that will help prevent this situation.

https://state.disroot.org/incident/61

BTW. Since searx is just a meta search, we could add some yacy instances to the mix. If you guys know any public ones give us a shout. We are thinking of running one in the near future

We're having some performance issue on diaspora.

We're looking into it now.
https://state.disroot.org/incident/54