Cups server Error: Cups Scheduler not running

[mzsade]

I thought i had it made when i successfully made a full backup custom iso with Remastersys. As with my previous experience, after a Remastersys Jaunty install (http://forums.linuxmint.com/viewtopic.p ... 72#p176872), i get this error and the system shows the Printer as "not connected".
I have tried un-installing and then reinstalling all cups related stuff, but that didn't help. Is there any chance of repairing this, or should i just do a fresh install from the official Mint CD, and not waste time in vain? D@$%#, it will take me days to get back my system the way it was!

[lagagnon]

Run this command in a terminal: "ps aux | grep cups"
Do you see the cupsd daemon running?

[mzsade]

sade@sade-desktop ~ $ ps aux | grep cups
sade 3718 0.0 0.0 3336 784 pts/0 S+ 08:25 0:00 grep --colour=auto cups

This is all...
I have been to Administration>>Services and confirmed that the Printer Service (cups) box is checked.

[aehjr1]

So, your process listing shows no CUPS daemon running although the Administration/Services shows CUPS is checked off to be started during the boot processing.

I suggest next you check the CUPS error and access logs, the most important being the error_log file(s) found under /var/log/cups. You should see a listing something like this:

Code: Select all

arnold@arnold-laptop /var/log/cups $ ls -l
total 52
-rw-r----- 1 root adm     8841 2009-09-26 23:17 access_log
-rw-r----- 1 root adm     1086 2009-09-26 10:54 access_log.1.gz
-rw-r----- 1 root adm      372 2009-09-25 15:43 access_log.2.gz
-rw-r----- 1 root adm      698 2009-09-24 13:42 access_log.3.gz
-rw-r----- 1 root adm      580 2009-09-23 11:16 access_log.4.gz
-rw-r----- 1 root adm      705 2009-09-22 09:48 access_log.5.gz
-rw-r----- 1 root adm      962 2009-09-21 10:01 access_log.6.gz
-rw-r----- 1 root adm     3165 2009-09-20 00:26 access_log.7.gz
-rw------- 1 root lpadmin    0 2009-04-24 12:35 cups-pdf_log
-rw-r----- 1 root lpadmin    0 2009-09-14 10:53 error_log
-rw-r----- 1 root adm      246 2009-09-13 21:20 error_log.1.gz
-rw-r----- 1 root adm       74 2009-09-09 12:57 error_log.2.gz
-rw-r----- 1 root adm      205 2009-08-22 10:38 error_log.3.gz

(Unfortunately, selecting "Code" is the only thing I can select to make the listing display in non-proportional font.)

As you can see from my sample listing, I've had no errors to log since I booted my laptop on 9/13. However, you should have something in yours as it seems that either the CUPS daemon is dying after startup or something else is happening during startup. If it's the latter, review the log files for the system; Administration/Log File Viewer.

HTH

[mzsade]

These are the last few lines of my Daemon.log from Administration>>Log file viewer:
Sep 27 08:44:51 sade-desktop hal_lpadmin: Running hal_lpadmin
Sep 27 08:44:53 sade-desktop hal_lpadmin: hal_lpadmin triggered by low-level USB device
Sep 27 08:44:53 sade-desktop hal_lpadmin: Getting device ID from the usblp HAL entry ...
Sep 27 08:44:53 sade-desktop hal_lpadmin: Device ID for /dev/usb/lp0: MFG:Hewlett-Packard;MDL:HP LaserJet M1005;DES:HP LaserJet M1005;CMD:ACL;
Sep 27 08:44:53 sade-desktop hal_lpadmin: Written device ID into HAL database entry: MFG:Hewlett-Packard;MDL:HP LaserJet M1005;DES:HP LaserJet M1005;CMD:ACL;
Sep 27 08:44:53 sade-desktop hal_lpadmin: Unable to connect to CUPS: 'httpConnectionEncrypt failed'. Is CUPS running?

And these are the lines from the error_log:
E [24/Sep/2009:20:35:54 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [25/Sep/2009:08:20:02 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [25/Sep/2009:12:10:48 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [25/Sep/2009:14:35:49 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [25/Sep/2009:21:22:21 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [26/Sep/2009:01:13:37 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [26/Sep/2009:07:05:42 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [26/Sep/2009:11:50:20 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [26/Sep/2009:18:00:32 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [26/Sep/2009:22:35:12 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:13:18 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:36:05 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:36:09 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:39:31 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:39:37 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory
E [27/Sep/2009:07:43:09 +0530] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory

Edit: Meanwhile i am going through this, https://help.ubuntu.com/community/LinuxLogFiles--will let you know if i get anywhere with that.

The printer is identified, right? Lines from /var/log/debug: Sep 27 07:35:51 sade-desktop hal_lpadmin: Written device ID into HAL database entry: MFG:Hewlett-Packard;MDL:HP LaserJet M1005;DES:HP LaserJet M1005;CMD:ACL;
Sep 27 07:40:37 sade-desktop hal_lpadmin: Running hal_lpadmin
Sep 27 07:40:38 sade-desktop hal_lpadmin: hal_lpadmin triggered by low-level USB device
Sep 27 07:40:38 sade-desktop hal_lpadmin: Using device ID from HAL database entry
Sep 27 07:43:13 sade-desktop kernel: [ 113.762547] forcedeth 0000:00:07.0: irq 2300 for MSI/MSI-X
Sep 27 07:43:23 sade-desktop kernel: [ 124.324541] eth0: no IPv6 routers present
Sep 27 08:44:51 sade-desktop hal_lpadmin: Running hal_lpadmin
Sep 27 08:44:53 sade-desktop hal_lpadmin: hal_lpadmin triggered by low-level USB device
Sep 27 08:44:53 sade-desktop hal_lpadmin: Getting device ID from the usblp HAL entry ...
Sep 27 08:44:53 sade-desktop hal_lpadmin: Device ID for /dev/usb/lp0: MFG:Hewlett-Packard;MDL:HP LaserJet M1005;DES:HP LaserJet M1005;CMD:ACL;
Sep 27 08:44:53 sade-desktop hal_lpadmin: Written device ID into HAL database entry: MFG:Hewlett-Packard;MDL:HP LaserJet M1005;DES:HP LaserJet M1005;CMD:ACL;
Sep 27 09:53:59 sade-desktop hal_lpadmin: Running hal_lpadmin
Sep 27 09:54:00 sade-desktop hal_lpadmin: hal_lpadmin triggered by low-level USB device
Sep 27 09:54:00 sade-desktop hal_lpadmin: Using device ID from HAL database entry

[aehjr1]

The error_log file is specifically telling you the (at least a) problem; you are supposed to have a file--in this case the file is a symbolic link--which is missing or not correctly defined. CUPS uses a secure signing protocol named SSL, and the error is telling you the problem lies in that directory.

What I've done below is change directory to "/etc/cups" then "list" the "ssl" directory. It is owned by root and no one else can see the directory contents. So I trick the permissions out by using "sudo" to list the contents of the "ssl" directory and this shows the symbolic links are pointing to new files in the "/etc/ssl/certs" directory. Then, to make sure the link points to an actual file, I list the link info, and find out it actually does exist.

Code: Select all

arnold@arnold-laptop /etc/cups $ ls -ld ssl
drwx------ 2 root lp 4096 2009-04-20 10:05 ssl
arnold@arnold-laptop /etc/cups $ sudo ls -l ssl
total 0
lrwxrwxrwx 1 root root 36 2009-08-21 13:20 server.crt -> /etc/ssl/certs/ssl-cert-snakeoil.pem
lrwxrwxrwx 1 root root 38 2009-08-21 13:20 server.key -> /etc/ssl/private/ssl-cert-snakeoil.key
arnold@arnold-laptop /etc/cups $ ls -l /etc/ssl/certs/ssl-cert-snakeoil.pem
-rw-r--r-- 1 root root 607 2009-08-21 13:29 /etc/ssl/certs/ssl-cert-snakeoil.pem

I suspect if you do the same you will find a problem.

HTH

[mzsade]

Thanks, what worked for me was that opened the /etc/cups/ssl as root, deleted the 'server.crt' and 'server.key' links, and did a "sudo /etc/init.d/cups start", as described here:http://crunchbanglinux.org/forums/topic ... ng-broken/, printer works now.