Blank Page after Login and Invalid KS

You are not the only one, same thing here:
http://www.kaltura.org/blank-page-trying-login-adminconsole

We have the exact same situation - Ubuntu 10.04 (also tried 9.10), strictly following the setup guide, tweaking apache.conf, and then, nothing!

Anybody out there any idea what is happening?!

OK excellent. I've just voted here. Let's hope this is solved soon!

Please see if the following solved your issue - http://www.kaltura.org/setting-error-reporting-estrict-may-cause-apiv3-c...

Ok I had this issue and just solved it. So I thought of sharing the information.

When I looked in my apache error log file, I saw this:

I guess that there are many things that can cause this.

The "invalid ks" error that you see in your apache log means that there was something wrong with the call to the Kaltura API login service.

You have to first check your api error log file to see what caused this.

To locate it, check in your kaltura api logger conf file. For me it is:

/opt/kaltura/app/api_v3/config/logger.ini

Inside, you can see this

writers.stream.stream = /opt/kaltura/log//kaltura_api_v3.log

So when I looked in this file, I saw what was the real error:

So PHP couldn't connect to the MySQL server.

Why that? I had to compile manually MySQL from source in order to get the latest 5.1.x version, which wasn't available in my ubuntu packages (Still using 8.04 at work). The mysql socket wasn't stored at the usual location of /var/run/mysqld, but rather in /tmp. Of course I had changed the path in the my.ini file, but forgot to add it in the PHP configuration file (which used the default path of /var/run/mysqld).

Thus, if you encounter this same error, just make sure that the mysql socket path in PHP matches the one used by your MySQL daemon!

I.e in /etc/php5/apache2/php.ini :

Hope it helps someone.

Hi !
First, thanks for the answers.

Unfortunately, I tried both solutions from Kalturian and alexandre.mclean and no one worked fine. I saw no change after applied Kalturian's patch and I have no mysql error in my logs.
Please find below my api_v3 logs, if that could help you to understand.

Tips : e-mail and password have been replaced by xxxx but appears correctly in real logs.

Great to see these possible solutions. However, for me this also did not change the problem. The blank screen still appears and nothing appears to have changed. This is found in the api_v3 log:

If I read this correctly, an error is reported here:

exception 'Zend_Config_Exception' with message 'Error parsing /opt/myKaltura/app/api_v3/config/database.ini on line 6

On line 6 the password for the mysql (root) user is provided. This is the same password that was used to set up the system to begin with, and this should work just fine. It has not changed.

Anybody any idea?

Hi all,

Is there anybody with news on this topic? Kalturian, there are full logs from two users in the bug report. Does this perhaps help to analyze this problem? Is there anything we can do?

Thanks,
Paul

I agree with P.Paul.
And for other users, because there seems to be some people which can use Kaltura :
When do you installed Kaltura ?
Which Version ?
Which OS ?
On which hardware are you based ?
Have you followed the guide strictly or not (and if not what have you changed ?)

If someone could help us, this could be very usefull.
Over a month to install a software program which is given to work is really unthinkable !

Thanks

I have same problem.

I installed KalturaCE 2.0.2 on Sep.9 reading this page.
http://www.kaltura.org/kaltura-ce-setting-prerequisites-centos-55-wxampp

Then I could use Kaltura, upload and view just 2days.

