- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Spooler Error From SAM
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
Discussions
Discussions
Forums
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
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
тАО07-28-2005 01:33 AM
тАО07-28-2005 01:33 AM
Attempted to determine if the fileset "LP-SPOOL" from the product "PrinterMgmt" exists on your system but the swlist command failed.
Stderr from swlist is: ERROR: Could not contact host "hostname". Make sure the hostname is correct and an absolute pathname is specified (beginning
with "/").
ERROR: More information may be found in the daemon logfile on this target (default location is meyer:/var/adm/sw/swagentd.log).
This log file doesn't seem to tell me anything. Any ideas on what this means?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 01:49 AM
тАО07-28-2005 01:49 AM
Re: Spooler Error From SAM
Try:
swlist -l fileset | grep SPOOL
This should repsond with something like:
DistributedPrint.PD-SPOOLER B.11.11 PD-SPOOLER
PrinterMgmt.LP-SPOOL B.11.11 LP-SPOOL
What has changed? Is this a new server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 01:57 AM
тАО07-28-2005 01:57 AM
Re: Spooler Error From SAM
Result of grep command:
ERROR: Could not contact host "hostname". Make sure the hostname is
correct and an absolute pathname is specified (beginning with
"/").
ERROR: More information may be found in the daemon logfile on this
target (default location is meyer:/var/adm/sw/swagentd.log).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:02 AM
тАО07-28-2005 02:02 AM
Re: Spooler Error From SAM
Make sure there is ping connectivity to the remote servers referred to in the answers you are getting from nslookup.
Knowing where the server is is not the same as actually getting access.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:04 AM
тАО07-28-2005 02:04 AM
Re: Spooler Error From SAM
Hi Shannon,
I think the error is related to the swlist command not the grep.
I would like to see what is in the log file can you please post the relevant section of the file.
If you want a cleaner swagentd logfile to look at.
Try clearing out your log and tailing it as you encounter the problem.
cd /var/adm/sw
# If you would like to keep a copy
cp swagentd.log swagentd.log.old
# empty the log
> swagent.log
# Then tail the file and try a swlist again
tail ├в f swagentd.log # just so you can view the action as it happens
regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:06 AM
тАО07-28-2005 02:06 AM
Re: Spooler Error From SAM
that last command should read:
tail -f swagentd.log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:10 AM
тАО07-28-2005 02:10 AM
Re: Spooler Error From SAM
I know this is like trying to remember where you put your keys last but I'm going to ask anyway, what has changed since you last successfully added a printer?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:17 AM
тАО07-28-2005 02:17 AM
Re: Spooler Error From SAM
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=766239
Could it be that the hosts file has another entry for the same (local) server which has been added recently?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 02:32 AM
тАО07-28-2005 02:32 AM
Re: Spooler Error From SAM
one is empty even after I swlist again and I get the same error about the host name. Nothing has changed other than I added our dns server to the resolv.conf file because I was having trouble with sendmail a few weeks ago. It solved my sendmail problem.
06/01/05 16:45:51 EST
* Started source agent on "/tmp/HP11e134.SD" for root@hostname,
pid=23136, 06/01/05 16:46:37 EST
NOTE: The target "/tmp/HP11e134.SD" currently open for reading is a
tape. pid=23136 06/01/05 16:46:37 EST
* Started install agent on "/" for root@meyer, pid=23266,
06/01/05 16:48:56 EST
* Agent pid=23131 completed. 06/01/05 16:48:56 EST
* Agent pid=23136 completed. 06/01/05 16:49:03 EST
* Agent pid=23266 completed. 06/01/05 16:49:03 EST
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 03:11 AM
тАО07-28-2005 03:11 AM
Re: Spooler Error From SAM
It is the bit that says hostname rather than meyer that bothers me. Almost like swlist is picking up hostname from somewhere.
I suppose you could try adding the fully qualified domain name to /etc/hosts after the short hostname.
What order is your /etc/nsswitch.conf in? Ours is:
hosts: files [NOTFOUND=continue] dns