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

maintaining log files that are locked

SOLVED
Go to solution
Paul Coviello
Frequent Advisor

maintaining log files that are locked

Hi we have an 8.2 system with a 1GB log file from TCPIP$ROUTED_OUTPUT.LOG and a 4 node cluster with 1.5 GB files on each node. I'm wondering how to regain this space back...

and of course rebooting isn't an option :-)
at least hope not...

thanks
Paul
10 REPLIES
Steven Schweda
Honored Contributor

Re: maintaining log files that are locked

Having only a static default route, hence
knowing nothing, I'd assume/expect that
something like:
TCPIP STOP ROUTING
TCPIP START ROUTING [/LOG]
would have some effect.
Jan van den Ende
Honored Contributor

Re: maintaining log files that are locked

Paul,

Steven deserves more, he gave the answer.

Only: Put a RENAME of the LOG file BETWEEN the STOP & START.

Same for other TCPIP ( & APACHE) LOG files.

HTH

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Paul Coviello
Frequent Advisor

Re: maintaining log files that are locked

>Mar 10, 2008 18:26:45 GMT 2 pts

--------------------------------------------------------------------------------
>Having only a static default route, hence
knowing nothing, I'd assume/expect that
something like:
> TCPIP STOP ROUTING
> TCPIP START ROUTING [/LOG]
> would have some effect.


well I looked at help and it has a different log file name! and it's not the default setting...
START ROUTING /LOG

Optional. Applies to ROUTED. Do not use with /GATED.

Logs routing activity to
SYS$SYSDEVICE:[TCPIP$ROUTED]TCPIP$ROUTED.LOG.

Default: No logging.



so I'm not sure where this log get created...

thanks
Paul
Hein van den Heuvel
Honored Contributor

Re: maintaining log files that are locked

So you do:
$ SHOW DEVI/FILE xxx /OUT=SHOW_DEV_xxx.LOG
$ SEAR SHOW_DEV_xxx.LOG ROUTED_OUTPUT
$ ANALYZE/SYSTEM
SDA> SET PROC
SDA> SHOW PROC /CHAN

And, if you have not done so already, you may want to $TYPE/PAGE the file to see what is it all about.

I know nothing about this file either... but if it is a shared write file (unlikely), the you copy the contents (as desired) and call $truncate back to the being, all while the file is open.

But surely you STOP, rename, START is the right approach.

Cheers,
Hein.


Steven Schweda
Honored Contributor
Solution

Re: maintaining log files that are locked

> Only: Put a RENAME [...]

I normally try it once without, to see if I
get a new version. If not, then yes, RENAME.
For example, DISABLE+ENABLE SERVICE FTP ("HP
TCP/IP Services for OpenVMS Alpha Version
V5.4 - ECO 6") seems to make a new
SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG
without any extra effort. (Of course,
expecting consistency among TCPIP components
tends to lead to disappointment.)

> Steven deserves more, [...]

In so many ways.
Paul Coviello
Frequent Advisor

Re: maintaining log files that are locked

I apologize I don't remember how to copy all the previous posts...


here is show device/file it's not pretty...

and what actually stops when I issue the command and since the default is no log how do I keep one from being created?

thanks
Paul


TCPIP$INETACP 000000A3 [VMS$COMMON.SYSEXE]TCPIP$INETACP.EXE;1
00000000 [VMS$COMMON.SYS$LDR]TCPIP$INTERNET_SERVICES.EXE;1
00000000 [VMS$COMMON.SYS$LDR]TCPIP$TNDRIVER.EXE;1

TCPIP$ROUTED 000000A4 [VMS$COMMON.SYSEXE]TCPIP$ROUTED.EXE;1
00000000 [VMS$COMMON.SYS$LDR]TCPIP$PROXY_SERVICES.EXE;1
TCPIP$ROUTED 000000A4 [SYS0.SYSMGR]TCPIP$ROUTED_OUTPUT.LOG;6
00000000 [VMS$COMMON.SYSEXE]TCPIP$FTP_CHILD.EXE;1
00000000 [VMS$COMMON.SYSEXE]TCPIP$FTP_SERVER.EXE;1
Paul Coviello
Frequent Advisor

Re: maintaining log files that are locked

just as a follow-up I issued the command below and according to that there is no log file... so I'm waiting on a call back from HP

$ tcpip show config start rout

Dynamic Routing Configuration

GATED: Disabled

ROUTED
Supply: Disabled
Default:
Log: Disabled
$
Hein van den Heuvel
Honored Contributor

Re: maintaining log files that are locked

>> I apologize I don't remember how to copy all the previous posts...

You can't. It just gives the original topic.
You'll need to clone a second window (^N in IE) or Tab and do a 'back' ALT <- in there.


>> here is show device/file it's not pretty...

Seems normal. It shows a version ;6, so there is good hope a restart will at least create a fresh version, if it restarts logging. It is not the default name and the HELP commands do not suggest you can pick one

>> and what actually stops when I issue the command

Routing?
;-)

>> and since the default is no log how do I keep one from being created?

Maybe was pre-set or left set with something like:
SET CONFIGURATION START ROUTING/LOG ?

Maybe it was renamed after the fact?
Maybe there is some config file we have not found yet?

A brute-force "SEARC/FORM=NON SYS$SYSTEM:TCPIP$ROUTED output" does not find that filename, so it was likely provided externally. Or cleverly hidden, but I don't think so as searching for LOG
finds "SYS$SYSDEVICE:[TCPIP$RO
UTED]TCPIP$ROUTED.LOG"

>> TCPIP$ROUTED 000000A4 [SYS0.SYSMGR]TCPIP$ROUTED_OUTPUT.LOG;6

You were supposed to use that to feed into ANALYZE/SYSTEM to make sure we talk about the right process / file.

I suspect it is the last, first and only rms file for the process TCPIP$ROUTED.
So you can also do SDA>SHOW PROC/RMS=(FAB,NAM).
You'll see full-access, no sharing.
For me it shows "NLA0:"

But... this will probably only confirm, but not help.

fwiw,
Hein.
Wim Van den Wyngaert
Honored Contributor

Re: maintaining log files that are locked

I would check what is in it. Do you really need VMS to do routing or did someone just activate it without reason ?

Wim
Wim
Paul Coviello
Frequent Advisor

Re: maintaining log files that are locked

stopped routing and was able to delete file also stopped from restarting, it isn't necessary... I will say if you don't know any better, it is easy enough to start going thru config,

thanks for all your help

Paul