When we run the kaltura cron on our site, we get the following error: "PHP Fatal error: Call to a member function getEntries() on a non-object in /home/urbmi5/public_html/modules/kaltura/kaltura.module on line 487"

CommentFileSizeAuthor
#5 kaltura.log_.txt8.86 KBEvanDonovan

Comments

Zohar.Babin’s picture

Zohar.Babin commented
Status: Active » Postponed (maintainer needs more info)

did you finish the module configuration ? the error is due to failure in creating a client object.
when creating client object, the class tries to open session with kaltura's server, so failure could be caused by various reasons:
1. wrong partner details (like wrong secret etc.)
2. no connection to kaltura's server
3. lack of detail (if you didn't finish configuration)

What are the statuses in the "server integration settings" page ?

EvanDonovan’s picture

EvanDonovan commented

- Drupal to Kaltura Session Test: Session Status: OK (green)
- Cron job status: Cron has run (green)
- CrossDomain.xml Status: crossdomain.xml is in place and seems to be OK (green)

The partner info is all filled out.

Zohar.Babin’s picture

Zohar.Babin commented

I will add If() statement before using this object, but this is like taking Paracetamol when you have tooth ache instead of going to the dentist...

I'd like to understand why you fail to get the object in the first place.

If you could upload kaltura.log file so I'll take a look it could be very helpful.
I'd suggest that you clear the log (backup the old one), run cron and upload the new log (this way it would be smaller)

EvanDonovan’s picture

EvanDonovan commented

When I ran just the kaltura cron function, here is what I got.

I don't know if something is different when it runs via the cron daemon. I couldn't wait till the cron daemon ran it, because it seems like the kaltura cron is not run every time our cron runs, but instead only runs once every few days.

EvanDonovan’s picture

EvanDonovan commented
StatusFileSize
new kaltura.log_.txt8.86 KB

Sorry the file didn't attach for some reason.

Zohar.Babin’s picture

Zohar.Babin commented

that seems to be fine. it is not representing the fatal error case.

what happens if you run cron manually ?

the function getEntries() will not be called only i case you have no Kaltura nodes.
if you have at least one kaltura node, that function should be called, and in case there is still a problem you'll get the fatal error again.

EvanDonovan’s picture

EvanDonovan commented

Thanks for your help. I'll get back to you the next time that we receive the error email from the cron daemon. I don't think I can run cron manually, because we have so many modules installed that it runs the risk of destabilizing the system.

We have around 4 Kaltura nodes.

kpm’s picture

kpm commented

I just received the same error. It's been running error free since set up a couple months ago. Only recent change was an upgrade from 6.10 to 6.12. Just checked server status, and all have green checks. Checked the kaltura content on the site and it's fine. Maybe this is just a dropped connection at the time cron ran??

kpm’s picture

kpm commented

update...
Cron started emailing me Kaltura errors again on Sept 29th... Today I had time to investigate, simply logged in to server integration settings directly (using the Drupal Admin module, navigating to Site Configuration > Kaltura > server integration settings, and saw that all three Server Status points had a large red 'x' beside each, rather than that large green check mark I was hoping for... All I did, was click on the top Kaltura admin menu, which closed all of the sub sections, then clicked on the Kaltura servier integration settings again, and the green check marks were back, all Kaltura statuses reporting OK.

oferc’s picture

oferc commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.