[nos-bbs] JNOS in TTY console on bootup
Bob Tenty
bobtenty at gmail.com
Mon Jan 31 14:30:53 EST 2011
Boot from your older kernel and see or jnos runs in tty4
If that is OK, it is something related to your new kernel
Boot from your new kernel
Stop tty4 (initctl stop tty4) and first try to run jnos manually (with
the jnos startup options) with your new kernel
At least you will know or it has anything has to with the jnos binary
itself related to the new kernel.
73,
Bob VE3TOK
On 11-01-31 10:15 AM, MJ Inabnit wrote:
> indeed we did get a giant update over this past weekend. I just copied and pasted my apt log so you might find the component that borked Jnos. I hope this helps.
>
> 73
>
> Start-Date: 2011-01-29 09:47:58
> Install: linux-headers-2.6.32-28-generic (2.6.32-28.55), linux-headers-2.6.32-28 (2.6.32-28.55), linux-image-2.6.32-28-generic (2.6.32-28.55)
> Upgrade: libpurple0 (2.6.6-1ubuntu4.2, 2.6.6-1ubuntu4.3), tomboy (1.2.1-0ubuntu1, 1.2.2-0ubuntu1), plymouth-theme-ubuntu-text (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), gwibber-service (2.30.3-0ubuntu1, 2.30.3-0ubuntu2), libblkid1 (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), linux-headers-generic (2.6.32.27.29, 2.6.32.28.32), libapparmor1 (2.5.1-0ubuntu0.10.04.2, 2.5.1-0ubuntu0.10.04.3), libplymouth2 (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), plymouth-x11 (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), util-linux (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), linux-image-generic (2.6.32.27.29, 2.6.32.28.32), libapparmor-perl (2.5.1-0ubuntu0.10.04.2, 2.5.1-0ubuntu0.10.04.3), plymouth-label (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), liblircclient0 (0.8.6-0ubuntu4.1, 0.8.6-0ubuntu4.2), hpijs (3.10.2-2ubuntu2.1, 3.10.2-2ubuntu2.2), hplip (3.10.2-2ubuntu2.1, 3.10.2-2ubuntu2.2), system-tools-backends (2.9.4-0ubuntu1, 2.9.4-0ubuntu1.1), uuid-runtime (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), libhpmud0 (3.10.2-2ubuntu2.1, 3.10.2-2ubuntu2.2), bsdutils (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), plymouth-theme-ubuntu-logo (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), media-player-info (6-1, 12-1~lucid1), libuuid1 (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), libpurple-bin (2.6.6-1ubuntu4.2, 2.6.6-1ubuntu4.3), apparmor (2.5.1-0ubuntu0.10.04.2, 2.5.1-0ubuntu0.10.04.3), mount (2.17.2-0ubuntu1.10.04.1, 2.17.2-0ubuntu1.10.04.2), apparmor-utils (2.5.1-0ubuntu0.10.04.2, 2.5.1-0ubuntu0.10.04.3), gwibber (2.30.3-0ubuntu1, 2.30.3-0ubuntu2), linux-generic (2.6.32.27.29, 2.6.32.28.32), linux-firmware (1.34.1, 1.34.3), plymouth (0.8.2-2ubuntu2.1, 0.8.2-2ubuntu2.2), hplip-data (3.10.2-2ubuntu2.1, 3.10.2-2ubuntu2.2)
> End-Date: 2011-01-29 09:51:48
>
> On Mon, 31 Jan 2011 05:42:05 -0500
> Mark Phillips<g7ltt at g7ltt.com> wrote:
>
>> Sounds to m like something got upgraded and in turn "broken".
>>
>> What does ls -l /dev/tty[0-9] produce? I'm betting that the permissions
>> are all wrong after a background update of some sort.
>>
>> Try this ;
>>
>> # rm /dev/tty4
>> # mknod /dev/tty4 c 4 4
>>
>> Mark
>>
>> On 01/31/2011 04:19 AM, Wm Lewis wrote:
>>> Hello All:
>>>
>>> In December of 2010 I started using JNOS on my new Ubuntu 10 machine.
>>>
>>> I wanted JNOS to automatically start when the computer booted, and a few
>>> people helped me do that.
>>>
>>> First I was told I needed to change the file: /etc/init/tty4.conf to
>>> read the following:
>>>
>>> ========================================================
>>> # tty4 - getty
>>> #
>>> # This service maintains a getty on tty4 from the point the system is
>>> # started until it is shut down again.
>>> start on runlevel [23]
>>> stop on runlevel [!23]
>>> respawn
>>> # exec /sbin/getty -8 38400 tty4
>>> exec /jnos/startnos tty4
>>> ========================================================
>>>
>>>
>>>
>>> Next I had to change the file: /jnos/startnos to read this
>>>
>>> ========================================================
>>> rm -f /jnos/spool/mqueue/*.lck 2> /dev/null
>>> rm -f /jnos/spool/mail/*.lck 2> /dev/null
>>> exec /jnos/jnos -a 40 -d/jnos</dev/tty4> /dev/tty4 2>&1
>>> ========================================================
>>>
>>>
>>> After rebooting the computer, JNOS did indeed automatically run.
>>>
>>> Now, 3 weeks ago JNOS crashed with gibberish across the screen.
>>> Since that time, JNOS will no longer automatically run on computer bootup.
>>>
>>> The tty4 console just has a blinking cursor and is non-responsive if I type
>>> at the keyboard.
>>>
>>> I have tried using a different console to see if it was just a glitch in
>>> tty4. No matter what
>>> console I use, JNOS will no longer automatically run on startup of the
>>> computer.
>>>
>>> I can go to any active console (say console 3) and change to the /JNOS
>>> directory and
>>> then run JNOS manually just fine.
>>>
>>> Looking at the logs for tty4 I see this:
>>>
>>> =============================================================
>>> 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
>>> =============================================================
>>>
>>>
>>> My question is ... has anyone had a situtation like this ?
>>>
>>> I have no idea why JNOS wont automatically run on bootup now.
>>>
>>> Suggestions are appreciated.
>>>
>>> Bill
>>> KG6BAJ
>>>
>>>
>>>
>>> _______________________________________________
>>> nos-bbs mailing list
>>> nos-bbs at tapr.org
>>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>> --
>>
>>
>> /\/\ark Phillips
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>
>
More information about the nos-bbs
mailing list