New to percdata, can't pass connection verification

Discuss all DVBLink EPG Loader products here!

New to percdata, can't pass connection verification

Postby linguica101 » Sun Jun 26, 2016 5:29 pm

So I just signed up for trial of percdata and I entered my login and password for it on the dvblink epg loader plugin, but it says "connection test failed"

What did I do wrong?

I'm using dvblink server 4.6 and Dvblink EPG loader for percdata build 8669
linguica101
 
Posts: 49
Joined: Wed Feb 15, 2012 3:11 am


Re: New to percdata, can't pass connection verification

Postby rmeden » Mon Jun 27, 2016 3:46 pm

on the percdata credentials, are you using your Perc username or email? (they are not necessarily the same)
rmeden
 
Posts: 11
Joined: Thu May 30, 2013 6:55 pm

Re: New to percdata, can't pass connection verification

Postby linguica101 » Mon Jun 27, 2016 4:38 pm

I've tried both, using the login username and the email used to sign up. Both come back with the same results: "connection test failed"
linguica101
 
Posts: 49
Joined: Wed Feb 15, 2012 3:11 am

Re: New to percdata, can't pass connection verification

Postby linguica101 » Tue Jun 28, 2016 4:35 pm

Any one? I'm running out of days for my free trial of percdata and from what I've read this is the missing piece I need to get rid of WMC completely.
linguica101
 
Posts: 49
Joined: Wed Feb 15, 2012 3:11 am

Re: New to percdata, can't pass connection verification

Postby the_man » Wed Jun 29, 2016 2:49 pm

You may ask the new trial for percdata loader at the info@dvblogic.com

As for issue. Most probably it is the firewall or antivirus issue. Try to disable all of them, make a repair of the loader and check the connection once more.
NETGEAR RNDU2000; Synology DS112j, DS 212j, DS213+, DS 712+; Western Digital WD ex2; Asustor AS3, RPI2 ...
PCTV 460,461e,292e; TT 4400, 4650CI;DVBSKy S960; DD octopus net; Inverto sat2ip multibox; TBS DVB-C ...
the_man
 
Posts: 4696
Joined: Mon Dec 02, 2013 1:11 pm

Re: New to percdata, can't pass connection verification

Postby lotsacaffeine » Tue Jul 19, 2016 5:02 am

I have a paid account...a fresh install...and a registered Perc plug-in and get the same message.



016-Jul-18 22:41:21: ==============================================================
2016-Jul-18 22:41:21: Logging is started
2016-Jul-18 22:41:21: ==============================================================
2016-Jul-18 22:41:21: [I] DVBLink server product id: xxxxx
2016-Jul-18 22:41:21: [I] ---------------------------
2016-Jul-18 22:41:21: [I] Installed DVBLink products:
2016-Jul-18 22:41:21: [I] DVBLink Server, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink TVSource, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink for IPTV, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink EPG Loader for PercData, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] ---------------------------
2016-Jul-18 22:41:43: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:46: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:49: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:52: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:55: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:58: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:01: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:04: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:07: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:10: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:13: [E] epg_storage::update_epg_impl(): 10 attemps of provider_->get_channel_list() failed
lotsacaffeine
 
Posts: 1
Joined: Tue Jul 19, 2016 4:48 am

Re: New to percdata, can't pass connection verification

Postby the_man » Tue Jul 19, 2016 11:03 am

lotsacaffeine wrote:I have a paid account...a fresh install...and a registered Perc plug-in and get the same message.



016-Jul-18 22:41:21: ==============================================================
2016-Jul-18 22:41:21: Logging is started
2016-Jul-18 22:41:21: ==============================================================
2016-Jul-18 22:41:21: [I] DVBLink server product id: xxxxx
2016-Jul-18 22:41:21: [I] ---------------------------
2016-Jul-18 22:41:21: [I] Installed DVBLink products:
2016-Jul-18 22:41:21: [I] DVBLink Server, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink TVSource, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink for IPTV, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] DVBLink EPG Loader for PercData, 6.0.0, 12901
2016-Jul-18 22:41:21: [I] ---------------------------
2016-Jul-18 22:41:43: [E] PercData: start EPG update session failed
2016-Jul-18 22:41:46: [E] PercData: start EPG update session failed
2016-Jul-18 22:42:13: [E] epg_storage::update_epg_impl(): 10 attemps of provider_->get_channel_list() failed

