Restarting or Reloading Apache seems to cause the VOD module\nginx to start to fail

Community Forums Backend Server Support
1

Hey all,

Related to this thread:
https://forum.kaltura.org/t/nginx-issues-presumably-after-upgrade/7853/7

I think I’ve isolated how my kaltura cluster starts to fail playback via HLS after upgrading. Every time I reload or restart apache, playback starts to fail and you see this error in the nginx logs:

2018/01/03 21:10:16 [error] 17439#17439: *7733 media_set_parse_json: failed to parse json -1: expected digit got 0x0 while sending to client, client: 10.4.16.32, server: kaltura-prod-stream.intranet.hdr, request: "GET /hls/p/103/sp/10300/serveFlavor/entryId/0_djsuyld6/v/2/ev/4/flavorId/0_uuc59qwm/name/a.mp4/index.m3u8 HTTP/1.1", host: "kaltura-prod-stream.intranet.hdr:88", referrer: "http://hdrtv.intranet.hdr/watch.aspx?id=0_djsuyld6"

If I run kaltura-config-all.sh with my answer file, everything starts working again. I haven’t been able to figure out why this is.

I have two front end servers in my cluster. Each running nginx as well. Apache and nginx are behind a load balancer.

Any help or tips would be appreciated. I am running Kaltura 14.10 on Oracle Linux 6.

2

So, this randomly started happening again today. This time, it seems kaltura-config-all doesn’t fix it.

I’m disabling HLS on my players until I can figure this out.

3

Hi @david.hahn1,

That error means the Nginx VOD module got an invalid JSON file.
You need to figure out why that is… Start by running a HTTP sniffer before hitting “play” [you can use your browser’s devtool for that], capture the playManifest request the player made, make the same request using curl -v and inspect the response. In parallel, check both /opt/kaltura/log/kaltura_api_v3.log and /opt/kaltura/log/kaltura_apache_errors*.log for errors.

4

Thanks for the pointers, @jess. I’ll see if I can’t track this down. :slight_smile:

5

@jess, when you say the above, where should the JSON file have come from? The client’s browser or the API?