Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-07 Thread David Henderson 
Another error I have discovered on CentOS7 is that I can't even import audio onto a cut - I get the message as shown in the attached screenshot..
 

 

 
 

Sent: Sunday, October 06, 2019 at 8:45 PM
From: "David Henderson" 
To: rivendell-dev@lists.rivendellaudio.org
Subject: Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance


This doesn't work for me... Running v2.19.3 on CentOS7.. Worked fine on CentOS6...
--
Sent from my Android phone with GMX Mail. Please excuse my brevity.

On 04/10/2019, 17:29 Fred Gleason  wrote:
On Oct 3, 2019, at 03:07, Brandon <bran...@subliminalradio.net> wrote:

 



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?





Known issue, fixed in Git ‘master’. It will appear in the next regular release.

 

In the meantime, a workaround is to end the metadata pattern with a delimiter —e.g. ‘%t_%a.’ instead of ‘%t_%a’.

 

Cheers!

 

 


|-|

| Frederick F. Gleason, Jr. |             Chief Developer             |

|                           |             Paravel Systems             |

|-|

|         A room without books is like a body without a soul.         |

|                                                                     |

|                                                         -- Cicero   |

|-|


 
___ 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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-07 Thread Rob Landry 


I don't generally use the Rivendell dropbox feature; instead, I monitor 
dropboxes with a Perl script that invokes rdimport.


I do this for two reasons:

1) The script is set up to move any file that cannot be imported (for 
instance, an Adobe Audition .pk file) into a 'bad' folder; and


2) The script maintains a detailed log of every file that gets imported, 
so when I get a call from someone who says the news that just ran was 
yesterday's news, I can look at the log and establish when the file was 
imported.



Rob

--
Сквозь грозы сияло нам солнце свободы
И Linus великий нам путь озарил;
Нас вырастил Stallman на верность народу,
На труд и на подвиги нас вдохновил.___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-06 Thread David Henderson 
This doesn't work for me... Running v2.19.3 on CentOS7.. Worked fine on CentOS6... 
-- 
Sent from my Android phone with GMX Mail. Please excuse my brevity.On 04/10/2019, 17:29 Fred Gleason  wrote:
On Oct 3, 2019, at 03:07, Brandon  wrote: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?Known issue, fixed in Git ‘master’. It will appear in the next regular release.In the meantime, a workaround is to end the metadata pattern with a delimiter —e.g. ‘%t_%a.’ instead of ‘%t_%a’.Cheers!|-|| Frederick F. Gleason, Jr. |             Chief Developer             ||                           |             Paravel Systems             ||-||         A room without books is like a body without a soul.         ||                                                                     ||                                                         -- Cicero   ||-|___
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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-06 Thread David Henderson 

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" 
To: "David Henderson" 
Cc: "Robert Jeffares" , "Rivendell Dev List" 
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 appliance



Hi 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:


Hello 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!!

 


-- 














Brandon Anjeleno

Subliminal Radio

(213) 839-7667















 

 

___
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

 

 
--














Brandon Anjeleno

Subliminal Radio

(213) 839-7667

















___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-05 Thread Brandon 
Hi Mike,

Yes, I read Fred's response after Robert's, but caught the context.

Thank you,
Brandon






On Sat, Oct 5, 2019, 9:28 AM Mike Carroll  wrote:

> Hi, Brandon.  The fix isn't released into the packaging stream yet, so yum
> doesn't know anything about it.  See Fred's sentence:  "Known issue, fixed
> in Git ‘master’. >>It will appear in the next regular release.<<"
>
> If you're a site that builds Rivendell itself, rather than using the
> pre-packaged system, you would need to pull the latest Rivendell source
> updates from the github repository and do a mass build. Otherwise you'll
> need to wait until Fred & Co. release the next 3.x package.
>
> Mike
>
> On Fri, Oct 4, 2019 at 11:01 PM Brandon 
> wrote:
>
>> Hi Robert,
>>
>> So last night, we ran yum update -y as root on the server and there were
>> no updates to apply... Removing the %i wildcard on the server also didn't
>> fix the issue (even though it worked on my virtualbox Rivendell test
>> server/client setup).
>>
>> We installed the client last night and ran yum update -y as root. The
>> dropboxes still fail to import with metadata wildcards. However, dropboxes
>> on the client successfully import to the server without the metadata
>> wildcards.
>>
>> Thanks for the help!!
>>
>> On Thu, Oct 3, 2019 at 10:56 AM Robert Jeffares <
>> jeffares.rob...@gmail.com> wrote:
>>
>>> Hi 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:
>>>
>>> Hello 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!!
>>>
>>> --
>>> Brandon Anjeleno
>>> Subliminal Radio 
>>> (213) 839-7667 
>>>
>>> ___
>>> Rivendell-dev mailing 
>>> listRivendell-dev@lists.rivendellaudio.orghttp://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>>
>>> ___
>>> Rivendell-dev mailing list
>>> Rivendell-dev@lists.rivendellaudio.org
>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>>
>>
>>
>> --
>> Brandon Anjeleno
>> Subliminal Radio 
>> (213) 839-7667 
>> ___
>> 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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-05 Thread Mike Carroll 
Hi, Brandon.  The fix isn't released into the packaging stream yet, so yum
doesn't know anything about it.  See Fred's sentence:  "Known issue, fixed
in Git ‘master’. >>It will appear in the next regular release.<<"

