When editing a kaltura media node and saving, sometimes the following error is shown:
Fatal error: Uncaught exception 'Exception' with message 'Operation timed out after 10000 milliseconds with 0 bytes received' in xxx/sites/all/modules/kaltura/kaltura_client/KalturaClientBase.php:117 Stack trace: #0xxx/sites/all/modules/kaltura/kaltura_client/KalturaClient.php(3439): KalturaClientBase->doQueue() #1 xxx/sites/all/modules/kaltura/plugins/node_kaltura_entry/node_kaltura_entry.module(745): KalturaMediaService->update('1_nbk1txr4', Object(KalturaMediaEntry)) #2 xxx/sites/all/modules/kaltura/plugins/node_kaltura_entry/node_kaltura_entry.module(536): kaltura_update_entry_tags('1_nbk1txr4', '', '') #3 xxx/modules/node/node.module(659): node_kaltura_entry_update(Object(stdClass), NULL, NULL, NULL) #4 xxx/modules/node/node.module(937): node_invoke(Object(stdClass), 'update') #5 xxx/modules/node/node.pages.inc(456): node_save(Object(stdClass)) #6 xxx/dru n xxx/sites/all/modules/kaltura/kaltura_client/KalturaClientBase.php on line 117

Where in #6 the path should be drupaltest2 not /dru

Any ideas what this can cause?

Comments

patrickroma’s picture

patrickroma commented

Is there a Way to Rise the Time out Limit to more than 10000 milliseconds?

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Title: Uncaught exception 'Exception' with message 'Operation timed out after 10000 milliseconds with 0 bytes received' » Increase timeout for Kaltura save operations
Status: Active » Needs work

Yes, that facility has been added now (it's in 6.x-2.0-beta2 and later). See #1221752: Add configurable curl timeout setting.

However the default timeout remains at 10s. We should expand the timeout depending on what's happening (eg admin / write tasks generally should be more tolerant than anonymous / read tasks).