Hi Brandon,
It was a fresh install from the appliance image yes, so was a bit puzzled as to why it happened too
Sent: Friday, October 04, 2019 at 10:21 PM
From: "Brandon" <bran...@subliminalradio.net>
To: "David Henderson" <david.hender...@gmx.co.uk>
Cc: "Robert Jeffares" <jeffares.rob...@gmail.com>, "Rivendell Dev List" <rivendell-dev@lists.rivendellaudio.org>
Subject: Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance
From: "Brandon" <bran...@subliminalradio.net>
To: "David Henderson" <david.hender...@gmx.co.uk>
Cc: "Robert Jeffares" <jeffares.rob...@gmail.com>, "Rivendell Dev List" <rivendell-dev@lists.rivendellaudio.org>
Subject: Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance
Hi David,
Wonder what went wrong... I didn't have any issues after updating.
Were these fresh installs from the appliance, or upgrades from an earlier beta?
Brandon
On Thu, Oct 3, 2019 at 10:46 PM David Henderson <david.hender...@gmx.co.uk> wrote:
_______________________________________________Hi Robert,I tried the yum update command - it downloaded a whole load of stuff for the operating system but nothing for Rivendell. After the update, Rivendell wouldn't run - error about being "unable to start the daemons".Sent: Thursday, October 03, 2019 at 6:56 PM
From: "Robert Jeffares" <jeffares.rob...@gmail.com>
To: rivendell-dev@lists.rivendellaudio.org
Subject: Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 applianceHi Brandon,
do a # yum update -y [as root] and the metadata wildcards should then work.
as will the logging bit.
The dropbox code was broken but has been fixed.
I run update a couple of times after install as a matter of course.
regards
Robert
On 10/3/19 8:07 PM, Brandon wrote:_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-devHello everyone!Not sure if I discovered a bug in v3.1.0... Or a glitch specific to our install at UCLA Radio in LA.Just did a fresh Server/Client Riv 3.1.0 install on CentOS 7 with the appliance script. Converted the DB from previous V2.10.3 install. Everything seemed to go without a hitch.The problem: Dropbox is ignoring files and not reporting any errors in the error log. When I run rdimport from the command line, it threw an error (which I don't recall at the moment -- but Googling made it sound like an Apache error) -- but this seems unlikely since we installed from the appliance script.After experimenting with different Dropbox configs all night, removing %i from the Dropbox Metadata Pattern field fixed the issue and Dropbox resumes importing files. Using %t_%a metadata pattern also fails to import anything.Is anyone else experiencing Dropbox import issues when specifying metadata patterns?We can live without it, but %i gives us the cleanest cut titles without "imported from..." in the titles, although doesn't fix cart titles. Worked as expected in 2.10.3.Thank you!!--_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
--
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