May you check your login data for PercData at the PercData site?
Then set log level to info at the DVBlink web UI -> General Settings and reproduce the issue with activation the EPGLoader at the Sources-> EPGSources. And attach zipped log files here.
NETGEAR RNDU2000; Synology DS112j, DS 212j, DS213+, DS 712+; Western Digital WD ex2; Asustor AS3, RPI2 ...
PCTV 460,461e,292e; TT 4400, 4650CI;DVBSKy S960; DD octopus net; Inverto sat2ip multibox; TBS DVB-C ...
the_man
 
Posts: 4696
Joined: Mon Dec 02, 2013 1:11 pm

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Wed Aug 16, 2017 11:54 pm

I just started having a similar issue with the PercData plugin not downloading guide data, this after working since Jan. of this year. If I click on the configure/wrench icon for PercData, I just get an un-ending Wait dialog. I've tried repairing, uninstalling PercData (that hangs), uninstalling and reinstalling DvbLink Server several times. I enter my login/password and check the connection and that is fine. But I never see PercData show up in the Channels - EPG Sources selection box. Log file attached. This is on a Synology DS1513+ NAS. The TV Source plug-in works fine as does the ATSC/EIT scanner and I do see that EPG source in the Channels menu.
Attachments
dvblink-log-20170816-1542.zip
(79.47 KiB) Downloaded 68 times
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA

Re: New to percdata, can't pass connection verification

Postby the_man » Thu Aug 17, 2017 2:57 pm

Your log files looks good. Please try to disable the firewall on the NAS if it is enabled. Also check the date/time on the NAS, is it correct?
NETGEAR RNDU2000; Synology DS112j, DS 212j, DS213+, DS 712+; Western Digital WD ex2; Asustor AS3, RPI2 ...
PCTV 460,461e,292e; TT 4400, 4650CI;DVBSKy S960; DD octopus net; Inverto sat2ip multibox; TBS DVB-C ...
the_man
 
Posts: 4696
Joined: Mon Dec 02, 2013 1:11 pm

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Thu Aug 17, 2017 7:55 pm

the_man wrote:Your log files looks good. Please try to disable the firewall on the NAS if it is enabled. Also check the date/time on the NAS, is it correct?


The time looks good, the NAS is set up for a network time server. I've not changed the firewall settings on the NAS in several years. Is there any specific port that I need to check? I'm hesitant to turn off the firewall as the NAS gets hit periodically by hackers trying to log in.

I did have the cable/ISP company change out my cable modem/gateway on Monday from an SMC to a Cisco unit. I've tried to set it up as close as possible to the old unit and have the firewall set to the "lowest security" option. Any specific ports I need to open up?

I'm unable to delete the PercData-1 EPG source nor am I able to delete the PercData EPG loader plugin. Doing either of those causes the DvbLink server to not be responsive. Also hangs if I try to edit the PercData-1 instance (wrench icon) once it has been configured.

I also get the flashing red triangle notification saying I have an EPG source that's not been assigned to any channels, yet when I go to the Channels-EPG tab, I only see the TVSource (EIT) EPG source available. PercData doesn't show up there at all.

I tried repairing the recorder database, both with the Settings-Recorder button and also with the sqllite.exe manual process. No change in the issue.
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Sat Aug 19, 2017 7:30 pm

I uninstalled DvbLink, the turned off the NAS firewall and reinstalled the server, TV Source and PercData. I'll attach the log file from that session, but there is no difference, the PercData-1 EPG source still is not there after 40 minutes or so. I also still get the flashing red notification triangle saying I have an EPG source that's not assigned to any channels. Yet in Channels->EPG Sources I only see TVSource-1.

I can't upload the attachment due to this error: "Sorry, the board attachment quota has been reached."
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Tue Aug 22, 2017 2:02 am

I've tried uninstalling and reinstalling the DVBLink server and add-ons and now I can only get the Server to load. When I try to install the TVsource add-on, the DVBLink Viewer just hangs with the "Please wait..." dialog for 15 minutes then finally times out saying "Installation error". I can't seem to get it to do anything more than this. I've tried both the latest server build off the DVBlogic downloads page as well as the original Synology supplied version with no change. I tried turning off the firewall on my new cable modem/gateway and no change.

