[App_rpt-users] Beagle bone black and timedatectl

Doug Crompton doug at crompton.com
Mon Oct 27 18:00:31 EDT 2014


 There is an issue in asterisk that causes all sorts of problems if the time is changed when it is running. This has been mostly but not entirely corrected in version 1.2.1 so I suspect you will still have the problem.

The quick reason is that in many instances throughout the code the real time clock rather then a continuously running and incrementing clock is used for timing in critical code. Not a good idea!!

The answer is to NOT change the time while asterisk is running. Instead stop asterisk. Set the time and restart asterisk. I suspect that changing the time and then just restarting asterisk would work equally well.  

This is a known problem that also would exist in an acid release but rarely shows up because users do not make time changes like that once it boots.

Version 1.2.1 was released now without all the timing problems corrected so that users could benefit from many of the other fixes and features. There will be another release once this problem is completely corrected and tested. I must emphasize though that the vast majority of users with Internet connections will not have this problem.

Also since the primary reason to have Allstar is communications over the Internet your case is probably very isolated.

Please ask questions relating to the BBB on the arm-allstar list if possible.
73 Doug

Date: Mon, 27 Oct 2014 16:24:57 -0400
From: mike.lussier at gmail.com
To: app_rpt-users at ohnosec.org
Subject: [App_rpt-users] Beagle bone black and timedatectl

Good afternoon to all. 
I have posted on this issue before. I have and off site repeater with no internet access atleast until spring time, Hopefully...
My allstar node time is way off. so I try to correct it. The outcome is a lock up condition. The repeater no longer responses. The only fix appears to be a reboot. This only brings me back to square one. The time is way off again.

Is there something else to do once I reset the time short of a reboot to bring the system up on line ? is there a way to reset the system and use the new time stamp ? 

Seriously contemplating an NTP server at the site. I just don’t have the time to put into one right now.   

I have the new 1.2 code. I'm not ready to deploy this to either of the repeaters just yet. 
command issued this morning that caused the trouble.

tmedatectl " 2014-10-27 11:35:00"

Thank you 

Mike AE4ML
"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan

App_rpt-users mailing list
App_rpt-users at ohnosec.org

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20141027/821ab85b/attachment.html>

More information about the App_rpt-users mailing list