In regards to “Cannot connect to the monit daemon. Did you start it with http support?”, it’s important to note that this is not imperative for Kaltura CE to work. Enabling http support will simply allows you to communicate with Monit [used for monitoring and as a watchdog for the Kaltura daemons over HTTP]. It’s a nice feature but since this is a sensitive interface [it allows you to control the various daemons from a web I/F], I suggest you only allow it from a small subset of IPs and of course, use a strong passwd as well.
In regards to your second issue, which IS critical, take a look at /opt/kaltura/log/kaltura_api_v3.log looking for erroneous patterns, like so:
# grep -A 1 -B 1 --color "ERR:\|PHP\|trace\|CRIT\|\[error\]" /opt/kaltura/log/kaltura_api_v3.log
It might be easier to locate the relevant error by first truncating the existing log and re-running the script.
Note that you can run only the failing test manually by calling:
# /opt/kaltura/bin/upload_test.php <service_url> <partnerid> <secret> </path/to/asset>
The partner can be any valid non-system partner you have [partner_id >= 100].
You can get the partner user secret, which the script expects as the third argument, from KMC->Settings->Integration Settings or with this query:
mysql> select secret from partner where id=$PARTNER_ID;