Opened 2 months ago

Closed 2 months ago

#31095 closed defect (fixed)

crispum appears unused -- decommission

Reported by: weasel Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: tom Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

crispum is supposed to be the tb-crashes host which we have maintained for two years but which appears to never have been used by the team that requested it.

decommission?

Child Tickets

Change History (9)

comment:1 Changed 2 months ago by gk

Cc: tom added

Fine with me, tom?

comment:2 Changed 2 months ago by tom

Do it

comment:3 Changed 2 months ago by anarcat

i've scheduled a shutdown for tomorrow, as a first test to see if anything will break. then if we can survive without the box for a little longer, i will destroy it with fire.

Shutdown scheduled for Tue 2019-07-09 16:34:40 UTC, use 'shutdown -c' to cancel.

comment:4 Changed 2 months ago by anarcat

should we destroy backups too?

comment:5 Changed 2 months ago by tom

Maybe keep one backup if it's small, just so we don't lose the config files for the setup? Or if you want you can just send me the backup and I'll extract what I need and archive them

comment:6 Changed 2 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

comment:7 Changed 2 months ago by anarcat

Maybe keep one backup if it's small, just so we don't lose the config files for the setup? Or if you want you can just send me the backup and I'll extract what I need and archive them

do you have access to the server normally? (I know that you might not have now, because it's in shutdown, but normally...) in that case, you could perform the archival yourself...

what would need to be archived there anyways that's not on git.tpo or archive.tpo? crash data? maybe that should be destroyed anyways because it's a PII liability?

comment:8 in reply to:  7 Changed 2 months ago by tom

Replying to anarcat:

Maybe keep one backup if it's small, just so we don't lose the config files for the setup? Or if you want you can just send me the backup and I'll extract what I need and archive them

do you have access to the server normally? (I know that you might not have now, because it's in shutdown, but normally...) in that case, you could perform the archival yourself...

what would need to be archived there anyways that's not on git.tpo or archive.tpo? crash data? maybe that should be destroyed anyways because it's a PII liability?

No, not the crashes (don't think there are any) rather how the server was configured. I looked around for it, but couldn't find it. If we ever get this working anyway we'll just redo it, I think the knowledge has been lost at this point. Nuke it all.

comment:9 Changed 2 months ago by anarcat

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.