I just did a fresh install of Kaltura on Centos 6.6. Everything seems to go fine until I try to log into the Admin Console at which I get Invalid credentials provided.
Is there a way to reset this? When I pull up the kaltlog all it complains about PHP Warning about date(). I did go into the php.ini file and manually set the date to America/New York
Thanks.
Hello,
Did you restart Apache after changing the date.timezone directive?
Note that the installer prompts you about that and should insert it automatically to the kaltura PHP INIs, for instance:
[ec2-user@kaltura-sphinx1 ~]$ grep date.timezone /etc/php.d/zz-kaltura-*ini
/etc/php.d/zz-kaltura-batch.ini:date.timezone=‘America/New_York’
/etc/php.d/zz-kaltura-front.ini:date.timezone=‘America/New_York’
Do you have that?
When trying to login, what else do you see in kaltlog? this error may indicate the DB population phase did not pass successfully. Did you get any errors during the install scripts run?
Thanks,
Thanks for the reply Jess.
When I run grep date.timezone /etc/php.d/zz-kaltura-*ini I get exactly what shows in your message.
I just redid the install with a fresh Centos image. Config fails after the following:
CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons…
Connectivity test passed:)
Cleaning cache…
Populating DB with data… please wait…
Output for /opt/kaltura/app/deployment/base/scripts/installPlugins.php being logged into /opt/kaltura/log/installPlugins.log
Output for /opt/kaltura/app/deployment/base/scripts/insertDefaults.php being logged into /opt/kaltura/log/insertDefaults.log
Archving logs to /opt/kaltura/log/log_11_11_14_15_32.tar.gz…
ERROR: we failed on something else…
the insertDefaults log shows as follows at the end.
PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log.php on line 135
PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log.php on line 135
PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /opt/kaltura/app/alpha/lib/model/om/BasePartner.php on line 1138
PHP Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead' in
/opt/kaltura/app/alpha/lib/model/om/BasePartner.php:1150
Stack trace:
#0 /opt/kaltura/app/alpha/lib/model/om/BasePartner.php(1150): DateTime->__construct('2014-11-11 15:3...')
#1 /opt/kaltura/app/alpha/lib/model/om/BasePartner.php(2373): BasePartner->setUpdatedAt(1415737933)
#2 /opt/kaltura/app/alpha/lib/model/om/BasePartner.php(2100): BasePartner->preUpdate(Object(KalturaPDO))
#3 /opt/kaltura/app/alpha/lib/model/Partner.php(63): BasePartner->save(NULL)
#4 /opt/kaltura/app/alpha/apps/kaltura/lib/kPermissionManager.php(1027): Partner->save()
#5 /opt/kaltura/app/alpha/apps/kaltura/lib/kPermissionMan in /opt/kaltura/app/alpha/lib/model/om/BasePartner.php on line 1150Hello,
What is the value you set in the timezone directive? it is probably just not a valid one…
Thanks,
I set America/New York
Are there any compatibility issues with installing it on a VM (VMWare)?
You need America/New_York
No spaces. Then it should be fine.
That seemed to have fixed the install portion. I still get the invalid credentials login error and when I run the sanity check the following gets returned.
[check_studio_index_page] [PASSED, RC: 0] - [1.152835345]
[Create Partner] [FAILED, RC: 255] - [.231775897]
Partner creation failed. I will skip all tests that require it.
[Red5 file upload] [PASSED, RC: 0] - [3.722384450]
I’m also getting a number of errors when running kaltlog.
2014-11-12 09:59:00 [714771415] [KalturaClientBase->doQueue] DEBUG: execution time for [http://kaltura:80/api_v3/index.php?service=dropfolder_dropfolder&action=list]: [0.033499002456665]
2014-11-12 09:59:00 [714771415] [KAsyncDropFolderWatcher->getDropFoldersList] ERR: exception 'Exception' with message 'Cannot get drop folder list - The access to service [dropfolder_dropfolder->list] is forbidden' in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(110): KalturaLog::err('Cannot get drop...')
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 734
PHP Fatal error: Uncaught exception 'KalturaException' with message 'The access to service [batch->suspendJobs] is forbidden' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1145): KalturaClientBase->throwExceptionIfError(Array)
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 734
PHP Fatal error: Uncaught exception 'KalturaException' with message 'The access to service [system->ping] is forbidden' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4328): KalturaClientBase->throwExceptionIfError(Array)
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 734
PHP Fatal error: Uncaught exception 'KalturaException' with message 'The access to service [batch->updatePartnerLoadTable] is forbidden' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1128): KalturaClientBase->throwExceptionIfError(Array)
--
==> /opt/kaltura/log/batch/synchronizedistribution-0-2014-11-12.err.log <==
PHP Fatal error: Uncaught exception 'KalturaException' with message 'The access to service [contentdistribution_contentdistributionbatch->updateSunStatus] is forbidden' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2426): KalturaClientBase->throwExceptionIfError(Array)
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 734
PHP Fatal error: Uncaught exception 'KalturaException' with message 'The access to service [liveStream->list] is forbidden' in /opt/kaltura/app/batch/client/KalturaClientBase.php:734
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(3996): KalturaClientBase->throwExceptionIfError(Array)
Did you run kaltura-drop-db.sh and rerun the kaltura-config script?
Can you paste the config script output?
Also, I’ve added a validation for the timezone so that this thing will not happen to others:)
Thanks,
Still Invalid login credentials. Here’s what I ran including the drop_db most recently.
[root@kaltura ~]# /opt/kaltura/bin/kaltura-drop-db.sh
This will drop the following DBs:
kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
and remove users:
kaltura etl
on 127.0.0.1
NOTE: this is not reversible.
It is recommended you also back up the current data using mysqldump before continuing.
You can use /opt/kaltura/bin/kaltura-export-db.sh to export the data.
Are you absolutely certain you want this? [n/Y]
y
Aborting. To remove hit UPPER CASED 'Y'
[root@kaltura ~]# /opt/kaltura/bin/kaltura-drop-db.sh
This will drop the following DBs:
kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
and remove users:
kaltura etl
on 127.0.0.1
NOTE: this is not reversible.
It is recommended you also back up the current data using mysqldump before continuing.
You can use /opt/kaltura/bin/kaltura-export-db.sh to export the data.
Are you absolutely certain you want this? [n/Y]
Y
root DB passwd:
Removing kaltura
Removing kaltura_sphinx_log
Removing kalturadw
Removing kalturadw_ds
Removing kalturadw_bisources
Removing kalturalog
[root@kaltura ~]# /opt/kaltura/bin/kaltura-config-all.sh
Running base config...
kaltura-base-9.19.5-1.noarch
Welcome to Kaltura Server 9.19.5 post install setup.
To keep up with the bi-weekly Kaltura releases, and stay up to date with
the latest news, security and bug updates, and connect with the global
Kaltura community - sign up for our regular Kaltura Community updates.
Please enter your email to sign up, or enter NO to pass.
[Email\NO]:NO
In order to finalize the system configuration, please input the following:
CDN hostname [kaltura]:
kaltura
Apache virtual hostname [kaltura]: kaltura
Vhost port to listen on [80]: 80
DB port [3306]: 3306
MySQL super user [only for install, default root]: root
Analytics DB hostname [127.0.0.1]:127.0.0.1
Analytics DB port [3306]:3306
Sphinx hostname [127.0.0.1]: 127.0.0.1
Secondary Sphinx hostname [leave empty if none]:
Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character):
Confirm passwd:
Your time zone [see http://php.net/date.timezone], or press enter for [America/New York]: America/New_York
Your Kaltura install name (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]:Daemen Video Platform
Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]: http://www.daemen.edu
Your 'Contact us' phone number [+1 800 871 5224]:+1 800 462 7652
========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_12_11_11_40.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================
Configuration of Kaltura Server 9.19.5 finished successfully!
Running FrontEnd config...
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:
# rm /opt/kaltura/app/base-config.lock
# /opt/kaltura/bin/kaltura-base-config.sh
kaltura-front-9.19.5-1.noarch
It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y]
y
Which port will this Vhost listen on? [80]
80
Please select one of the following options [0]:
0. All web interfaces
1. Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipApp
2. KAC - Kaltura Admin Console
0
Enabling Apache config - apps.conf
Enabling Apache config - var.conf
Enabling Apache config - admin.conf
========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_12_11_11_40.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================
Stopping httpd: [ OK ]
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName
[ OK ]
Shutting down monit: [ OK ]
Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Running Sphinx config...
kaltura-sphinx-2.2.1-16.x86_64
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:
# rm /opt/kaltura/app/base-config.lock
# /opt/kaltura/bin/kaltura-base-config.sh
Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Configuring your Kaltura DB...
Checking MySQL version..
Ver 5.1.73 found compatible
CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons...
Connectivity test passed:)
Cleaning cache..
Populating DB with data.. please wait..
Output for /opt/kaltura/app/deployment/base/scripts/installPlugins.php being logged into /opt/kaltura/log/installPlugins.log
Output for /opt/kaltura/app/deployment/base/scripts/insertDefaults.php being logged into /opt/kaltura/log/insertDefaults.log
Output for /opt/kaltura/app/deployment/base/scripts/insertPermissions.php being logged into /opt/kaltura/log/insertPermissions.log
Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log
Generating UI confs..
Shutting down monit: [FAILED]
Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Running Batch config...
kaltura-batch-9.19.5-1.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:
# rm /opt/kaltura/app/base-config.lock
# /opt/kaltura/bin/kaltura-base-config.sh
Reloading httpd:
Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Running DWH config...
kaltura-dwh-9.4.0-2.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:
# rm /opt/kaltura/app/base-config.lock
# /opt/kaltura/bin/kaltura-base-config.sh
Deploying analytics warehouse DB, please be patient as this may take a while...
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.
sending incremental file list
MySQLInserter/
sent 133 bytes received 25 bytes 316.00 bytes/sec
total size is 2646419 speedup is 16749.49
sending incremental file list
MappingFieldRunner/
sent 147 bytes received 25 bytes 344.00 bytes/sec
total size is 90670 speedup is 527.15
sending incremental file list
GetFTPFileNames/
sent 141 bytes received 25 bytes 332.00 bytes/sec
total size is 7308893 speedup is 44029.48
sending incremental file list
FetchFTPFile/
sent 135 bytes received 25 bytes 320.00 bytes/sec
total size is 5783119 speedup is 36144.49
sending incremental file list
DimLookup/
sent 122 bytes received 25 bytes 294.00 bytes/sec
total size is 3687964 speedup is 25088.19
sending incremental file list
sent 80 bytes received 12 bytes 184.00 bytes/sec
total size is 34770 speedup is 377.93
current version 5999
DWH configured.
====================================================================================================================
Setup completed successfully!
To access your Kaltura tools visit:
http://kaltura:80
To begin, access the Admin Console using the Admin email and password you've entered while installing.
When logged in to the KAC, create a new publisher account to being using Kaltura.
Visit http://www.kaltura.org to join the community and get help!
Visit http://knowledge.kaltura.com to read documentation and learn more.
=====================================================================================================================
Thank you for running Kaltura! To keep Kaltura viable, stable and tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.
Sanity check returned this afterwards.
[root@kaltura ~]# /opt/kaltura/bin/kaltura-sanity.sh
[Space on /] [PASSED, RC: 0] - [.032709601]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.004598985]
[Check httpd daemon status] [PASSED, RC: 0] - [.187229820]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [9.684515593]
[check daemon httpd init status] [PASSED, RC: 0] - [.058842259]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.088535000]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [7.236946597]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.005789804]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.113829862]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [5.278938202]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.005603403]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.053219600]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.005907945]
[Check memcached daemon status] [PASSED, RC: 0] - [.031783395]
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [6.313209947]
[check daemon memcached init status] [PASSED, RC: 0] - [.004985620]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.180523050]
[kaltura-kdp3 ver in KMC config.ini] [PASSED, RC: 0] - [.045309031]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.103232326]
[Get KMC SWFs] [PASSED, RC: 0] - [2.437178061]
[check_testme_page] [PASSED, RC: 0] - [13.870009972]
[check_kmc_index_page] [PASSED, RC: 0] - [.063987603]
[check_admin_console_index_page] [PASSED, RC: 0] - [.208500233]
[check_studio_index_page] [PASSED, RC: 0] - [.860676009]
[Create Partner] [PASSED, RC: 0] - [1.792064518]
[Local dropfolder creation succeeded] [PASSED, RC: 0] - [.382412957]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.717849683]
Napping 10 seconds to allow entry 0_4rmmerom to digest..
Napping 10 seconds to allow entry 0_4rmmerom to digest..
Napping 10 seconds to allow entry 0_4rmmerom to digest..
Napping 10 seconds to allow entry 0_4rmmerom to digest..
Napping 10 seconds to allow entry 0_4rmmerom to digest..
[kaltura_logo_animated_blue.flv - 0_4rmmerom status] [PASSED, RC: 0] - [51.474035004]
[Thumb for 0_4rmmerom identical to /opt/kaltura/bin/kaltura_logo_animated_blue_1_sec.jpg] [PASSED, RC: 0] - [1.093130377]
[Clipping 0_4rmmerom Succeeded] [PASSED, RC: 0] - [.776527135]
[Trimming 0_4rmmerom Succeeded] [PASSED, RC: 0] - [.365883073]
[Mock playback 0_4rmmerom succeeded] [PASSED, RC: 0] - [.417789535]
[Entry reconversion of 0_4rmmerom succeeded] [PASSED, RC: 0] - [1.303182756]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-kaltura@kaltura.com[PID is 101] in /var/log/maillog] [PASSED, RC: 0] - [30.041080097]
Testing analytics, be patient..
Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404
[DWH cycle] [FAILED, RC: 255] - [9.304118556]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [3.644164101]
[Upload bulk using CSV] [PASSED, RC: 0] - [.913104104]
[Upload bulk using XML] [PASSED, RC: 0] - [.602469005]
[Create player] [PASSED, RC: 0] - [.233573893]
[Generate thumb] [PASSED, RC: 0] - [1.311107783]
[Delete parnter] [PASSED, RC: 0] - [.501016481]
[Red5 file upload] [PASSED, RC: 0] - [3.269278343]
Thank you for running Kaltura! To keep Kaltura viable, stable and well tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.
Re-ran a fresh install following above recommendations. All is right with the world. Thanks Jess!
Good to hear:)
Happy Kalturing,