Troubleshooting tips lp cannot print file-error-service-server unavailable

Table of Contents

Is your PC running slow? Do you have problems starting up Windows? Don't despair! Fortect is the solution for you. This powerful and easy-to-use tool will diagnose and repair your PC, increasing system performance, optimizing memory, and improving security in the process. So don't wait - download Fortect today!

1. Download Fortect

2. Follow the on-screen instructions to run a scan

3. Restart your computer and wait for it to finish running the scan, then follow the on-screen instructions again to remove any viruses found by scanning your computer with Fortect

Location: Chicago and the surrounding area

Distribution: Fedora Core

Posts: 8

How do I start the lpsched print services?

If the scheduler is not running, you become superuser, lp, or equivalent. Like the planner, start by using one of the reading methods. Use the lpsched command. Number of services running / usr / lib / lpschedPrint. A message is loaded indicating that print services did not start as expected.

Representative:

lp: Failed to create file: Server error service unavailable

I noticed all sorts of posts on the net describing a similar problem, but there was no actual process or explanation that would make sense. Here’s what’s going on:

I am eating Fedora Core 3_64 on an Athlon 64 3000+ server with Arary, 1GB raid5 RAM, various EIDE drives that I use for copies, and multiple users on the device. I got a strong aversion to CUPS (I can’t seem to get it to work reliably in my environment ..) and installed LPRng on that console – turn off the cupsd daemon. It seems that I can print perfectly to all printers that I have connected in different ways when I (or all users) manually ask the system to take a picture. It looks like lprngtool zucan configure and manage modules (although it’s a bit slow ….).

The problem I am running into is that I am running a real shell script on the crontab where it contains the “lp” command: luteal phase -dsystem / Absolute / pathname. Every time the script runs, I get an error in my email:

lp: unable to print directory: server-error-service-unavailable

When I run a very similar script from the command line, the concept seems to be correct. If I enter the same lp command at the same time on the command line, it is successful.

I – think – it’s a good CUPS, but a bug like Microsoft’s Blue Screen Of Death – this particular error message doesn’t have enough useful information to try to debug something. All it does is just tell me that some kind of error has occurred – not a good indicator WHY? Not even sure if this is another CUPS bug, although I think it is. Good workers attached to CUPS (and / or FC3) really need it for EVERYONE. Oh, I’m talking now.

I suspect it is the FC3 core and / or the Bourne Again Spend or Cron daemon.It may be overkill to expect CUPS and CUPS alone to provide you with printing services.

Anyway – if anyone on the internet can EXACTLY help find the reasons that might be causing this error, I would appreciate your input. Thanks.

I have seen all sorts of posts describing a similar problem, but there were no real solutions or simple explanations that made sense to us. Here’s what happened:

I ran Fedora Core 3_64 on an Athlon 64 3000+ server with a RAID5 array, 1GB of RAM, other EIDE drives that I use for backups, and multiple users on the system. I got a strong aversion to CUPS (can’t work reliably in my environment ..), then I installed LPRng in this setting – turn off the cupsd daemon. It seems that I can fix all the tools I have connected in different ways when I (or another user) ask the system to print only one thing on its own. Lprngtool seems to be quite ready to set up and manage printers (although that should be a little slow …).

SamplesThe lema I ran into is that I run the output script on the crontab created with the “lp” command: lp -dsystem / Absolute / pathname. Every time the script runs, I get an error in my email:

When I run the same script from the command line, the problem looks correct. If I immediately type the same lp command on the command line, it works without issue.

I think this is definitely a CUPS bug, but – just like Microsoft’s Blue Screen Of Death – there is ALMOST useful information in this error message to try and debug something. Everything it does can be described as if it is a brand new error – not a very good indication of why? I’m not even sure if this is the best bug in CUPS, although in my opinion it is. Nice people who work with CUPS (and / or FC3) should really take a step back and think about posting some important error messages and leaving some kind of printer switch in place until CUPS is realistic and works well for all. Oh, I’m talking now.

I suspectI roar that this is the FC3 kernel and / or the Bourne Again Invest or Cron daemon may have started getting bogged down waiting for CUPS and only CUPS to create print services.

Anyway – if anyone on the net can help determine EXACTLY which methods might be causing this error, I would appreciate your input. Thanks.