Operating System - OpenVMS
1748185 Members
4032 Online
108759 Solutions
New Discussion юеВ

Re: unable to start LPD CLIENT

 
Jan van den Ende
Honored Contributor

unable to start LPD CLIENT

Hi,

yesterday we had a temporary (planned) power down on one location.
After the systems came back up, we could not start LPD queues.
The message during TCPIP startup was
%TCPIP-E-STARTFAIL, failed to start LPD_CLIENT
%TCPIP-E-NOSERVREC cannot find LPD_CLIENT service database record.

It now came to the surface that this functionality was activated some two years ago on only one node, by someone who has since long left.

I have NOT been able to find how to get this corrected !! The service manual is not much help either. :-(

VMS 7.3-2 -- ICPIP services 5.4 ECO 4.

I am sure that it will be too trivial to enter into a manual, but we are at a loss right now.

Thanks in advance!

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
32 REPLIES 32
Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,

the LPD_CLIENT service seems to come from TCPIP V5.1. Have a look at SYS$MANAGER:TCPIP$V51_CONVERSION.COM - it talks about merging LPD and LPD_CLIENT.

I can't find a LPD_CLIENT service entry after configuring LPD on TCPIP V5.6.

$ TCPIP SHOW CONF ENA SERVICE *

Volker.

Wim Van den Wyngaert
Honored Contributor

Re: unable to start LPD CLIENT

Also try Volkers command with /common to verify the enabled services. Some wisenose could have used it (I did but IMO it's not correctly implemented).

Wim
Wim
EdgarZamora
Trusted Contributor

Re: unable to start LPD CLIENT


WAG...

try (may have to define tcpip commands first):

$ tcpip$lpd_utilities -f START_CLIENT_QUEUES
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Volker, Wim,
found that already. Conversion was done in 2003 (.FLG files for every node still there to prove it).

Edgar,
will try that tomorrow. Points assignment awaits the result.

Meanwhile, I have set one node to no longer accept new connections, so tomorrow I can do a full TCPIP shutdown & startup, and if that does not help a reboot.
If either fixes the issue, I will initiate a rolling down-up cycle.

Meanwhile, if anybody has more ideas (or, perhaps, documentation on this issue?), I am more than interested!

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Walter Miller_1
Valued Contributor

Re: unable to start LPD CLIENT

On the node that LPD was ORIGINALLY activated try.

TCPIP SHOW SERVICE/PERM/FULL LPD

In a cluster only one node has to be configured but that node does have to start the service. Look for logicals that should be defined.

SHOW LO *LPD*

Especially look for the printcap file logical.
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Edgar,

alas.

Walter,

all _LOOKS_ correct, and not different from another cluster that is functioning OK.

The real "trouble" manifests itself when trying to start an LPD que:

Message number 07648312
after $ SET MESSA SYS$MESSAGE:TCPIP$MSG that is:
%TCPIP-E-FACNOTSTART, attempt made to run a TCPIP image before starting the facility

So, a nice un-VMSsy non-informal message: why does it not say / how do I find out WHICH facility?

I did on one node
- stop & disable LPD
- stop TCPIP entirely
- start TCPIP
- enable & start LPD

No difference.

On all nodes
- stop & disable LPD
- enable & start LPD

No difference.

I am getting desparate (as are the users and my managers!)

HELP!!!!

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,

exactly on which command do you get those error message ? Di you run the appropriate DCL procedures with SET VERIFY to find out the exact command ? Did you consider to use SET WATCH FILE/CLASS=MAJ after you've isolated the offending command ?

Without being able to exactly see or reproduce the failure, it will be hard for anyone to try to help you.

Volker.
Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,

after looking around further in TCPIP$*.COM and TCPIP$*.EXE files, I'm getting the impression, that there definitely is no LPD_CLIENT service anymore in the more recent versions of TCPIP (beyond V5.1). The reference in TCPIP$CONFIG.COM just seems to be a leftover.

Could it be, that there is some 'old' procedure or image lying around, which explicitly references LPD_CLIENT ?

Volker.
Walter Miller_1
Valued Contributor

Re: unable to start LPD CLIENT

Search through sys$manager:tcpip*.com for LPD_CLIENT. I found TCPIP$V51_CONVERSION.COM stating that LPD and LPD_CLIENT were merged together. It adds LPD to the configuration database, removes LPD_CLIENT from the configuration database and adds LPD to the service database (as needed). See if you have a conversion file on one of the nodes.
I have attached a copy of the V51 com file.