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

[Mark Langkau]

Hi Blair,

I made the changes, but still no luck. I've waited several hours in the past
with no output. It's been about 30 minutes now since I changed the
start_orcallator script. The only difference is that it remains in the
foreground. Still no output to stdout or filesystem. Running "ps" shows "se"
running, and it goes away when I run "stop_orcallator." Does that mean
orcallator is running?

Bummer. Anything special steps for Solaris 7? I'm probably overlooking something
very simple.

Cheers,
Mark

Blair Zajac wrote:

> 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
>