[nos-bbs] JNOS TTY console - No Visual

[George [ham] VerDuin]

On 02/07/2011 10:53 PM, Wm Lewis wrote:
> I guess I'm just not being specific enough!
>
> If the startnos script *always worked just fine* then one day JNOS 
> crashed and then this issue began, the what in the bajibies make you 
> think a working startnos script suddenly is the issue ??
Simply stated:
     A) because the underlying OS changes over time
     B) all change is not a bug
     C) Isolating a cause of failure in absence of a specific error code 
reason requires some change

Example?
In the future, if your autoexec.nos uses "shell ifconfig ..." in 
attaching tun, with no change to jnos you should expect a failure some 
day.  Today the OS command "ifconfig" is on the chopping block in 
preference to the command "ip ...".  When that happens, it's not a bug.  
I'm pretty convinced ifconfig is not part of todays failure, and if we 
are lucky when ifconfig is deprecated it will remain available as an 
add-on...

>
> I don't think this has a damn thing to do with JNOS or any component 
> thereof.
Well perhaps, but consider your original 1/31 error text again:

   1. The 19:07:18 entry may have been the result of your personal
      action, the root cause of which we don't yet understand.
   2. The 19:07:25 entry is failure to start jnos -- so what does
      "status 2" tell you [ubuntu may want to know].
   3. The 10 cycles of respawn in less than 1 second is easily caused by
      the missing "sleep" in your script.  Notice? --> 21226 - 21223 = 3
      the same number of steps in your script.
   4. Finally init throws in the towel on tty4 and does something else
      not documented in this thread that leaves a running jnos incidence
      somewhere in the ps tree.

Inserting sleep into startnos most probably won't fix the problem.  
However -- some sleep may change the nature of the error so in fact you 
can see the root cause.  Here it is to save looking back two weeks...
 > > =============================================================
 > > Jan 30 19:07:18 linux init: tty4 main process (14630) killed by 
TERM signal
 > > Jan 30 19:07:25 linux init: tty4 main process (21223) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21226) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21229) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21232) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21235) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21238) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21241) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21244) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21247) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21250) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 main process ended, respawning
 > > Jan 30 19:07:25 linux init: tty4 main process (21253) terminated with
 > > status 2
 > > Jan 30 19:07:25 linux init: tty4 respawning too fast, stopped
 > > =============================================================
>
> I believe Maiko is on the correct path in that it is an Ubuntu issue.
>
> This issue is now closed and being moved to Ubuntu forums.
That is a valid choice.
I hope you will publish your finding here if others could be effected.

And IMHO if you are pissed, it doesn't have much to do with your being 
not-specific.

Again:  --  Best of luck
Skip