After weekend, on Sep.13, I saw blankpage of Kaltura admin console, and KMC issue many errors. (KMC can't access my some video contents.)
Between this period, I did just installed moodle and its plugin.

I installed on CentOS5.5 with XAMPP, but this envronment is constructed on Mac Parallels Desktop.

Thank you Kagoya.
So the problem grows up...

Kaltura's team, an idea ?

Is there anything we can do to speed up the resolution of this issue? Its clearly pretty serious, if more information is needed from us than we should hear something about it.

i have setup several KalturaCE v2.0.2 Xen VPS servers since its initial release that all work fine

all run ubuntu 10.04 x64 LTS with the install instructions followed precisely

absolutely nothing additional is put on these servers and no additional configuration is performed outside of some server hardening

i dont know if that helps at all...

This remains a complicated and by now frustrating issue. There is a large group of people out there with this problem, there are many messages in the forum, there is a 'critical bug' report that is open for three weeks already, and so far the only reply from Kaltura is a link to a bug fix that attends to another problem with the date format. Yes, Kaltura is free and that is great, and this message is not meant to complain about Kaltura. However, I would like to point out that for the Kaltura platform to be a success, its users should be able to trust on their product. At this moment, I am seeing that if I get Kaltura running in the future, and there is a new version available which I install, that if it breaks down like this my problems could be serious. With not enough knowledge in the user community, not enough information in the documentation, and no responses from the Kaltura team, it means whatever I am doing with the Kaltura platform could be down for weeks. That is a serious issue for anything that is in production, and it makes me reconsider the use of Kaltura. And that is a shame, because it looks like such a great product!

So Kaltura team, please let us know what we can expect. Even a "We are looking into this, give us a week" message would be great. If you need more info, you can see several here are ready to provide this. We eagerly await your response!

Thanks,
Paul

Ubuntu 10.0.4 64bit running on VMWare 3.5, installed according to instructions on this site.

Got the same problem as others when loading the Management Console.

Ok, delved into the config files, and may have made some progress

Edited /opt/mykalturaApp/app/alpha/config/kConf.php

Made these changes;

"cdn_host" => "{myservername}",
"iis_host" => "{myservername}",
"www_host" => "{myservername}",
"rmtp_host" => "{myservername}",

"apphome_url" => "http://{myservername}",
"apphome_url_no_protocol" => "{myservername}",

Previously these parameters were set to {domainname}. IE, i now have kaltura.mydomain.com, whereas before the params were set to mydomain.com

Also

"memcache_host" => "{myservername}",

I now get a login dialog displayed.

Like others, my Management console now gives me a login dialog box, and admin console gives me a login dialog box.

Admin console goes to a blank page after I login, and the Mgmt Console returns "You have entered invalid data"

Any news on this topic? Workflowers, have you booked any progress?

We are currently using version 1.5 which works fine, but this is far from ideal. Migration seems to be difficult and that will be a hurdle if we really start to use this.

I don't know if it's just luck but if I install Kaltura with a blank mysql root password the admin module works. If I secure the mysql server, the admin console is blank.

Well that is interesting! Perhaps just coincidence but let's give it a shot. I'll be installing v2.02 with no root password, let's see what happens. I will be reporting back here...

We finally have Kaltura v2 running!!

This trick was in the MySQL root password, as jeand mentioned. Jeand, thanks for this tip!!

This is obviously very strange behavior and I am not too comfortable having no root password for MySQL, but for the moment the system is running and that is great news! I hope this also works for others. Also, hopefully somebody from Kaltura can assist in fixing this bug now that we know this underlying issue.

I'm not comfortable with this idea either. I find that kaltura seems "weak" from a security stant point. Why use root? They create a kalturaRead user why can't they create a kalturaWrite account and use that.

Just my .02$

Agreed. However, I guess this is a bug rather than intended. After all, this is nowhere mentioned in the documentation. And hopefully this is fixed soon because it is indeed not ideal.

Try with the default port.

This version seems to want it's own server (apache, mysql, etc.) Froma security perspective I find this version scary.

My server stoppped working. I now also have the blank admin page. Thank god for VMWare snapshots. I really wish Kaltura would at least respond.

Yes, it is very odd. Kaltura team members are active in other topics but just not report anything here. Also, the critical bug report that was posted is outstanding for over a month now, which is quite extreme as well. We currently have things running thanks to your leave-mysql-without-root-password hint. However, we are stuck with a system with no MySQL root password, which is not healthy either. So any input from Kaltura would be highly appreciated.

*Kalturian* - sorry for singling you out but I see you are currently active in other threads on this forum - could you give an update on this issue? Is Kaltura currently investigating this? Can we expect a fix soon? Even if this is not case, it would be great to know in order to take into account in our planning - I think the same applies to other (potential) users.

Thanks in advance!

Hi Paul,

This doesn't seem to be a bug but a problem with your installation flow. Tests with both ubuntu and CentOS do not produce these issues, so I'm led to believe something is wrong with the installation docs that caused confusion during your installation flow.

I've created a sample step by step log of my personal installation on a Rackspace ubuntu machine.
Can you please compare with your installation flow and see if there are differences?

If you can create a similar step by step log of your installation flow it might help pin point the issue you experience.

Guys, this is truly AMAZING. I have no idea how you find out that parenthesis could be the cause of this major problem jardar, but to me it appears you are totally right. We indeed HAD parenthesis in the initial password and that always - with no exception - caused a blank screen. Then we used an empty (and insecure) password and all worked as well. And while we were halfway installing the new server on our development machine for the test install Kalturian recommended, we read about this.... and got it solved by just reinstalling Kaltura and changing the root database to alphanumeric characters only. Incredible!

In any way, Kalturian, thanks for your response. I think that we now have it solved though. And give it a try and use a parenthesis-including root password to try this out. It does look like a bug related to the password in MySQL. I will post some comments around this website so others will not experience the same trouble. And now we can finally get down to use Kaltura!

Regards,
Paul

hi everybody.
I tried every suggested solution but...nothing worked for me. Then I follow the advice alexandre.mclean, but in a differente way:
if you have xammp installed you can run mysql under lampp (/opt/lamp/lamp statmysql) or by the ordinary daemon (/etc/init.d/). in the first case you get a connection error (can't connect to the /var/run/sock), in the second case you won't find the dbase...both lead to the famous blankpage.
I solved running mysqld from lamp but configuring apache2/php.ini with the correct socket path, that you can find in /opt/lampp/etc/my.cnf

now i've kalturaCe full working on ubuntu 10.10

hope this could be helpful

I am not sure if this matters to anyone anymore but this is how I solved my problem.

I modified {kaltura app base directory}/app/vendor/symfony/vendor/creole/drivers/mysql/MySQLConnection.php

After line 77 add your database info

77 if ($dbhost && $user && $pw) {
78 $dbhost = 'localhost'; <----added
79 $user = 'db user '; <-- added
80 $pw = 'db password; <-- added

Hope this helps someone.

I had the same situation with the v3.0 version. After i try to log in - blank screen.

I am not sure, if it has a direct connection, but i change the settings in the "/etc/hosts". Have a look here - http://www.kaltura.org/kmc-login-problems-0#comment-5537.
Perhaps it helps.