- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Printing Issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 03:58 AM
03-17-2006 03:58 AM
Printing Issue
I have lots of printers. Last nite jobs got stuck in one of them. I can ping the printer ok, so I lpshut lpsched. Still no go. Nothing interesting in /var/spool/lp/log. So I cancelled the jobs and sent another simple job to the queue. It's stuck again and I get the following in /var/spool/lp/log:
waitpid: Interrupted system call
rev-4104 root rev Mar 17 08:41
also, for some reason 2 lpsched processes are running, which I think is not the way it's supposed to work...
>ps -ef |grep lpsched
lp 4907 1 0 08:09:13 ? 0:00 lpsched
root 6338 3877 1 08:57:57 pts/3 0:00 grep lpsched
lp 5744 4907 0 08:41:12 ? 0:00 lpsched
lpstat just shows the jobs in the queue
whadda ya think?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 04:03 AM
03-17-2006 04:03 AM
Re: Printing Issue
I think it's the printer itself.
You don't have 2 lpsched running - the 1st is the grep command - normal.
Can u print to it via Windoze?
Can it do a self-test?
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 04:03 AM
03-17-2006 04:03 AM
Re: Printing Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 04:13 AM
03-17-2006 04:13 AM
Re: Printing Issue
Hi,
try
#lpstat -t
This will display full information
such as
scheduler status
system default destination
queue status ---
etc...
hope this helps...
Siva.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 07:51 AM
03-17-2006 07:51 AM
Re: Printing Issue
lpshut - grep for and kill lpsch and hpnpf processes - fine
powercycle printer - restart lpsched - ping printer - fine
test printer - stuck in queue! It also launches another instance of lpsched when I send the first print job ....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 11:31 AM
03-17-2006 11:31 AM
Re: Printing Issue
BTW, the second lpsched (PID 5744) is the child of the first one (PID 4907). I just checked my system and I have one stuck since yesterday and they have that parent/child relationship.
Marlou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2006 03:52 PM
03-17-2006 03:52 PM
Re: Printing Issue
As far as the hangs are concerned, is this a network printer (which means an HP JetDirect LAN card), or a non-HP LAN card, or some computer acting as a print server? Each connection requires very different troubleshooting steps.
Bill Hassell, sysadmin