Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #30693
Closed (moved) (moved)
Open
Created May 30, 2019 by David Fifield@dcf

Delete old unsanitized logs

After #21304 (moved), in the 2019-04-18 team checkin, we agreed to delete the pre-sanitization logs by 2019-06-01. Before then, we have a chance to extract any useful sanitized information from them.

Cf. comment:8:ticket:30125 regarding the location of logs.

=== Broker

On the broker, there are three files to delete:

/var/log/snowflake-broker/unstanitized.tar:: Contains three files: * '''unsanitized.tar.1''', pre-rotation logs from 2017-07-15 to 2019-03-22 and rotated logs from 2017-03-22 to 2019-04-16. * '''@400000005cb771341453839c.s''', logs from 2019-04-16 to 2019-04-17. * '''current''', empty file. /var/log/snowflake-broker/mv:: Probably the result of a typo, it is a tar file that contains a single file unsanitized.tar which is identical to the unsanitized.tar.1 inside /var/log/snowflake-broker/unstanitized.tar. /var/log/snowflake-broker/x.tar:: contains a subset of what /var/log/snowflake-broker/mv contains.

I think the most complete logs come from /var/log/snowflake-broker/unstanitized.tar, extracting the contained unsanitized.tar.1 and combining it with the contained @400000005cb771341453839c.s.

=== snowflake-server

/var/log/tor/unsanitized.tar:: contains rotated logs dated 2019-02-18 to 2019-04-11.

=== proxy-go /home/snowflake-proxy/snowflake-proxy-17h.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-23h.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-29h.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-restartless.log.d/unsanitized.2.tar:: /home/snowflake-proxy/snowflake-proxy-restartless.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-17h.log.d/unsanitized.2.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-17h.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-23h.log.d/unsanitized.2.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-23h.log.d/unsanitized.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-29h.log.d/unsanitized.2.tar:: /home/snowflake-proxy/snowflake-proxy-standalone-29h.log.d/unsanitized.tar:: /home/snowflake-proxy/unsanitized_old.tar::

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking