[Orca-users] RE: Problem starting ORCA via SSH command
Waltner, Steve
swaltner at lsil.com
Thu Apr 18 05:44:16 PDT 2002
This is an warning message and isn't really an error message. If you login
to the system and do a "ps auxwww | grep 21012" you will find that process
21012 has a very long argument list. nawk is complaining about this. It's a
non issue since orca is just trying to find if there is already a copy of
orcallator running on the system to keep from running two at a time. You can
safely ignore the error message.
Steve
> ----------
> From: Sean O'Neill
> Reply To: orca-users at yahoogroups.com
> Sent: Wednesday, April 17, 2002 11:26 AM
> To: orca-users at yahoogroups.com
> Subject: [orca-users] Problem starting ORCA via SSH command
>
> Anyone seen a problem where you start ORCA over an ssh like below and get
> a
> NAWK burp every so often:
>
> ssh ${DST} "/local/home/perfboy/orca/bin/start_orcallator"
> /usr/bin/nawk: input record `uccnet 21012 2.4 ...' too long
> input record number 1
> source line number 1
> Writing data into /local/home/perfboy/orca/var/orca/orcallator/prod-app02/
> Starting logging
>
> I don't get this for all the systems I start ORCA on - it flip/flops
> between servers but they all do it from time to time. The NAWK command in
>
> start_orcallator and stop_orcallator are getting/doing something funny. I
>
> modified the stop_orcallator script so that it contains only the
> following:
>
> pkill se.sparcv9
> exit 0
>
> This fixed it in that file. But the start_orcallator still "burps"
> occassionaly - VERY ANNOYING. I know this isn't an ORCA problem but a
> NAWK
> through SSH problem.
>
> Just curious if anyone has seen this and done something about it already
> for their ORCA installation.
>
>
> --
> ........................................................
> ......... ..- -. .. -..- .-. ..- .-.. . ... ............
> .-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...
>
> Sean O'Neill
>
>
>
>
>
>
>
>
More information about the Orca-users
mailing list