Author Topic: YateBTS not starting  (Read 6355 times)

tonyjacobk

  • Newbie
  • *
  • Posts: 1
    • View Profile
YateBTS not starting
« on: October 01, 2015, 10:55:21 AM »
I installed YateBTS and started it with sudo yate -sd -vvvvv -l /var/log/yate1.log . YateBTS is not starting and logs give the following message. In one of the forum I read that setting
[modules]
gsmtrx.yate=no  in yates.bts will help but that too has not . How should I further debug this ?


2015-10-01_18:27:20.011182 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
2015-10-01_18:27:20.015418 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
2015-10-01_18:27:20.016739 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
2015-10-01_18:27:20.017229 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
2015-10-01_18:27:20.017785 <nib:INFO> Checked that only NIB is enabled.
2015-10-01_18:27:20.017913 <ALL> Rescanning handler list for 'engine.start' [0x7ffe88acae80] at priority 100
Yate engine is initialized and starting up on yatebts-HP-15-Notebook-PC
2015-10-01_18:27:20.018022 <INFO> Creating first message dispatching thread
2015-10-01_18:27:20.825671 <cpuload:NOTE> Updating CPU core number from 1 to 4
2015-10-01_18:27:20.931508 <gsmtrx:NOTE> Received command 'POWEROFF': transceiver not running
2015-10-01_18:27:20.932175 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
2015-10-01_18:27:21.932148 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
2015-10-01_18:27:21.932363 <gsmtrx:NOTE> Received command 'POWEROFF': transceiver not running
2015-10-01_18:27:22.933201 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
2015-10-01_18:27:22.933448 <gsmtrx:NOTE> Received command 'POWEROFF': transceiver not running
2015-10-01_18:27:23.934941 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
2015-10-01_18:27:23.935281 <gsmtrx:NOTE> Received command 'POWEROFF': transceiver not running
ALERT 140032046630784 18:27:24.9 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
2015-10-01_18:27:24.936668 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
2015-10-01_18:27:24.936815 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
2015-10-01_18:27:24.936908 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
5700/udp:            31843
2015-10-01_18:27:25.122461 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver-bladerf w/ 1 ARFCNs and Args:
2015-10-01_18:27:25.287374 <transceiver:NOTE> bladeRFDevice.cpp:110:open: Opened bladeRF serial=bed68a2046b339db44ea13c29695353f firmware version 1.8.0 (1.8.0)
2015-10-01_18:27:25.498151 <transceiver:NOTE> Transceiver.cpp:68:Transceiver: running 1 ARFCNs with oversampling 4
Starting transceiver
2015-10-01_18:27:29.937522 <gsmtrx:NOTE> Received command 'READFACTORY sdrsn': transceiver not running
ALERT 140032046630784 18:27:29.9 TRXManager.cpp:603:getFactoryCalibration: READFACTORY failed with status 4




Ioana Stanciu

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
Re: YateBTS not starting
« Reply #1 on: October 02, 2015, 01:29:41 AM »
Hi,

You must make that configuration in yate.conf. It's not clear from your message where you made that configuration,  but the log indicates that you are starting gsmtrx in conjuction with mbts that expects the old transceiver.

Also check that you are editing the right file (see configpath in the result of status engine command in telnet.