[Orca-users] Re: percol dies without any notice

[Martin Hepworth]

HI

I'd always invoke se/orcalator with the nohup command to stop this. Also 
if you reboot se should be set to start to boot by placing that startup 
scripts in /etc/init.d and linking to /etc/rc3.d as normal.

Martin

jstuckey at privada.com wrote:

> I recently had this problem as well. It turned out (on my systems) to 
> be an environment issue that I do not completely understand. I have a 
> stack of Netras running SunOs 5.7 and installed Orca-0.26 beta1. We 
> use ssh and allow direct root logins to the boxes. I would ssh into a 
> box (as root) and start '../se.sparcv9.5.7  ../orcallator.se' using 
> the start script in /etc/rc3.d. As soon as I logged out of this box 
> the process would die. I confirmed this several times by logging in on 
> another terminal and running a truss -v on the orcallator pid. As soon 
> as I logged out of the root shell that invoked orcallator.se, 
> orcallator would die at the exact same time.
> 
> I then decided to login with a normal user account and su - to invoke 
> /etc/profile. If I did this, after restarting, orcallator would 
> continue to run after logging out of the box. None of these machines 
> have a problem with orcallator after rebooting, that works just 
> fine... So it appears to be an environment issue with the root login.
> 
> I then checked for differences between the two environments and found 
> the following:
> 
> When directly ssh into the box as root, the following variables's are 
> the only thing different from the su - environment. Path's and 
> everything else are the same...
> 
> SSH_CLIENT=192.168.1.172 2648 22
> SSH_TTY=/dev/pts/3
> USER=root
> 
> So I am guessing that somehow when the ssh_tty dies so does 
> Orcallator.se? Its not a great problem but I thought others may be 
> interested and/or have some thoughts.
> 
> Thanks
> Joel Stuckey
> Privada Inc.
> 
> 
> 
> --- In orca-users at egroups.com, dave.pyles at b... wrote:
> 
>> If you are starting it by using the /etc/rc?.d scripts and a normal 
>> bootup it should work, if you start it manually, try using nohup.
>> 
>> --- In orca-users at egroups.com, ?Trent Melcher? ?tmelcher at t...? 
> 
> wrote:
> 
>> ? Im using the version that came with the 3.1preFCS release of the 
>> SEToolkit.
>> ? I got more info for you,  Im running the percol out of the 
>> /etc/init.d, when
>> ? I logout of the machine thats when it stops running.
>> ? 
>> ? Trent
>> ? 
>> ? 
>> ? -----Original Message-----
>> ? From: Blair Zajac [mailto:blair at a...]
>> ? Sent: Wednesday, May 31, 2000 8:00 PM
>> ? To: orca-users at egroups.com
>> ? Subject: Re: [orca-users] percol dies without any notice
>> ? 
>> ? 
>> ? I have no idea.  Try running orcallator.se under truss and see 
> 
> what
> 
>> ? happens.
>> ? 
>> ? Another thing to try is to run orcallator.se with an extremely 
> 
> short
> 
>> ? time to print the output, say 5 seconds, and have the output go
>> ? to standard output.  Then look at the last several lines to see 
>> what's
>> ? going on.
>> ? 
>> ? Which version of orcallor.se are you using?
>> ? 
>> ? Blair
>> ? 
>> ? tmelcher at t... wrote:
>> ? 
>> ? ? Sorry if this is a repeated question....I just started running
>> ? ? orcallator.se yesterday.  I have read through most of the
>> ? ? documentation.  My problem is the percol keeps dieing after 
> 
> about 
> 
>> 1
>> ? ? 1/2 hours, I cant find any error messages telling me why it 
> 
> dies.
> 
>> ? ? Anyone have any clues????   Im running 3.0 of the Toolkit on a 
>> Ultra2
>> ? ? running 2.6 Solaris (Sun_OS 5.6)
>> ? ?
>> ? ? Thanks
>> ? ? Trent
>> ? ?
>> ? ? 
>> 
> 
> 
> 



-------------------------- eGroups Sponsor -------------------------~-~>
eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9699/5/_/804404/_/973704190/
---------------------------------------------------------------------_->