
On a Linux system, the Venafi agent logs events to the following SQLite file.
/var/opt/venafi/agent/data/events.sq3
The vagent command with the --list all flag can be used to display the current log level.
/opt/venafi/agent/bin/vagent --list all
In this example, the log level is info.
Module Venafi Agent:
report_type INTERVAL_HOURS
report_step 1
report_start 7
report_random 5
logging Info
logging_facility Daemon
event_row_count 50000
vacuum After
reserved_freespace 50
server_url https://venafi.example.com/vedclient
proxy_url
proxy_username
proxy_password
registration_password ********
rolling_code root:In Use
server_thumbprint
checkin_now
crl_checking Disabled
log_communications Enabled
dump_statistics
certificate_security Disabled
client_id root:Client+Default:11:1674
checkin_delay 0
heartbeat_interval 0
The vagent command with the -m or --modify option can be used to temporarily change the log level.
/opt/venafi/agent/bin/vagent --modify logging=debug
Something like this should be returned.
logging debug; was set or modified.
The vagent command with the -v (verbose) flag can be used to display contents of the events.sq3 file.
/opt/venafi/agent/bin/vagent -v
Something like this should be returned.
3822512|2021-05-18 03:26:21.867|1621326381|140097524754176|1729|8|Debug:vagent_1729 Venafi Agent Library: CURL operation: vam_client_op_deliver(), elapsed time: 0.186
3822513|2021-05-18 03:26:21.890|1621326381|140097524754176|300|8|Debug:ksprovision_300 VED Agent KeyStore Provision: received provision processing operation DELAY.
3822514|2021-05-18 03:26:21.908|1621326381|140097524754176|802|8|Debug:ksprovision_802 VED Agent KeyStore Provision: provision processing DELAY operation, delaying 1 seconds.
3822515|2021-05-18 03:26:22.928|1621326382|140097524754176|1732|8|--- vam_client_op_deliver() request: Tue May 18 08:26:22 2021 ---
route: /certificate/provisioning/retrieve content_length:24
{
"RetrieveCount": 40659
}
End: vam_client_op_deliver() request
Additionally, events will be appended the logger daemon, which on Linux, typically means the events will be in the journal. At log level info, the journal will probably have something like this.
May 18 04:28:24 server001 Venafi-Agent[1768]: Informational:vagent_1720 Venafi Agent Library: Server checkin started on Tue May 18 04:28:24 2021
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:vagent_1722 Venafi Agent Library: Base work configuration processing started on Tue May 18 04:28:26 2021
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:vagent_1009 Venafi Agent Library: work handle: da7c6554-0a82-4566-9bd5-18d40c341135, not implememnted
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:vagent_1004 Venafi Agent Library: assignment: 92CE445D-B0D9-4673-9F0E-E296886227EE, for service module: VED Agent KeyStore Provision, scheduled to run on Tue May 18 04:28:25 2021
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:vagent_11 Venafi Agent Library: VED Agent KeyStore Provision assignment processing started on Tue May 18 04:28:26 2021
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:ksprovision_306 VED Agent KeyStore Provision: provision processing operation completed on Tue May 18 04:28:26 2021
May 18 04:28:26 server001 Venafi-Agent[1768]: Informational:vagent_15 Venafi Agent Library: VED Agent KeyStore Provision assignment processing concluded on Tue May 18 04:28:26 2021, status:0
At log level debug, the journal should have something like this.
May 18 05:29:23 server001 Venafi-Agent[1768]: Informational:vagent_1720 Venafi Agent Library: Server checkin started on Tue May 18 05:29:23 2021
May 18 05:29:23 server001 Venafi-Agent[1768]: Debug:vagent_1721 Venafi Agent Library: Server checkin count since epoch: 208
May 18 05:29:23 server001 Venafi-Agent[1768]: Debug:vagent_1714 Venafi Agent Library: Unexpected protocol response from server: https://venafi.example.com/vedclient/client/checkin, code: 401, msg: HTTP/1.1 401 '/vedclient/client/checkin' is an invalid API key
May 18 05:29:23 server001 Venafi-Agent[1768]: Debug:vagent_1725 Venafi Agent Library: CURL operation: op_checkin, attempting to reauthorize. Attempt num
ber: 1, delay: 1
May 18 05:29:24 server001 Venafi-Agent[1768]: Debug:vagent_1704 Venafi Agent Library: Successfully acquired session key from: https://venafi.example.com/vedclient/
May 18 05:29:25 server001 Venafi-Agent[1768]: Debug:vagent_1729 Venafi Agent Library: CURL operation: vam_client_op_session(), elapsed time: 0.083
May 18 05:29:25 server001 Venafi-Agent[1768]: Debug:vagent_1709 Venafi Agent Library: Received work item count: 5
May 18 05:29:25 server001 Venafi-Agent[1768]: Debug:vagent_1729 Venafi Agent Library: CURL operation: vam_client_op_checkin(), elapsed time: 1.282
May 18 05:29:25 server001 Venafi-Agent[1768]: Debug:vagent_1011 Venafi Agent Library: assignment: 1c27913f-4d3a-4d96-9b6b-7794bbf2f320, retaining
May 18 05:29:25 server001 Venafi-Agent[1768]: Informational:vagent_1722 Venafi Agent Library: Base work configuration processing started on Tue May 18 0
5:29:25 2021
May 18 05:29:25 server001 Venafi-Agent[1768]: Informational:vagent_1009 Venafi Agent Library: work handle: da7c6554-0a82-4566-9bd5-18d40c341135, not imp
lememnted
May 18 05:29:25 server001 Venafi-Agent[1768]: Informational:vagent_1004 Venafi Agent Library: assignment: 92CE445D-B0D9-4673-9F0E-E296886227EE, for service module: VED Agent KeyStore Provision, scheduled to run on Tue May 18 05:29:24 2021
May 18 05:29:25 server001 Venafi-Agent[1768]: Informational:vagent_11 Venafi Agent Library: VED Agent KeyStore Provision assignment processing started on Tue May 18 05:29:25 2021
May 18 05:29:26 server001 Venafi-Agent[1768]: Informational:ksprovision_306 VED Agent KeyStore Provision: provision processing operation completed on Tue May 18 05:29:26 2021
May 18 05:29:26 server001 Venafi-Agent[1768]: Informational:vagent_15 Venafi Agent Library: VED Agent KeyStore Provision assignment processing concluded on Tue May 18 05:29:26 2021, status:0
Did you find this article helpful?
If so, consider buying me a coffee over at