Agent Log Description

On each host, the agent log is generated by the NuoDB agent or broker. By default, the agent log also captures output from transaction engines (TEs) and storage managers (SMs).

On Linux, the agent log is written to agent.log. For more information, see Manually rolling over agent.log.

On Windows:

Manually rolling over agent.log

To manage the amount of disk space consumed by agent logging, you can manually roll over agent.log.

Note: Perform the steps described here as: the nuodb user; a user that has nuodb user group privileges; or as the root user.

To manually roll over agent.log, do the following:

  1. Make a copy of the current log file.
    $ cp agent.log agent-Jan-04-2018.log
  2. $ gzip agent-Jan-04-2018.log
  3. Truncate agent.log.
  4. $ echo "$(tail -1000 agent.log)" > agent.log

Note: The last command truncates agent.log and retains the last 1000 lines of the current version of the file.

Examples of Log Entries

DDL statements executed

ddl-audit log entries use the following format:

[ddl-audit] DDL Statement='<ddl>' User='<user>' Client Host='<ip address>

For a description of the ddl-audit log logging category, see Description of Logging Categories.

An example of log lines generated by ddl-audit, after running DDL statements, is as follows:

SQL> create table a(a int);
SQL> create user bla password 'foo';
SQL> alter table a add column s string;
SQL> drop user bla;
SQL> create view va as select * from a;
SQL>
2018-10-09T11:33:05.415+0100: [TE] i7/127.0.0.1:35295 (DEFAULT_REGION) [ pid = 2133 ] [ db = test ] [ nodeId = 5 ] RUNNING=>[ddl-audit] DDL Statement='create table a(a int)' User='DBA' Client Host='127.0.0.1'
2018-10-09T11:33:19.023+0100: [TE] i7/127.0.0.1:35295 (DEFAULT_REGION) [ pid = 2133 ] [ db = test ] [ nodeId = 5 ] RUNNING=>[ddl-audit] DDL Statement='create user bla password ****************' User='DBA' Client Host='127.0.0.1'
2018-10-09T11:33:45.019+0100: [TE] i7/127.0.0.1:35295 (DEFAULT_REGION) [ pid = 2133 ] [ db = test ] [ nodeId = 5 ] RUNNING=>[ddl-audit] DDL Statement='alter table a add column s string' User='DBA' Client Host='127.0.0.1'
2018-10-09T11:34:47.173+0100: [TE] i7/127.0.0.1:35295 (DEFAULT_REGION) [ pid = 2133 ] [ db = test ] [ nodeId = 5 ] RUNNING=>[ddl-audit] DDL Statement='drop user bla' User='DBA' Client Host='127.0.0.1'
2018-10-09T11:34:58.831+0100: [TE] i7/127.0.0.1:35295 (DEFAULT_REGION) [ pid = 2133 ] [ db = test ] [ nodeId = 5 ] RUNNING=>[ddl-audit] DDL Statement='create view va as select * from a' User='DBA' Client Host='127.0.0.1'

DDL Statements Executed Without Locks

The following log entry is generated in agent.log if a DDL operation is executed without a lock on the table.

The following operation did not acquire a table lock and could be potentially insecure:
<DDL OPERATION>

Note: NuoDB recommends an exclusive lock for all potentially insecure DDL operations. For more information see LOCK.