Still can't upload attachments, but here's the dvblink_server.log file from the latest install session:
Code: Select all
2017-Aug-21 17:08:49:   
2017-Aug-21 17:08:49:   ==============================================================
2017-Aug-21 17:08:49:                      Logging is started
2017-Aug-21 17:08:49:   ==============================================================
2017-Aug-21 17:08:49:   [I] DVBLink server product id: 189954c4-29ae-4b7c-bea8-14a98884a565
2017-Aug-21 17:08:49:   [I] ---------------------------
2017-Aug-21 17:08:49:   [I] Installed DVBLink products:
2017-Aug-21 17:08:49:   [I] DVBLink Server, 6.0.0, 14499
2017-Aug-21 17:08:49:   [I] ---------------------------
2017-Aug-21 17:10:52:   [I] epg_updater_t::update_thread_func. epg updater thread has finished
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::reset. There is no wakeup timer currently set
2017-Aug-21 17:10:52:   [I] recorder_engine::purge_schedules.
2017-Aug-21 17:10:52:   [I] recorder_engine::purge_deleted_recordings.
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 1
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 2
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 4
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 6
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 10
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 11
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 12
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 13
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 14
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 19
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 20
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 21
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 22
2017-Aug-21 17:10:52:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 23
2017-Aug-21 17:19:47:   [I] package_manager_t::preinstall_package. Starting preinstall for package.dvk
2017-Aug-21 17:19:47:   [I] external_control::untar: Starting untar process for /var/packages/DVBLinkServer/target/packages/temp/package.dvk
2017-Aug-21 17:19:47:   [I] external_control::untar. start tar: "tar" xvzf "/var/packages/DVBLinkServer/target/packages/temp/package.dvk" -C "/var/packages/DVBLinkServer/target/packages/temp/e95e5d1c-6f4b-4174-9768-6c76e2b1455b"
2017-Aug-21 17:19:48:   [I] external_control::untar. tar returned: -1
2017-Aug-21 17:19:48:   [I] external_control::untar: tar process finished successfully
2017-Aug-21 17:19:48:   [I] package_manager_t::preinstall_package. Reading package information from /var/packages/DVBLinkServer/target/packages/temp/e95e5d1c-6f4b-4174-9768-6c76e2b1455b/package.xml
2017-Aug-21 17:19:48:   [E] package_manager_t::preinstall_package. Failed to read the package information for package.dvk
2017-Aug-21 17:20:11:   [I] Received SIGINT: Interrupt from keyboard.
2017-Aug-21 17:20:12:   [I] broker::shutdown(): begin...
2017-Aug-21 17:20:12:   [E] unknown error in py part
2017-Aug-21 17:22:12:   
2017-Aug-21 17:22:12:   ==============================================================
2017-Aug-21 17:22:12:                      Logging is started
2017-Aug-21 17:22:12:   ==============================================================
2017-Aug-21 17:22:12:   [I] log_server. address: localhost, port: 39880
2017-Aug-21 17:22:12:   [I] dvblink_server daemon started (pid=3749)
2017-Aug-21 17:22:12:   [I] DVBLink server product id: 189954c4-29ae-4b7c-bea8-14a98884a565
2017-Aug-21 17:22:12:   [I] ---------------------------
2017-Aug-21 17:22:12:   [I] Installed DVBLink products:
2017-Aug-21 17:22:12:   [I] DVBLink Server, 6.0.0, 14499
2017-Aug-21 17:22:12:   [I] ---------------------------
2017-Aug-21 17:22:12:   [I] broker::start(): Waiting for network initialization...
2017-Aug-21 17:22:12:   [I] broker::start(): Continue with start-up
2017-Aug-21 17:22:12:   [I] configuration_server. address: localhost, port: 39877
2017-Aug-21 17:22:12:   [I] channel_logo_manager::init()
2017-Aug-21 17:22:12:   [I] sink_manager::start(): Found 3 modules
2017-Aug-21 17:22:12:   [I] sink_manager::load_mod(): Loading module "dlna_server"
2017-Aug-21 17:22:12:   [I] sink_base::start(): sink dlna_server, get cluster_interface...
2017-Aug-21 17:22:12:   [I] sink_base::start(): sink dlna_server, get cluster_interface... found
2017-Aug-21 17:22:12:   [I] sink_base::start(): sink dlna_server, cluster initializing...
2017-Aug-21 17:22:12:   [I] dlna_server: initialization started
2017-Aug-21 17:22:12:   [I] dlna_server: initialization finished
2017-Aug-21 17:22:12:   [I] sink_base::start(): sink dlna_server, cluster initializing... succeeded
2017-Aug-21 17:22:12:   [I] sink_base::start(): sink dlna_server, sink::instance_quantity() returned 8
2017-Aug-21 17:22:14:   [I] sink::get_recorder_interface(): sink dlna_server, get recorder_interface...
2017-Aug-21 17:22:14:   [I] sink::get_recorder_interface(): sink dlna_server, get recorder_interface... NOT FOUND
2017-Aug-21 17:22:14:   [I] sink_manager::load_mod(): module "dlna_server" loaded successfully
2017-Aug-21 17:22:14:   [I] sink_manager::load_mod(): Loading module "dlrecorder"
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink dlrecorder, get cluster_interface...
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink dlrecorder, get cluster_interface... found
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink dlrecorder, cluster initializing...
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink dlrecorder, cluster initializing... succeeded
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink dlrecorder, sink::instance_quantity() returned 16
2017-Aug-21 17:22:14:   [I] sink::get_recorder_interface(): sink dlrecorder, get recorder_interface...
2017-Aug-21 17:22:14:   [I] sink::get_recorder_interface(): sink dlrecorder, get recorder_interface... found
2017-Aug-21 17:22:14:   [I] sink_manager::load_mod(): module "dlrecorder" loaded successfully
2017-Aug-21 17:22:14:   [I] sink_manager::load_mod(): Loading module "network_streamer"
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink network_streamer, get cluster_interface...
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink network_streamer, get cluster_interface... found
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink network_streamer, cluster initializing...
2017-Aug-21 17:22:14:   [I] configuration_server. address: localhost, port: 39881
2017-Aug-21 17:22:14:   [I] network_streamer::init: number of sinks 8
2017-Aug-21 17:22:14:   [I] network_streamer: initialization succeeded
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink network_streamer, cluster initializing... succeeded
2017-Aug-21 17:22:14:   [I] sink_base::start(): sink network_streamer, sink::instance_quantity() returned 8
2017-Aug-21 17:22:15:   [I] Starting external port mapper. Mapping mask 0
2017-Aug-21 17:22:15:   [I] sink::get_recorder_interface(): sink network_streamer, get recorder_interface...
2017-Aug-21 17:22:15:   [I] sink::get_recorder_interface(): sink network_streamer, get recorder_interface... NOT FOUND
2017-Aug-21 17:22:15:   [I] sink_manager::load_mod(): module "network_streamer" loaded successfully
2017-Aug-21 17:22:15:   [I] sink_manager::start(): 3 modules have been loaded
2017-Aug-21 17:22:15:   [I] aux_manager::start(): Found 2 modules
2017-Aug-21 17:22:15:   [I] aux_manager::load_mod(): Loading module "social"
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux social, get cluster_interface...
2017-Aug-21 17:22:15:   [I] aux_base::start(): aux social, get cluster_interface... found
2017-Aug-21 17:22:15:   [I] aux_base::start(): aux social, cluster initializing...
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux social, cluster initializing... succeeded
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux social, aux::instance_quantity() returned 1
2017-Aug-21 17:22:15:   [I] send_to_manager::manager_thread_function. Starting main processing thread. Waiting for DVBLink server to become operational
2017-Aug-21 17:22:15:   [I] aux_manager::load_mod(): module "social" loaded successfully
2017-Aug-21 17:22:15:   [I] aux_manager::load_mod(): Loading module "updater"
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux updater, get cluster_interface...
2017-Aug-21 17:22:15:   [I] aux_base::start(): aux updater, get cluster_interface... found
2017-Aug-21 17:22:15:   [I] aux_base::start(): aux updater, cluster initializing...
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux updater, cluster initializing... succeeded
2017-Aug-21 17:22:15:   [I] aux_cluster::start(): aux updater, aux::instance_quantity() returned 1
2017-Aug-21 17:22:15:   [I] aux_manager::load_mod(): module "updater" loaded successfully
2017-Aug-21 17:22:15:   [I] aux_manager::start(): 2 modules have been loaded
2017-Aug-21 17:22:15:   [I] updater_engine::updater_thread_function. Next update check is scheduled for 1503446400
2017-Aug-21 17:22:15:   [I] source_manager::init(): Found 1 sources
2017-Aug-21 17:22:15:   [I] source_manager::load_source(): "52f25a9b-379d-4bbb-a3e4-cd4309732468"
2017-Aug-21 17:22:15:   [I] source_module::load(): Loading module "52f25a9b-379d-4bbb-a3e4-cd4309732468"
2017-Aug-21 17:22:15:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, get cluster interface...
2017-Aug-21 17:22:15:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, get cluster interface... succeeded
2017-Aug-21 17:22:15:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, init cluster interface...
2017-Aug-21 17:22:15:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, init cluster interface... succeeded
2017-Aug-21 17:22:15:   [I] source::create_source_instance(): 52f25a9b-379d-4bbb-a3e4-cd4309732468 {aa4c94b8-6779-4e6b-89e4-e6830d010a40} succeeded
2017-Aug-21 17:22:15:   [I] source_manager::load_source(): "play_error_ts"
2017-Aug-21 17:22:15:   [I] source::init(): source play_error_ts, create cluster interface...
2017-Aug-21 17:22:15:   [I] source::init(): source play_error_ts, create cluster interface... succeeded
2017-Aug-21 17:22:15:   [I] source::init(): source play_error_ts, init cluster interface...
2017-Aug-21 17:22:15:   [I] source::init(): source play_error_ts, init cluster interface... succeeded
2017-Aug-21 17:22:15:   [I] source::create_source_instance(): play_error_ts {0050bcf3-cff8-4c8c-b03f-34d1cebb02c9} succeeded
2017-Aug-21 17:22:15:   [I] source::create_source_instance(): play_error_ts {3c19f447-4cfd-46b5-9d03-7c3521c37661} succeeded
2017-Aug-21 17:22:15:   [I] source::create_source_instance(): play_error_ts[3] {dfa2d29e-8ecf-42bc-951e-90f0d4fe68ee} succeeded
2017-Aug-21 17:22:15:   [I] discovery_server started
2017-Aug-21 17:22:15:   [I] sink::init_recorder_interface(): sink dlrecorder, recorder initialization...
2017-Aug-21 17:22:15:   [I] sink::init_recorder_interface(): sink dlrecorder, recorder initialization... succeeded
2017-Aug-21 17:22:15:   [I] Setting up default recorder ID and IP address to local machine
2017-Aug-21 17:22:15:   [I] recorder_database_t::init(): Opening database file /var/packages/DVBLinkServer/target/share/database/dlrecorder.db
2017-Aug-21 17:22:15:   [I] recorder_engine::recorder_thread_func(). Started.
2017-Aug-21 17:22:15:   [I] broker::start(): ...succeded
2017-Aug-21 17:22:15:   [I] recorder_engine::run_active(). Switched to active mode
2017-Aug-21 17:22:15:   [I] recorder_engine::run_active(). Waiting for DVBLink server to become operational
2017-Aug-21 17:22:15:   [I] recorder_engine::run_active(). DVBLink server is operational. Continue with rescheduling
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::reset. There is no wakeup timer currently set
2017-Aug-21 17:22:15:   [I] recorder_engine::purge_schedules.
2017-Aug-21 17:22:15:   [I] recorder_engine::purge_deleted_recordings.
2017-Aug-21 17:22:15:   [I] send_to_manager::manager_thread_function. DVBLink server is operational
2017-Aug-21 17:22:15:   [I] send_to_manager::apply_power_state. Enabling standby
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 1
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 2
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 4
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 6
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 10
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 11
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 12
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 13
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 14
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 19
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 20
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 21
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 22
2017-Aug-21 17:22:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 23
2017-Aug-21 17:24:15:   [I] epg_updater_t::update_thread_func. epg updater thread has finished
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::reset. There is no wakeup timer currently set
2017-Aug-21 17:24:15:   [I] recorder_engine::purge_schedules.
2017-Aug-21 17:24:15:   [I] recorder_engine::purge_deleted_recordings.
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 1
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 2
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 4
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 6
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 10
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 11
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 12
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 13
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 14
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 19
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 20
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 21
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 22
2017-Aug-21 17:24:15:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 23
2017-Aug-21 17:40:11:   [I] Received SIGINT: Interrupt from keyboard.
2017-Aug-21 17:40:11:   [I] broker::shutdown(): begin...
2017-Aug-21 17:40:11:   [E] unknown error in py part
2017-Aug-21 17:41:30:   
2017-Aug-21 17:41:30:   ==============================================================
2017-Aug-21 17:41:30:                      Logging is started
2017-Aug-21 17:41:30:   ==============================================================
2017-Aug-21 17:41:30:   [I] log_server. address: localhost, port: 39880
2017-Aug-21 17:41:30:   [I] dvblink_server daemon started (pid=11224)
2017-Aug-21 17:41:30:   [I] DVBLink server product id: 189954c4-29ae-4b7c-bea8-14a98884a565
2017-Aug-21 17:41:31:   [I] ---------------------------
2017-Aug-21 17:41:31:   [I] Installed DVBLink products:
2017-Aug-21 17:41:31:   [I] DVBLink Server, 6.0.0, 14499
2017-Aug-21 17:41:31:   [I] ---------------------------
2017-Aug-21 17:41:31:   [I] broker::start(): Waiting for network initialization...
2017-Aug-21 17:41:31:   [I] broker::start(): Continue with start-up
2017-Aug-21 17:41:31:   [I] configuration_server. address: localhost, port: 39877
2017-Aug-21 17:41:31:   [I] channel_logo_manager::init()
2017-Aug-21 17:41:31:   [I] sink_manager::start(): Found 3 modules
2017-Aug-21 17:41:31:   [I] sink_manager::load_mod(): Loading module "dlna_server"
2017-Aug-21 17:41:31:   [I] sink_base::start(): sink dlna_server, get cluster_interface...
2017-Aug-21 17:41:31:   [I] sink_base::start(): sink dlna_server, get cluster_interface... found
2017-Aug-21 17:41:31:   [I] sink_base::start(): sink dlna_server, cluster initializing...
2017-Aug-21 17:41:31:   [I] dlna_server: initialization started
2017-Aug-21 17:41:31:   [I] dlna_server: initialization finished
2017-Aug-21 17:41:31:   [I] sink_base::start(): sink dlna_server, cluster initializing... succeeded
2017-Aug-21 17:41:31:   [I] sink_base::start(): sink dlna_server, sink::instance_quantity() returned 8
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink dlna_server, get recorder_interface...
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink dlna_server, get recorder_interface... NOT FOUND
2017-Aug-21 17:41:33:   [I] sink_manager::load_mod(): module "dlna_server" loaded successfully
2017-Aug-21 17:41:33:   [I] sink_manager::load_mod(): Loading module "dlrecorder"
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink dlrecorder, get cluster_interface...
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink dlrecorder, get cluster_interface... found
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink dlrecorder, cluster initializing...
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink dlrecorder, cluster initializing... succeeded
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink dlrecorder, sink::instance_quantity() returned 16
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink dlrecorder, get recorder_interface...
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink dlrecorder, get recorder_interface... found
2017-Aug-21 17:41:33:   [I] sink_manager::load_mod(): module "dlrecorder" loaded successfully
2017-Aug-21 17:41:33:   [I] sink_manager::load_mod(): Loading module "network_streamer"
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink network_streamer, get cluster_interface...
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink network_streamer, get cluster_interface... found
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink network_streamer, cluster initializing...
2017-Aug-21 17:41:33:   [I] configuration_server. address: localhost, port: 39881
2017-Aug-21 17:41:33:   [I] network_streamer::init: number of sinks 8
2017-Aug-21 17:41:33:   [I] network_streamer: initialization succeeded
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink network_streamer, cluster initializing... succeeded
2017-Aug-21 17:41:33:   [I] sink_base::start(): sink network_streamer, sink::instance_quantity() returned 8
2017-Aug-21 17:41:33:   [I] Starting external port mapper. Mapping mask 0
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink network_streamer, get recorder_interface...
2017-Aug-21 17:41:33:   [I] sink::get_recorder_interface(): sink network_streamer, get recorder_interface... NOT FOUND
2017-Aug-21 17:41:33:   [I] sink_manager::load_mod(): module "network_streamer" loaded successfully
2017-Aug-21 17:41:33:   [I] sink_manager::start(): 3 modules have been loaded
2017-Aug-21 17:41:33:   [I] aux_manager::start(): Found 2 modules
2017-Aug-21 17:41:33:   [I] aux_manager::load_mod(): Loading module "social"
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux social, get cluster_interface...
2017-Aug-21 17:41:33:   [I] aux_base::start(): aux social, get cluster_interface... found
2017-Aug-21 17:41:33:   [I] aux_base::start(): aux social, cluster initializing...
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux social, cluster initializing... succeeded
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux social, aux::instance_quantity() returned 1
2017-Aug-21 17:41:33:   [I] aux_manager::load_mod(): module "social" loaded successfully
2017-Aug-21 17:41:33:   [I] aux_manager::load_mod(): Loading module "updater"
2017-Aug-21 17:41:33:   [I] send_to_manager::manager_thread_function. Starting main processing thread. Waiting for DVBLink server to become operational
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux updater, get cluster_interface...
2017-Aug-21 17:41:33:   [I] aux_base::start(): aux updater, get cluster_interface... found
2017-Aug-21 17:41:33:   [I] aux_base::start(): aux updater, cluster initializing...
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux updater, cluster initializing... succeeded
2017-Aug-21 17:41:33:   [I] aux_cluster::start(): aux updater, aux::instance_quantity() returned 1
2017-Aug-21 17:41:33:   [I] aux_manager::load_mod(): module "updater" loaded successfully
2017-Aug-21 17:41:33:   [I] aux_manager::start(): 2 modules have been loaded
2017-Aug-21 17:41:33:   [I] source_manager::init(): Found 1 sources
2017-Aug-21 17:41:33:   [I] updater_engine::updater_thread_function. Next update check is scheduled for 1503446400
2017-Aug-21 17:41:33:   [I] source_manager::load_source(): "52f25a9b-379d-4bbb-a3e4-cd4309732468"
2017-Aug-21 17:41:33:   [I] source_module::load(): Loading module "52f25a9b-379d-4bbb-a3e4-cd4309732468"
2017-Aug-21 17:41:33:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, get cluster interface...
2017-Aug-21 17:41:33:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, get cluster interface... succeeded
2017-Aug-21 17:41:33:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, init cluster interface...
2017-Aug-21 17:41:33:   [I] source::init(): source 52f25a9b-379d-4bbb-a3e4-cd4309732468, init cluster interface... succeeded
2017-Aug-21 17:41:34:   [I] source::create_source_instance(): 52f25a9b-379d-4bbb-a3e4-cd4309732468 {aa4c94b8-6779-4e6b-89e4-e6830d010a40} succeeded
2017-Aug-21 17:41:34:   [I] source_manager::load_source(): "play_error_ts"
2017-Aug-21 17:41:34:   [I] source::init(): source play_error_ts, create cluster interface...
2017-Aug-21 17:41:34:   [I] source::init(): source play_error_ts, create cluster interface... succeeded
2017-Aug-21 17:41:34:   [I] source::init(): source play_error_ts, init cluster interface...
2017-Aug-21 17:41:34:   [I] source::init(): source play_error_ts, init cluster interface... succeeded
2017-Aug-21 17:41:34:   [I] source::create_source_instance(): play_error_ts {0050bcf3-cff8-4c8c-b03f-34d1cebb02c9} succeeded
2017-Aug-21 17:41:34:   [I] source::create_source_instance(): play_error_ts {3c19f447-4cfd-46b5-9d03-7c3521c37661} succeeded
2017-Aug-21 17:41:34:   [I] source::create_source_instance(): play_error_ts[3] {dfa2d29e-8ecf-42bc-951e-90f0d4fe68ee} succeeded
2017-Aug-21 17:41:34:   [I] discovery_server started
2017-Aug-21 17:41:34:   [I] sink::init_recorder_interface(): sink dlrecorder, recorder initialization...
2017-Aug-21 17:41:34:   [I] sink::init_recorder_interface(): sink dlrecorder, recorder initialization... succeeded
2017-Aug-21 17:41:34:   [I] Setting up default recorder ID and IP address to local machine
2017-Aug-21 17:41:34:   [I] recorder_database_t::init(): Opening database file /var/packages/DVBLinkServer/target/share/database/dlrecorder.db
2017-Aug-21 17:41:34:   [I] recorder_engine::recorder_thread_func(). Started.
2017-Aug-21 17:41:34:   [I] broker::start(): ...succeded
2017-Aug-21 17:41:34:   [I] recorder_engine::run_active(). Switched to active mode
2017-Aug-21 17:41:34:   [I] recorder_engine::run_active(). Waiting for DVBLink server to become operational
2017-Aug-21 17:41:34:   [I] recorder_engine::run_active(). DVBLink server is operational. Continue with rescheduling
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::reset. There is no wakeup timer currently set
2017-Aug-21 17:41:34:   [I] recorder_engine::purge_schedules.
2017-Aug-21 17:41:34:   [I] recorder_engine::purge_deleted_recordings.
2017-Aug-21 17:41:34:   [I] send_to_manager::manager_thread_function. DVBLink server is operational
2017-Aug-21 17:41:34:   [I] send_to_manager::apply_power_state. Enabling standby
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 1
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 2
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 4
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 6
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 10
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 11
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 12
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 13
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 14
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 19
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 20
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 21
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 22
2017-Aug-21 17:41:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 23
2017-Aug-21 17:43:34:   [I] epg_updater_t::update_thread_func. epg updater thread has finished
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::reset. There is no wakeup timer currently set
2017-Aug-21 17:43:34:   [I] recorder_engine::purge_schedules.
2017-Aug-21 17:43:34:   [I] recorder_engine::purge_deleted_recordings.
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 1
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 2
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 4
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 6
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 10
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 11
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 12
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 13
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 14
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 19
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 20
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 21
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 22
2017-Aug-21 17:43:34:   [I] recorder_engine_impl::generate_timers_for_schedule. 0 timers were generated for schedule 23
2017-Aug-21 17:49:53:   [I] package_manager_t::preinstall_package. Starting preinstall for package.dvk
2017-Aug-21 17:49:53:   [I] external_control::untar: Starting untar process for /var/packages/DVBLinkServer/target/packages/temp/package.dvk
2017-Aug-21 17:49:53:   [I] external_control::untar. start tar: "tar" xvzf "/var/packages/DVBLinkServer/target/packages/temp/package.dvk" -C "/var/packages/DVBLinkServer/target/packages/temp/f355074a-90b5-46a7-b935-3afccd85f0ee"
2017-Aug-21 17:49:55:   [I] external_control::untar. tar returned: -1
2017-Aug-21 17:49:55:   [I] external_control::untar: tar process finished successfully
2017-Aug-21 17:49:55:   [I] package_manager_t::preinstall_package. Reading package information from /var/packages/DVBLinkServer/target/packages/temp/f355074a-90b5-46a7-b935-3afccd85f0ee/package.xml
2017-Aug-21 17:57:59:   [I] package_manager_t::preinstall_package. Starting preinstall for package.dvk
2017-Aug-21 17:57:59:   [I] external_control::untar: Starting untar process for /var/packages/DVBLinkServer/target/packages/temp/package.dvk
2017-Aug-21 17:57:59:   [I] external_control::untar. start tar: "tar" xvzf "/var/packages/DVBLinkServer/target/packages/temp/package.dvk" -C "/var/packages/DVBLinkServer/target/packages/temp/5946c869-9504-4caf-9f1a-597f36c180a0"
2017-Aug-21 17:58:01:   [I] external_control::untar. tar returned: -1
2017-Aug-21 17:58:01:   [I] external_control::untar: tar process finished successfully
2017-Aug-21 17:58:01:   [I] package_manager_t::preinstall_package. Reading package information from /var/packages/DVBLinkServer/target/packages/temp/5946c869-9504-4caf-9f1a-597f36c180a0/package.xml
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Tue Aug 22, 2017 4:03 am

