On 02/04/2014 07:39 AM, Maykel Franco wrote: <snip> >>>>>> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address >>>>>> [v1.::1]:631 - Address already in use. >>>>>> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address >>>>>> 127.0.0.1:631 - Address already in use. >>>>>> >>>>>> >>>>>> And the printing not works... >>>>>> >>>>>> Thanks in advanced. <snip> >> It seems that cups is running fine. Check it with >> >> % systemctl status cups.service >> >> Do you have the correct printer driver on your system? >> > > The service is OK: > > cups.service - CUPS Printing Service > Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled) > Active: active (running) since mar 2014-02-04 12:52:24 CET; 1h 42min ago > Main PID: 8761 (cupsd) > CGroup: /system.slice/cups.service > └─8761 /usr/bin/cupsd -f > > feb 04 12:52:24 maykel-arch systemd[1]: Started CUPS Printing Service. > > But the printer not impress... In debian works fine. > > I add printer with tool system-config-printer or cups gui web. The printer > add work fine but not works... > > The printer is Canon LBP7750C and the driver is OK: Canon LBP7750C/5460 UFR > II ver.2.7 > > But the printer not found. The work send to printer arrived OK, but no > printing... > > Log cups access: > > localhost - - [04/Feb/2014:14:37:06 +0100] "POST > /printers/Canon-LBP7750C-5460 HTTP/1.1" 200 220 Create-Job successful-ok > localhost - - [04/Feb/2014:14:37:06 +0100] "POST > /printers/Canon-LBP7750C-5460 HTTP/1.1" 200 12759 Send-Document > successful-ok > > > > http://imageshack.com/a/img837/8846/knr7.png > > Why not work?? > > I thought the error was because the port was in use > > Thanks > Maykel, I have seen this exact error when something tries to use cups before cups is started. I mistakenly added 'cups' to the old DAEMONS line in rc.conf (instead of 'cupsd') and it produced this exact error (see old thread: "[arch-general] cups not starting on boot after last 2 kernel updates? -- where to put it in the DAEMONS line?") Since my latest install during Dec 2013, I have seen this error again once when cups failed to start on reboot after kernel update. I don't know why. Manually restarting cups solved the problem and cups has started automatically every time since. It just looks to me like something tried to probe or user cups before it was running. I just checked my install and I have not seen the error in the past 30 days. If you show cups running and still can't print, then I would propose stopping and starting cups manually as a test. I am still unclear whether it matter if you start 'cups' or 'cupsd' the .service files are identical. At present I have started and enabled 'cups' and not 'cupsd'. -- David C. Rankin, J.D.,P.E.
