Re: [mythtv-users] Long term stability?
Donavan Stanley wrote: On 11/8/05, *Robert Denier* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? I'd wager most people do. The PVR 350 is picky about it's PCI interface. It crashed no matter what slot I had it in when I was running an intel D815EEA2 motherboard. So I bought a new board, and now it crashes if I put it in the last slot, but the other two slots are fine. I now have 30+ day uptimes. It only goes down for extended power outages, kernel upgrades, etc... Bottom line: Try a different PCI slot. If that doesn't work, get a newer motherboard (not VIA though). If it still crashes, make sure you try all slots on the new board. If it still crashes then you're unlucky and you've got 2 incompatible boards. It's not the drivers fault. -- Jesse Guardiani Programmer/Sys Admin [EMAIL PROTECTED] ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On November 8, 2005 06:33 pm, Robert Denier wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... I run for many weeks at a time with no problems (except some IR blaster issues, see some of my threads). Actually, I don't recall having any mythtv stability problems since I swapped motherboards. I'm using prepackaged 0.18.1 debs. If people do, perhaps a few could give their 1) PVR hardware 3 Hauppauge Freestyles (OEM 250's) 2) Motherboard chipset SiS 745 (Aopen AK75 Motherboard)/ Duron 800 MHz 3) Kernel version 2.6.12.5 rolled my own. 4) IVTV version. ivtv 0.2.0 rc3k 5) Firmware version? 2.04.211 6) System Memory 256 MB and, well, anything else they think relevant to stability. I run Debian, if that helps. Also, I run with the side of my case open. Otherwise, my biggest advice is to stay far away from older VIA chipsets. When I changed from a VIA based board to a SiS based board, things got a lot better for me. Mark Actually, I wonder if there is a database anywhere of such things, or if such a thing would be useful. If nothing else, this might give someone a bit of guidance when putting together a system. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On 11/8/05, Robert Denier [EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonablyheavy use? I'd wager most people do. 1) PVR hardware 1x PVR 250 (master) 1x HDTV 3k (master) 1x PVR250 (slave) 2) Motherboard chipsetSome cheap Intel mobo (master) Chaintek 7NIF2 (slave) 3) Kernel version2.6.13 (master) 2.6.11.6 (slave) 4) IVTV version.version 0.3.7 (k) (master) version 0.2.0 (rc3a) (slave) 5) Firmware version?Whatever the reccomended version was for the driver. 6) System Memory512MB The only time my machines go down is when there's a power outage. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
Robert Denier wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... This system has been up for 16:37:40 up 44 days, 20:34, 1 user, load average: 0.23, 0.05, 0.02 Pretty much. With SVN as of about 2 or 3 weeks ago, my last nagging problem of getting a waiting for threads... message on my backend has disappeared and I don't have any issues I can think of. Kevin -- Looking for affordable webhosting? http://www.sitecity.net ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On 8-Nov-05, at 5:33 PM, Robert Denier wrote: I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... I observed some memory leaks in the ScheduledRecording class last spring but couldn't find the source. There was a fix in that area since then but I don't remember when. Post 0.18 for sure. Anyway, the first thing I'd look at is memory. A ps -F -C mythbackend in a hourly or daily cron job directed to some log file would confirm or eliminate this angle. - George ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Long term stability?
Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... If people do, perhaps a few could give their 1) PVR hardware 2) Motherboard chipset 3) Kernel version 4) IVTV version. 5) Firmware version? 6) System Memory I'm running 0.18.1 and my backend has been up for over 3 months solid. I use: -SuSE 9.3 with a 2.6.13 kernel -pcHDTV HD-3000 and PVR-150 SuSE doesn't seem all that popular in this crowd, but I think it does an excellent job with MythTV; hardly any tweaking needs to be done. For more details, check out http://www.dastrup.com/template_mythtv_specs.asp winmail.dat___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On 11/8/05, Robert Denier [EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... If people do, perhaps a few could give their 1) PVR hardware 2) Motherboard chipset 3) Kernel version 4) IVTV version. 5) Firmware version? 6) System Memory and, well, anything else they think relevant to stability. Here's all my relevent info. I believe the mobo is a MSI MicroATX with no AGP slot (the model number escapes me, but it's 2.5 years old at least). I'm running 512 MB of memory. I install using Jarod's guide. My uptime would be over 100 days if it weren't for a power outage. So far this has been the most stable build I've had since I've been using Myth. [EMAIL PROTECTED] ~]$ cat /etc/issue Fedora Core release 3 (Heidelberg) Kernel \r on an \m [EMAIL PROTECTED] ~]$ uname -r 2.6.10-1.760_FC3 [EMAIL PROTECTED] ~]$ /sbin/lspci 00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03) 00:02.0 VGA compatible controller: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) 00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82) 00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801DB (ICH4) IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02) 01:00.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) 01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) [EMAIL PROTECTED] ~]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 1 model name : Intel(R) Pentium(R) 4 CPU 1.70GHz stepping: 2 cpu MHz : 1700.762 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips: 3366.91 [EMAIL PROTECTED] ~]$ uptime 16:58:57 up 44 days, 23:08, 4 users, load average: 0.00, 0.00, 0.00 [EMAIL PROTECTED] ~]$ rpm -qa | grep ivtv perl-Video-ivtv-0.13-6.rhfc3.at ivtv-0.1.10-49.2_pre2_ck100zz.rhfc3.at ivtv-firmware-1.8a-4.at ivtv-firmware-dec-2.02.023-4.at ivtv-kmdl-2.6.10-1.760_FC3-0.1.10-49.2_pre2_ck100zz.rhfc3.at ivtv-firmware-enc-2.04.024-4.at [EMAIL PROTECTED] ~]$ free total used free sharedbuffers cached Mem:508076 370724 137352 0 26120 126184 -/+ buffers/cache: 218420 289656 Swap: 10522162401051976 Actually, I wonder if there is a database anywhere of such things, or if such a thing would be useful. If nothing else, this might give someone a bit of guidance when putting together a system. http://pvrhw.goldfish.org/tiki-pvrhwdb.php HTH, Josh ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tuesday 08 November 2005 17:51, James C. Dastrup wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... If people do, perhaps a few could give their 1) PVR hardware 2) Motherboard chipset 3) Kernel version 4) IVTV version. 5) Firmware version? 6) System Memory I'm running 0.18.1 and my backend has been up for over 3 months solid. I use: -SuSE 9.3 with a 2.6.13 kernel -pcHDTV HD-3000 and PVR-150 SuSE doesn't seem all that popular in this crowd, but I think it does an excellent job with MythTV; hardly any tweaking needs to be done. For more details, check out http://www.dastrup.com/template_mythtv_specs.asp sounds good for me, I'll be running debian with 2.6.13 a HD3000 and a PVR-150 as soon as my hardware gets here! Looks like the MythRoku is working out well as well, your blog answered a question I had about it regarding watching live TV! Steve ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... My uptime was around 81 days until I had to reboot because something went wrong with ivtv and it wasn't recording anymore. If people do, perhaps a few could give their 1) PVR hardware 1 PVR 250 2) Motherboard chipset VIA K8T800 Pro + VT8237R - AMD64 3200+ 3) Kernel version 2.6.9r14 4) IVTV version. 0.3.6f 5) Firmware version? 22037 (?) 6) System Memory 1Gb PC3200 I'm running Gentoo AMD64 with Myth 0.18.1-r2 It's been remarkably stable for me - I think the problem that happened this weekend was the first backend trouble I've had since I started running Myth back in March or so. Greg ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tue, 2005-11-08 at 17:33, Robert Denier wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... I have a master backend/frontend that has been up for 20 days now and a slave backend/frontend that was rebooted about 12 days ago when I swapped around the UPS systems. 18:39:49 up 20 days, 11:35, 3 users, load average: 1.07, 1.01, 0.93 18:41:51 up 12 days, 2:59, 3 users, load average: 0.08, 0.02, 0.01 If people do, perhaps a few could give their 1) PVR hardware In both systems I have a PVR-350 and PVR-250, total four capture cards. 2) Motherboard chipset Masterbackend: P5GD2 deluxe motherboard Slavebackend: ECS 760GX-M 3) Kernel version Masterbackend: FC3 2.6.10-1.760_FC3smp Slavebackend: FC4 2.6.12-1.1447_FC4 4) IVTV version. Masterbackend: ivtv-0.3.2d-67.rhfc3.at Slavebackend: ivtv-0.3.7k-96.rhfc4.at (I have been wanting to update ivtv but things are working) 5) Firmware version? ?? 6) System Memory Master: total used free sharedbuffers cached Mem: 20749241369224 705700 0 3384 281632 -/+ buffers/cache:1084208 990716 Swap: 2031608 52962026312 Slave: total used free sharedbuffers cached Mem: 19457721896416 49356 0 2608 1802288 -/+ buffers/cache: 915201854252 Swap: 2031608 10482030560 and, well, anything else they think relevant to stability. I have four SATA 300GB harddrives in the masterbackend system with a 1TB file system setup for /video which is where I put all the recordings. One issue that I noted early on with the masterbackend/frontend system, under heavy load it would have heat problems if the doors to the TV stand were closed. I put all my systems on UPSs since my power company likes to drop power on a semi regular basis. Most recordings are done using the two cards in the masterbackend but all four are used several times a week at the same time. Note that on the P5GD2 Deluxe motherboard it has a marvel chip set for the ethernet interface. To get this to work I had to download and build the driver, it is not natively supported by FC. At least not FC3. The ECS board worked with not problems, nic, sound, video. Make sure your cooling is good and have a power supply that is large enough to handle the drives you plan to install. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
Kevin Kuphal wrote: Robert Denier wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... This system has been up for 16:37:40 up 44 days, 20:34, 1 user, load average: 0.23, 0.05, 0.02 Pretty much. With SVN as of about 2 or 3 weeks ago, my last nagging problem of getting a waiting for threads... message on my backend has disappeared and I don't have any issues I can think of. Kevin Sorry, I'm running with: 2 BTTV Win-TV Go cards Motherboard is VIA chipset I believe Kernel is Redhat 9, 2.4.20-31_38 no IVTV/firmware 512MB RAM -- Looking for affordable webhosting? http://www.sitecity.net ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Long term stability?
Robert asked : Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... Yes (and the only thing that kills it is the pvr-350 locks up under fast-forward when also recording sometimes). Currently: 11:55pm up 7 days 2:35, 3 users, load average: 0.93, 0.77, 0.42 Used fairly heavily used (min 2 hours watched per day, about 3-4hours recorded per day) Not had any recording problems (touches wood franticly) AFAIR with the current setup. Uptime is only 7days atm cos I rebooted it the other week to nick the dvd drive. :-) If people do, perhaps a few could give their 1) PVR hardware PVR-350 (TV/X output) Nova-T 2) Motherboard chipset Pundit-R, dunno the chipset, 3GHz/800MHz P4 (OTT for what I'm using it for, considering downgrading to run cooler) 3) Kernel version 2.6.11-rc2-bk3-20050125153357-default (Kernel of the day, take a guess when I built it ;-) ) Under SuSE 9.1, that kernel was needed for the dvb support. 4) IVTV version. 0.3.8 5) Firmware version? ivtv-fw-dec.bin - Version 2.02.023 ivtv-fw-enc.bin - Version 2.04.211 6) System Memory 512Mb HTH David ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tue, Nov 08, 2005 at 05:49:48PM -0600, Greg Mitchell wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... My uptime was around 81 days until I had to reboot because something went wrong with ivtv and it wasn't recording anymore. Everyone seems to be posting uptime stats, but I don't really see them as relevant to the original question. He asked whether people have been able to keep myth running with no... cron jobs and mentions that he has to occasionally do a /etc/init.d/mythbackend restart. Cron jobs and running restarts out of init.d only work on systems that are up and running, so it seems clear that he's *not* asking about hardware or system stability, but rather the mythbackend daemon specifically. If your mythbackend started when you booted the system and has been running continuously without having to be restarted since then, please say so. If it hasn't, then your uptime is irrelevant to the question. As for myself, my frontend/backend combined system currently has an uptime of 35 day(s), 11:45:18, with the last downtime caused by a power outage. However, I usually have to restart mythbackend once or twice a week after it decides to stop talking to the database (it continues to run, but any function which requires access to the database hangs and eventually times out, plus any recording in progress immediately stops). These problems appear to be caused by programs being deleted (either manual deletion or the deletion of the original MPEG2 .nuv when transcoding is complete) while another database update is in progress, although I haven't tried too hard to verify this. I suspect that's the sort of situation (and the type of stability) that the original poster was asking about. And if anyone knows a good way to detect automatically when this happens so that I can set up a cron job to notice it and restart mythbackend, I'd love to hear about it... -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On 11/9/05, Robert Denier [EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... If people do, perhaps a few could give their 1) PVR hardware 2) Motherboard chipset SHUTTLE SN95G5 BAREBONE PC Athlon 64 3000+ 512 MB RAM Albatron FX5200EP GeForceFX5200 DVICO Fusion Lite HDTV Card 3) Kernel version FC 3 2.6.10-1.770_14.rhfc3.at mythtv-0.18.1-113.rhfc3.at and, well, anything else they think relevant to stability. 11:33:50 up 32 days, 51 min I had to reboot due to my USB network adaptor stopping, had uptime of about 3 months before that. No idea why it stopped but a reboot got it going again. Rebooting probably wasn't necessary, but with limited linux knowledge and no internet on the box to trouble shoot it seemed the easiest solution. Btw, I wouldn't recommend a USB network adaptor, absolute pain to get going. I have occasional frontend crashes (maybe once a month) and just need to restart mythfrontend to recover. They're always when moving about between menus, and thus it's not really a problem to just restart. Backend is rock solid. Ben ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tue, 2005-11-08 at 19:44, Dave Sherohman wrote: Everyone seems to be posting uptime stats, but I don't really see them as relevant to the original question. He asked whether people have been able to keep myth running with no... cron jobs and mentions that he has to occasionally do a /etc/init.d/mythbackend restart. Cron jobs and running restarts out of init.d only work on systems that are up and running, so it seems clear that he's *not* asking about hardware or system stability, but rather the mythbackend daemon specifically. If your mythbackend started when you booted the system and has been running continuously without having to be restarted since then, please say so. If it hasn't, then your uptime is irrelevant to the question. The uptimes I posted was continues running of mythbackend and frontend. The master is a headless box only connected to the TV via the PVR-350. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tue, Nov 08, 2005 at 06:44:15PM -0600, Dave Sherohman wrote: On Tue, Nov 08, 2005 at 05:49:48PM -0600, Greg Mitchell wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... My uptime was around 81 days until I had to reboot because something went wrong with ivtv and it wasn't recording anymore. Everyone seems to be posting uptime stats, but I don't really see them as relevant to the original question. He asked whether people have been able to keep myth running with no... cron jobs and mentions that he has to occasionally do a /etc/init.d/mythbackend restart. Cron jobs and running restarts out of init.d only work on systems that are up and running, so it seems clear that he's *not* asking about hardware or system stability, but rather the mythbackend daemon specifically. If your mythbackend started when you booted the system and has been running continuously without having to be restarted since then, please say so. If it hasn't, then your uptime is irrelevant to the question. I've never had to restart mythbackend unless I'm playing with the ivtv drivers (ivtv-0.4.0-98.rhfc3.at, mythtv-suite-0.18.1-55.at, PVR 500). I only reboot the machine when fedora issues a kernel update (2.6.12-1.1381_FC3, currently - usually a 30-60 day uptime per boot). The backend seems perfectly stable to me, but are most folks using SVN nowadays? As for myself, my frontend/backend combined system currently has an uptime of 35 day(s), 11:45:18, with the last downtime caused by a power outage. However, I usually have to restart mythbackend once or twice a week after it decides to stop talking to the database (it continues to run, but any function which requires access to the database hangs and eventually times out, plus any recording in progress immediately stops). These problems appear to be caused by programs being deleted (either manual deletion or the deletion of the original MPEG2 .nuv when transcoding is complete) while another database update is in progress, although I haven't tried too hard to verify this. I suspect that's the sort of situation (and the type of stability) that the original poster was asking about. I had a similar problem once when I forgot to cold boot my machine after changing ivtv firmwares. With the PVRs, I always have trouble if I just shutdown -r now when switching firmware, and its exactly like the problem you describe. Why it manifests itself in this way, I have no idea... And if anyone knows a good way to detect automatically when this happens so that I can set up a cron job to notice it and restart mythbackend, I'd love to hear about it... Although not what it was intentionally designed for, could mythwelcome/shutdown (currently in SVN) be used for this: http://cvs.mythtv.org/trac/changeset/7571 ? HTH, Tim -- Morals? I eat communism and $h!t America, brother. --Seanbaby ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
On Tuesday 08 November 2005 05:33 pm, Robert Denier wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... Mine's been up for several months, with only an occasional frontend crash, and it's working near 100% most of the time. Three tuners, small hard drive, everything gets transcoded and commercial flagged from Mpeg2 to Mpeg4. If people do, perhaps a few could give their 1) PVR hardware AMD 2500, 512MB, 120G drive, GOOD power supply 2) Motherboard chipset VIA KT400A 3) Kernel version Knoppmyth R5Asomething. 0.18.1 myth build. 4) IVTV version. Fairly old one. 5) Firmware version? Who knows. 6) System Memory 512MB ram, good quality. As with all things computer, give it good clean power, keep it cool, and you should get rid of lots of bugs... ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
--- Robert Denier [EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... Uptime 23 days, frontend/backend, pretty decent usage. I *have* had to restart mythbackend a couple of times, both were caused when trying to channel-flip in Live TV with my Matrox Marvel card as the tuner (That's seems to be hinkey in live tv, but good for recording). Otherwise, it's been good. 1) PVR-250 and Matrox Marvel G400-TV 2) Epox motherboard, Nforce2 chipset 3) Kernel 2.6.13.1 (from kernel.org) 4) IVTV 4.0ish from SVN right when 4.0 was released. Marvel driver from CVS at Sourceforge, right after change to make it work with kernel 2.6.13. 5) No idea on firmware. Whatever ATRPMs had. 6) 512MB RAM So again, the Marvel is a bit flakey when trying to tune a channel, but the PVR has been a rock. I need to figure a way to sync my hardware clock to the system clock without rebooting :) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Long term stability?
Dedicated backend running 0.18.1 has been up for 70 days. System was rebooted then to upgrade kernel and go to 0.18.1 from 0.18. Since the upgrade to 0.18 I can't remember my backend crashing ever. All recording storage is nfs mounted from a seperate server. Database is on a separate server as well. System is running FC3. 1) PVR hardware 4 x PVR-250 2) Motherboard chipset ECS K7S5A Motherboard (SIS 735 chipset) with AMD 1700 XP 3) Kernel version from ATRPMS - 2.6.10-1.770_14.rhfc3.at 4) IVTV version. from ATRPMS - ivtv-0.2.0-68_rc3j.rhfc3.at 5) Firmware version? from ATRPMS - ivtv-firmware-1.8a-4.at 6) System Memory 512MB On 11/8/05, Mark Kundinger [EMAIL PROTECTED] wrote: --- Robert Denier [EMAIL PROTECTED] wrote: Does anyone have a backend that runs for a week or more under reasonably heavy use? By run, I mean with no manual intervention or cron jobs resetting things/etc. I still have to occasionally do a /etc/init.d/mythbackend restart although I'm not quite sure why... Uptime 23 days, frontend/backend, pretty decent usage. I *have* had to restart mythbackend a couple of times, both were caused when trying to channel-flip in Live TV with my Matrox Marvel card as the tuner (That's seems to be hinkey in live tv, but good for recording). Otherwise, it's been good. 1) PVR-250 and Matrox Marvel G400-TV 2) Epox motherboard, Nforce2 chipset 3) Kernel 2.6.13.1 (from kernel.org) 4) IVTV 4.0ish from SVN right when 4.0 was released. Marvel driver from CVS at Sourceforge, right after change to make it work with kernel 2.6.13. 5) No idea on firmware. Whatever ATRPMs had. 6) 512MB RAM So again, the Marvel is a bit flakey when trying to tune a channel, but the PVR has been a rock. I need to figure a way to sync my hardware clock to the system clock without rebooting :) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Long term stability?
I need to figure a way to sync my hardware clock to the system clock without rebooting :) man hwclock ? --cro ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
