Telcontar:~ # rccups restart
Shutting down cupsd done
Starting cupsdcupsd: Child exited with status 1
startproc: exit status of parent of /usr/sbin/cupsd: 2 failed
Telcontar:~ #
and this message gets printed to ALL opened terminals, which is a nuisance:
Telcontar:/etc/apparmor.d #
Message from syslogd@Telcontar at Aug 19 23:07:25 ...
cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting!
but this is a secondary problem. What I want now is get cups running again.
Telcontar:~ # l /etc/cups/cupsd.conf
-rw-r----- 1 root lp 6442 Aug 19 14:33 /etc/cups/cupsd.conf
The permissions are the same as in a pristine 12.1 system. How come it can not read that file?
It is not apparmor.
I tried to give “-rw-r–r–” permissions to the file, no go.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
You could rename /etc/cups/cupsd.conf and the reinstall the cups package
such that a pristine /etc/cups/cupsd.conf is installed to see if it is
something in the content of the file which cups does not like.
If it works then diff the two files to see what might have caused the
trouble.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.5 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
On 2012-08-19 23:34, Martin Helm wrote:
> You could rename /etc/cups/cupsd.conf and the reinstall the cups package
> such that a pristine /etc/cups/cupsd.conf is installed to see if it is
> something in the content of the file which cups does not like.
> If it works then diff the two files to see what might have caused the
> trouble.
I did not believe you, but I renamed the config file and copied the working config file from
another partition (12.1 fresh). And cups started! I’m surprised indeed.
Why did cup say “unable to read” instead of complaining of the actual error in the file?
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Am 20.08.2012 01:18, schrieb Carlos E. R.:
> Why did cup say “unable to read” instead of complaining of the actual error in the file?
Good question, I vaguely remembered to have changed some setting a few
years ago with a typo and got the same or similar (do not remember
exactly) useless message.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.5 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
I did not believe you, but I renamed the config file and copied the working config file from
another partition (12.1 fresh). And cups started! I’m surprised indeed.
Take a close look at the typo or corruption. It is a relatively common cause, from what I’ve read online.
Why did cup say “unable to read” instead of complaining of the actual error in the file?
Am 20.08.2012 01:06, schrieb deano ferrari:
>
> Alternatively, you could try renaming /etc/cups/cupsd.conf as Martin
> suggested, and copy cupsd.conf.default to cupsd.conf, then try
> restarting CUPS.
>
I am today in the mood for brute force solutions
Of course that is much better for the next one who looks at that thread.
On 2012-08-20 01:46, deano ferrari wrote:
>
>> I did not believe you, but I renamed the config file and copied the
>> working config file from
>> another partition (12.1 fresh). And cups started! I’m surprised indeed.
> Take a close look at the typo or corruption. It is a relatively common
> cause, from what I’ve read online.
The compare is complex, there are many differences. The file was taken from the .rpmorig file
plus some changes taken from the old file. Obviously there are errors, but I’m not going to
investigate them if the current setup works. I printed the page I needed.
The next problem is whether I can print from my virtual machines - some other day.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2012-08-20 01:58, Martin Helm wrote:
> Am 20.08.2012 01:06, schrieb deano ferrari:
>>
>> Alternatively, you could try renaming /etc/cups/cupsd.conf as Martin
>> suggested, and copy cupsd.conf.default to cupsd.conf, then try
>> restarting CUPS.
>>
> I am today in the mood for brute force solutions
> Of course that is much better for the next one who looks at that thread.
In this machine I have several installs. There is the main one I use (production, lets say),
then 3 smaller ones I have with other versions (and spare partitions for more). I installed
12.1 fresh in one of them, tested it, then upgraded my main partition from 11.4 to 12.1.
I simply took the config from the working install
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On Sun, 19 Aug 2012 21:18:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:
>
>12.1 (upgraded from 11.4, of course)
>
>It gets
>
>
>
>Telcontar:~ # rccups restart
>Shutting down cupsd done
>Starting cupsdcupsd: Child exited with status 1
>startproc: exit status of parent of /usr/sbin/cupsd: 2 failed
>Telcontar:~ #
>
and this message gets printed to ALL opened terminals, which is a nuisance:
>Telcontar:/etc/apparmor.d #
>Message from syslogd@Telcontar at Aug 19 23:07:25 ...
> cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting!
>
but this is a secondary problem. What I want now is get cups running again.
>Telcontar:~ # l /etc/cups/cupsd.conf
>-rw-r----- 1 root lp 6442 Aug 19 14:33 /etc/cups/cupsd.conf
>
>
>The permissions are the same as in a pristine 12.1 system. How come it can not read that file?
>
>It is not apparmor.
>
>I tried to give “-rw-r–r–” permissions to the file, no go.
I have seen policykit do things like that as well.
