Error -50 with Canon MF9170, Mac OSX 10.6.4

Hello PAHU,

thanks for checking!

Yes, these ports have been identified as "Open TCP Port". Here's the list:

Open TCP Port: 80 http
Open TCP Port: 515 printer
Open TCP Port: 981
Open TCP Port: 9002 dynamid
Open TCP Port: 9007
Open TCP Port: 9011
Open TCP Port: 9013
Open TCP Port: 9014
Open TCP Port: 9015
Open TCP Port: 9016
Open TCP Port: 9017
Open TCP Port: 9100 hp-pdl-datastr
Open TCP Port: 47545
Open TCP Port: 47546

What irritates me, is that when I try to open the UFR II, I immediately get the message, that the printer does not respond. I have the Net Monitor Sidekick installed to watch the traffic and I can see that the Mac doesn't even try to reach the printer. In contrast, I can see a communication between the printer and the Mac when I add the printer in the settings menu. When I enter the IP address, the Mac checks that IP address and this shown on the Net Monitor list:

192.168.XX.XX UDP (protocol) SNMP (remote port) Private (local port) 2,2 kB (in data) 2,1 kB (out-data)

I also noticed, that when I have this queue: cntdbmu://MCD UFR2_LPR/CanonFarblaser/lpd://192.168.XX.XX/ the printer does not respond at all, it's like I disconnected it. Whereas when I use the lpd://192.168.XX.XX/LP queue the printer reacts at least with printing the -50 error message and I see some traffic on the Net Monitor.

Could it be, that it's not a network problem but a driver (queue related) problem?

Another point might be relevant, which I have forgotten to mention: The printer worked on this Mac for one day but when I came to the office the next day, the error messages started again, although I cannot remember having changed a thing (at least to my knowledge).

Thanks again,
Jörg

* B R E A K I N G N E W S * B R E A K I N G N E W S * B R E A K I N G N E W S * B R E A K I N G N E W S * B R E A K I N G N E W S *

PAHU!

I could print! I had the queue set to cntdbmu://MCD UFR2_LPR/_192_168_5599/lpd://192.168.55.99/ fixed disk permission, tried here and there, uninstalled, reinstalled and eventually the printer really printed. I saved the console logs of this day so that it probably can be seen what really happened. I get the 'printer info' when printing from an application and selecting 'special features'.

So far so good. What I cannot do, is to start the printer tool in the MacOS settings > Printers & Fax > Options & Supplies > Miscellaneous (= the button after supplies). So something is still wrong.

I'm not sure, if it will last. I'll report tomorrow.

Thanks again!

Jörg

Hi Pahu,

and now after restart, everything works. Sooo strange, because I didn't do anything at all. The only thing that doesn't work are the filling levels of the toner cartridges.

Was it the disk permissions? But I'm cautious. I've been at this point before when I thought it was all set.

I'll let you know tomorrow.

Have a good day!

Jörg

Hi PAHU,

I could print a couple of minutes ago, but now the UFR Printmonitor says: "Printer is not responding", the queue is paused, and when I try to start that pause printjob I get an IO 10554 memory error.

The only thing I did between the "printable" and "nonprintable" time was to surf the internet (during which I marked the prolbem as 'solved').

Now I don't know what to try now.

Thanks again for watching!
Jörg

Hi PAHU,

after working myself through the console logs, I found this entry which syncs with the event of unsuccessful printing:

07.09.10 18:37:36 sandboxd[1195] cupstomcdufr2(1187) deny file-write* /private/var/spool/cups/Library
07.09.10 18:37:36 sandboxd[1195] cupstomcdufr2(1187) deny file-write* /private/var/spool/cups/Library

So something prevents the access to write to "/private/var/spool/cups/Library" which seems quite essential for printer access 😉

I googled these terms and got some hits from within this forum, where people had this problem, too. Unfortunately, no solution is described, that I haven't tried already dozens of times.

Thanks,
Jörg

Hi Pahu,

unfortunately the sandbox process is does not show in my activity monitor, although I remember that I had to deal with it on my iPhone 4, but didn't make real problems there.
A couple of months ago I installed a free filter software that was recommended on computers that could be accessed by children. It didn't work for me, so I uninstalled it. Could that sandbox be a remnant of this installation? But you wrote, that you have it running, too, so I probably isn't.

When I press the 'Printer info' button in the 'Special features' menu I get this log in the console:

08.09.10 11:13:55 [0x0-0x19019].org.mozilla.firefox[335] shmget: Cannot allocate memory

And at a printing attempt, I get the sandbox-error:

08.09.10 11:24:19 sandboxd[721] cupstomcdufr2(714) deny file-write* /private/var/spool/cups/Library

In the meantime I checked permissions of the cups folder "/private/var/spool/cups/" and found out that cups is accessing that folder via a user called "_ld". In the permissions list of the cups folder, this "_ld" has no rights at all. When trying to change permissions, it's not possible, because each time I change the setting it jumps back to 'no rights' immediately.

I appreciate your efforts with all that trying and researching very much!!

Thanks again,
Jörg

I can confirm your findings. When checking the console logs, I, too, get the sandbox error in combination with successful printjobs, whereas the 'shmget cannot allocate memory' occours only in combination with unsuccessful printjobs.

I googled 'shmget cannot allocate memory' and found some unix stuff, but I couldn't produce anything useful, yet.

Have a good day,
Jörg

Hi Pahu,

I think I have gotten something!!

I googled "shmget cannot allocate memory" (as this is the only problem-specific log entry) and really found something interesting (see below), that might resolve the problem. I didn't understand everything but the problem is caused in fact by a low memory, because by default the shared memory is set to a comparably low value, but as each BOINC requires a certain amount of memory, one can easily run out of memory. The distribution of memory for this case is done by a file named sysctl.conf, which was not present on my system. So I followed the instructions, and created a sysctl.conf in /etc with the described values and (until now) with fingers and toes crossed I've really gotten rid of the shmget error.

If you are interested, the whole story can be read here:
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=5605

This explains, too, that sometimes the printer worked and sometimes didn't. It just could have depended on the amount of free shared memory.

I just wanted to let you know that this time the problem might be solved and HOPEFULLY your research is not necessary and I do not want you doing it in vain.

I will report... 🙂

Thanks, Pahu!

Jörg

* Edit last post *

It is of course not a BOINC, that's a specific software described on the climateapps site. What I meant is just 'process' (and a BOINC is a process, but has nothing to do with the solution of my problem)

😉

Hello PAHU,

until now, I got no errors at all, the printer works like a charm, and the UFRII print monitor recognizes and diagnoses as it should do (except the display of the filling levels of the toner cartridges) so that the redistribution of the shared memory seems to have an effect.

Although I am still wary, I guess we solved it! Without your help I wouldn't have been able to find a solution.

I hope not to bother you again but would be grateful if you could have a look, if the next (-60?) error occours 😉

Thanks a lot for all your effort!

Greetins,
Jörg