Let's hope! However check apache log after you import music: 1) /var/log/apache2/access.log 2) /var/log/apache2/error.log
Alessio 2014-11-20 10:15 GMT+01:00 Geoff Barkman <[email protected]>: > Hi Alessio > I found the conf file that you mentioned... I added another 0 to the > end making it 3000... will test out to see if it works. > Its just so weird... my Lubuntu set up works good as gold. Only > difference is I can see is the size of his database (20 thousand)... > double the number of songs... whereas mine only has 10 thousand.... > and mine is a database that is over 7 years old.... and its migrated > up through versions up to its present v 2.9.3. > Whereas his database is only 6 months old... and I think started at > about v 2.8.1 and migrated upto the prersent v 2.9.3 > Its so strange.... Hopefully the apache fix will do it. > Many thanks > Geoff Barkman > > On 11/20/14, Alessio Elmi <[email protected]> wrote: >> Hi, >> not sure if it solves the problem.. We don't use dropboxes, our >> problem was that long tracks (like pre-recorded entire shows) give >> error when imported. Anyway track is present in terms of wav file and >> database audio length. >> So I checked the log but I will try to tweak on that the next days. >> Anyway you can experiment a bit on the field by tweaking Apache >> configuration file. In case you constate that it fix that behaviour >> please share that with us. >> We use Debian 7 (so Apache is 2.2, while yours probably is 2.4) so >> there may be difference in behaviour. >> Anyway you can find Apache config file in >> /etc/apache2/apache2.conf and there is a timeout value, which is 300 >> by default I think. >> More info here: >> http://httpd.apache.org/docs/current/mod/mod_reqtimeout.html (for >> current apache version). >> >> Alessio >> >> 2014-11-20 1:10 GMT+01:00 Geoff Barkman <[email protected]>: >>> Hi Alessio and Wayne >>> How do you increase the apache timeout? I take it is one of the conf >>> files? >>> I did notice when running "top" the rdxport.cgi process was using 25% >>> of the cpu and importlog.txt has messages like "Database connection >>> failed: select FILE_DATETIME from DROPBOX_PATHS" >>> >>> Many Thanks >>> Geoff >>> >>> On 11/20/14, Alessio Elmi <[email protected]> wrote: >>>> Nice tip Wayne thank you! We experienced the same problem and checking >>>> in the Apache log: >>>> [Mon Nov 17 10:52:15 2014] [error] [client 127.0.0.1] Script timed out >>>> before returning headers: rdxport.cgi >>>> Thank you! >>>> >>>> 2014-11-19 15:24 GMT+01:00 Wayne Merricks >>>> <[email protected]>: >>>>> Hi, >>>>> >>>>> Just a thought are you running into the apache script time out limit? >>>>> I'd >>>>> imagine a 52minute mp3 would take some time to import and apache's >>>>> default >>>>> time outs are quite conservative by default. >>>>> >>>>> Wayne Merricks >>>>> The Voice Asia >>>>> >>>>> >>>>> On 19/11/14 07:34, Geoff Barkman wrote: >>>>>> >>>>>> I've set up Rivendell dropboxes for my friends Radio Station. >>>>>> Running Lubuntu 14.04 Rivendell v 2.9.3 >>>>>> >>>>>> His machine is also identical specs to mine. Apart from having more >>>>>> ram and 20 thousand songs in the database. My system has about half of >>>>>> that. >>>>>> >>>>>> I've made shared folders that his production machine saves files to >>>>>> (using samba). These shared folders are dropboxs for a series of carts >>>>>> in his system. >>>>>> >>>>>> The problem we are having with his system is Files not importing... >>>>>> deleting the existing audio and leaving an empty cart. We then have to >>>>>> manually import which sometimes works. We get an Audio Error OK... but >>>>>> the file has imported. >>>>>> >>>>>> The Audio carts are about 52 minutes long (128k mp3) ... should I make >>>>>> them half that length? >>>>>> >>>>>> Any thoughts >>>>>> Geoff Barkman >>>>>> _______________________________________________ >>>>>> Rivendell-dev mailing list >>>>>> [email protected] >>>>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Rivendell-dev mailing list >>>>> [email protected] >>>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>>> >> _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
