[arm-allstar] I am new, and the time is wrong

Thu Aug 29 20:21:34 EDT 2019

I figured it out. That was enough help to let me look in the right place.

I was able to connect to it via ssh, but by ssh from another Raspberry 
Pi on the same lan. I had a static address of 192.168.1.15.

The networks at home and at the repeater site are both 192.168.1.xxx and 
it worked at home.

I tried to ping google.com from the Allstar pi, and was unsuccessful.

What I had forgotten was at home the gateway was 192.168.1.1 (like a 
normal person would do it.)
But we have ATT DSL at the repeater site, and the ATT router/gateway is 
at 192.168.1.254, so it could not find the way out. I fixed the gateway 
number, rebooted, and it is working now.

Yes, my timezone in Texas is Central Time. That was O.K.

It says Network Time is on and NTP synchronization is on,
but ntpq is a command not found.

How does this system set the time? Can I use a local stratum 1 timeserver?

Thanks,
Kip

On 8/28/19 9:10 PM, "Doug Crompton via ARM-allstar" wrote:
> Kip,
>
>   Time is automatic in Hamvoip Allstar as long as you have Internet access.
> Apparently you have some block there? Also the timezone is set as part of
> the setup. I presume central time is accurate for you. There is no realtime
> clock on the Pi. It depends on Internet access to set the time.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Aug 28, 2019 at 9:23 PM "Kipton Moravec via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> I found examples on the internet, for setting the time with timedatectl at
>> https://wiki.archlinux.org/index.php/System_time
>>
>>
>> [root at K5PRK_UHF asterisk]# hwclock --systohc
>> hwclock: Cannot access the Hardware Clock via any known method.
>> hwclock: Use the --debug option to see the details of our search for an
>> access method.
>> [root at K5PRK_UHF asterisk]# timedatectl set-time "2019-08-28 20:17:00"
>> Failed to set time: Automatic time synchronization is enabled
>> [root at K5PRK_UHF asterisk]#
>>
>> Kip
>> AE5IB
>>
>> On 8/28/19 8:03 PM, "Kipton Moravec via ARM-allstar" wrote:
>>> I am trying to learn how to use this system.
>>>
>>> I loaded the system, and have it hooked to my repeater through our
>>> club's RLC Club-Deluxe repeater controller. The advantage is I can
>>> link the ports for testing and unlink the ports if it is screwed up.
>>>
>>> The node and repeater are in a watertower, which means I have to call
>>> the city to let me in. So I am linking in remotely with ssh.
>>>
>>> I made a ulaw file with the ID and it seems to be working. I have also
>>> changed the courtesy tone. And made some new ones that correspond to
>>> the different weather events everyone here is accustomed to on the VHF
>>> repeater. (I am on the less used UHF repeater.)
>>>
>>> Today I noticed the time was way off when it said it.
>>>
>>> So the first thing I tried was
>>>
>>> ntpq -p
>>>
>>> It said command not found. so no NTP
>>>
>>> So I looked and found the timedatectl status command on the web site,
>>> and it returned
>>>    [root at K5PRK_UHF asterisk]# timedatectl status
>>>        Local time: Tue 2019-08-13 19:59:33 CDT
>>>    Universal time: Wed 2019-08-14 00:59:33 UTC
>>>          RTC time: n/a
>>>         Time zone: America/Chicago (CDT, -0500)
>>>   Network time on: yes
>>> NTP synchronized: no
>>>   RTC in local TZ: no
>>> [root at K5PRK_UHF asterisk]#
>>>
>>> Except this is Wednesday September 28 and the local time (Central
>>> time) is 7:48 p.m.
>>>
>>> Normally Raspbian gets the time automatically from the internet, with
>>> ntp. I do not know what is going on with this version of Arch Linux. I
>>> use Ubuntu, Debian, Mint, and Raspbian.
>>>
>>> i tried apt-get install ntp and apt-get does not work on Arch Linux. I
>>> have not looked yet to see what Arch Linux uses to get packages.
>>>
>>> How do you deal with time in Allstar? Why does it not set the time
>>> automatically? I would think that would be a basic function that
>>> should work right out of the box. And I have not seen anything about
>>> setting the time and date.
>>>
>>> That is one of the things I do not like about the RLC controller, It
>>> has its own clock that is fast by about 30 seconds a week. So I have
>>> to reset it all the time. I have written a Python script to reset it
>>> once a week at 3:00 a.m. on Sunday but I have not installed it yet.
>>>
>>> My other Raspberry Pi computers do not have this problem, and I have
>>> one set up as a Stratum 1 time server with a GPS hat.
>>>
>>> How do I fix the time so it is set automatically?
>>>
>>> Kip
>>>
>>> _______________________________________________
>>>
>>> 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
> _______________________________________________
>
> 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