Hi,
Error occurred during reading below line: timer t3103 0
I may be wrong, but it's probably related to recent change:
http://git.osmocom.org/openbsc/commit/?id=ab2454e776f1a4bc4977ef48ec2844600f...
In short, it doesn't make sense to set '0' value to any timer. So, updating the software, please also keep your configuration updated ;)
With best regards, Vadim Yanitskiy.
Thanks for the heads up Vadim.
We’ll try changing the timer value to non-zero.
Best regards,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Jul 22, 2017, at 7:00 PM, Vadim Yanitskiy <axilirator@gmail.commailto:axilirator@gmail.com> wrote:
Hi,
Error occurred during reading below line: timer t3103 0
I may be wrong, but it's probably related to recent change:
http://git.osmocom.org/openbsc/commit/?id=ab2454e776f1a4bc4977ef48ec2844600f...
In short, it doesn't make sense to set '0' value to any timer. So, updating the software, please also keep your configuration updated ;)
With best regards, Vadim Yanitskiy.
On Sat, Jul 22, 2017 at 11:13:30AM +0000, Ron wrote:
We’ll try changing the timer value to non-zero.
just remove all lines specifying timers with '0', the system will use reasonable defaults.
Thanks for the advice Harald.
We'll also do that.
BR, Ron
-------- Original Message -------- Subject: Re: osmo-nitb error during execution (Error occured... timer t3103 0) From: Harald Welte To: Ron CC: Vadim Yanitskiy ,OpenBSC Mailing List
On Sat, Jul 22, 2017 at 11:13:30AM +0000, Ron wrote:
We’ll try changing the timer value to non-zero.
just remove all lines specifying timers with '0', the system will use reasonable defaults.
-- - Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Sun, Jul 23, 2017 at 12:18:18PM +0200, Harald Welte wrote:
On Sat, Jul 22, 2017 at 11:13:30AM +0000, Ron wrote:
We’ll try changing the timer value to non-zero.
just remove all lines specifying timers with '0', the system will use reasonable defaults.
Actually, I think we should start accepting '0' as valid input in validating the config file, but simply ignore it and use the compile-time default if the value is 0.
On Sun, Jul 23, 2017 at 3:11 PM, Harald Welte laforge@gnumonks.org wrote:
On Sun, Jul 23, 2017 at 12:18:18PM +0200, Harald Welte wrote:
On Sat, Jul 22, 2017 at 11:13:30AM +0000, Ron wrote:
We’ll try changing the timer value to non-zero.
just remove all lines specifying timers with '0', the system will use reasonable defaults.
Actually, I think we should start accepting '0' as valid input in validating the config file, but simply ignore it and use the compile-time default if the value is 0.
That's a very good idea.
On Sun, Jul 23, 2017 at 02:11:59PM +0200, Harald Welte wrote:
On Sun, Jul 23, 2017 at 12:18:18PM +0200, Harald Welte wrote:
On Sat, Jul 22, 2017 at 11:13:30AM +0000, Ron wrote:
We’ll try changing the timer value to non-zero.
just remove all lines specifying timers with '0', the system will use reasonable defaults.
From a user interface perspective, IMHO it makes more sense to keep '0' as "take action immediately", even though we're not using that at the moment. How about https://gerrit.osmocom.org/3339
~N
-
Alexander Chemeris -
Harald Welte -
Neels Hofmeyr -
Ron -
Vadim Yanitskiy