ZOOM: no longer creating putlogs

[FreddieAkeroyd]

ZOOM is no longer logging channel access puts - it looks line this stopped yesterday lunchtime and coincides with the following in the ioclog server log

[Tue Jun 5 11:42:04 2018] IOC Client 127.0.0.1:52244 disconnected

[Tue Jun 5 11:42:23 2018] IOC Client 127.0.0.1:52260 connected

[Tue Jun 5 11:42:23 2018] [Fatal Error] :1:249: An invalid XML character (Unicode: 0x17) was found in the CDATA section.

[Tue Jun 5 11:42:23 2018] Could not parse XML formatted message.
[Tue Jun 5 11:42:23 2018] IOC Client 127.0.0.1:52260 disconnected
[Tue Jun 5 11:42:24 2018] Database error, error: 'Message Type "-" not recognised' Will retry.
[Tue Jun 5 11:42:25 2018] Database error, error: 'Message Type "-" not recognised' Will retry.
[Tue Jun 5 11:42:26 2018] Database error, error: 'Message Type "-" not recognised' Will retry.
[Tue Jun 5 11:42:27 2018] Database error, error: 'Message Type "-" not recognised' Will retry.

The final message continues to be repeated at regular intervals

Added requirements: Reproduced locally by @aaron-long and @John-Holt-Tessella :

1. Start a new run to make putlog empty
2. Write the title caput -S TE:NDLT1095:DAE:TITLE a
3. Observe the putlog write
4. Run the log server writer:

   cd C:\Instrument\Apps\EPICS\ISIS\IocLogServer\master\dev-tools
   python ioc_message_simulator.py
   

5. Hold alt and on keypad type 0017 to produce the offending character
6. Write a new title
7. This does not appear in the put log

[KathrynBaker]

This has happened again on ZOOM, whilst trying to figure out what went wrong for something else. The lack of these logs makes it harder to diagnose some types of support call. so this needs looking at and resolving. It may be a symptom of something else, or something else may be causing it, but these putlogs are very useful to some of us

[DominicOram]

This also corresponded with the following on the BLOCKSVR logs:

[Fri Dec 7 16:30:26 2018] [1544200226.57] MAJOR: Could not restart IOC ALARM: Could not get auto-restart property for IOC (IN:ZOOM:CS:PS:ALARM) got '��E�'

The unicode characters here are not valid XML. I've modified inst_servers to ensure that it only gives valid XML at ISISComputingGroup/EPICS-inst_servers#183. I'm still investigating why procserver/alarmserver gave such an odd response in the first place.