Centova Technologies Forum
Centova Cast v3 => Bugs and issues => Topic started by: heisenberg on June 01, 2016, 05:01:14 am
-
The latest few Centova updates brought lots of problems to us. The artist became shown as "Unknown" and FTP login stopped to work. They released a fix but it didn't fix the problem completely. Some stations still experience those problems. We have loads of support tickets about "Unknown" artists and FTP problems; our customers are frustrated and my tech support staff is frustrated with them. I'm really getting tired of new bugs that almost every new update introduces.
Centova developers, please do something about quality control of your releases. We're paying for quality, not to be beta testers.
-
Yes FTP went out for me for me also, updated last night things are running good again :)
-
Last month was indeed a pretty bad one for us, in terms of updates, and we're truly sorry for that.
However, the bugs you've mentioned have been fixed for about a week now.
A new situation came up though, that's only affecting Icecast KH users. This problem does not actually have anything to do with Centova Cast, and it's caused by the fact that Icecast KH is splitting up the artist and title into two different XML elements. That is nonstandard behavior introduced by the -kh branch of IceCast; in proper IceCast builds, there is only a single "title" element that contains the artist AND song title separated by a hyphen (as in, "artist - title"), and this is what Centova Cast expects to find.
We do not test against IceCast-kh during development (we use the official, mainline IceCast tree for all testing), but as many of our clients do use -kh, we do our best to resolve compatibility issues like this one as they arise.
With that said, we are working, as we speak, on a solution for this problem as well.
-
The KH server is fixed, thanks for that. Not sure about FTP problem, but it's not a priority as a new bug is discovered!
And it's a major one. For some weird reason Centova thinks that it's from the future. It says that it was released on July 13, 2016. Because of that it says that the license is not valid (license expires June 18, 2016).
Again. I am software developer myself and can understand bugs in the software. But this bug is show-stopper and it's serious. Our customers can't access their control panels, they constantly receive "licensing errors".
Why Centova locks out? If it allowed updating, then IT HAS TO WORK after the update is made!
Why it doesn't send email to server's admin notifying about this? It can issue an email allowing some time (e.g. 7 days) to do something - in this case, wait until fixed Centova is released.
-
The KH server is fixed, thanks for that. Not sure about FTP problem, but it's not a priority as a new bug is discovered!
And it's a major one. For some weird reason Centova thinks that it's from the future. It says that it was released on July 13, 2016. Because of that it says that the license is not valid (license expires June 18, 2016).
Again. I am software developer myself and can understand bugs in the software. But this bug is show-stopper and it's serious. Our customers can't access their control panels, they constantly receive "licensing errors".
Why Centova locks out? If it allowed updating, then IT HAS TO WORK after the update is made!
Why it doesn't send email to server's admin notifying about this? It can issue an email allowing some time (e.g. 7 days) to do something - in this case, wait until fixed Centova is released.
Hello heisenberg,
This issue was fixed within a few hours after it was first reported.
If you are being affected, simply run the update utility script.
You can also use the following command via SSH if you don't want to wait to wait 30 minutes for the error message to go away.
/usr/local/centovacast/bin/ccmanage cronjob --job=pollhosts --force
HTH
-
Yes, this was fixed fast, thanks for that.
But the core issue still exists:
1. Why Centova allows an update and after the update it ceases working? I use permanent licenses. It should NEVER disable because of expired license. Either prohibit the update if the license doesn't allow it, or if it's installed - it has to work.
2. Why it doesn't notify administrator about problems like this? It simply stops working and that's it.
3. It need not to lock immediately. Give reasonable time to act and solve the problem.
The new FTP password handling brought nothing to us except the problems. People whose accounts are on "control daemon" servers still not able to use the FTP feature. This is frustrating. We lost some customers because of this. We receive numbers of tickets about the FTP problem. What was the purpose of changing that? The FTP worked, no one complained. Now it doesn't work. But we have better FTP password security now - what a relief :-\
-
Very glad I checked before doing the upgrade. I had a problem with the last one too, so I'm a lot more careful about just accepting an upgrade now.
-
Very glad I checked before doing the upgrade. I had a problem with the last one too, so I'm a lot more careful about just accepting an upgrade now.
Hello Krypton,
At the time of writing this, there are no known issues or pending bug reports with the current release, it should be safe to update.
-
The FTP bug with control daemons is still not fixed completely. Some users are still unable to access the FTP :( I'll send more details in my ticket.
-
yes FTP complaints are coming in for us as well :(
-
We've only had three reports for this issue, after the latest version (from June 1st). Two from you guys and one from someone else, who I'm not sure if he's using the latest version. (waiting for his confirmation) It's a bit weird, as this sort of problems usually brings tons of tickets with reports.
We would also gladly investigate this further, but we don't have much to work with at the moment. We would need access to a server that's manifesting this problem (root access), so if anyone is able to provide that, please open a ticket with our support department.
-
ticket opened :)
-
The latest FTP security changes should be reverted. Or at least made optional. I'm really annoyed of all those FTP complaints coming from our users. We're losing customers and money for no reason. Who needed those FTP password changes in the first place? What was the purpose in this enhanced FTP security?
-
As it turned out, Pure-FTP was segfaulting on 32 bit operating systems. This has been fixed in the latest build.
-
We use 64-bit OS and the latest update didn't fix the issue. I provided more information in the ticket.
I still like an answer to my previous questions:
1. Why Centova locks out with permanent license? See my previous message about the wrong release date. And why there's no notification for the server admin about the lockout? Why there's no "grace period" or something so that admin could have a chance to take an action (in my case - wait until you fix the problem)?
2. What was the purpose of changing the FTP password handling (or what was changed that introduced all those FTP problems)?
-
We use 64-bit OS and the latest update didn't fix the issue. I provided more information in the ticket.
I'm sorry, but we currently have no active tickets with relation to FTP issues.
It is possible that you have closed your ticket by mistake, in which case we would need the ticket number in order to find it and reply.
I still like an answer to my previous questions:
1. Why Centova locks out with permanent license? See my previous message about the wrong release date. And why there's no notification for the server admin about the lockout? Why there's no "grace period" or something so that admin could have a chance to take an action (in my case - wait until you fix the problem)?
Centova Cast doesn't "lock out" anymore, since 3.0, after a license check fails, the panel will go into read-only mode -- which means you cannot make changes --, however it will allow your stations to continue normal operations for many days, while you sort out the problem or wait for a fix in case there is a problem with your license on our side.
2. What was the purpose of changing the FTP password handling (or what was changed that introduced all those FTP problems)?
In an effort to keep up with security standards, our developers moved on to use the bcrypt library to encrypt all passwords.
This change worked well across all other components except for Pure-FTP which had fallen behind in supporting bcrypt.
-
Thanks for your reply.
By "lock out" I mean that netiher admninstrator nor users can make any changes to their streams. This is frustrating, especially when you have "permanent" license.