A140 Logging

This forum is dedicated to the discussion of how Cilutions implements digital signage using the DMB Media Player.

A140 Logging

Postby Henry.G » Thu Jan 12, 2012 4:03 pm

I have a network of A140 STBs which retrieve their screens from an FTP Server at boot-up and offer multiple VOD channels each playing a live IP Multicast stream. What log files are available on the A140 to help me analyze any reported problems?
Henry.G
 
Posts: 45
Joined: Mon Apr 25, 2011 12:54 pm

Re: A140 Logging

Postby Cilutions Support » Tue Jan 17, 2012 6:19 pm

The low level logging on the A140 and A540 STBs consists of a set of files accessible to a knowledgeable support engineer from telnet or ssh command access into the STB. Accessing the STB and logging in (username/password) are covered in other support forums and/or through inquiry sent to support@cilutions.com (for security reasons). The log files are:

    /PVR/pdreceiver/log_ftpc.txt - a text file describing any and all activity initiated by the local STB when retrieving content (e.g., pulling) from an external FTP Server.
    /PVR/pdreceiver/log_ftpd.txt - a text file describing any and all activity initiated by an external FTP client logging into the local STB when pushing content from, say, a DMB Screen Builder application to the STB.
    /PVR/pdreceiver/log_epg.txt - a text file describing any and all activity initiated by the local DMB Media Player when displaying elements on the locally attached TV. This includes parsing screenlists, retrieving RSS feeds, playing videos, etc. If the TV does not play an element you expect or the TV screen appears to have a problem this is the first log you should examine to see if there are errors reported.

These text files can be reviewed in typical Linux log file fashion (e.g., tail -200 /PVR/pdreceiver/log_epg.txt to view the last 200 lines of the log file showing TV activity).

Also, the logs wrap around when they grow to 1MBytes in size to keep their resource demands low.
Cilutions Support
Site Admin
 
Posts: 139
Joined: Mon Feb 07, 2011 3:03 pm

Re: A140 Logging

Postby Cilutions Support » Sat Sep 01, 2012 4:44 pm

Note that log_epg.txt is also accessible from the local web form main page as a View Playback Log button on the main page.

To access this page use the following URL: http://<IP_of_STB>

Example access to an STB with IP address 192.168.1.55: http://192.168.1.55
Cilutions Support
Site Admin
 
Posts: 139
Joined: Mon Feb 07, 2011 3:03 pm

Re: A140 Logging - FTP Retrieval

Postby Cilutions Support » Wed Jul 30, 2014 10:24 am

This link describes how to execute a command to measure bandwidth between an STB and a Server and retrieve the test results, a log file on the STB, by HTTP POSTing it back to a Web Server to be store as a local file: viewtopic.php?f=27&t=308#p971

Then an operator can review the log file on the Web Server without having to telnet/ssh (or http browse)into the STB directly.

This same mechanism can be used, really, to retrieve any text file (e.g., performance logs) from an STB.

Here is an example finstall_ftp file which posts the log_ftpc.txt file back to an HTTP Server (example address 192.168.1.45):
Code: Select all
#!/bin/sh
#Only run this if we just downloaded finstall_ftp
if [ $1 = "/PVR/finstall_ftp" ]; then
    curl -T /PVR/log_ftpc.txt http://192.168.1.45/Uploads/receive.pl
fi
exit 0

IMPORTANT: The finstall_ftp file must be created using Unix/Linux end-of-line formatting. Be careful to avoid DOS/Windows/MAC formatting as these formats will not execute on the Linux STBs.
Cilutions Support
Site Admin
 
Posts: 139
Joined: Mon Feb 07, 2011 3:03 pm


Return to Digital Signage

Who is online

Users browsing this forum: No registered users and 1 guest

cron