Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Wierd messages at boot

 
Fredrik.eriksson
Valued Contributor

Wierd messages at boot

Hi all :)

I have these somewhat wierd messages that doesn't really make any sense to me in my operator.log from the boot sequence.

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
RP: lp

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
SD: TCPIP$LPD_SPOOL

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
BP: TCPIP$LPD_QUEUE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
PA: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
ND: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
CR: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
SN: FALSE

Does this tell anyone anything?

Best regards
Fredrik Eriksson
22 REPLIES 22
marsh_1
Honored Contributor

Re: Wierd messages at boot

hi,

they look like entries from your ucx/tcpip$printcap.dat displayed during lpd startup.

fwiw

Jim_McKinney
Honored Contributor

Re: Wierd messages at boot

Found in the printcap file...

RP=remote printer
SD=spool directory
BP=banner program
PA=passall flag
ND=nodelete flag
CR=carriage return flag
SN=
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

So this basiclly just tells me what settings is set in the printcap file?

Best regards
Fredrik Eriksson
Hoff
Honored Contributor

Re: Wierd messages at boot

Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

I tried it with all LPD log options enabled. Got several messages but not yours. VMS 7.3, tcp 5.3 eco 2.

Any (undocumented) LPD logicals active ?

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

But of course it's not the service LPD that doing it. The outbound symbiont is doing it. Found the messages in tcpip$lpd_shr.exe.

Activated by TCPIP$LPD_RECV_DEBUG ?

Tried with value 1 but no success.

Wim
Wim
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

This is the only logical defined containting "lpd" i have.
"TCPIP$LPD_ROOT" = "DSA0:[SYS1.TCPIP$LPD.]"

This must be something that is set somewhere else :/

Thank you for all the replies so far :)

Best regards
Fredrik Eriksson
Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

Did you try sh log *lpd*/tab=* ?
It could be given local to the process.

Wim
Wim
marsh_1
Honored Contributor

Re: Wierd messages at boot

hi,

if there is nothing directly in systartup_vms.com do you call any other site-specific routines during startup that are doing things with print queue setup ?

fwiw

Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

GOT IT ! Exectly the same messages.

def/sys/exec tcpip$lpd_symb_debug 15

Restart tcpip and you get the messages.
May be the logical is removed after the usage ?

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

7.3.1 release notes
TCPIP$LPD_DEBUG
LPD_DEBUG

Replaced by TCPIP$LPD_SYMB_DEBUG.

It was from 5.3 upwards.

Wim
Wim
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

So it's just debug messages?
Then i'll try to figure out what file is setting that logical since apperantly it will be set somewhere.

NODE1>sea dsa0:[*...]*.com "lpd_symb","lpd_debug"
%SEARCH-I-NOMATCHES, no strings matched

Seems somewhat elusive thou.

Best regards
Fredrik Eriksson
Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

Which tcp version ?
Boots can be modified and can use ANY file for containing the command. Try *.*/excl=(*.exe,*.olb).

And of course one can do @ of something on another disk (we do).

Wim
Wim
Hakan Zanderau ( Anders
Trusted Contributor

Re: Wierd messages at boot

The debugoptions for LPD have changed from logicals to options in TCPIP$LPD_ROOT:[000000]TCPIP$LPD.CONF in later versions of TCPIP.

Hakan
Don't make it worse by guessing.........
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

We're TCPIP V5.4-15 on OpenVMS 7.3-2 (we don't dare upgrade these machines :P).

Anyway, cannot find a tcpip$lpd.conf and searching throu all the files with excl=(*.exe,*.olb) did not yield any results.

I'm very certain that there are no boot files on other disks.

Can this be some default setting or something you can disable in the printcap file?

