Is the machine hostname really tig03.hiphopservers.com? if so, is tig03.hiphopservers.com resolvable in the server?
Also, if yes, make sure the configuration in /opt/kaltura/app/configurations/batch/batch.ini is correct and has:
[tig03.hiphopservers.com : mainTemplate]
Then try:
# find /opt/kaltura/app/cache/ -type f -exec rm {} ;
# /etc/init.d/kaltura-batch restart
and recheck the log.
All subdomains used actually resolve to the server. tig03 is the actual name of the host itself. However, I used cdn as hostname when setting up Kaltura. I made the changes you recomended and restarted. This time the process kept running unlike before.
[root@tig03 ~]# nano /opt/kaltura/app/configurations/batch/batch.ini
[root@tig03 ~]# find /opt/kaltura/app/cache/ -type f -exec rm {} ;
[root@tig03 ~]# service kaltura-batch restart
Stopping Batch Manager…
Service Batch Manager not running [ FAILED ]
Starting Batch Manager…
Batch Manager started with PID [ OK ]
[root@tig03 ~]# /etc/init.d/kaltura-batch status
Batch Manager running with PID 4834 [ OK ]
This is what the log return after I completed the changes and restarted.
[root@tig03 ~]# kaltlog
==> /opt/kaltura/log/batch/dbcleanup-0-2016-02-28.err.log <==
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1300): KalturaClientBase->throwExceptionIfError(Array)
--
==> /opt/kaltura/log/batch/jobsuspender-0-2016-02-28.err.log <==
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1138): KalturaClientBase->throwExceptionIfError(Array)
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(640): KalturaClientBase->throwExceptionIfError(Array)
--
==> /opt/kaltura/log/batch/partnerloadcleanup-0-2016-02-28.err.log <==
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1123): KalturaClientBase->throwExceptionIfError(Array)
--
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4130): KalturaClientBase->throwExceptionIfError(Array)You’ll need to look at the lines leading to the final error to understand what’s causing it.
Is this error the reason my dropbox ingested videos are still in processing two days later? That is my only issue with the system. Should I delete the files entries in cue and let it repopulate to see if they process properly now? I am not sure what success path to take nor what is actually causing these errors.
Hi,
Seeing how ingesting files requires the batch daemon, yes, it is why it did not progress.
Assuming you got batch up and running now, the jobs should start processing. Regardless, need to check the logs and understand where the fatals are coming from.
I check the contents of this log file:
This is what was found in the log file:
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaC$
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1138): KalturaClientBase->throwExceptionIfError(Array)
#1 /opt/kaltura/app/batch/batches/Cleanup/KAsyncJobSuspender.class.php(28): KalturaBatchService->suspendJobs()
#2 /opt/kaltura/app/batch/batches/Cleanup/KAsyncJobSuspenderExe.php(11): KAsyncJobSuspender->run()
#3 {main}
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
Are there any other specific logs I should check to investigate this issue?
Hi,
Like I said, you need to check the lines leading to the final exception to understand what happened.
Also, look at /opt/kaltura/log/kaltura_api_v3.log which is the main API log.
In addition, what is not working currently?
Here is a copy of the caption log.
This is a just a sample of what I found in the log.
The specific issue I am having is; I place 1244 media files in various drop folders that I configured. They all were found and uploaded and eventually went into processing status. They have been in processing status for threed days now. None of them after three days is done or available for playback in Kaltura. So my only issue at this point is that none of the video ingested from dropbox are being trans coded and available to stream through Kaltura.
This is the only error I see in my ‘kaltlog’ at this point.
==> /opt/kaltura/log/kaltura_scripts.log <==
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(253): KalturaLog::err('Skipping call t...')
--
2016-03-08 18:55:12 [1457299858] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert('ERROR - Permiss...')
I have also updated the /opt/kaltura/log/kaltura_api_v3.log file found at the link provided with the current log since I re-installed a fresh copy of Kaltura using the most recent repository file and update RPM files.
As I attempted to explain before the issue I am having is KMC console shows that the files are detected then uploaded to system and then in processing. However, even after hours later none of the files every appear as done processing. Nor do any of the files ever appear in the Kaltura admin_console batch report as uploading, processing or completed.
Batch is running and active. The sample videos converted properly and appear in the concole as completed also they show in the batch console as when processing well. None of the media ingested via drop folder is being process to completion.
@jess
Please review my responses and proved some input on resolving this issue. This is the ONLY operational issue left for this specific installation. Since I need to ingest over 1000+ videos using the Drop Floder method I need to get Kaltura to complete the processing of each video after uploading. It is not giving me a failed error it just never moving past “processing” status after three days.
Here are the errors I found in the “kaltura_api_v3.log” previously provided.
2016-03-08 18:55:14 [0.000172] [107.152.128.122] [665107164] [120] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/api_v3/lib/types/KalturaObject.php line 377 - include_once(/opt/kaltura/app/cache//api_v3/fromObject/Map_KalturaUser_kuser.php): failed to open stream: No such file or directory
2016-03-08 18:55:14 [0.000078] [107.152.128.122] [665107164] [121] [API] [KalturaFrontController->errorHandler] WARN: /opt/kaltura/app/api_v3/lib/types/KalturaObject.php line 377 - include_once(): Failed opening '/opt/kaltura/app/cache//api_v3/fromObject/Map_KalturaUser_kuser.php' for inclusion (include_path='/opt/kaltura/app/vendor/htmlpurifier/library:/opt/kaltura/app/vendor/ZendFramework/library:.:/usr/share/pear:/usr/share/php:/opt/kaltura/app:/opt/kaltura/app/vendor/symfony:/opt/kaltura/app/vendor/symfony/vendor:/opt/kaltura/app/vendor/ZendFramework/library:/opt/kaltura/app/alpha:/opt/kaltura/app/alpha/lib:/opt/kaltura/app/alpha/apps/kaltura/lib')
Curently, this is the only errors I see it the log right now. I will re-run the DropFolder process with fewer files to import.
Your permissions of /opt/kaltura/app/cache/ are wrong.
# chown -R kaltura.apache /opt/kaltura/app/cache/
# chmod 775 /opt/kaltura/app/cache/
finally, remove old files with:
# find /opt/kaltura/app/cache/ -type f -exec rm {} ;
After completing the commands previously mention and following instructions found in this thread
I got rid of most of my errors except the following showing up in ‘kaltlog’ now.
--
2016-03-12 20:14:07 [0.003151] [107.152.128.122] [1684349000] [16] [API] [KalturaEntryService->prepareEntryForInsert] DEBUG: Creating new entry of API type [] core type [] class [entry]
2016-03-12 20:14:07 [0.000855] [107.152.128.122] [1684349000] [17] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Conversion profile id "11" not found' in /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php:503
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php(481): KalturaBaseEntry->validateConversionProfile(NULL)
--
2016-03-12 20:14:07 [0.000282] [107.152.128.122] [1684349000] [24] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.0001981258392334 seconds
2016-03-12 20:14:07 [0.000165] [107.152.128.122] [1684349000] [25] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Entry id "" not found' in /opt/kaltura/app/api_v3/services/BaseEntryService.php:108
Stack trace:
#0 [internal function]: BaseEntryService->addContentAction('', Object(KalturaDropFolderFileResource))
--
2016-03-12 20:14:09 [0.004065] [107.152.128.122] [1215345678] [16] [API] [KalturaEntryService->prepareEntryForInsert] DEBUG: Creating new entry of API type [] core type [] class [entry]
2016-03-12 20:14:09 [0.000892] [107.152.128.122] [1215345678] [17] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Conversion profile id "11" not found' in /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php:503
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php(481): KalturaBaseEntry->validateConversionProfile(NULL)
--
2016-03-12 20:14:09 [0.000322] [107.152.128.122] [1215345678] [24] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00022101402282715 seconds
2016-03-12 20:14:09 [0.000168] [107.152.128.122] [1215345678] [25] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Entry id "" not found' in /opt/kaltura/app/api_v3/services/BaseEntryService.php:108
Stack trace:
#0 [internal function]: BaseEntryService->addContentAction('', Object(KalturaDropFolderFileResource))
--
2016-03-12 20:15:48 [0.000271] [66.249.66.43] [717365057] [15] [PS2] [KalturaStatement->execute] DEBUG: Sql took - 0.00018787384033203 seconds
2016-03-12 20:15:48 [0.000188] [66.249.66.43] [717365057] [16] [PS2] [KExternalErrors::dieError] ERR: exception 'Exception' with message 'exiting on error 22 - requested ui_conf not found' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/KExternalErrors.class.php(128): KalturaLog::err('exiting on erro...')
--
2016-03-12 20:15:48 [0.000266] [66.249.66.40] [1250217625] [15] [PS2] [KalturaStatement->execute] DEBUG: Sql took - 0.00018501281738281 seconds
2016-03-12 20:15:48 [0.000191] [66.249.66.40] [1250217625] [16] [PS2] [KExternalErrors::dieError] ERR: exception 'Exception' with message 'exiting on error 22 - requested ui_conf not found' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/KExternalErrors.class.php(128): KalturaLog::err('exiting on erro...')
I am finding a lot of items not found. Regardless of which Coversion profile I select in the configuration menu I get the same error that it is not found.
I have completed the update to the latest version on one of my systems and I am still getting an error in my ‘kaltlog’ saying that my conversion profile is not found or missing. Please advise how I am to resolve this issue?
--
2016-03-15 12:33:37 [0.004787] [107.152.128.122] [1459366536] [16] [API] [KalturaEntryService->prepareEntryForInsert] DEBUG: Creating new entry of API type [] core type [] class [entry]
2016-03-15 12:33:37 [0.000945] [107.152.128.122] [1459366536] [17] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Conversion profile id "11" not found' in /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php:503
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/types/entry/KalturaBaseEntry.php(481): KalturaBaseEntry->validateConversionProfile(NULL)
--
2016-03-15 12:33:37 [0.000265] [107.152.128.122] [1459366536] [24] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00018095970153809 seconds
2016-03-15 12:33:37 [0.000153] [107.152.128.122] [1459366536] [25] [API] [KalturaFrontController->getExceptionObject] ERR: exception 'KalturaAPIException' with message 'Entry id "" not found' in /opt/kaltura/app/api_v3/services/BaseEntryService.php:108
Stack trace:
#0 [internal function]: BaseEntryService->addContentAction('', Object(KalturaDropFolderFileResource))Something is wrong with your DB deployment. This is shown by many of the logs you posted.
I honestly think the best thing to do is to drop the DB and repopulate it.
Follow https://github.com/kaltura/platform-install-packages/blob/Kajam-11.11.0/doc/kaltura-packages-faq.md#fresh-database-installation on how to do that.
If, when redeploying, you come across issues, report them with the exact logs and I’ll help you.
Correctly a bad DB deployment by hand is very complex and hardly worth the time.
Thank you,
I completed the reconfiguration. Here is what I came accross in the various logs
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
Nothing appears in the first two logs.
installPlugins.log
insertDefaults.log
I found the following errors in the ‘insertPermissions’ log.
2016-03-15 14:18:59 [KalturaStatement->execute] DEBUG: /* tig03.hiphopservers.com[928451227][propel] */ SELECT permission.ID, permission.TYPE, permission.NAME, permission.FRIENDLY_NAME, permission.DESCRIPTION, permission.PARTNER_ID, permission.STATUS, permission.DEPENDS_ON_PERMISSION_NAMES, permission.TAGS, permission.CREATED_AT, permission.UPDATED_AT, permission.CUSTOM_DATA FROM `permission` WHERE permission.NAME='PARTNER_-1_GROUP_*_PERMISSION' AND permission.TYPE IN ('1','4') AND permission.PARTNER_ID IN ('0','0','-1') AND permission.STATUS<>'3' LIMIT 1
2016-03-15 14:18:59 [KalturaStatement->execute] DEBUG: Sql took - 0.00021791458129883 seconds
2016-03-15 14:18:59 [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [PARTNER_-1_GROUP_*_PERMISSION] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert('ERROR - Permiss...')
#1 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(197): addItemToPermissions(Object(kApiActionPermissionItem), Array, '0')
#2 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(40): addActionPermissionItem(Object(Zend_Config))
#3 {main}
2016-03-15 14:18:59 [KalturaStatement->execute] DEBUG: /* tig03.hiphopservers.com[928451227][propel] */ SELECT permission_item.ID, permission_item.TYPE, permission_item.PARTNER_ID, permission_item.PARAM_1, permission_item.PARAM_2, permission_item.PARAM_3, permission_item.PARAM_4, permission_item.PARAM_5, permission_item.TAGS, permission_item.CREATED_AT, permission_item.UPDATED_AT, permission_item.CUSTOM_DATA FROM `permission_item` WHERE permission_item.PARAM_1='groupuser' AND permission_item.PARAM_2='delete' AND permission_item.PARTNER_ID IN ('0','0') AND permission_item.TYPE='kApiActionPermissionItem' LIMIT 1
2016-03-15 14:18:59 [KalturaStatement->execute] DEBUG: Sql took - 0.00014710426330566 seconds
2016-03-15 14:18:59 [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [PARTNER_-1_GROUP_*_PERMISSION] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert('ERROR - Permiss...')
#1 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(197): addItemToPermissions(Object(kApiActionPermissionItem), Array, '0')
#2 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(40): addActionPermissionItem(Object(Zend_Config))
#3 {main}
2016-03-15 14:18:59 [KalturaStatement->execute] DEBUG: Sql took - 0.00021481513977051 seconds
2016-03-15 14:18:59 [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [PARTNER_-1_GROUP_*_PERMISSION] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert('ERROR - Permiss...')
#1 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(197): addItemToPermissions(Object(kApiActionPermissionItem), Array, '0')
#2 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(40): addActionPermissionItem(Object(Zend_Config))
#3 {main}
2016-03-15 14:19:45 [KalturaStatement->execute] DEBUG: /* tig03.hiphopservers.com[1783304601][propel] */ SELECT permission_item.ID, permission_item.TYPE, permission_item.PARTNER_ID, permission_item.PARAM_1, permission_item.PARAM_2, permission_item.PARAM_3, permission_item.PARAM_4, permission_item.PARAM_5, permission_item.TAGS, permission_item.CREATED_AT, permission_item.UPDATED_AT, permission_item.CUSTOM_DATA FROM `permission_item` WHERE permission_item.PARAM_1='stats' AND permission_item.PARAM_2='reportkceerror' AND permission_item.PARTNER_ID IN ('0','0') AND permission_item.TYPE='kApiActionPermissionItem' LIMIT 1
2016-03-15 14:19:45 [KalturaStatement->execute] DEBUG: Sql took - 0.00048184394836426 seconds
2016-03-15 14:19:45 [KalturaStatement->execute] DEBUG: /* tig03.hiphopservers.com[1783304601][propel] */ INSERT INTO permission_item (`ID`,`TYPE`,`PARTNER_ID`,`PARAM_1`,`PARAM_2`,`PARAM_3`,`PARAM_4`,`PARAM_5`,`TAGS`,`CREATED_AT`,`UPDATED_AT`) VALUES (NULL,'kApiActionPermissionItem','0','stats','reportkceerror','','','','','2016-03-15 14:19:45','2016-03-15 14:19:45')
2016-03-15 14:19:45 [KalturaStatement->execute] DEBUG: Sql took - 0.022797107696533 seconds
2016-03-15 14:19:45 [kObjectCreatedEvent->__construct] DEBUG: Event [kObjectCreatedEvent] object type [kApiActionPermissionItem] id [271]
2016-03-15 14:19:45 [kObjectSavedEvent->__construct] DEBUG: Event [kObjectSavedEvent] object type [kApiActionPermissionItem] id [271]
2016-03-15 14:19:45 [addActionPermissionItem] NOTICE: New permission item id [271] added for [stats->reportkceerror] partner id [0]
Everything after that seems to repeat the same errors over and over. I will submit the result of the DWH logs in my other thread related to analytic reporting issues.
Let me note that my installation is configured as an SSL installation. I have done two other installation with non-SSL and oddly even with the various issues. When I run the config all script it actually runs completely though without errors assuming everything is in order. The SSL enable configuration never runs completely without breaking at the same part.
This then requires me to fix the issue in the non httpd zzzkaltura.conf file then manually re-run the last two steps of the script. My guess is that this is part of the issue with the configuration never actually completing fully. If I am missing some of the steps after the break point then this could be the point where things go array.
Generating UI confs..
Shutting down monit: [FAILED]
Starting monit: Starting Monit 5.13 daemon with http interface at [*]:2812
[ OK ]
Running Batch config...
kaltura-batch-11.10.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
Reloading httpd: not reloading due to configuration syntax error
[FAILED]
kaltura-batch-config.sh FAILED with: 18597 on line 98
Archving logs to /opt/kaltura/log/log_15_03_16_19_37.tar.gz...
ERROR: /opt/kaltura/bin/kaltura-batch-config.sh failed:( You can re-run it when the issue is fixed.
The issue causing the break here is the script does not correctly insert the proper token values for the HTTP port and paths to the log files. So HTTPD can not properly restart. I would request that this be fixed to work properly during SSL installation on RPM setups in the next release. It would make for a smoother install avoiding breaking the system installation.
I figured out what the missing or unable to find transcoding profile comes from. By default there is only one Transcoding profile for each publisher and that is the default which is profile number 6. However, when setting up a drop folder you get multiple option to choose from depending on what you have setup in your configuration for that publisher. None, of them work except the default because none of them existing in the Publishers transcoding profile list except the Default (6).
Hence the error I was getting because profiles number 11 and 14 do not existing for any users including administrator. I am not sure why they even appear in the list not why passthrough which is number 11 is the default if the default (6) is the only one that works.
Now, that Kaltura is ingesting the videos and attempting to encode them my next problem is after Kaltura connects to my host and captures a list of files to ingest ‘kaltlog’ spits the following error.
--
2016-03-15 21:55:16 [0.000668] [1750917290] [22] [BATCH] [KCurlWrapper->setSourceUrlAndprotocol] INFO: Setting source URL to [ftp://ftpuser@bbwcamhouse.com:passcode@bbwcamhouse.com/vod_import/1057.mp4]
2016-03-15 21:55:16 [0.048919] [1750917290] [23] [BATCH] [KJobHandlerWorker->closeJob] ERR: exception 'Exception' with message 'Couldn't read file. Error: Couldn't resolve host 'bbwcamhouse.com:passocde@bbwcamhouse.com'' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/batch/batches/KJobHandlerWorker.class.php(372): KalturaLog::err('Couldn't read f...')
The second pass to connect is not using proper syntax to connect to the FTP host again. Neither by browser or FTP client. An it should not be trying to connect using a web accessable directory because there isn’t one. Hence the reason for connect via FTP. I have no clue why it is passing the connection information in this way.
Please provide the output of:
mysql> select * from drop_folder\G
While masking your user, passwd and actual host of course and I’ll take a look.
Return the following information:
*************************** 1. row ***************************
id: 1
partner_id: 99
name: VOD
description: Test
type: 2
status: 1
dc: 0
path: /vod_import
conversion_profile_id: 6
file_delete_policy: 3
file_handler_type: 1
file_name_patterns: *
file_handler_config: O:34:“DropFolderContentFileHandlerConfig”:3:{s:54:" DropFolderContentFileHandlerConfig contentMatchPolicy";i:1;s:45:" DropFolderContentFileHandlerConfig slugRegex";s:30:"/(?P.+)[.]\w{2,}/";s:14:" * handlerType";i:1;}
tags: bbwch
error_code: NULL
error_description: NULL
created_at: 2016-03-15 21:47:07
updated_at: 2016-03-16 12:16:01
custom_data: a:14:{s:24:“file_size_check_interval”;i:30;s:21:“auto_file_delete_days”;i:0;s:25:“ignore_file_name_patterns”;s:0:"";s:11:“incremental”;b:1;s:19:“metadata_profile_id”;i:0;s:30:“categories_metadata_field_name”;s:0:"";s:19:“enforce_entitlement”;b:0;s:18:“should_validate_ks”;b:0;s:8:“ftp_host”;s:15:“mydomain.com";s:8:“ftp_port”;i:21;s:12:“ftp_username”;s:20:"ftpuser@mydomain.com”;s:12:“ftp_password”;s:9:“the-passowrd”;s:16:“last_accessed_at”;i:1458144961;s:19:“last_file_timestamp”;i:1458092760;}
1 row in set (0.00 sec)
The information here and what was display at the time of the error are different. As I mention part of the information in the second pass to connect was cut off in review of the error log.