Izio, it worked perfectly. I had disabled ipv6 ages ago when trying to
troubleshoot a different problem and since all I ever run is v4, never needed
to re-enable it. Once I put it back in and recompiled Python (just in case), it
worked fine.
Now... if I can just figure out why the frontend GUI quits all by itself. Could
it be something it ingested on Monday that is giving it a tummyache? ^_^
Any help with that problem would be greatly appriciated. I'll see what I can do
after making the logs more verbose.
Oh, and sorry about stealing threads... I didn't realize it still kept a record
of where the message belonged even if I changed the subject line to something
new. I'll create new messages from now on. Thanks for pointing that out!
James
----- Original Message ----
> From: Fabrizio Ferraro <izio...@fastwebnet.it>
> To: freevo-users@lists.sourceforge.net
> Sent: Mon, May 31, 2010 11:56:33 PM
> Subject: Re: [Freevo-users] Spontainious crash and collateral damage during
> attempted repair...
>
> James Trietsch wrote:
> In an attempt to fix, I updated kaa and freevo
> from SVN and now I really broke it. Now the webserver and recordserver won't
> start, but at least they're throwing an exception. Something about network
> sockets and type needing to be an integer, related to trying to talk to the
> recordserver I think.
>
>
Seems like kaa svn needs
> ipv6 and your installed version of python does
not have ipv6 support
> compiled in.
I'm running Gentoo and I had the same problem as I disabled ipv6
> support
with a global USE flag when I built the system a long time
> ago.
If this is your case too, you just have to enable ipv6 and rebuild the
>
system with emerge --newuse --deep world . You may have to recompile
>
your kernel, too.
Hope this
> helps.
------------------------------------------------------------------------------
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
