HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lpshut and lpsched needed after a reboot to print ...
Operating System - HP-UX
1833758
Members
2994
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
07-29-2003 05:53 PM
07-29-2003 05:53 PM
(posted in print servers as well but I thought I may get more response here).
Interesting problem here.
I am running HP-UX B 11.00 U on a 9000 A Class.
I have set up a default HP laser printer as a network printer using JetAdmin Ver E.10.34.
It works and prints ok.
But when I reboot the HP server - the printing won't work. I do a lpstat -t and it shows the scheduler is running and the default is the laser printer.
I do a "lp /etc/hosts" then a lpstat -t and it shows the job in the queue. Then I repeat the "lpstat -t" and the job disappears. Sounds great, but no print job at the printer. I try again to print another file, no luck - print job apepars in queue and then disappears. I can ping the printer successfully. I can use diagnostic in JetAdmin and it says the printer is ok. The print job disappears from the queue to indicate all is ok. But its not all OK.
Then I do a lpshut, followed by a lpsched to stop and start the scheduler.
I do a "lp /etc/hosts" and the file prints.
No problem now till I reboot the server.
As I am setting up the customers servers, I can't have the customer do this each time they reboot the server.
Also installed the latest printing patch (PHCO_28320) - still no luck.
If anyone has any ideas what could be causeing this I would appreciate their help.
Thanks in advance
PA
Interesting problem here.
I am running HP-UX B 11.00 U on a 9000 A Class.
I have set up a default HP laser printer as a network printer using JetAdmin Ver E.10.34.
It works and prints ok.
But when I reboot the HP server - the printing won't work. I do a lpstat -t and it shows the scheduler is running and the default is the laser printer.
I do a "lp /etc/hosts" then a lpstat -t and it shows the job in the queue. Then I repeat the "lpstat -t" and the job disappears. Sounds great, but no print job at the printer. I try again to print another file, no luck - print job apepars in queue and then disappears. I can ping the printer successfully. I can use diagnostic in JetAdmin and it says the printer is ok. The print job disappears from the queue to indicate all is ok. But its not all OK.
Then I do a lpshut, followed by a lpsched to stop and start the scheduler.
I do a "lp /etc/hosts" and the file prints.
No problem now till I reboot the server.
As I am setting up the customers servers, I can't have the customer do this each time they reboot the server.
Also installed the latest printing patch (PHCO_28320) - still no luck.
If anyone has any ideas what could be causeing this I would appreciate their help.
Thanks in advance
PA
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2003 05:56 PM
07-29-2003 05:56 PM
Solution
Hi PA,
Check the permissions on the directory /etc/lp/interface/model.orig. It should be lp:bin
Worth a try and hope it helps
Check the permissions on the directory /etc/lp/interface/model.orig. It should be lp:bin
Worth a try and hope it helps
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2003 06:16 PM
07-29-2003 06:16 PM
Re: lpshut and lpsched needed after a reboot to print - why ?
JetAdmin has been obsolete for several years (not Y2K compliant) and should not be used. Delete your default printer using the removequeue command (part of JetAdmin). Use swremove to take off the old product and then download HPPI (HP Printer Installer) from:
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?locale=en_US&taskId=135&prodSeriesId=27349&prodTypeId=18972
(sorry for the ugly URL). Install the HPPI software then add your printer by using the addqueue command as in:
addqueue -d -h IP-or-Hostname -q local-queuename -b off
This one command does everything that hppi (was called jetadmin) does but a lot faster.
Bill Hassell, sysadmin
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?locale=en_US&taskId=135&prodSeriesId=27349&prodTypeId=18972
(sorry for the ugly URL). Install the HPPI software then add your printer by using the addqueue command as in:
addqueue -d -h IP-or-Hostname -q local-queuename -b off
This one command does everything that hppi (was called jetadmin) does but a lot faster.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2003 06:49 PM
07-29-2003 06:49 PM
Re: lpshut and lpsched needed after a reboot to print - why ?
Thanks Tim - it worked once I changed the permissions - they were root:sys.
The bootup sequence must not have been able to read the model.orig but root must have once I did a lpshut and lpsched. Very good thinking Tim. Thanks again.
Bill - it was my error - I have JetDirect installed not JetAdmin. I think I wrote jetAdmin because it was in m head from a previous installtion I had. Thanks for your advice anyway.
PA
The bootup sequence must not have been able to read the model.orig but root must have once I did a lpshut and lpsched. Very good thinking Tim. Thanks again.
Bill - it was my error - I have JetDirect installed not JetAdmin. I think I wrote jetAdmin because it was in m head from a previous installtion I had. Thanks for your advice anyway.
PA
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP