I have searched the forums and Google and have not found the solution. My myth web is very slow. It takes about 20s to go from one section to another but it dos work.
In my mythbackend log file it just gives me this error.

2005-08-02 19:39:08.557 unknown socket
2005-08-02 19:39:20.361 unknown socket
2005-08-02 19:39:40.453 unknown socket
2005-08-02 19:39:47.031 unknown socket
2005-08-02 19:40:07.083 unknown socket
2005-08-02 19:40:28.143 unknown socket
2005-08-02 19:41:58.309 unknown socket

I am using R5A16. In the initial setup screen when you type myth-setup I have set both ip as the actual ip of my mythtv box. I have also tried with the loop back ip with no change in results. The only suggested solution I have seen is updating the firmware on your home router. My router is up to date. I also hade the same result when the mythtv box was at my office.

Everything ells seems to work ok.

Sorry that last post was by me. Loged in with bugmenot by mistake.

How does Apache perfrom otherwise? I taken it MySQL, Apache and the backend are all on the same system? How is network perform between the backend and your other system?

_________________
cesman

When the source is open, the possibilities are endless!

Believe it or not it is all on the same box. Apache seems to work just fine as aviManager works very fast. It isn’t a network problem per say as samba is blazing fast.

One thing of note when the backend was off the web page for mythweb was lightning fast. Of course it didn’t work as the backend was down. When I brought the backend back up it went very slow again. I assume it has to do with apache/mysql’s communication with mythbackend.

Hi,
I don't mean to be a pain however, I find the speed of the web pages is dependant on several variables. Version of knoppmyth (I see the R5A16, good choice), processor speed, memory, number of recordings, size of your listings, record / play in progress, etc.

To look at a list of 3 recorded programs will appear much quicker than a list of 103 recordings. It has to build the thumb nails first. I haven't actually "timed" the events but it is obvious.

Maybe this helps somewhat.

I think I have seen the socket error when the /.qt wasn't available, not 100% sure but it doesn't cost anything to make it.
Mike

Thanks for the help thus fare. You are are helping me eliminate a few things.
My myth TV box specks are.
1.1 GHz processor
256 ram
128 mb gforce 5200
Pvr 150
DVD
100mb LAN connection.
160gb HD
I currently have no recordings yet as I just set up the box and have to use an ir blaster to change channels that I have not built yet. All I have is about 30g of moves and a few games pictures and music.

I do recall seeing an error with the /.qt I will look into that but I think I corrected it.

what part is slow? even my 3.0G PIV is fairly slow listing channels, but I use digital cable and broadcast hdtv so that's around 400 channels. that it has to build the data for.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I don’t mean to be an ass but read my first post. "Mythweb is slow".

I don't mean to be an ass, but mythweb has 4 or 5 parts/pages

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Ok so we are both asses. Lol

Every part is equally slow. It takes 20 to 30 sec to bring up any part. Whatever it is seems to be happening across the board. My assumption is it has something to do with it connecting to the backend because of the socket errors. It looks like it tries and tries then finely gets through. Any ideas?

Heir is a clip of a tcpdump when i access mythweb. The ip of my myth bos is 192.168.44.99. Th ip on the computer accesing it is 192.168.44.102 and the router is 192.168.44.1.

