If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)

Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

GitLab comedy gold

01-02-2017 10:46pm

#1

gctest50

Registered Users, Registered Users 2 Posts: 9,605 ✭✭✭

Join Date: September 2012

Posts: 9499

https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7_z_6jHdVik/pub

Suggested recovery solutions:

Sid: try to undelete files?

CW: Not possible! `rm -Rvf` Sid: OK

So in other words, out of 5 backup/replication techniques deployed none are working reliably or set up in the first place.

0

Comments

#2 01-02-2017 10:49pm

Creamy Goodness

Registered Users, Registered Users 2 Posts: 26,584 ✭✭✭✭

Join Date: November 2001

Posts: 25713

Wouldn't say it's comedy gold. We've all been in similar scenarios and thinking back to how I felt during/and days afterwards it wasn't great.

It serves as a good lesson. Back up, test them and then test them again.

They have to be commended for how transparent they're being. Although apparently they were live streaming them fixing it, don't do that. That's just weird.

0
#3 01-02-2017 10:58pm

purpleisafruit

Registered Users, Registered Users 2 Posts: 508 ✭✭✭

Join Date: November 2015

Posts: 481

Everyone has messed up like that in work. I've locked myself and everyone else out of production machines when updating iptables rules. The particular machine was the DB for the whole system and without access, we were in serious crap. Thankfully, my ineptitude with iptables meant a reboot stopped the service as I'd failed to persist the service in /etc/init.d
Moral of the story, sometimes not knowing enough about something can save your arse. I now have a cronjob that I setup to flush iptables every 15 mins whilst trying to do anything that might lock me out

0