[HPADM] SUMMARY: hppi / jetadmin transferqueue not working

From: Jeff Lightner (jlightner_at_water.com)
Date: 04/07/05

  • Next message: Harm Ensing: "[HPADM] timezone - revisited"
    Date: Thu, 7 Apr 2005 15:10:18 -0400
    To: <hpux-admin@dutchworks.nl>
    
    

    All,

     

    First thanks to those who responded:

    Rita Workman

    Bill Hassell

    Dan Zucker

    Steve Ilgen.

     

    Rita got me thinking about doing some extra work with pstatus and
    qstatus and Bill suggested just adding the printers with a for loop
    using addqueue. His follow up to a question about pstatus led me to a
    solution. I believe the issue was that the pstatus and qstatus files
    had a different structure having been originally created by Jetadmin
    than they needed for HPNPL (hppi).

     

    Here's what I did to solve the problem:

     

    Note: these are the steps I think were necessary to resolve it though I
    didn't necessarily do them in a linear fashion without intermediate
    steps that added no value. In the below "target system" is the system
    to which I am adding the printers and "source system" is the system from
    which the printers came.

     

         1) Installed HPNPL E.10.34 (hppi - replaces Jetadmin) on target
    system.

     

         2) Ran "/opt/hpnpl/bin/transferqueue local" to convert existing
    printers from old Jetadmin to hppi on target system.

     

         3) Copied /opt/hpnpl/bin/transferqueue from hppi on target system
    to source system as /tmp/transferqueue.

     

         4) On source system ran "/tmp/transferqueue backup" to create the

            /tmp/queues.tar file. (Basically just a tar of

            /var/spool/lp/interface including
    /var/spool/interface/model.orig)

            This complained about not being able to create log and tmp files
    but

            these aren't necessary for the tar file to be created.

     

         5) Copied /tmp/queues.tar from the source system to the target
    system.

     

         6) On target system ran "/opt/hpnpl/bin/transferqueue".

            Without arguments it simply installs the printers from
    /tmp/queues.tar.

            This was done to add the printers from source system to those
    that already existed on target system.

     

         7) Again ran "/opt/hpnpl/bin/transferqueue backup" on the target
    system.

            This was to create a new /tmp/queues.tar that contained all
    printers.

     

         8) Ran "lpshut" to turn off lpsched.

     

         9) cd /var/spool/lp

            cp -p pstatus pstatus.old

            cp -p qstatus qstatus.old

    > pstatus

    > qstatus

            This saved the original pstatus and qstatus files then made
    empty versions for fresh start.

     

        10) Ran the following for loop:

              for PRINTER in `tar tvf /tmp/queues.tar |grep -v model.orig \

               |awk '{print $NF}'`

              do rm /etc/lp/member/$PRINTER

                 rm /var/spool/lp/interface/$PRINTER

                 rm /var/spool/lp/interface/model.orig/$PRINTER

                 rm -rf /var/spool/lp/request/$PRINTER

                 lpadmin -p$PRINTER -mdumb -v/dev/null

              done

            versions for fresh start.

            This removes all entries relevant to the old printers then
    re-adds them using the "dumb" printer model.

            Verified this added entries to pstatus and qstatus.

     

        11) cd /var/spool/lp/interface

            tar xvf /tmp/queues.tar

            This basically replaced the interface and model.orig files
    created during the for loop with the actual ones bundled by

             transferqueue earlier (thereby replacing the model "dumb" I'd
    specified above).

     

        12) Ran the following for loop:

              for PRINTER in `tar tvf /tmp/queues.tar |grep -v model.orig \

               |awk '{print $NF}'`

              do enable $PRINTER

                 accept $PRINTER

              done

            This enabled all the printers and set them to accept print
    requests.

     

    Also I installed PHCO_31016, a cumulative spooler patch, on the target
    system but I'm not sure that was necessary for the fix. Since it has
    been out for some time its probably a good idea.

     

    Steve had pointed out that early versions of transferqueue had the wrong
    chmod value for $MODEL. The version that comes with HPNPL E.10.34 had
    the correct value.

     

    As noted previously this had worked fine when I did the transferqueue to
    11i servers but those servers did not have pre-existing queues of their
    own as this 11.0 target system did. Since they started with empty
    pstatus and qstatus files there was no problem adding the printers.

     

    My original question follows:

    ________________________________

    From: Jeff Lightner
    Sent: Wednesday, April 06, 2005 4:08 PM
    To: hpux-admin@dutchworks.nl
    Subject: hppi / jetadmin transferqueue not working

     

    All,

     

    When trying to enable a printer moved by transferqueue utility I am
    seeing messages such as:

    "printer "yumap1" has disappeared!"

    What can be done to make it think the printers are OK?

     

    Details:

    I am attempting to migrate printers from one HP-UX 11.0 server to
    another. Both were originally at the same version of Jetadmin. The
    transferqueue utility allows for this to be done. Previously I
    successfully used this utility to migrate printers from the source 11.0
    server to target 11i servers. The transferqueue for the target 11.0
    server is an older version but gave no errors.

     

    What I've attempted so far:

    1) Found that entries for /var/spool/lp/request and /etc/lp/member
    were not created so created same by hand.

    2) Verified permissions and ownership of all key files / entries
    as discussed in various archive and a document received from HP support.

    3) Since above still didn't work I removed my original Jetadmin
    and installed the replacement HPPNL (E.10.34) which is what was used on
    the 11i servers this had previously worked on.

    4) Redid the transferqueue run using the newer version of that
    utility that came in with the above install.

    5) Again created missing request and member files.

    6) Worked through all suggestions in DOC from HP to no avail.
    This included cleaning up outputq and deleting a printer that didn't
    show up in all 3 of lpstat -p, lpstat -v and lpstat -a.

    7) Manually added a bogus printer via lpadmin successfully.

     

    If not for item 7 I'd think my pstatus was corrupt but running
    /usr/sam/lbin/pmgr -l on it is successful and it DID add the manual
    printer.

     

    Does anyone have a clue before I have to manually add the 400+ printers?

     

     

    --
                 ---> Please post QUESTIONS and SUMMARIES only!! <---
            To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
           Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
     
     Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
                http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)
    

  • Next message: Harm Ensing: "[HPADM] timezone - revisited"

    Relevant Pages

    • Re: Enterprise NLB Terminal Server Print Spooler Jam. New Flavor
      ... is connecting by a cable modem, and one is connected by a ... clustered terminal servers as IP printers with local ports. ... print jobs moving again is to 1. ...
      (microsoft.public.windows.terminal_services)
    • Enterprise Print Spooler Jam. New Flavor
      ... The problem I am writing about has to do with print spoolers that seem ... to keep getting jammed up for no reason. ... clustered terminal servers as IP printers with local ports. ...
      (microsoft.public.windows.server.general)
    • Enterprise NLB Terminal Server Print Spooler Jam. New Flavor
      ... The problem I am writing about has to do with print spoolers that seem ... to keep getting jammed up for no reason. ... clustered terminal servers as IP printers with local ports. ...
      (microsoft.public.windows.terminal_services)
    • Re: print management
      ... "Robert Britton" wrote: ... >>> We have several HP JetDirect based print servers as well ... >>> networked printers with built in network adapters. ... I need the ability to have a night manager move jobs between printers ...
      (microsoft.public.win2000.printing)
    • Re: Terminal server remote printing
      ... the servers which don't autocreate your local printers don't have ... the appropriate drivers for those printers. ... driver on the Terminal Server, unless it is a Windows Hardware ... servers running Citrix presentation server 4.0. ...
      (microsoft.public.windows.terminal_services)