On Tue, Apr 19, 2011 at 02:29:35PM -0400, Tom Metro wrote:

> > # grep -c myth:// mvpmc-debug.192.168.13.9-20110418.out
> > 348
> 
> ...yeah, that's not many. (Was the log transcript you posted to the
> devel list edited, as it appeared to show the "not responding" error
> after only a few programs had been loaded.)

Yes, the log transcript I sent had ellipses to indicate where I put in
cuts.

> So one possibility that there is something unusual in your mvpmc setup
> that is resulting in less free memory. You might want to telnet to it
> after a bootup and before attempting to load the recording list. Post
> the output of 'free' and 'ps'.

# free
              total         used         free       shared      buffers
  Mem:        13684        13320          364            0         3612
 Swap:            0            0            0
Total:        13684        13320          364
# ps
  PID  Uid     VmSize Stat Command
    1 root        340 S   init
    2 root            SW  [keventd]
    3 root            SWN [ksoftirqd_CPU0]
    4 root            SW  [kswapd]
    5 root            SW  [bdflush]
    6 root            SW  [kupdated]
    7 root            Z   [cifsoplockd]
    8 root            SW  [mtdblockd]
   66 root        284 S   /usr/sbin/telnetd
   94 root        316 S   udhcpc -i eth0 -n
  115 root            SW  [rpciod]
  133 root        920 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  150 root       8772 R   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  151 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  152 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  153 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  154 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  155 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  156 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  157 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  158 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  159 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  160 root       8772 S   mvpmc -f /etc/helvB18.pcf --classic -s 192.168.13.1 
-F /media/set
  211 root        412 S   -sh
  215 root        344 R   ps

> Another possibility is that there is a parse failure in the parsing of
> the show structure, resulting in a hang. (Just a guess.) If so, then it
> should consistently fail after the 348th recording, and doing things to
> alter the available free memory should not impact the recording number
> that it fails on. Also deleting (or nuvexporting and deleting) that
> 384th recording should permit it to load the full list (or at least go
> much further).

I tried deleting the last recording in the log, the one immediately
before it, and the next one in the sniffer output.  No go.  It still
died at exactly the same number of recordings.  It died at the same
point (i.e. after 348 recordings), altough #348 is now a different
recording.

>  -Are you using wired or wireless?

I test with wired.

>  -Can you flood ping to/from the MVP without error?

Yes.

>  -Have you tried a bandwidth test using the file system browser (its a
> "context" menu option), and if so, what numbers did you achieve?

I tried three times.  The middle result was 16.09Mbps.  The other two
results were 12.x Mbps and 17.77Mbps.

>  -Do you have any playback performance issue when using the file system
> browser?

No.

> -Take a look at the code (if you grok C) that is producing the error
> message and see what it is actually testing for.

I tried "make host".  The host dongle isn't having this problem -- I
can go to "watch recordings" and see a full list.  The same code used
to build an MVP dongle has this error.  So it seems like the problem
is more about resources and/or the MVP environment rather than an
actual code issue.

> -Try other versions of the dongle. (If you are running a recent MythTV
> version, your choices may be limited.)

I tried a number of versions on the mvpmc, as per earlier emails.  No
joy.

> -Try some of the other MythTV client functions, such as viewing the list
> of upcoming recordings, and see if they work.

Upcoming Recordings -- no, same error ("mythtv backend connection is
  not responding")

Live TV -- working.

Schedule Recordings -- no, same error ("mythtv backend connection is
  not responding")

Program finder -- allows browsing of show titles.  If I actually
  select a show to list episodes, same error ("mythtv backend
  connection is not responding")

mythtv utilities | previously recorded -- hangs.

mythtv utilities | delete recordings -- hangs.

> -Configure the database connection and try the database test (MythTV
> settings menu in mvpmc).

"All test successful".

>  -Tom

-- 
                           Mordechai T. Abzug
Linux red-sonja 2.6.31-23-generic #74-Ubuntu SMP Mon Feb 28 22:20:11 UTC 2011 
x86_64 GNU/Linux
There are 10 types of people in the world; those who understand binary and
  those who don't.

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to