topic Re: Spooler Error From SAM in Operating System - HP-UX

Spooler Error From SAM

Shannon_1 — Thu, 28 Jul 2005 08:33:50 GMT

Have always used SAM/LP spooler to add network printers to system. Get this error now:

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?

Re: Spooler Error From SAM

Gavin Clarke — Thu, 28 Jul 2005 08:49:49 GMT

SAM is looking to see if LP-SPOOL is installed.

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?

Re: Spooler Error From SAM

Shannon_1 — Thu, 28 Jul 2005 08:57:51 GMT

This server has been rebuilt but we have set up several printers since. Seems to be a problem with resolving the host name but it is in /etc/hosts and nslookup returns correct info.

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).

Re: Spooler Error From SAM

Steven E. Protter — Thu, 28 Jul 2005 09:02:04 GMT

suggestion:

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

Re: Spooler Error From SAM

Ronaldinho — Thu, 28 Jul 2005 09:04:38 GMT

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

Re: Spooler Error From SAM

Ronaldinho — Thu, 28 Jul 2005 09:06:28 GMT

the formatting got messed up a bit..
that last command should read:
tail -f swagentd.log

Re: Spooler Error From SAM

Gavin Clarke — Thu, 28 Jul 2005 09:10:30 GMT

It is interesting that you have already added some printers.

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?

Re: Spooler Error From SAM

Gavin Clarke — Thu, 28 Jul 2005 09:17:16 GMT

This link is a similar problem:

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?

Re: Spooler Error From SAM

Shannon_1 — Thu, 28 Jul 2005 09:32:22 GMT

This is the tail of my swagentd.old log file. (That I just created) The new
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

Re: Spooler Error From SAM

Gavin Clarke — Thu, 28 Jul 2005 10:11:09 GMT

Doesn't sound like a drastic change.

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

Re: Spooler Error From SAM

Gavin Clarke — Thu, 28 Jul 2005 10:30:22 GMT

How about this post?

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=910607

Does that help?

Re: Spooler Error From SAM

melvyn burnard — Thu, 28 Jul 2005 10:37:40 GMT

one test would be to move resolv.conf file out of the way, and retry.
i.e:
mv /etc/resolv.conf /etc/resolve.conf

test and see if this helps, then
mv /etc/resolve/conf /etc/resolv.conf

If it works after the first move, and not when you restore the file, then you have DNS resolution issue.
Configure /etc/nsswitch.conf to use files first, then dns e.g.
hosts: files [NOTFOUND=continue] dns

Re: Spooler Error From SAM

Shannon_1 — Thu, 28 Jul 2005 12:18:02 GMT

Thanks melvyn....I had to change my nsswitch.conf...it had dns and then files.
Works like a charm!