Swapping audio cards fixed this issue.  Thanks to everyone who helped.
It didn't get me much farther though.  When I try to restore the
database, that I have just backed up on my production machine, it
crashes and corrupts the database.  If I dump the database it will
create a new one, but still will not allow me to restore.  Both systems
are on the same version 2.10.3.  I will tackle it again tomorrow, but I
think I'm ready to dump the appliance and go back to Ubuntu.



On Fri, 2016-02-05 at 10:20 +1300, Robert Jeffares wrote:
> edit as root  /etc/asound.conf
> 
> pcm.rd0 {
>    type hw
>    card 0
>    device 0
>   rate 48000 <--- add this line to match what your system is set to
> }
> ctl.rd0 {
>    type hw
>    card 0
> }
> pcm.rd1 {
>    type hw
>    card 0
>    device 1
>   rate 48000 <------ add this line...
> }
> ctl.rd1 {
>    type hw
>    card 0
> 
> save
> restart
> 
> This is one of the few linux times it's smarter to restart the whole server.
> 
> regards
> 
> Robert
> 
> On 05/02/16 02:21, Jamie Dominey wrote:
> > Here is what I have in /var/log/messages
> >
> >
> > Feb  4 06:14:29 rdserv caed: Starting ALSA Play Device rd0:
> > Feb  4 06:14:29 rdserv caed:   Device started successfully
> > Feb  4 06:14:29 rdserv caed: Starting ALSA Capture Device rd0:
> > Feb  4 06:14:29 rdserv caed:   Asked for sample rate 48000, got 96000
> > Feb  4 06:14:29 rdserv caed:   Sample rate unsupported by device
> > Feb  4 06:14:29 rdserv caed: TwoLAME encoder library not found, MPEG L2
> > encoding not supported
> > Feb  4 06:14:29 rdserv caed: Found MAD decoder library, MPEG L2 decoding
> > supported
> > Feb  4 06:14:29 rdserv kernel: caed[1829]: segfault at 2d0 ip
> > 0000003122c086f6 sp 00007ffecd1990b0 error 4 in
> > libpthread-2.12.so[3122c00000+17000]
> >
> >
> > On Wed, 2016-02-03 at 21:01 -0500, Cowboy wrote:
> >> On Wednesday 03 February 2016 05:31:25 pm Jamie Dominey wrote:
> >>>   I
> >>> believe this updated the OS to Centos 6.7  Now the rivendell daemons
> >>> will not start.  Is there an easy fix for this, or do I need to start
> >>> over and only update Rivendell?
> >>   We have several instances running on CentOS 6.7 without problem.
> >>   Need more info from you. /var/log/messages ??
> >>
> >
> > _______________________________________________
> > 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

Reply via email to