Centova Technologies Forum
Centova Cast v3 => Bugs and issues => Topic started by: Stream101 on February 15, 2013, 06:34:34 am
-
Ran the utility and it is looking for ccmanage.php in the downloaded export22x folder. I manually modified the path to show /home/centovacast/system (which it should just be set to anyways).
The sqls export, then it moves on to the following error (changed the account name for privacy):
Exporting account data via local copy ...
Exporting account bxxxxs ...
cp: cannot stat `index.html/*': Not a directory
Error copying files for account bxxxs
-
Ran the utility and it is looking for ccmanage.php in the downloaded export22x folder. I manually modified the path to show /home/centovacast/system (which it should just be set to anyways).
Exactly how is that manifesting? It should never look for ccmanage.php in the export22x directory -- it should look for it in the parent directory, which should be /home/centovacast/system, which is where ccmanage.php SHOULD exist.
Are you sure you're following the instructions and putting the export22x directory under /home/centovacast/system? (eg: the complete path should be /home/centovacast/system/export22x). It sounds like you're putting it elsewhere.
The sqls export, then it moves on to the following error (changed the account name for privacy):
This could be a bug, but more likely it's the result of you putting the export22x directory in the wrong place. It MUST be in /home/centovacast/system/export22x or the export will fail in exactly the manner you described, because the utility has no other way of knowing where CCv2 is installed.
-
Are you sure you're following the instructions and putting the export22x directory under /home/centovacast/system? (eg: the complete path should be /home/centovacast/system/export22x). It sounds like you're putting it elsewhere.
The sqls export, then it moves on to the following error (changed the account name for privacy):
This could be a bug, but more likely it's the result of you putting the export22x directory in the wrong place. It MUST be in /home/centovacast/system/export22x or the export will fail in exactly the manner you described, because the utility has no other way of knowing where CCv2 is installed.
The path is: /home/centovacast/system/export22x. I redid the whole process without modifying the path to /home/centovacast/system and I get this every time:
Unable to locate Centova Cast files.
The export directory should be placed under your Centova Cast system directory,
eg: /home/centovacast/system/export
Also PWD
[root@cloud1 export22x]# pwd
/home/centovacast/system/export22x
-
Here is what I did to make at least the first part work the last time.
HERE=$(dirname $0)
cd $HERE
[ -f /etc/ccbuild_uname ] && HERE=/home/ccstable/system/export
SYSTEM_PATH=$(dirname $HERE)
TO
HERE=$(dirname $0)
cd $HERE
[ -f /etc/ccbuild_uname ] && HERE=/home/ccstable/system/export
SYSTEM_PATH=/home/centovacast/system
-
Ahh, thank you -- you were right, I was wrong. A new, fixed build will be on the download server in about 5 minutes.
-
TOLD YOU SO! (Just kidding!) Just trying to help out as much as I can!
-
Much appreciated. :) Any further problems, let us know!
-
Still getting the copying issue:
Exporting account data via local copy ...
Exporting account bxxxxxs ...
cp: cannot overwrite directory `/usr/local/centovacast/var/vhosts/_226import/bxxxxxs/index.html' with non-directory
Error copying files for account bengeens (/home/centovacast/vhosts//bxxxxxs/index.html)
[/quote]
-
If the import process fails you have to reinstall v3 and try again. The above error is because the previous half-copied account still exists in v3. (Technically you could try just removing /usr/local/centovacast/var/vhosts/_226import instead of reinstalling since it failed so early in the process, and it should probably still work... but safest bet is to reinstall v3 using the automated reinstallation script noted in the sticky.)
-
Gotcha. Trying that now!
-
Reinstalled,
More errors:
cp: cannot create link `/usr/local/centovacast/var/vhosts/_226import/bxxxxs/va r/spool/ondemand/_covers/promo_only_country_radio_june_67fe385f.jpg': Invalid cr oss-device link
-
Ahh, you're copying between partitions and apparently cp doesn't fall back gracefully from hardlinking to a standard copy. Our same-server upgrade testing was done on virtual machines which only have a single disk and partition, so this issue didn't arise on those.
There's a new build on the download server now that detects and handles this -- thanks for your patience!
-
New error:
Exporting account bxxxs ...
cp: cannot stat `var': No such file or directory
Error copying database dump for account bxxxs
-
Grr, most of these are turning out to be silly little errors that are just unique enough to not show up in our own testing. Once again, this is fixed and a new build is up on the download server... thanks!
-
I suppose thats what beta testing is, huh? You must be seeing a lot of server traffic from me lol
-
Looks like its going, but I'm getting this:
head: cannot open 'DBFILENAME' for reading: No such file or directory
Exporting account bxxxxn1 ...
head: cannot open 'DBFILENAME' for reading: No such file or directory
Exporting account bxxxxn2 ...
head: cannot open 'DBFILENAME' for reading: No such file or directory
Exporting account bxxxxn3 ...
etc
-
Bloody hell -- sorry, that was a typo. I've put up a new build; if there are any more substantial issues in this one, I'll probably just set up vanilla Debian virtual machine, install v2 and v3 on it, and tinker with it until it succeeds... hate making you the guinea pig for this. :)
-
FYI while we did do some same-server testing, most of our testing of the utility was remote-server testing (eg: installing v3 on a separate machine from v2) which uses a different mechanism for copying. That's why you're running into so many seemingly-obvious bugs.
-
Hey no problem. How do I specify a custom install of Icecast2 (KH build specifically). This is a pretty plain CentOS box.
-
If you've installed your own IceCast, you can enable it in CCv3 with:
/usr/local/centovacast/sbin/enable_package ICECAST /path/to/icecast
Replace /path/to/icecast with the actual path to IceCast, of course.
-
Does the importer map their existing IPs?
-
It is NOT importing their existing Port Numbers. It is assigning them new ones based on the range specified in the setup of CCv3.
Is this possible to get working?
-
Does the importer map their existing IPs?
It uses the default IP address configured for the v3 server.
It is NOT importing their existing Port Numbers. It is assigning them new ones based on the range specified in the setup of CCv3.
Is this possible to get working?
Hmmm, that's actually a very good point. What we'll have to do is set it up so that it uses the originally-configured port IF it's available, and auto-allocates a new one if not. The reason for this is because it's possible to import multiple v2 installation into a single v3 installation (or to import v2 accounts into a v3 installation that already contains accounts), so there may be port conflicts... I hadn't even noticed/considered that it reallocated them though, and clearly we do want at least a best effort.
Working on that now, back in a bit...
-
GET ON IT! Haha! Awaiting a new update :)
-
OK, I think we're good to go -- a new build is on the download server. Just make sure that your port range in v3 (Settings -> Defaults -> Port range for new servers) includes all of the ports that your streams use, and it should maintain the port numbers during import.
-
Didnt work for me. It still assigned the port numbers starting at the lowest value (8000)
-
For me the custom Config is not auto-configuring the IP's and stays with the "defaults" from the skeleton - 192.168.x and port 8050
-
Just seeing if this got caught Steve.
Thanks!
-
Didnt work for me. It still assigned the port numbers starting at the lowest value (8000)
I tried a few different upgrades of a few different servers today and I can't seem to reproduce this... it faithfully reproduces the v2 port configuration on v3 whenever I try it.
The only thing I know of that would cause this to happen is if you had your port range set to 8000-9000 in v3, and your streams in v2 were using ports outside of that range. The upgrader will enforce the port range set in v3, and will renumber the accounts if they're outside that range.
I also uploaded a new update to the download server -- you may want to try again with that one and see if it works any better.
-
We'll try it again. I even gave a range of 2000 to 90000 just to test
-
65535 is the maximum possible TCP port number. :) but that should do it anyway.
-
I know that...just emphasizing my point :p.
Havent had a chance to test it, but I will be doing so soon!
-
Still not working for me. Would you like to look at the server?
Also a question regarding template customization. Does the "custom" directory still work?
-
Still not working for me. Would you like to look at the server?
Certainly, being able to run through an upgrade or two myself should be very helpful in tracking down the problem. You can either PM me your server information or open a ticket with the installations department Attn: Steve. The latter is more secure and less permanent.
Also a question regarding template customization. Does the "custom" directory still work?
Yes, absolutely.
-
I Put in a ticket
-
I Put in a ticket
Thank you! This was extremely helpful in finding what turned out to be another corner case that didn't show up on our own servers.
This is fixed now and a new build is available. I've updated your server with it as well, so it's ready for you to run another import if you'd like to do so.
-
Sweet. I'll work on it when I get home.