Call list is not updating

[Chris]

Good day Datatex.

Our call list stopped updating on 20161114. The call list is populated up to this point but no further.
My Farsouth Base software Com.X base system version 1.4 (x86 generic) 1.4.51.
The TNG version is Version 1.1.1.12 [4*]

The log entry for this date is as follows.

2016-11-14 00:00:00:005 [1.1.1.12] - AMI connected to port 5038 on 127.0.0.1
2016-11-14 00:00:01:008 [1.1.1.12] - AMI Disconnected:0 -
2016-11-14 00:00:01:009 [1.1.1.12] - AMI Exception:Connection Closed Gracefully. - repeated 76470 times
2016-11-14 00:00:01:009 [1.1.1.12] - AMI Exception:Connection Closed Gracefully.
2016-11-14 00:00:01:135 [1.1.1.12] - AMI connected to port 5038 on 127.0.0.1
2016-11-14 00:00:02:138 [1.1.1.12] - AMI Disconnected:0 -
2016-11-14 00:00:02:264 [1.1.1.12] - AMI connected to port 5038 on 127.0.0.1

[Luanda_Junzi]

Hi Chris.

1.Can you check errors on the log, before it stopped updating?
2.Did you have any power failures ?
3.Did you restart tng deamon ? give it time to load all extensions.

Regards
Luanda

[Chris]

Good day Luanda

1) The error log for the day that the system stopped logging is
2016-11-14 00:00:01:009 [1.1.1.12] - AMI Exception:Connection Closed Gracefully. - repeated 76470 times
2) There has been no power failures onsite.
3) Are you referring to the "sudo killall tng" command?
Yes we attempted this yesterday @ 17:00
There has been no change in the call list.
Please assist

[Chris]

Good day,

Any feedback?

[Belinda Frick]

Chris

As discussed by phone please do the following:

1. Stop the TNG daemon.
   See forum post: How do I stop and start the TNG service on LINUX?
2. Rename the master.csv
3. Start the TNG daemon.
   See forum post: How do I stop and start the TNG service on LINUX?

If still not loading check the TNG log file for errors:

go to directory:

Code: Select all

cd /opt/tng/logs/20161230

file name : tng.log

or view it in TNG Webadmin under logs (accessible from the Home Page).
NOTE: It will show newest event first on the screen.

[Chris]

Good day,

Thank you for getting back to me.
I have performed all the actions listed from 1-3.

Herewith the logfile errors.

2016-12-30 11:02:31:776 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:31:650 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:30:646 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:30:520 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:29:517 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:29:390 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:28:387 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:28:261 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:27:257 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:27:131 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:26:128 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:26:001 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:24:998 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:24:871 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:23:868 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:23:742 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:22:739 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:22:613 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:21:609 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:21:483 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:20:479 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:20:353 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:19:349 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 11:02:19:223 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 11:02:18:220 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250

[Belinda Frick]

Chris

Thank you for the feedback.

Can you please attach the entire tng.log file for 30 December 2016.

We need to investigate events since startup of tng deamon.

From this extract you need to look at the Asterisk 'writetimeout' settings, refer to forum post:

TNG4* Custom CSV is correct format but not logging calls
NOTE: This setting will depend on the number of entries that needs to load and will vary from system to system due to setup and/or resources.

[Chris]

Hi,

Herewith the log file requested

[Chris]

Hi there,

I have looked at and performed the steps outlined the the forum post

"TNG4* Custom CSV is correct format but not logging calls"

increasing the writetimeout=10000
I double-checked and stop/started the tng Deamon.

I still get the Waiting on Dial Plan and Peer List issue.
Viewing /opt/datatex/tng/logs/20161230/tng.log

2016-12-30 15:30:28:227 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 15:30:28:101 [1.1.1.12] - AMI Disconnected:0 -
2016-12-30 15:30:27:154 [1.1.1.12] - [AMI LOG] - Waiting on Dial Plan and Peer List
2016-12-30 15:30:27:097 [1.1.1.12] - AMI connected to port 5038 on 192.168.2.250
2016-12-30 15:30:26:971 [1.1.1.12] - AMI Disconnected:0 -

[Chris]

Good day Support,

Any update yet?