root@mythtv:~# tcpdump -a -vi eth0 not port 22
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
22:40:30.230724 IP (tos 0x0, ttl 64, id 635, offset 0, flags [DF], proto: UDP (17), length: 241) mythtv.netbios-dgm > 192.168.44.255.netbios-dgm: NBT UDP PACKET(138)
22:40:30.416149 IP (tos 0x0, ttl 64, id 636, offset 0, flags [DF], proto: UDP (17), length: 235) mythtv.netbios-dgm > 192.168.44.255.netbios-dgm: NBT UDP PACKET(138)
22:40:30.303215 arp who-has 192.168.44.1 tell mythtv
22:40:30.303572 arp reply 192.168.44.1 is-at 00:40:05:30:59:7d (oui Unknown)
22:40:30.303597 IP (tos 0x0, ttl 64, id 6336, offset 0, flags [DF], proto: UDP (17), length: 73) mythtv.32915 > 192.168.44.1.domain: 6366+ PTR? 255.44.168.192.in-addr.arpa. (45)
22:40:30.415499 IP (tos 0x0, ttl 247, id 8465, offset 0, flags [DF], proto: UDP (17), length: 150) 192.168.44.1.domain > mythtv.32915: 6366 NXDomain 0/1/0 (122)
22:40:30.416344 IP (tos 0x0, ttl 64, id 6450, offset 0, flags [DF], proto: UDP (17), length: 71) mythtv.32915 > 192.168.44.1.domain: 6367+ PTR? 1.44.168.192.in-addr.arpa. (43)
22:40:30.458824 IP (tos 0x0, ttl 248, id 47369, offset 0, flags [DF], proto: UDP (17), length: 148) 192.168.44.1.domain > mythtv.32915: 6367 NXDomain 0/1/0 (120)
22:40:33.533359 IP (tos 0x0, ttl 127, id 1449, offset 0, flags [none], proto: UDP (17), length: 281) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 253
22:40:33.533806 IP (tos 0x0, ttl 64, id 9568, offset 0, flags [DF], proto: UDP (17), length: 74) mythtv.32915 > 192.168.44.1.domain: 6368+ PTR? 250.255.255.239.in-addr.arpa. (46)
22:40:33.534030 IP (tos 0x0, ttl 127, id 1450, offset 0, flags [none], proto: UDP (17), length: 299) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 271
22:40:33.534694 IP (tos 0x0, ttl 127, id 1451, offset 0, flags [none], proto: UDP (17), length: 353) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 325
22:40:33.535768 IP (tos 0x0, ttl 127, id 1452, offset 0, flags [none], proto: UDP (17), length: 345) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 317
22:40:33.537052 IP (tos 0x0, ttl 127, id 1453, offset 0, flags [none], proto: UDP (17), length: 275) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 247
22:40:33.537700 IP (tos 0x0, ttl 127, id 1454, offset 0, flags [none], proto: UDP (17), length: 317) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 289
22:40:33.538795 IP (tos 0x0, ttl 127, id 1455, offset 0, flags [none], proto: UDP (17), length: 349) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 321
22:40:33.540135 IP (tos 0x0, ttl 127, id 1456, offset 0, flags [none], proto: UDP (17), length: 295) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 267
22:40:33.540798 IP (tos 0x0, ttl 127, id 1457, offset 0, flags [none], proto: UDP (17), length: 347) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 319
22:40:33.541858 IP (tos 0x0, ttl 127, id 1458, offset 0, flags [none], proto: UDP (17), length: 341) 192.168.44.1.1900 > 239.255.255.250.1900: UDP, length 313

Hi,
I never really timed the various web page delivery cycles however now that the discussion has come up with real estimated clock times, I would venture a guess and say that it is probably normal because of the priority being the main backend duties. My 600 mhz and 1.3 ghz seem to render in about the same amount time. My 266 mhz takes considerably longer

A few days ago I manually scheduled a few shows for recording, and then went back to make some changes. It was quite a lengthly process.

Maybe we can have some official clarification some time as to what is to be considered "normal" time windows? Personnally, I am satisfied as it works well, and besides, I don't move that fast either any more.

Good question!
Mike

The reason I don’t think it should be this slow is because a friend of mine who has mythtv on gentoo on a computer with the same specs takes one or two secedes to bring up a page vs my 30+.

well I would say that 30 sec is excessive on decent hardware. my 3g does the channel list is about 10 sec the first time I go in slightly less if I go back quickly, and recorded programs run in maybe 5 sec the first time (I only have about 6 recordings on this box) and about 1 to 2 seconds if I go back to it. none of these are exact they are just 1 Mississippi type counts, and are probably a bit high actually.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I'm using R5A22 and I also see some pretty slow MythWeb page loads for program_listing.php. My browser is Firefox 1.5rc1. I sometimes also get a message about a long-running script on the page.

When I look at the same page with the latest version of IE, it seems to load noticeably faster.