[arm-allstar] Allstar Node Scheduler

Sun Nov 11 21:56:07 EST 2018

Steve,

 saytime.pl has been in the distribution for years and just works. My
questions is - does your node work properly when the saytime call in cron
is commented out? Is it only saytime that causes a problem? saytime merely
forms the time in a gsm file and then sends it out using the localplay
directive.

This sounds like an issue with how you have it interfaced to your
controller and/or your configuration settings. You do know that Allstar
itself can be a repeater controller and you can connect multiple servers or
multiple nodes on a server to form as many ports as you want eliminating
the stand-alone controller. What controller are you using, how do oyu have
it connected, what setting in rpt.conf have you changed from stock?

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sun, Nov 11, 2018 at 9:23 PM Steve Thompson <steve.n7tx at gmail.com> wrote:

> Doug,
>
> Thanks for walking me thru this. When I do a crontab-l, I am seeing
> exactly what you said I’d see.
>
> When I run saytime.pl manually, it does the same thing as I have been
> seeing at the top of each hour (I’m hearing the repeater deadkey from port
> 2 - which is where on my external controller I’ve got the allstar node
> connected). Allstar node times out after 3 mins and sends “TO” in cw, then
> unkeys.
>
> When I echo $NODE1 at a Linux prompt, I do see my primary node number.
>
> I also checked to confirm that it’s not COR hanging up. When I use “v” on
> the simple-usb-tune menu, it is “CLEAR” when the repeater is not in use.
> When I transmit on the repeater, COS shows “KEYED”.
>
> So, whether saytime.pl is executed manually or on schedule, it is not
> working. Any other thoughts on what could be causing this?
>
> It’s as if there is some sort of dependency that saytime.pl has, and that
> dependency isn’t there or isn’t working as expected.
>
> Steve
>
>
> > On Nov 9, 2018, at 18:32, Doug Crompton via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > Steve,
> >
> > The hourly time is a cron process.  At the Linux prompt do  -  crontab
> > -l   You should see this -
> >
> > # Do not remove the following line
> > # required for lsnodes and allmon
> > 15 03 * * * cd /usr/local/sbin; ./astdb.php cron
> > 00 0-23 * * * (source /usr/local/etc/allstar.env ; /usr/bin/nice -19
> > /usr/bin/perl /usr/local/sbin/saytime.pl $NODE1 > /dev/null)
> >
> > There may be other lines if you added them but the forth line showing  00
> > 0-23 .......      is the one that does the time on the hour. Goggle cron
> to
> > see all the parameters.  The first 00 means the 0 minute and then 0-23
> > means each of the hours of the day.  Apparently something is wrong when
> > this happens. I cannot determine what without more input. You can run
> this
> > manually by typing  saytime.pl <node> at the Linux prompt and you should
> > hear the current time.  If your node was 40000 then the command would be
> > saytime.pl 40000   The $NODE1 variable should be set to your first node.
> > Check that by typing  'echo $NODE1' at the Linux prompt. It should be
> your
> > primary node number on the server.  It sounds like you do not have a
> radio
> > connected if you are using the pseudo node. Is that correct?
> >
> > The time should just work on the hour and certainly should not tie things
> > up for 4 minutes. If you want to disable the hourly time do
> > crontab -e     then edit that like by placing a # at the beginning. This
> > makes the line a comment and you can always remove it in the future to
> > reinstate.  Save the file and it will turn off the hourly time.
> >
> > It does seem like something else is going on here. Possibly a bad image
> > load. Have you messed with anything other than doing thte normal setup?
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Fri, Nov 9, 2018 at 8:19 PM "Steve Thompson via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> I’ve recently created a new Allstar node from the latest hamvoip image
> for
> >> RPi, and I’m working my way through some issues. One issue is that every
> >> hour, on the hour, the node transmits a dead carrier for 3 minutes, then
> >> there’s a CW message telling me it’s a timeout. Then the node unkeys.
> >>
> >> Very early on in the process of bringing my new node alive, the node was
> >> transmitting the time (in voice) at the top of the hour. So I have to
> >> believe this was the same process which is now working incorrectly. And
> >> perhaps I did something at some point to cause it to error out.
> >>
> >> When this issue occurs, I get this logged:
> >>
> >> <DAHDI ...> playing /tmp/current-time
> >>
> >> Then I get two separate lines logged that say:
> >> Hungup ‘DAHDI pseudo...’
> >>
> >> There IS a file in /tmp named “current-time.gsm”. I don’t know what the
> >> .gsm extension means though. The file is not a text file.
> >>
> >> I’ve searched through all the conf files in /etc/asterisk and the only
> >> reference to any sort of schedule is in rpt.conf.  In the [schedule...]
> >> section, the only two lines (which reference a macro to be run on the
> hour)
> >> are both commented out with semi-colons. I did not comment them out. I
> >> would think since they are commented out, they’d not be running ..
> unless
> >> there’s something somewhere else triggering this behavior.
> >>
> >> What is “DAHDI”?
> >> Any thoughts on how this is scheduled?
> >> And why it’s erroring out?
> >> Where else can I see what is going on with a schedule? Any thoughts on
> how
> >> to (1) in the short term, disable this scheduled event, and (2) in the
> long
> >> term, fix it so that it works properly?
> >>
> >> I have an extensive IT background but not much familiarity with Linux
> OS,
> >> so go easy on me.
> >>
> >> Steve N7TX
> >> _______________________________________________
> >>
> >> ARM-allstar mailing list
> >> ARM-allstar at hamvoip.org
> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>
> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>