Quantcast
Viewing all articles
Browse latest Browse all 7410

Updating 11.13 to 12.0 Help

Hi @jess,

I went through the DWH process manually and can see the plays get updated on the other end. I checked the various DWH log files (hourly, daily, dims, retention) and no errors were flagged. All the DB items: locks table clean, apache logs show up in kalturadw_ds.files, events show up in katluradw.dwh_fact_events. The other sanity tests all pass (only DWH fails), so perhaps there's nothing further to worry about.

Thanks for the extra info regarding the flavor none-comply errors, it makes sense that they aren't really errors. The missing parameter "event" one is still a little troubling, but perhaps it only occurs during the test, since it seems to work fine outside.

I'm also curious about one other thing. When performing the various upgrade tests, I watched a little closer on the permissions in the /opt/kaltura/app/cache folder. I checked the file /opt/kaltura/app/cache/api_v3/classMap.cache, since it seems to be one of the first loaded in most operations. The permissions seemed to get flipped to apache:apache after running the kaltura-config-all.sh script. Prior to running it, they were set to 755 with kaltura:apache as the ownership. It seems that I need to run that script, then run the command to flip the ownership to kaltura:apache recursively. Any thoughts on why this might happen?


Viewing all articles
Browse latest Browse all 7410

Trending Articles