Reports until 12:37, Wednesday 18 October 2017
H1 CDS
patrick.thomas@LIGO.ORG - posted 12:37, Wednesday 18 October 2017 - last comment - 15:18, Tuesday 31 October 2017(39070)
conlog down
It appears that some process variables are taking on values with characters that do not conform to JSON:

Oct 18 11:10:12 conlog-master conlogd[7334]: terminate called after throwing an instance of 'sql::SQLException'
Oct 18 11:10:12 conlog-master conlogd[7334]: what():  Invalid JSON text: "Invalid escape character in string." at position 44 in value for column 'events.data'.
Oct 18 11:41:52 conlog-master conlogd: Server started. prefix: 'H1:CDS-CONLOG_' database: 'conlog' max inserts: 500 max time: 30 keep alive period: 30 time source: 0 create_messages: 1
Oct 18 11:59:32 conlog-master conlogd[8524]: terminate called after throwing an instance of 'sql::SQLException'
Oct 18 11:59:32 conlog-master conlogd[8524]: what():  Invalid JSON text: "Invalid escape character in string." at position 44 in value for column 'events.data'.
Oct 18 12:19:34 conlog-master conlogd: Server started. prefix: 'H1:CDS-CONLOG_' database: 'conlog' max inserts: 500 max time: 30 keep alive period: 30 time source: 0 create_messages: 1
Oct 18 12:34:12 conlog-master conlogd[9092]: terminate called after throwing an instance of 'sql::SQLException'
Oct 18 12:34:12 conlog-master conlogd[9092]: what():  Invalid JSON text: "Invalid escape character in string." at position 44 in value for column 'events.data'.

The same error repeats at each loading of the channel list.
Comments related to this report
patrick.thomas@LIGO.ORG - 15:18, Tuesday 31 October 2017 (39235)
Restarted the MySQL server with the general query log enabled to log the SQL query causing the crash. Restarted conlog. Crash did not occur on restart this time. Will leave log enabled for now.