[FADCA] ax25ipd not starting

[Chuck Hast]

On 6/16/05, Dan Garley <dpgarley at earthlink.net> wrote:
> On Wednesday 15 June 2005 22:36, Chuck Hast wrote:
> > On 6/14/05, Dan Garley <dpgarley at earthlink.net> wrote:
> > > On Monday 13 June 2005 23:41, Bill Sinbine wrote:
> > > > At 11:31 PM 6/13/2005, Chuck Hast wrote:
> > > > >On 6/13/05, Bill Sinbine <n4xeo at bellsouth.net> wrote:
> > > > > > At 06:58 PM 6/13/2005, Chuck Hast wrote:
> > > > > > >Bill,
> > > > > > >I assume that you are shutting down and starting up your ax25
> > > > > > > stack since every so often I find that the ax25ipd daemon is not
> > > > > > > running. I think
> > > > >
> > > > > you are
> > > > >
> > > > > > >probably restarting it with the rcax25 restart command which I do
> > > > > > > not
> > > > >
> > > > > think
> > > > >
> > > > > > >runs the ax25-up script. Your ax25ipd start up along with the
> > > > > > > start up of fpac is in the ax25-up script and if it is not being
> > > > > > > run that explains
> > > > >
> > > > > why I
> > > > >
> > > > > > >find the link to you gone and can not bring it back up when I try
> > > > > > > it,
> > > > >
> > > > > after I
> > > > >
> > > > > > >go in and restart the ax25ipd daemon then the link comes right up
> > > > > > > and runs just fine...
> > > > > > >
> > > > > > >Tell me how you are starting your ax25 and fpac stuff does it
> > > > > > > start automaticly
> > > > > > >when you boot the machine or do you have to manually start stuff?
> > > > > >
> > > > > > It all starts automatically
> > > > > >
> > > > > > It might have to do with the dialup. I only get 12 hours runso I
> > > > > > reboot
> > > > >
> > > > > it 3 times a day so it can be used all the time. this weekend
> > > > >
> > > > > > was a little different on the times. I normally re dial it at 6am
> > > > > > before work then when I get home and before I go to bed.
> > > > >
> > > > >For some reason the ax25ipd daemon is not starting, I keep on going in
> > > > > and finding that it is not running, I am trying to figure out why it
> > > > > is not starting if
> > > > >all of the rest is running.
> > > > >
> > > > >Maybe need to put a longer sleep in front of it.
> > > > >
> > > > >Why do you have to reboot it, why not just cause it to redial? I have
> > > > > not done dialup but know that a lot of people do it and do not have
> > > > > to reboot the machine,
> > > > >just have the dialer re-dial.
> > > >
> > > > I'm sorry that I said reboot it should have been re dial...
> > > >
> > > > > > OAN it was locked up again today and I had to kill it to get it to
> > > > > > reboot....Are there any utilities like Norton that I can run on it
> > > > > > to see if there are any problems??
> > > > >
> > > > >Are there any sort of messages anywhere prior to the lockup? I wonder
> > > > >what would be causing them... Well there are all sort of tools, but a
> > > > >lockup is not so common unless something is messing memory up or
> > > > >something else.
> > > >
> > > > I haven't seen it lock up I just walk in here and it is not running. I
> > > > do have a gui open that I'm working with. I have to have that open so
> > > > if it disconnects the dialup when I'm not here Barbara can come in and
> > > > make it connect again. This is one of the things that I still need to
> > > > get done. I still need to get the dialup loading at boot up and just
> > > > reconnect or connect on demand. Then I wouldn't need to have the gui
> > > > running other than to do stuff.. The screen just looks like a picture
> > > > of the way I left it no message or anything at all. Remember I told you
> > > > that it did it on Saturday also....
> > >
> > > Being new to the list I don't know where you are in the linux curve, so
> > > heres .02 $.
> > >
> > > Linux is multiuser, you have multiple terminals available, use for
> > > instance ctrl-alt-F4 to hop to the terminal on TTY4, then u can log in,
> > > check logs, ps to check process etc.  Many times when a session locks,
> > > all the other vt's are available. Your normal login session is most
> > > likely on  vt7, so ctrl-alt-F4 will put u back there.
> >
> > Dan, I am accessing it using ssh sessions, usually I will have 2 of them
> > going so I can see what happen when one goes off in the weeds, but at times
> > I have taken both of them out. I am over in Tampa, Bill is in Ft Pierce...
> >
> > > Also, can use the cron facility to schedule stuff, like launch script
> > > every 5 min, check if modem active, redial if not. Endless possibilities
> > > for automation based on schedule.
> > > Run suse 9.3 here.
> >
> > I use SuSE on my work laptop so as to avoid the viru/trojan/worm atractor
> > that is WinXP that I have to have on that machine since it belongs to my
> > employer, but they have allowed me to partition the thing and put SuSE
> > on the other partition, which is just fine to me.
> >
> > Back to Bill's problem, we are trying to get the fpacuser login that I
> > have running on my switch up and running on his, i.e. if you ssh into
> > 24.129.134.206
> > login fpacuser
> > password fpac
> > You can give it your call at that point and you are in the switch as though
> > you had connected to it from the radio side. Bill wants to make that
> > standard network wide where we can, so I was trying to set his machine up
> > to work the same way but something just is not allowing it. I have set up a
> > user called fpacuser given it fpac as the password, when I log into it, it
> > just folds up shop and goes away. I have set things up in /etc/passwd and
> > also in /etc/shells, also the permissions are set correctly but something
> > :"ain't right:"
> > So that is where we are right now.
> Is fpacuser a member of the appropriate groups?  If you get past the login and
> can enter a callsign, perhaps the next part of the code calls an app or
> service that requires specific group membership? For instance, in most
> non-ham apps if you want to use a modem u must be a member of "dialup" group
> etc.  Just guessing right now, havent seen the fpac code yet (but I have a
> pointer to it, haven't dl'd it yet).  Is there a ssh user/pw thatll allow
> general "poking around" in the files (read only would be fine).  I realise
> these are very basic suggestion, but sometimes it is that simple.
> 73 Dan WH6A
> 
It is part of the same group, what is happening is that the unix login
takes place
but it appears that as soon as the fpacnode app is called the whole thing shuts
down, and the whole terminal goes away. You do not even get the prompt for the
callsign. But if you replace the fpacnode with /bin/bash and then log
in you get a
bash prompt, and if you call fpacnode it comes up just fine. 

Yes there is a user called radio (real imaginative yea?!?) and the password is
radio, you can use that to go in and look around at things.

Same goes for my machine which does work. you can use radio to go in and
poke around and see what you can see.

Also ssh into it and try the switch app if you have not done so. That
will let you
see how we are trying to make Bill's machine work.

Go ahead and start looking at the files and docs.



-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."