ejs » Samba http://ejs.seniejitrakai.net a snaphot of time Mon, 09 Jan 2012 22:10:04 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Make Samba and CUPS in Debian friends again http://ejs.seniejitrakai.net/2008/04/15/lets-make-samb-and-cups-friends-again/ http://ejs.seniejitrakai.net/2008/04/15/lets-make-samb-and-cups-friends-again/#comments Tue, 15 Apr 2008 18:28:20 +0000 ejs http://ejs.seniejitrakai.net/2008/04/15/lets-make-samb-and-cups-friends-again/ I’ve seen a lot of these entries in logfiles recently:

[] printing/print_cups.c:cups_job_submit(656)
Unable to print file to - client-error-bad-request

And the printing is stopped, of course.

The solution is simple:

LANG=en_US.UTF-8 /etc/init.d/samba restart

In short:
/var/log/cups/error_log shows a lot of

E [] Unsupported character set "iso-8859-1"!

CUPS requires UTF-8.
In the case of default login in Debian, the console IS in UTF-8, but is not if you have customized it and use `su` for administrative tasks.

C’ia.

]]> http://ejs.seniejitrakai.net/2008/04/15/lets-make-samb-and-cups-friends-again/feed/ 0 Troubles in remote server management http://ejs.seniejitrakai.net/2007/11/19/troubles-in-remote-server-management/ http://ejs.seniejitrakai.net/2007/11/19/troubles-in-remote-server-management/#comments Mon, 19 Nov 2007 16:00:48 +0000 ejs http://ejs.seniejitrakai.net/?p=48 Had a severe issue with Samba server recently: it refused to serve after some undefined amount of time. It could work for a days perfectly or could be completely unreachable in several minutes after restart. Logs were useless, even in the highest possible debug level.

The problem was found accidentally. I have some information in national language and I usually edit /etc/samba/smb.conf from X environment or msWindows, using Unicode-aware editors. But at some time share comments in config file were edited using pico in ISO-8859-1 terminal. Pico is perfect editor for me (i hate complexity of vi or emacs) , but in this case the combination of wront terminal and ANSI-type editor was lethal. The UTF-8 strings were mangled and the configuraton was wrong (althow `testparm` showed it’s OK).
So, don’t do this at work ;)

]]> http://ejs.seniejitrakai.net/2007/11/19/troubles-in-remote-server-management/feed/ 0