After an day without issues i just received an phone call about an
printing issue and i found a few "illegal multibyte sequence" errors in
the log file again.
Unfortunately i can not reproduce the situation where this error occured
an second try to print that document out of the archive worked but since
it's an crystal report form generated out of an database from our
business software something may be different when printing from the
archive. Hope i'll get an reproducible situation so i can grab an
wireshark trace and more detailed samba log info's.
achim~
Am 15.09.2011 17:01, schrieb Achim Gottinger:
Update:
Checked logs of all my debian print servers and none had these error
messages today, i guess i had forgotten to restart samba on that
server whom still showed the error. I had also found that erroro
message on a few other servers with an missing unix charset line whom
i all moodified and restarted. (There is still a chance that they did
not print anything which triggered that error.)
Here is an bug report for that problem, that's where i found that unix
charset fix.
https://bugzilla.samba.org/show_bug.cgi?id=8082
Checked the default if that variable is not explicity declared in
smb.conf with terstparam -v and it is
unix charset = UTF-8
display charset = LOCALE
Seems debian has an problem with UTF-8 but not with UTF8. =-O
These are my locale settings
#locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
https://bugzilla.samba.org/show_bug.cgi?id=8082
Am 15.09.2011 01:04, schrieb Achim Gottinger:
It is odd here also, on one server (debian lenny with samba 3.5.6
from backports) using
dos charset = 850
unix charset = UTF8
fixed that issue on an other server (same osand versions) i also had
to add the unix charset line and it worked for an document which did
not work without and generated an error log entry like yours. looking
at the log file i still see a few of those SPOOLSS error messages.
Users did not report problems but i have to ask em if they have had
issues with printing this week.
If the error occures there is no print job generated at the cups
server at all and errors like those above appear in log.smbd
[2011/09/14 16:09:28.780842, 0]
lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@<DD>^W^TH<DD>^X^T^A^D)
[2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:09:29.001633, 0]
lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@<DD>^W^TH<DD>^X^T^A^D)
[2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:05.843419, 0]
lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(<88><DF>^H^N<E0><9F>^T^T`<D9>^K^T)
[2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:06.107415, 0]
lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(<88><DF>^H^N<E0><9F>^T^T`<D9>^K^T)
[2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
achim~
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
