Very Secure

The First Batch of TheFleet's Logs

To view TheFleet's first batch of logs, setup postgres,1 create a user named "thefleet", grant thefleet all privileges on schema public, and create a database named "fleetbotdb".2 Then download and load one of the two sql files that contain the collected data.

fleet2 sql tarball
fleet3 sql tarball

Instructions with commands:

Download the tar of the logs. (You can switch fleet2 to fleet3)

tar -zxvf thefleet2_mar_27_2020.sql.tar.gz; 

Create a home for TheFleet logs by creating a user and database.

su postgres

create user thefleet;
create database fleetbotdb;
grant all privileges on schema public to thefleet;

Load the .sql file into the created db and test to make sure you have at least a couple million rows in the irclog table.

psql -U thefleet fleetbotdb < thefleet2_mar_27_2020.sql

psql -U thefleet fleetbotdb
select count(*) from irclog;
  1. For installing Postgres on Centos6 you can look at the relevant section in my guide to setting up logbot. Name your postgres user thefleet and your database fleetbotdb. []
  2. You can make your life easier by opening pg_hba.conf (found at /var/lib/pgsql/9.4/data/pg_hba.conf on my machine) and changing local connections so that they don't require a password by setting the last value in the column to "trust":

    # "local" is for Unix domain socket connections only
    local   all             all                                     trust
    # IPv4 local connections:
    host    all             all               trust


2 Responses to “The First Batch of TheFleet's Logs”

  1. Diana Coman says:

    Thrown like this, an archive with no context and no information is ~rubbish, not data. And not like I haven't said it already, ffs. If you find it difficult to answer, it does NOT mean you just don't answer it and all is fine.

    Add the context there as clear as there is, at the very least and stop ignoring feedback because it's inconvenient.

Leave a Reply