We're Moving!

The Vertica Forum is moving to a new OpenText Analytics Database (Vertica) Community.

Join us there to post discussion topics, learn about

product releases, share tips, access the blog, and much more.

Create My New Community Account Now


LOGIN_FAILURES to post to syslog — Vertica Forum

LOGIN_FAILURES to post to syslog

In Vertica 7.1.2 I can see that we can record events to syslog .. however this doesn't include login failures. I can see the table LOGIN_FAILURES but is there a way to record these login failures to the syslog please?

Comments

  • Hi!

     

    https://my.vertica.com/docs/7.1.x/HTML/Content/Authoring/AdministratorsGuide/Monitoring/Vertica/ConfiguringReportingForSyslog.htm

     

    Supported events:

     

    • Low Disk Space
    • Read Only File System
    • Loss Of K Safety
    • Current Fault Tolerance at Critical Level
    • Too Many ROS Containers
    • WOS Over Flow
    • Node State Change
    • Recovery Failure
    • Recovery Error
    • Recovery Lock Error
    • Recovery Projection Retrieval Error
    • Refresh Error
    • Refresh Lock Error
    • Tuple Mover Error
    • Timer Service Task Error
    • Stale Checkpoint
  • Yep .. found that .. shame it doesn't do login failures ..

    The Data Collector does collect login failure information but it puts this information into a log file that is time stamped - believe it is /<catalog Mount>/<DBName>/<NodeName>/DataCollector ... log file is called <component>_<timestamp>.log

    LoginFailures_497354796314479.log

     

    http://my.vertica.com/docs/7.1.x/HTML/index.htm#Authoring/SQLReferenceManual/SystemTables/MONITOR/DATA_COLLECTOR.htm?Highlight=data collector

     

    This link shows that there should be a IN_VERTICA_LOG and IN_DB_LOG columns which you can switch on to log data collector data to vertica.log and db.log ... but when I query the table data_collector these 2 columns are missing.... anybody else see these columns in the data_collector table?

  • Hi!

     

    dbadmin=> select version();
    -[ RECORD 1 ]-------------------------------
    version | Vertica Analytic Database v7.1.1-3

    dbadmin=> SELECT * FROM data_collector where table_name ilike '%login%';
    -[ RECORD 1 ]----------+------------------------------
    node_name              | v_metanetworks_node0001
    component              | LoginFailures
    table_name             | dc_login_failures
    description            | Failed login attempts
    access_restricted      | t
    in_db_log              | f
    in_vertica_log         | f
    memory_buffer_size_kb  | 200
    disk_size_kb           | 5000
    set_interval           | f
    interval_time_s        | 0
    record_too_big_errors  | 0
    lost_buffers           | 0
    lost_records           | 0
    retired_files          | 0
    retired_records        | 0
    current_memory_records | 0
    current_disk_records   | 71
    current_memory_bytes   | 0
    current_disk_bytes     | 21603
    first_time             | 2015-01-11 08:28:54.275311-05
    last_time              | 2016-02-11 08:05:44.851191-05
    kb_per_day             | 0.0532371522598615

     

     

  • Hi!

     

    >> ..shame..

    A lot of features are missing. If you are Enterprise customer you can open a feature request.

     

    PS

    You can define observer on dc_login_failures file in DataCollector dir and when it modified write to syslog

     

    [dbadmin@host DataCollector]$ ls -1 | grep  Login
    COPY_LoginFailures_TABLE.sql
    CREATE_LoginFailures_TABLE.sql
    LoginFailures_474298134275414.log
    [dbadmin@host DataCollector]$

     

  • In the version we are running 7.1.2-11 those two rows do not exist.

     

    dbadmin=> select version();
    -[ RECORD 1 ]--------------------------------
    version | Vertica Analytic Database v7.1.2-11

    dbadmin=> SELECT * FROM data_collector where table_name ilike '%login%';
    -[ RECORD 1 ]----------+-----------------------
    node_name              | v_tsys_ai_cdm_node0001
    component              | LoginFailures
    table_name             | dc_login_failures
    description            | Failed login attempts
    access_restricted      | t
    memory_buffer_size_kb  | 200
    disk_size_kb           | 5000
    interval_set           | f
    interval_time          | 0
    record_too_big_errors  | 0
    lost_buffers           | 0
    lost_records           | 0
    retired_files          | 0
    retired_records        | 0
    current_memory_records | 0
    current_disk_records   | 0
    current_memory_bytes   | 0
    current_disk_bytes     | 0
    first_time             |
    last_time              |
    kb_per_day             |
    -[ RECORD 2 ]----------+-----------------------
    node_name              | v_tsys_ai_cdm_node0003
    component              | LoginFailures
    table_name             | dc_login_failures
    description            | Failed login attempts
    access_restricted      | t
    memory_buffer_size_kb  | 200
    disk_size_kb           | 5000
    interval_set           | f
    interval_time          | 0
    record_too_big_errors  | 0
    lost_buffers           | 0
    lost_records           | 0
    retired_files          | 0
    retired_records        | 0
    current_memory_records | 0
    current_disk_records   | 0
    current_memory_bytes   | 0
    current_disk_bytes     | 0
    first_time             |
    last_time              |
    kb_per_day             |

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file