If you're a site that builds Rivendell itself, rather than using the
pre-packaged system, you would need to pull the latest Rivendell source
updates from the github repository and do a mass build. Otherwise you'll
need to wait until Fred & Co. release the next 3.x package.

Mike

On Fri, Oct 4, 2019 at 11:01 PM Brandon  wrote:

> Hi Robert,
>
> So last night, we ran yum update -y as root on the server and there were
> no updates to apply... Removing the %i wildcard on the server also didn't
> fix the issue (even though it worked on my virtualbox Rivendell test
> server/client setup).
>
> We installed the client last night and ran yum update -y as root. The
> dropboxes still fail to import with metadata wildcards. However, dropboxes
> on the client successfully import to the server without the metadata
> wildcards.
>
> Thanks for the help!!
>
> On Thu, Oct 3, 2019 at 10:56 AM Robert Jeffares 
> wrote:
>
>> Hi 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:
>>
>> Hello 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!!
>>
>> --
>> Brandon Anjeleno
>> Subliminal Radio 
>> (213) 839-7667 
>>
>> ___
>> Rivendell-dev mailing 
>> listRivendell-dev@lists.rivendellaudio.orghttp://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>
>> ___
>> Rivendell-dev mailing list
>> Rivendell-dev@lists.rivendellaudio.org
>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>
>
>
> --
> Brandon Anjeleno
> Subliminal Radio 
> (213) 839-7667 
> ___
> 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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-04 Thread Brandon 
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 
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" 
> *To:* rivendell-dev@lists.rivendellaudio.org
> *Subject:* Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0
> appliance
>
> Hi 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:
>
> Hello 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!!
>
> --
> Brandon Anjeleno
> Subliminal Radio <http://subliminalradio.net/popup-player>
> (213) 839-7667
>
>
> ___
> Rivendell-dev mailing 
> listRivendell-dev@lists.rivendellaudio.orghttp://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
>


-- 
Brandon Anjeleno
Subliminal Radio <http://subliminalradio.net/popup-player>
(213) 839-7667 
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-04 Thread Brandon 
Fred,

Thank you for the update and workaround!

I probably won't get back over to UCLA until next week, but I'll try the
delimiter the next time I go in.

Appreciate all that you do!! Rivendell is an incredible product. Better
than all of the proprietary systems combined :)

Brandon

On Fri, Oct 4, 2019 at 9:29 AM Fred Gleason 
wrote:

> On Oct 3, 2019, at 03:07, Brandon  wrote:
>
> 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?
>
>
> Known issue, fixed in Git ‘master’. It will appear in the next regular
> release.
>
> In the meantime, a workaround is to end the metadata pattern with a
> delimiter —e.g. ‘%t_%a.’ instead of ‘%t_%a’.
>
> Cheers!
>
>
> |-|
> | Frederick F. Gleason, Jr. | Chief Developer |
> |   | Paravel Systems |
> |-|
> | A room without books is like a body without a soul. |
> | |
> | -- Cicero   |
> |-|
>
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>


-- 
Brandon Anjeleno
Subliminal Radio 
(213) 839-7667 
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-04 Thread Brandon 
Hi Robert,

So last night, we ran yum update -y as root on the server and there were no
updates to apply... Removing the %i wildcard on the server also didn't fix
the issue (even though it worked on my virtualbox Rivendell test
server/client setup).

We installed the client last night and ran yum update -y as root. The
dropboxes still fail to import with metadata wildcards. However, dropboxes
on the client successfully import to the server without the metadata
wildcards.

Thanks for the help!!

On Thu, Oct 3, 2019 at 10:56 AM Robert Jeffares 
wrote:

> Hi 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:
>
> Hello 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!!
>
> --
> Brandon Anjeleno
> Subliminal Radio 
> (213) 839-7667 
>
> ___
> Rivendell-dev mailing 
> listRivendell-dev@lists.rivendellaudio.orghttp://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>


-- 
Brandon Anjeleno
Subliminal Radio 
(213) 839-7667 
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-04 Thread Fred Gleason 
On Oct 3, 2019, at 03:07, Brandon  wrote:

> 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?

Known issue, fixed in Git ‘master’. It will appear in the next regular release.

In the meantime, a workaround is to end the metadata pattern with a delimiter 
—e.g. ‘%t_%a.’ instead of ‘%t_%a’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-03 Thread David Henderson 
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" 
To: rivendell-dev@lists.rivendellaudio.org
Subject: Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance



Hi 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:


Hello 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!!

 


-- 














Brandon Anjeleno

Subliminal Radio

(213) 839-7667















 

 

___
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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-03 Thread Robert Jeffares 

Hi 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:

Hello 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!!

--
Brandon Anjeleno
Subliminal Radio 
(213) 839-7667 

___
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

Re: [RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-03 Thread David Henderson 
I had the same issue. Ended up having to go back to CentOS6 on the server.
-- 
Sent from my Android phone with GMX Mail. Please excuse my brevity.On 03/10/2019, 08:07 Brandon  wrote:
Hello 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!!-- Brandon AnjelenoSubliminal Radio(213) 839-7667
___
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

[RDD] Broken Rivendell Dropboxes on Rivendell v 3.1.0 appliance

2019-10-03 Thread Brandon 
Hello 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!!

-- 
Brandon Anjeleno
Subliminal Radio 
(213) 839-7667 
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev