i seam to be missing my licence file meaning the deamon wont start and cant make accounts.

not usre if its ment to but while exploring for scripts to run i found some in the extras folder... they refrence runascc but when going to that file i could only see the runascc.c file so i ran make... hasnt helped any tho

There are still lots of bugs in this version. There is also no estimate or what so ever when there is a new release, as far as i know.

hiya,

thanks, i am aware this is a beta product being a software deveoper and consultant myself.

im mearly trying to report issues, and your comment dosnt have any value added to the issue of the licence files not being setup on install.

KL Web what type of server, os are you running? I did not have a problem installation was seamless,  however last year I had spend many hours learning how to install without errors such as yours I have lots of notes ...  Are you able to click the "About" link top left, it will show your version, mine is 3.0.0b2.20120117.44 -- also under admin settings there is a license test button.


J.J. Draijer yes there were many bugs however so far the only problems I have found are very minor,  I remember it was very unstable last year but not anymore, I have not had to restart yet and I am amazed at just how well it's running very low server load compared to the ices_cc auto dj in the old version, you should try to update or a fresh install.

Hey MyAuto,

thanks for the reply.

The interface works so was able to grab that info, also the licence check works... but when starting from cmd line licence issues are reported... which is i guess why I can't make accounts. when i get time i will install the debugger as detailed in the sticky post and investigate some more.

the version is the same 3.0.0b2.20120117.44... noticed the recorded hostname on that page is just "radio" rather than the full domain, radio is the subdomain... wonder if that has somthing todo with it.

im running on 64bit Ubuntu 10.10 box

Yes if you have your radio url @ www.radio.yoursite.com and your have your license going to www.yoursite.com it will not work, you would need to go in and re-issue your license key in your Centova Cast Client Area, usually the first time you install if you have the incorrect path in your Centova client area the installer will correct it for you but that is not the case if you change it. At least that's how it is with v2, not sure about v3 I guess you only run the update line
-- in my Centoava the url is server.localdomain
also remember if you reissue your license key more than, I think 3 times in a 72 hour period it will lock you out

Also I have found a few more bugs, multiple accounts = multiple problems

hey,

ive got V2 running on the same box running streams at the moment, one thing i thought of is i used the web installer section via the ip and not the hostname....

i will have a proper dig about later today once ive cleared some client work and report my findings... any tips on places to look if there on the top of the mind would save some time and be quite awesome

I had first tried to install v3 on the same server as cPanel & Centova v2 last year but it would never work, Everything conflicted, mainly because of cpanel so I then got a new vps with only Centos5 and MYSQL installed, v3 has everything you need (FTP, Apache) the instructions they provide are great, I have been using vps.net a lot lately for testing (wish I could put my affiliate link here!) you can pay by the day and they set up instantly, it would cost you about $5 and it would take you about 1 hour to create the vps and install Centova, you would need to know how to create MySQL user, table and db via command line ..  I am sure you can run both v2 and v3 on the same server but I could never get it to work.

http://www.centova.com/doc/manuals/centovacast/quickref/quickstart.html

Hey folks, just a reminder that in order for us to help you diagnose an issue with your installation we really need you to include the actual error message(s) you're seeing.  Just hearing that "license issues are reported" doesn't tell us much because the "issues" could be just about anything.

Also FWIW if you're upgrading from an old (last year) beta, you might have better results just scrapping your current installation and reinstalling fresh... the new beta builds "unofficially" released over the past couple of months are quite a bit different, and we're not aware of any licensing issues with these ones.