Thanks, but that didn't help, same problem. tried it as rivendell, and 
root (it was root)

Nathaniel C. Steele
Assistant Chief Engineer/Technical Director
WTRM-FM / TheCrossFM


On 11/28/2011 5:01 PM, [email protected] wrote:
> Hi,
>
> I've run into the issue where rdlibrary can't see the audio wave form info.  
> For me it turned out to be a permissions
> thing on rdxport.cgi
>
> On the machine running Apache (or if you have Apache running separately on 
> each machine) double check your permissions
> on rdxort.cgi
>
> It should be mode 4755 (chmod 4755 rdxport.cgi) and according to the wiki 
> owned by the Rivendell system user and group.
> However I found that on one of my machines I had to leave the ownership with 
> root:root for it to work, but it did need
> me to do a  chmod 4755
>
> For me it's dumped that file into /var/www/rd-bin/ however it could be any 
> number of other locations on your system.
>
> Of course if you change the permissions on that file I recommend restarting 
> Apache.
>
> Hope this helps.
>
>
>
>> I'll try that. I also tried mounting directly tothe NAS from the prod
>> room at someones suggestion, the NAS has two eth interfaces also so i
>> put the other on the 10.100.x.x network. I could mount it, but I still
>> have import issues. I fear I have something really screwed up on the
>> server now. the error is something about unsupported audio parameters. I
>> also was able to play carts in rdlibrary, but when I try to edit markers
>> It cant draw the waveform, though the cut will play in the editor with
>> no waveform drawn. hm... maybe I should check that apache started back
>> up after the previous reboot....I'll let you know.
>>
>> Thanks for the suggestions, and your patience...
>>
>>
>> Nathaniel C. Steele
>> Assistant Chief Engineer/Technical Director
>> WTRM-FM / TheCrossFM
>>
>>
>> On 11/28/2011 2:53 PM, Cowboy wrote:
>>> On Monday 28 November 2011 12:02:02 pm Nathan Steele wrote:
>>>> Unmounting the NAS allowed the production room to mount the old var snd.
>>>> permissions looked ok between the two but to make sure is tried to set
>>>> the new var/snd to rivendell rivendell (like the old, except I
>>>> accidentally changed all permissions to everything in var (got too quick
>>>> on the keys and left out the /snd....) this caused me to have problems
>>>> with mysql after a reboot. I got that fixed and everything back to
>>>> working, but I have no idea what else I may have screwed up./ I set
>>>> everything in var back to root root, and the mysql stuff that gave me
>>>> errors back to mysql mysql, but is there a quicker way to fix anything
>>>> else than going to my other machine and looking at the permissions for
>>>> everything in var and going and fixing it on the server?
>>>    Some variation of rsync -u where you remove the destination prior to copy
>>>    as part of the copy. That way, the source file replaces the destination.
>>>    Not so good if the existing target is newer than the source, but rsync 
>>> does
>>>    have options that will allow you to deal with it. I just don't remember 
>>> the
>>>    permutations or syntax to make it happen.
>>>    man rsync
>>>    will be your friend.
>>>
>>>> anyway, everything looks the same permission wise but I still get the
>>>> error when trying to mount in the prod room: permission denied.
>>>>
>>>> The log (messages) on the server shows this:
>>>>
>>>> Nov 28 11:19:42 rdcs mountd[5223]: authenticated mount request from
>>>> 10.100.1.116:767 for /var/snd (/var/snd)
>>>> Nov 28 11:19:42 rdcs mountd[5223]: Cannot export /var/snd, possibly
>>>> unsupported filesystem or fsid= required
>>>    I suspect the new defaults in the new and improved NFSD.
>>>    Some time ago, they eliminated re-export to avoid loops.
>>>    Caused me no end of pain, as I depended on some of those
>>>    loops at the time, so by "fixing" it they broke much of what
>>>    I was doing.
>>>    You can still do it, but you need some explicit syntax in exports
>>>    though I forget what it is.
>>>    see
>>>    man exports
>>>    and specifically the nohide stuff.
>>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Rivendell-dev mailing list
>> [email protected]
>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>
>>
>> End of Rivendell-dev Digest, Vol 35, Issue 50
>> *********************************************
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>
>
>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to