Logging failure - recent versions including 4.69.

Posted by Toreador on Thu 11 Nov 2010 06:21 PM — 11 posts, 34,802 views.

USA #0
When I log, the files don't contain standard text. Instead, they're filled with various symbols.

How do I fix this?

Thanks.
Australia Forum Administrator #1
Might you have checked the "Raw" button on the logging configuration page? That logs the raw data from the MUD including ANSI colour codes, which may look like "various symbols".

Unless you have a particular reason to, leave that unchecked.
USA #2
I've checked my world preferences, Raw was unchecked.

This is a sample of what I find in logs:


畂瑲湯愠⁴桓湡⁧‭桔牵摳祡‬潎敶扭牥ㄠⰱ㈠㄰ⰰ㌠ㄺ‱䵐਍ⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭ਍਍桔獩椠⁳⁡整瑳氠杯映牯丠捩慇浭湯‬慭敤猠⁉慣敤潭獮牴瑡⁥桴⁥牰扯敬❉慨楶杮മ

Thanks.
USA #3
Ack. The sample of what I'm getting in the previous post is inaccurate. The symbols don't carry through into posting here.

The best description I can give is to say they look like Chinese language characters.

Thanks.
Australia Forum Administrator #4
Like this?



Well that's odd. What version worked for you (if any)?
Australia Forum Administrator #5
Do you log just by turning logging on in the world configuration? Or do you use the WriteLog script function?
Australia Forum Administrator #6
Also, if you edit the log files do you actually see "畂瑲湯" or do you see the "chinese" characters, and they just look like that on the forum?
Australia Forum Administrator #7
Can you email me one of the log files please? Zip it up in case the email program changes it somehow and sent it to:

(email address deleted to reduce spam)

Amended on Fri 12 Nov 2010 02:24 AM by Nick Gammon
USA #8
Email sample soon to come. The characters appear as you showed them in one of your replies. I log using the log session function under File tab.

This started to happen a few versions ago, I've been using MushClient for years, even had paid registration before you changed over.

How do I use the WriteLog script function?

Thanks.
Australia Forum Administrator #9
Template:function=WriteLog
WriteLog

The documentation for the WriteLog script function is available online. It is also in the MUSHclient help file.



However if you aren't using it I wouldn't necessarily start now. I am more interested to getting to the bottom of what is happening.

If you want to try, a low-sequence trigger, matching everything, and with "keep evaluating" checked, could use a small bit of script to send lines to the log file.
Australia Forum Administrator #10
I tried logging and it worked fine for me. Can you confirm a few other things?

  • Did you install other things recently? For example, Chinese fonts.
  • Have you started using encryption?
  • Did you set up some sort of automatic zip-up of your log files to save space?
  • What version of Windows do you have (or is it Ubuntu?)
  • Can you run a disk-check utility (eg. chkdsk or whatever it is called)? It is possible your disk is corrupted and you are reading back bad data.
  • Can you revert back to a version of MUSHclient that works? The Announcements section of the forum will have links to lots of older versions. If you can confirm that it works in version X, but not in X+1 that will help track it down.
  • Can you possibly try it on a different PC (eg, a laptop) to confirm if it is just confined to a particular PC?