OK, I think I got it all sorted out. Not really sure what the root problem was, but I removed and reinstalled everything from scratch, both on the NAS and on my main PC (client and viewer). I run the NAS on a VPN connection and since I seemed to be getting some connection and installation error messages, I tried changing the VPN server from one in Sweden to one in Switzerland and some combination of all that made it work. I now see the PercData EPG source as well as the ATSC/EIT source. This install was done with the NAS and cable modem/gateway firewall enabled, so that wasn't the issue.
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA

Re: New to percdata, can't pass connection verification

Postby the_man » Mon Aug 28, 2017 11:10 am

So, seems issue related to VPN (??)
NETGEAR RNDU2000; Synology DS112j, DS 212j, DS213+, DS 712+; Western Digital WD ex2; Asustor AS3, RPI2 ...
PCTV 460,461e,292e; TT 4400, 4650CI;DVBSKy S960; DD octopus net; Inverto sat2ip multibox; TBS DVB-C ...
the_man
 
Posts: 4696
Joined: Mon Dec 02, 2013 1:11 pm

Re: New to percdata, can't pass connection verification

Postby 4Crawler » Wed Sep 27, 2017 5:17 am

the_man wrote:So, seems issue related to VPN (??)


Sorry, didn't see this question until tonight. I always have the DiskStation on a VPN connection and normally that works fine. But somehow the VPN server I was connected to must have been messed up and while it still showed a connection, something was wrong when trying to access percdata.com. I switched to another server in a different country for a few weeks and have now switched back to the server that was causing the problem last summer and all seems to be working fine now. I usually have the situation where the VPN server will drop the connection. The DiskStation will notify me of that issue and then I'll change to an alternate server. But this one time, the connection wasn't dropped and it still showed network activity on that VPN link.
4Crawler
 
Posts: 33
Joined: Sun Oct 06, 2013 8:21 pm
Location: SF Bay Area, CA. USA


Return to DVBLink EPG Loader products

Who is online

Users browsing this forum: No registered users and 1 guest