From the log messages below, tlsrpt-reportd seems to be using the fetcher to correctly identify the test domain after daily rollover, but I can't explain the Invalid JSON. Does tlsrpt-reporter also need a json tool? Did I miss to give permissions or a path somewhere?
I am running tlsrpt-collectd and tlsrpt-reportd as systemd units with a /usr/bin/venv deployment on Rocky 9.6. tlsrpt-collectd receives tls data from postfix-tlspol/postfix. Same result with http_script variable uncommented.
Thank you
Mike
Jun 12 02:11:12 mx03.xxxxxx.com tlsrpt-reportd[7104]: 2025-06-12 02:11:12,811 tlsrpt_fetcher INFO tlsrpt 703 : Database /var/spool/tlsrpt-reporter/tlsrpt-collectd.sqlite.yesterday looks OK
Jun 12 02:11:12 mx03.xxxxxx.com tlsrpt-reportd[7104]: 2025-06-12 02:11:12,811 tlsrpt_fetcher INFO tlsrpt 712 : TLSRPT fetcher domain list starting for day 2025-06-11
Jun 12 02:11:12 mx03 xxxxxx.com tlsrpt-reportd[7099]: 2025-06-12 02:11:12,821 tlsrpt_reportd ERROR tlsrpt 1065 : Invalid JSON: Expecting value: line 1 column 1 (char 0)
Jun 12 02:11:12 mx03.xxxxxx .com tlsrpt-reportd[7099]: 2025-06-12 02:11:12,822 tlsrpt_reportd DEBUG tlsrpt 1218 : Create reports
Jun 12 02:11:12 mx03.xxxxxx.com tlsrpt-reportd[7099]: 2025-06-12 02:11:12,822 tlsrpt_reportd WARNING tlsrpt 1224 : Incomplete data for domain yyyyyyy.com by fetcher index 1
Jun 12 02:11:12 mx03.xxxxxx.com tlsrpt-reportd[7099]: 2025-06-12 02:11:12,822 tlsrpt_reportd DEBUG tlsrpt 1373 : Send out reports
Jun 12 02:11:12 mx03.xxxxxx.com tlsrpt-reportd[7099]: 2025-06-12 02:11:12,822 tlsrpt_reportd INFO tlsrpt 1440 : Sleeping for 9 seconds
Manually running fetcher script:
[root@mx03 ~]# /usr/local/bin/tlsrpt-fetcher_01.sh
2025-06-12 03:41:53,235 tlsrpt_fetcher INFO tlsrpt 1481 : CONFIGURATION with 3 settings:
2025-06-12 03:41:53,235 tlsrpt_fetcher INFO tlsrpt 1483 : CONFIG from cfg option storage is sqlite:///var/spool/tlsrpt-reporter/tlsrpt-collectd.sqlite
2025-06-12 03:41:53,235 tlsrpt_fetcher INFO tlsrpt 1483 : CONFIG from cfg option logfilename is /var/log/tlsrpt-reporter/tlsrpt-fetcher.log
2025-06-12 03:41:53,235 tlsrpt_fetcher INFO tlsrpt 1483 : CONFIG from cfg option log_level is debug
2025-06-12 03:41:53,236 tlsrpt_fetcher DEBUG tlsrpt 376 : Try to open database '/var/spool/tlsrpt-reporter/tlsrpt-collectd.sqlite.yesterday'
2025-06-12 03:41:53,237 tlsrpt_fetcher INFO tlsrpt 703 : Database /var/spool/tlsrpt-reporter/tlsrpt-collectd.sqlite.yesterday looks OK
2025-06-12 03:41:53,237 tlsrpt_fetcher INFO tlsrpt 712 : TLSRPT fetcher domain list starting for day 2025-06-11
TLSRPT FETCHER v1devel-c domain list
2025-06-12 09:41:53
2025-06-11
yyyyyyyy.com
.
/etc/tlsrpt-reporter/reportd.cfg:
------------------------------------------------
[tlsrpt_reportd]
dbname = /var/spool/tlsrpt-reporter/tlsrpt-reportd.sqlite
logfilename = /var/log/tlsrpt-reporter/tlsrpt-reportd.log
log_level = debug
#http_script = curl --silent --header 'Content-Type: application/tlsrpt+gzip' --data-binary @-
fetchers = /usr/local/bin/tlsrpt-fetcher_01.sh
interval_main_loop = 10
max_retries_domainlist = 2
min_wait_domainlist = 0
max_wait_domainlist = 1
max_retries_domaindetails = 2
min_wait_domaindetails = 0
max_wait_domaindetails = 1
spread_out_delivery = 3
organization_name = xxxxxx.com
contact_info = postmaster(a)xxxxxx.com
sender_address = no-reply-tls-reports(a)xxxxxx.com
