[OpenIndiana-discuss] cups does not work any more

[russell]

Hi

Just activated the BE created on the 30th December 2022 and 
svc:/application/cups/scheduler:default is running and CUPS is 
accessible on http://127.0.0.1:631/, this is not the case on the BE 
created on the 1st January 2023. So from my perspective the issue is a 
result of the changes that took place between

oihipster-20221203 NR     /          165.18G static 2022-12-30 18:46
oihipster-20230101 -      -          886.55M static 2023-01-01 12:31

Russell

On 1/11/23 14:20, russell wrote:
>
> Good Afternoon
>
> I found out today that I could also not print, the 
> svc:/application/cups/scheduler:default  was in maintenance because it 
> was restarting too fast.
> In order to print I reverted to a BE created on the 17th December 2022.
> I do have another BE created on the 30th December which I can check to 
> see if I can print.
>
> Russell
>
>> Date: Mon, 9 Jan 2023 12:45:29 +0100
>> From: Marc Lobelle<marc.lobelle at uclouvain.be>
>> To:openindiana-discuss at openindiana.org
>> Subject: Re: [OpenIndiana-discuss] cups does not work any more
>> Message-ID:<d9b537a8-d145-2530-da9a-15e170fce3fd at uclouvain.be>
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> cups problem not yet solved
>>
>> On 1/5/23 14:49, Marcel Telka wrote:
>>> On Thu, Jan 05, 2023 at 01:24:24PM +0100, Marc Lobelle wrote:
>>>> What should I do ?
>>> Load the core file into a debugger and try to root cause the problem.
>>>
>>> FYI, I'm running the same cups bits and it works okay here.
>>>
>>>
>>> HTH.
>>>
>> I tried. The core is not that of cupsd but that of cups-browsed, and
>> this did not crash but was killed by sigkill
>>
>> Reading symbols from /usr/sbin/cups-browsed...(no debugging symbols
>> found)...done.
>>
>> Note that I forgot to check how old this file was, thus it was not
>> necessarily relevant
>>
>> [New LWP 1]
>> [New LWP 2]
>> [New LWP 3]
>> [New LWP 4]
>> [New LWP 1]
>> [New LWP 2]
>> [New LWP 3]
>> [New LWP 4]
>> [Thread debugging using libthread_db enabled]
>> [New Thread 1 (LWP 1)]
>> [New Thread 2??????? ]
>> [New Thread 3 (LWP 3)]
>> [New Thread 4 (LWP 4)]
>> Core was generated by `/usr/sbin/cups-browsed'.
>> Program terminated with signal SIGKILL, Killed.
>> #0? 0x00007fffaf3f6f2a in __pwrite () from /lib/64/libc.so.1
>> [Current thread is 9 (Thread 1 (LWP 1))]
>> (gdb)
>>
>>
>> Then I looked at the startup script of the service
>> (/lib/svc/method/svc-cupsd) and this one starts gutenprint and then
>> /usr/sbin/cupsd.
>>
>> If I try to start cupsd manually, it works and does not stop. It prints?
>> the test page, although with a message "filter failed" on the cups web
>> page. If configured for black and white, the printing is OK, in colors,
>> the black is purple, but my printer is an old brother MFC9330-CDW
>> emulating a hp printer. However, when I print from a windows machine,
>> the colors are OK.
>>
>> I had the color problem before, but the service did not crash: thus its
>> probably anothe problem
>>
>>
>> Then I discovered that I had , in the svcs list, a legacy server
>> "cups-browsed" surviving from an old release:
>>
>> ls -l /usr/sbin/*cups*
>> -r-xr-xr-x 1 root bin? 294664 nov.? 18 12:57 /usr/sbin/cups-browsed*
>> -r-xr-xr-x 1 root bin?? 72696 nov.? 18 12:56 /usr/sbin/cups-genppd.5.3*
>> -r-xr-xr-x 1 root bin?? 28835 f?vr. 10? 2022 /usr/sbin/cups-genppdupdate*
>> -r-xr-xr-x 1 root bin?? 20512 janv.? 3 12:13 /usr/sbin/cupsaccept*
>> -r-xr-xr-x 1 root bin?? 21184 janv.? 3 12:13 /usr/sbin/cupsctl*
>> -r-xr-xr-x 1 root bin? 592640 janv.? 3 12:13 /usr/sbin/cupsd*
>> lrwxrwxrwx 1 root root???? 10 f?vr. 10? 2022 /usr/sbin/cupsdisable ->
>> cupsaccept*
>> lrwxrwxrwx 1 root root???? 10 f?vr. 10? 2022 /usr/sbin/cupsenable ->
>> cupsaccept*
>> -r-xr-xr-x 1 root bin?? 61688 janv.? 3 12:13 /usr/sbin/cupsfilter*
>> lrwxrwxrwx 1 root root???? 10 f?vr. 10? 2022 /usr/sbin/cupsreject ->
>> cupsaccept*
>>
>> removing the legacy service on /etc/rc3.d has apparently for result
>> that, on reboot, the cups service is running, but it crashes as soon as
>> I try to print something.
>>
>> If restart cupsd manually (/usr/sbin/cupsd), it starts and prints the
>> jobs remaining in the queue (all are marked :stopped filter failed)
>>
>> There is apparently no new core file (I checked running "updatedb;
>> locate -b '\core'|more")
>> The only difference between starting cupsd manually or as a service is
>> that, as a sevice, the gutenprint command is run before starting cupsd
>>
>>
>>
>>
>>