Best regards
Fredrik Eriksson
Hakan Zanderau ( Anders
Trusted Contributor

Re: Wierd messages at boot

The Printcap-file just holds information about the queues. Nothing for the configuration of LPD.

What happens if you start LPD manually after boot ? Add an EXIT at the top of the LPD-startupfile.

Hmmmm..... does LPD work as expected ?

Hakan
Don't make it worse by guessing.........
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

I have tried to restart LPD on our test cluster (which also have these messages) without getting any of the messages I get from the boot.

I would try a real reboot, but sadly this is not possible since the developers needs them online.

LPD is working as expected yes.

Best regards
Fredrik Eriksson
Hakan Zanderau ( Anders
Trusted Contributor

Re: Wierd messages at boot

Does your printcap-file look OK ?

Is there a queue called TCPIP$LPD_QUEUE ?

It's the queue where incoming LPD-jobs are placed by the LPDservice and processed before printcap is red for a target-queue.

In later versions the incomming queue is a generic queue called TCPIP$LPD_IN

Hakan

Du kan ringa mig for en muntlig diskussion om du vill..... 0501 - 353 26
Don't make it worse by guessing.........
Wim Van den Wyngaert
Honored Contributor

Re: Wierd messages at boot

In my vcersion stopping TCP didn't stop LPD symbionts. I had to stop/id. I think it(s a pure cliuent that hopes that TCP wil work again when the next reauest comes in.

Wim
Wim
Hakan Zanderau ( Anders
Trusted Contributor

Re: Wierd messages at boot

Cluster ????

Is the logical TCPIP$LPD_ROOT pointing to the same location on all nodes ?

Hakan
Don't make it worse by guessing.........
Fredrik.eriksson
Valued Contributor

Re: Wierd messages at boot

Hi again, sorry for the late reply.

The cluster shares a disk, but the configuration is done seperatly.

The content of the printcap.dat files are identical thou and the configuration output taken from the TCPIP$LPD_IN_NODE1__1.LOG is as follows:

%%%%%%%%%%%% 5-JUN-2009 18:18:33.97 %%%%%%%%%%%%
%TCPIP-I-LPD_LOGSUC, using log file TCPIP$LPD_ROOT:[000000]TCPIP$LPD_IN_BASNG1_1
.LOG

%%%%%%%%%%%% 5-JUN-2009 18:18:34.02 %%%%%%%%%%%%
%TCPIP-I-LPD_SYMBRUN, symbiont is running the queue TCPIP$LPD_IN_BASNG1_1

TCPIP LPD configuration data:
LPD Spooler Directory : TCPIP$LPD_ROOT:[000000]
Retry-Interval : 0 00:05:00.00
Retry-Maximum : 0 01:00:00.00
Idle-Timeout : 0 00:05:00.00
Inbound-Queues-Per-Node : 1
Utility-Queues-Per-Node : 0
Receiver-Debug : 0
Symbiont-Debug : 0
Utilities-Debug : 0
Loop-Max : 0
Droptime : 0
Probetime : 0
PS-Extensions : LPS
Stream-Passall : FALSE
VMS-Flagpages : FALSE
Persistent-Server : FALSE
Keepalive : FALSE
Synchronize-All-Jobs : TRUE
Setup-NoLF : FALSE
1st-VFC-Prefix-Special : FALSE

PCB for printer
PA: FALSE
ND: FALSE
CR: FALSE
SN: FALSE


Obviously, the last part shows the same kind of messages displayed in my operator.log, but I can't seem to find any way of changing these configuration settings or even just look at them.

This is the content of my printcap file:
TCPIP$LPD_QUEUE:\
:lp=TCPIP$LPD_QUEUE:\
:sd=TCPIP$LPD_SPOOL:

This is not a prioritized thing since it doesn't seem to break anything. It just annoys me that there is messages that doesn't make any sense :P

Best regards
Fredrik Eriksson
Hakan Zanderau ( Anders
Trusted Contributor

Re: Wierd messages at boot

Fredrik,

Could you supply a

$ SHOW LOGICAL TCPIP$LPD_ROOT

from all clustermembers and a

$ SHOW QUEUE *LPD*/FULL

Hakan

Kan jag kontakta dig per telefon ??



Don't make it worse by guessing.........