[Orca-users] Re: orcallator.se runs, but no output

Blair Zajac blair at akamai.com
Sun Jan 21 13:55:31 PST 2001


Hi Mark,

A couple of things:

How long are you waiting for the log file to appear?  I believe it
can take up to 7 1/2 minutes before the log file appears since it
always prints the log entry on integral multiples of the time
interval.

The orcallator.pid file is created by start_orcallator.sh, not by
orcallator.se, so the fact that it appears doesn't mean orcallator.se
is running.

Try editing start_orcallator and change the line 

$SE $LE_PATCH -DWATCH_OS $WATCH_WEB $libdir/orcallator.se &

to

$SE $LE_PATCH -DWATCH_OS $WATCH_WEB $libdir/orcallator.se 5

This should keep the process running in the foreground to see any
messages it prints and also reduces the logging interval to 5 seconds
which makes debugging easier.

If you are seeing orcallator.se fail, let me know what message you are
getting.

Regards,
Blair

Mark Langkau wrote:
> 
> Hi Blair,
> 
> I'm using /usr/local/bin/start_orcallator. OUTDIR gets set to
> "/usr/local/var/orca/orcallator/e5501" and the orcallator.pid file *does*
> get written there. I explicitly changed OUTDIR to this path in the script,
> but still no luck. Then I deleted the e5501 (hostname) dir to see if it got
> created when start_orcallator ran. It did.
> 
> Script is running as root, and I have made that dir world writable (not a
> good security thing, but I wanted to eliminate permissions as a cause for
> no data files). After running "start_orcallator" I see the start up
> messages, but nothing after that (no output to stdout).
> 
> I'm not trying to do anything fancy. Everything runs on one system - no nfs
> mounts. Straight "out-of-the-box" install of SE and Orca. To configure Orca
> I created a script with the config options, so I could later see how I ran
> configure. Here is that script:
> ==================================
> # more run-config.sh
> 
> #!/bin/sh
> 
> #Here is how we configured Orca:
> PREFIX=/usr/local
> 
> ./configure --prefix=$PREFIX \
>             --bindir=$PREFIX/bin \
>             --libdir=$PREFIX/lib \
>             --mandir=$PREFIX/man \
>             --with-rrd-dir=$PREFIX/var/orca/rrd \
>             --with-orcallator-dir=$PREFIX/var/orca/orcallator \
>             --with-html-dir=/usr/local/apache/htdocs/orca \
>             --with-ncsa-log=/usr/local/apache/logs/access_log
> #
> =================================
> 
> Here's what I see:
> 
> # start_orcallator
> Writing data into /usr/local/var/orca/orcallator/e5501/
> Using www access log file /usr/local/apache/logs/access_log
> Creating /usr/local/var/orca/orcallator/e5501/
> Starting logging
> #
> #ps
>    PID TTY      TIME CMD
>  21795 pts/5    0:00 sh
>  23736 pts/5    0:00 ps
>  23694 pts/5    0:25 se.sparc
> #
> # orcallator_running
> Now in /usr/local/var/orca/orcallator
> /usr/local/bin/orcallator_running: e5501/percol-2001-01-21 does not exist.
> #
> 
> Sorry to be such a pest, but I'm really stumped. Thanks a bunch for your
> help!
> 
> Cheers,
> Mark Langkau
> 
> Blair Zajac wrote:
> 
> > How are you starting orcallator.se?  Using the start_orcallator.sh
> > script?  This sets the OUTDIR environmental variable which is used
> > by orcallator.se.
> >
> > If the OUTDIR environmental variable is not set or is empty, then
> > orcallator.se will output to standard output, otherwise it'll create
> > an output log file in the OUTDIR directory.
> >
> > Please check to see what OUTDIR is set to.
> >
> > To run just orcallator.se you don't need to create the rrd directory.
> >
> > Regards,
> > Blair
> >
> > mark.langkau at pbmplus.com wrote:
> > >
> > > Hi Martin,
> > >
> > > The hostname directory does exist, and the "orcallator.pid" file gets
> > > written there. I'll try creating one in the rrd directory too.
> > >
> > > Thanks,
> > > Mark
> > >
> > > --- In orca-users at egroups.com, Martin Hepworth <maxsec at t...> wrote:
> > > > Hi
> > > >
> > > > you need to create the 'hostname' directory for oracallator.se to
> > > write
> > > > into. ie create directory /usr/local/var/orca/orcallator/e5501 then
> > > > everything should be fine. You _may_ need to create a corresponding
> > > rrd
> > > > directory as well.
> > > >
> > > >
> > > > martin
> > > >
> > > > Mark Langkau wrote:
> > > >
> > > > > Hi Everyone,
> > > > >
> > > > > I've installed orca-0.26.tar.gz on a Sun e5500 with Solaris 7.
> > > > >
> > > > > orcallator.se runs, but does not create any output (even after
> > > running
> > > > > more than an hour). Any ideas about what would cause orcallator
> > > not to
> > > > > make any data files?  I have installed the SE toolkit and it works
> > > (we
> > > > > use xoom.se), and orca finds it during configuration.
> > > > >
> > > > > Output of "orcallator_running" :
> > > > >
> > > > > # orcallator_running
> > > > > Now in /usr/local/var/orca/orcallator
> > > > > /usr/local/bin/orcallator_running: e5501/percol-2001-01-18 does
> > > not
> > > > > exist
> > > > > #
> > > > >
> > > > > Cheers,
> > > > > Mark Langkau



More information about the Orca-users mailing list