[Samba] Samba 4 DC log.smd flooded with Conversion error

Kinglok, Fong busywater at gmail.com
Wed Feb 13 08:07:55 MST 2013


Dear all,

After setting dos charset = CP950 (which is the codepage for traditional chinese), the same error still remains.

Furthermore, I have tried testing in a real production environment by the following steps:

1.  In smb.conf,
     I create a share called Chinese and increase the log level to 10.
	[global]
		workgroup = YAUOICHURCH
		realm = SAMBA4.YAUOI.ORG
		netbios name = FILE
		server role = active directory domain controller
		dns forwarder = 192.168.107.1
		log level = 10
		unix charset = UTF8
		dos charset = CP950
	[netlogon]
		path = /usr/local/samba/var/locks/sysvol/samba4.yauoi.org/scripts
		read only = No
	[sysvol]
		path = /usr/local/samba/var/locks/sysvol
		read only = No
...
	[Chinese]
		path = /home/chinese
		read only = No

2.  In the file server, I have created a directory /home/chinese and also, inside it, I have open a folder called "中文測試" and I have tested the name is in UTF-8.

3.  I made use of Windows 7 64-bit Traditional Chinese as client to try to browse the share Chinese and then the folder (the client has joined the domain already) and I install wireshark to capture the packet.
The wireshark capture is here:
http://kinglok.org/wireshark2.pcapng

4.  the log.smbd still show
[2013/02/13 18:12:11.869648,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:316(convert_string_handle)
  convert_string_internal: Conversion error: Illegal multibyte sequence(中æ<96><87>測試)
[2013/02/13 18:12:11.870614,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(¸­æ<96><87>測試)
[2013/02/13 18:12:11.871426,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(­æ<96><87>測試)
[2013/02/13 18:12:11.872210,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:316(convert_string_handle)
  convert_string_internal: Conversion error: Illegal multibyte sequence(æ<96><87>測試)
[2013/02/13 18:12:11.872970,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(<96><87>測試)
[2013/02/13 18:12:11.873757,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(<87>測試)
[2013/02/13 18:12:11.874520,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:316(convert_string_handle)
  convert_string_internal: Conversion error: Illegal multibyte sequence(測試)
[2013/02/13 18:12:11.875503,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(¸¬è©¦)
[2013/02/13 18:12:11.876199,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(¬è©¦)
[2013/02/13 18:12:11.876953,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:316(convert_string_handle)
  convert_string_internal: Conversion error: Illegal multibyte sequence(試)
[2013/02/13 18:12:11.877743,  3, pid=6810, effective(0, 100), real(0, 0)] ../lib/util/charset/convert_string.c:297(convert_string_handle)
  convert_string_internal: Conversion error: Incomplete multibyte sequence(©¦)

The whole log is here:
http://kinglok.org/log.smbd.2

Should I file a bug for it?

Kinglok, Fong


On 11 Feb 2013, at 11:14 PM, TAKAHASHI Motonobu wrote:

> From: "Kinglok, Fong" <busywater at gmail.com>
> Date: Sun, 10 Feb 2013 09:40:49 +0800
> 
>> Thank you for your help but…
>> 
>> I execute some commands to make sure the locale is in UTF-8 by
>> dpkg-reconfigure locales and even adding setting in /etc/environment
>> 
>> and using utility like convmv to turn all file and folder into UTF-8 (in fact, they were in UTF-8 already.)
>> 
>> I add option in smb.conf
>> unix charset = UTF8
>> dos charset is omitted as default (dos charset = CP850)
>> 
>> However, when I run
>> /usr/local/samba/bin/smbclient //localhost/Public -UAdministrator%'verysecurepasswd' -c 'ls'
>> 
>> The same error in my log floods……
> 
> No, you have to set 'dos charset' parameter correctly. In my Japanese
> environment, same errors occur unless I set "dos charset = CP932", which
> means Japanese. It seems that you use Chinese.
> 
> ---
> TAKAHASHI Motonobu <monyo at monyo.com> / @damemonyo 
>                   facebook.com/takahashi.motonobu
> 



More information about the samba mailing list