SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support

Notices

Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #2341  
Old 04-15-2018, 04:20 PM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
 
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 474
Im getting OPEN DTC locking up once or twice a week I have to restart it to fix it.Below is whats in the log. It goes on and on until I restart open DTC. I was away on business for a while and the WAF when way low .

Im using a streaming executable and it looks like its having trouble stopping. I don't have a stopping executable do I need one?

Thx Chris

sagetv.device.2060898.streaming_executable=C\:\\comskip\\ffmpeg.exe -i http\://p-c-iptv.net\:80/live/Email@email.com/Password/%c%.ts -c\:a copy -c\:v copy -f mpegts pipe\:1

Code:
INFO   | jvm 1    | 2018/04/14 11:20:25.167 | 11:20:25.111 [SageTVRequestHandler-147:CAM1] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1945 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:25.167 | 11:20:25.113 [SageTVRequestHandler-153:CAM2] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1885 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:26.167 | 11:20:26.111 [SageTVRequestHandler-147:CAM1] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1946 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:26.167 | 11:20:26.113 [SageTVRequestHandler-153:CAM2] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1886 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:27.167 | 11:20:27.111 [SageTVRequestHandler-147:CAM1] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1947 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:27.167 | 11:20:27.113 [SageTVRequestHandler-153:CAM2] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1887 seconds...
INFO   | jvm 1    | 2018/04/14 11:20:28.167 | 11:20:28.111 [SageTVRequestHandler-147:CAM1] WARN  InputStreamCaptureDeviceServices - Waiting for producer thread to stop for over 1948 seconds...
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Reply With Quote
  #2342  
Old 04-23-2018, 01:03 AM
rickgillyon's Avatar
rickgillyon rickgillyon is offline
Sage Icon
 
Join Date: Sep 2005
Location: Whitley Bay, England
Posts: 1,944
Anyone know of there's another plugin/method to get an IPTV source into Sage? Either OpenDCT or Sage is choking on the streams and there doesn't seem to be any way to diagnose what the problem is, so it looks like I need a different solution.
__________________
unRAID Server: Intel Core i5 7600K, 16GB DDR4, 2x512GB PCIe M.2 Cache Pool, 2x4TB SATA3 Parity Drive, 2x3TB + 1x4TB SATA Array, 1x TBS 6284 PCIe DVB-T2 Quad, 2x TBS 6205 PCIe DVB-T Quad, Cable TV from TBS2603 sat/IP, IPTV via Telly & node-ffmpeg-mpegts-proxy, unRAID 6.6.6, TVheadend for recording back end, OpenDCT, SDEPG, SageTV 9
Clients: 3 Nvidia Shields, 2 Android Miniclients (Amlogic S905X), 3 Win10 Pro PC Clients
Reply With Quote
  #2343  
Old 04-23-2018, 10:17 AM
KryptoNyte's Avatar
KryptoNyte KryptoNyte is offline
Sage Icon
 
Join Date: Dec 2006
Posts: 2,152
Would this apply?

https://forums.sagetv.com/forums/showthread.php?t=63855
Reply With Quote
  #2344  
Old 04-23-2018, 10:28 AM
rickgillyon's Avatar
rickgillyon rickgillyon is offline
Sage Icon
 
Join Date: Sep 2005
Location: Whitley Bay, England
Posts: 1,944
Quote:
Originally Posted by KryptoNyte View Post
Yeah, that's what doesn't work.
__________________
unRAID Server: Intel Core i5 7600K, 16GB DDR4, 2x512GB PCIe M.2 Cache Pool, 2x4TB SATA3 Parity Drive, 2x3TB + 1x4TB SATA Array, 1x TBS 6284 PCIe DVB-T2 Quad, 2x TBS 6205 PCIe DVB-T Quad, Cable TV from TBS2603 sat/IP, IPTV via Telly & node-ffmpeg-mpegts-proxy, unRAID 6.6.6, TVheadend for recording back end, OpenDCT, SDEPG, SageTV 9
Clients: 3 Nvidia Shields, 2 Android Miniclients (Amlogic S905X), 3 Win10 Pro PC Clients
Reply With Quote
  #2345  
Old 04-27-2018, 12:28 PM
mlcarson mlcarson is offline
Sage Advanced User
 
Join Date: Aug 2016
Location: Lompoc, CA
Posts: 79
I've actually been having rather good luck so far with the generic HTTP streaming. On a previous provider, the streams were more hit/miss and for any that were problematic, I had to use generic PIPE with FFMPEG reencoding. The IPTV thing has been more of an experiment/proof of concept but is now supplying some channels otherwise unavailable to me. OpenDCT has proven to be quite flexible.

The setup is a lot more complicated with SageTV than a Kodi/STB implementation but allows for a better end result and transparent integration into my original SageTV implementation.

The biggest gotchas for me involved the EPG. You need an XMLTV source and have to manually add the XMLTV import plug-in. I also had to write a utility to postprocess the XMLTV data since SageTV doesn't know what an MUI file is and therefore no concept of the "tvg-shift" field for per channel time-zone modification. At least I didn't see a way of doing this via the xmltv.properties file of the XMLTV importer.
Reply With Quote
  #2346  
Old 04-27-2018, 12:33 PM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
 
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 474
Quote:
Originally Posted by mlcarson View Post
The biggest gotchas for me involved the EPG. You need an XMLTV source and have to manually add the XMLTV import plug-in. I also had to write a utility to postprocess the XMLTV data since SageTV doesn't know what an MUI file is and therefore no concept of the "tvg-shift" field for per channel time-zone modification. At least I didn't see a way of doing this via the xmltv.properties file of the XMLTV importer.

Actually no Need for this. I use schedules Direct EPG service just add several Providers (I use SKY, DIRECTV, BELL) and then just use the zap2it id to manually add in the channel and I get over 600+ channels with full guide from multiple providers.

Chris
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Reply With Quote
  #2347  
Old 04-27-2018, 03:28 PM
mlcarson mlcarson is offline
Sage Advanced User
 
Join Date: Aug 2016
Location: Lompoc, CA
Posts: 79
There is a need for it unless I misunderstand you. I'm in the PDT time-zone. An IPTV service may provide channels in multiple time zones that aren't available in your DMA. I start off with using two providers in Schedules Direct - Comcast and OTA in my own zipcode because Comcast doesn't pick up all of the local OTA. Now maybe an IPTV stream has something that's on Dish and then something different that's only on DirecTV. So now I'm at 4 lineups without even getting out of my zipcode. I thought that each video source could only be given one Schedules Direct zipcode so you end up creating duplicate sources to get around this limitation.

So now maybe there are some channels that are broadcast from different time zones. There are national channels with eastern feeds and western feeds so now I need a zipcode on the East coast. Want to watch some Canadian channels then you need to add BELL; same thing for SKY.

XMLTV was a way of adding one video source and then pairing it with one XMLTV feed. I could change the timezone via the per channel tvg-shift post-processing of the XMLTV file. I'm using IPTV-EPG for that file at the moment. I only chose that option when the number of guide providers for Schedules Direct looked to be an issue and that I thought it would require duplicate video sources because of the 1:1 provider mapping. I suspect that the guide data of Schedules Direct will be better though.
Reply With Quote
  #2348  
Old 04-27-2018, 04:30 PM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
 
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 474
Quote:
Originally Posted by mlcarson View Post
There is a need for it unless I misunderstand you. I'm in the PDT time-zone. An IPTV service may provide channels in multiple time zones that aren't available in your DMA. I start off with using two providers in Schedules Direct - Comcast and OTA in my own zipcode because Comcast doesn't pick up all of the local OTA. Now maybe an IPTV stream has something that's on Dish and then something different that's only on DirecTV. So now I'm at 4 lineups without even getting out of my zipcode. I thought that each video source could only be given one Schedules Direct zipcode so you end up creating duplicate sources to get around this limitation.

So now maybe there are some channels that are broadcast from different time zones. There are national channels with eastern feeds and western feeds so now I need a zipcode on the East coast. Want to watch some Canadian channels then you need to add BELL; same thing for SKY.

XMLTV was a way of adding one video source and then pairing it with one XMLTV feed. I could change the timezone via the per channel tvg-shift post-processing of the XMLTV file. I'm using IPTV-EPG for that file at the moment. I only chose that option when the number of guide providers for Schedules Direct looked to be an issue and that I thought it would require duplicate video sources because of the 1:1 provider mapping. I suspect that the guide data of Schedules Direct will be better though.

When you add a channel manually by using the channel id it looks up all of your providers in SD. I have 4 total on one source but you can only have one you initial select.

My IPTV provider is heavy in SKY channels so i had that as the main source then I just remap them to the IPTV. I MANUALLY add in the DISH/Bell 'premium' which is about 150 channels this take a bit of time but the EPG is rock solid.

I dont need to add in NBC.ABC,FOX,CBS they are on my OTA HDHOMERUNS. But DISH has all the West coast Feeds as well as long as you get the proper Channel ID.

I've been running this setup for up to 2 years.

Chris
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Reply With Quote
  #2349  
Old 04-30-2018, 09:39 AM
egeller egeller is offline
Sage Advanced User
 
Join Date: Feb 2006
Location: Drexel Hill, PA
Posts: 237
Quote:
Originally Posted by technazz View Post
Actually no Need for this. I use schedules Direct EPG service just add several Providers (I use SKY, DIRECTV, BELL) and then just use the zap2it id to manually add in the channel and I get over 600+ channels with full guide from multiple providers.

Chris
I had been wondering how to do what you're doing. I understand the part about the zap2it id. Are you saying that you add the providers to your account in the Schedules Direct web site, and the channels become available to map in SageTV?

I think I tried to map channels, via the Zap2it ID, without adding a valid provider to my Sched Direct account and found that SageTV could not retrieve EPG guide data for the channels.

Erv
__________________
Server:UnRaid;2x Intel Xeon E5; SuperMicro moboard;Also:BM3000 w/ WMC; 2x Ceton ETH 6; OpenDCT
SageTV Extender:3x HD200 1x HD300
Sage TV: 9.1.10, Standard STVi, Comskip Playback, Web Interface, 24 Hour Clock, SRE, YouTube2015, Playon
All in lovely Drexel Hill, PA
Reply With Quote
  #2350  
Old 04-30-2018, 10:43 AM
technazz's Avatar
technazz technazz is offline
Sage Aficionado
 
Join Date: Jul 2004
Location: Hamilton, ON, CA
Posts: 474
Quote:
Originally Posted by egeller View Post
I had been wondering how to do what you're doing. I understand the part about the zap2it id. Are you saying that you add the providers to your account in the Schedules Direct web site, and the channels become available to map in SageTV?

I think I tried to map channels, via the Zap2it ID, without adding a valid provider to my Sched Direct account and found that SageTV could not retrieve EPG guide data for the channels.

Erv

No not in the website in Sage TV, when you select the Guide Data source you pick "Use Schedules Direct Guide Data with this source" then you can add more sources. I have 4 setup. Once setup using the Channel ID should let you manually add the channel into the lineup.

Chris
__________________
SageTV V9.xx 2 x HD300's, 2 x Nvidia Shields Running Mini Client
Reply With Quote
  #2351  
Old 05-15-2018, 05:27 AM
rickgillyon's Avatar
rickgillyon rickgillyon is offline
Sage Icon
 
Join Date: Sep 2005
Location: Whitley Bay, England
Posts: 1,944
Can anyone successfully using IPTV with OpenDCT please share or PM their opendct.properties?

And any UK iptv users, please PM/share your provider if working.

Thanks.
__________________
unRAID Server: Intel Core i5 7600K, 16GB DDR4, 2x512GB PCIe M.2 Cache Pool, 2x4TB SATA3 Parity Drive, 2x3TB + 1x4TB SATA Array, 1x TBS 6284 PCIe DVB-T2 Quad, 2x TBS 6205 PCIe DVB-T Quad, Cable TV from TBS2603 sat/IP, IPTV via Telly & node-ffmpeg-mpegts-proxy, unRAID 6.6.6, TVheadend for recording back end, OpenDCT, SDEPG, SageTV 9
Clients: 3 Nvidia Shields, 2 Android Miniclients (Amlogic S905X), 3 Win10 Pro PC Clients
Reply With Quote
  #2352  
Old 05-26-2018, 05:06 AM
KeithAbbott KeithAbbott is offline
Sage Icon
 
Join Date: Oct 2009
Location: Southeastern Michigan
Posts: 1,026
OpenDCT Docker Crashes

Boy, I sure wish OpenDCT had it's own sub-forum...

Anyhow, I am running crazifuzzy-opendct docker in unRaid, around 1-2 times per week OpenDCT crashes and requires a restart. So far, it has always happened overnight.

Here's a snippet from the log, hoping this might help somebody (i.e. EnterNoEscape) determine what's going on, and what I might need to do to correct this.

Code:
INFO | jvm 1 | 2018/05/25 22:37:00.133 | 22:37:00.068 [NIORTPProducerImpl-15523:DCT-HDHomeRun Prime Tuner 13231929-1] INFO NIORTPProducerImpl - Producer thread has disconnected.
INFO | jvm 1 | 2018/05/25 22:37:00.133 | 22:37:00.068 [NIORTPProducerImpl-15523:DCT-HDHomeRun Prime Tuner 13231929-1] INFO NIORTPProducerImpl - Producer thread has stopped.
INFO | jvm 1 | 2018/05/25 22:37:00.133 | 22:37:00.097 [MediaServerConsumerImpl-15527:DCT-HDHomeRun Prime Tuner 13231929-1] INFO MediaServerConsumerImpl - MediaServer thread stopped.
INFO | jvm 1 | 2018/05/25 22:37:00.133 | 22:37:00.102 [SageTVRequestHandler-15600:DCT-HDHomeRun Prime Tuner 13231929-1] INFO HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
INFO | jvm 1 | 2018/05/25 22:38:00.011 | 22:38:00.008 [NIORTPProducerImpl-15508:DCT-HDHomeRun Prime Tuner 13231929-0] INFO NIORTPProducerImpl - Producer thread has disconnected.
INFO | jvm 1 | 2018/05/25 22:38:00.011 | 22:38:00.008 [NIORTPProducerImpl-15508:DCT-HDHomeRun Prime Tuner 13231929-0] INFO NIORTPProducerImpl - Producer thread has stopped.
INFO | jvm 1 | 2018/05/25 22:38:00.011 | 22:38:00.009 [MediaServerConsumerImpl-15512:DCT-HDHomeRun Prime Tuner 13231929-0] INFO MediaServerConsumerImpl - MediaServer thread stopped.
INFO | jvm 1 | 2018/05/25 22:38:00.112 | 22:38:00.014 [SageTVRequestHandler-15609:DCT-HDHomeRun Prime Tuner 13231929-0] INFO HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
INFO | jvm 1 | 2018/05/26 00:07:24.823 | 00:07:24.728 [WrapperSimpleAppMain] INFO Config - Removed log file 'opendct.2018-04-25-2.log.gz' because it is over 30 days old.
ERROR | wrapper | 2018/05/26 00:41:55.481 | JVM appears hung: Timed out waiting for signal from JVM.
INFO | wrapper | 2018/05/26 00:42:40.668 | Wrapper Process has not received any CPU time for 70 seconds. Extending timeouts.
INFO | jvm 1 | 2018/05/26 00:43:04.089 | Wrapper Manager: The Wrapper code did not ping the JVM for 60 seconds. Quit and let the Wrapper resynch.
STATUS | wrapper | 2018/05/26 00:43:04.090 | JVM requested a restart.
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.399 [PowerMessageManagerShutdown] INFO Main - Stopping power messages...
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.402 [DiscoveryManagerShutdown] INFO Main - Stopping device discovery services...
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.402 [ChannelManagerShutdown] INFO Main - Stopping all channel update threads...
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.402 [SageTVManagerShutdown] INFO Main - Stopping all SageTV socket servers...
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.402 [NanoHTTPDShutdown] INFO Main - Stopping web server...
INFO | jvm 1 | 2018/05/26 00:43:11.483 | 00:43:11.403 [Shutdown] INFO Main - OpenDCT has received a signal to stop.
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.550 [PowerMessageManagerShutdown] WARN LinuxPowerMessagePump - System power state messages are currently not implemented for Linux.
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.550 [Shutdown] INFO Main - Saving current configuration...
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.551 [SageTVTuningMonitor-56] INFO SageTVTuningMonitor - Tuning monitor thread interrupted.
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.553 [UPnPDiscovery-34] INFO UpnpManager - UPnP discovery thread was interrupted => java.lang.InterruptedException: sleep interrupted
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.554 [ChannelManagerShutdown] INFO ChannelManager - Saving the channel lineup 'dct_hdhomerun'.
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.555 [NanoHTTPDShutdown] INFO NanoHTTPDManager - Stopping webserver on port 9091...
INFO | jvm 1 | 2018/05/26 00:43:11.583 | 00:43:11.555 [SageTVSocketServer-57:9000] INFO SageTVSocketServer - Stopped listening on port 9000...
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.555 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13256C0B-2' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.558 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13231929-2' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.560 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13231929-1' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.561 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13231929-0' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.562 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13256C0B-0' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:11.584 | 00:43:11.563 [SageTVManagerShutdown] INFO SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13256C0B-1' is being unloaded.
INFO | jvm 1 | 2018/05/26 00:43:13.286 | 00:43:13.188 [DiscoveryManagerShutdown] WARN DiscoveryRegistryListener - Before UPnP shutdown, the registry did not contain any devices.
INFO | jvm 1 | 2018/05/26 00:43:13.286 | 00:43:13.189 [DiscoveryManagerShutdown] INFO DiscoveryManager - UPnP discovery stopped.
INFO | jvm 1 | 2018/05/26 00:43:13.286 | 00:43:13.194 [DiscoveryManagerShutdown] INFO DiscoveryManager - HDHomeRun discovery stopped.
INFO | jvm 1 | 2018/05/26 00:43:13.286 | 00:43:13.194 [DiscoveryManagerShutdown] INFO DiscoveryManager - Generic HTTP discovery stopped.
INFO | jvm 1 | 2018/05/26 00:43:13.286 | 00:43:13.194 [DiscoveryManagerShutdown] INFO DiscoveryManager - Generic Pipe discovery stopped.
ERROR | wrapper | 2018/05/26 00:43:28.604 | Shutdown failed: Timed out waiting for the JVM to terminate.
ERROR | wrapper | 2018/05/26 00:43:36.047 | JVM did not exit on request, terminated
INFO | wrapper | 2018/05/26 00:43:36.215 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper | 2018/05/26 00:43:36.315 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper | 2018/05/26 00:43:40.465 | Reloading Wrapper configuration...
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[0] : /usr/bin/java
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[1] : -Dopendct_log_root=/var/log/opendct
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[2] : -Dconfig_dir=/etc/opendct/conf
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[3] : -Ddaemon_mode=true
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[4] : -XX:ErrorFile=/var/log/opendct/hs_err_pid%p.log
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[5] : -verbose:gc
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[6] : -XX:+UseG1GC
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[7] : -Xms128m
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[8] : -Xmx768m
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[9] : -Djava.library.path=/opt/opendct/jsw/lib:/opt/opendct/lib
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[10] : -classpath
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[11] : /opt/opendct/jsw/lib/wrapper.jar:/opt/opendct/lib/opendct-0.5.28.jar:/opt/opendct/lib/cling-core-2.1.1.jar:/opt/opendct/lib/log4j-api-2.5.jar:/opt/opendct/lib/log4j-core-2.5.jar:/opt/opendct/lib/jna-4.2.1.jar:/opt/opendct/lib/jna-platform-4.2.1.jar:/opt/opendct/lib/nanohttpd-2.3.0.jar:/opt/opendct/lib/nanohttpd-nanolets-2.3.0.jar:/opt/opendct/lib/gson-2.8.0.jar:/opt/opendct/lib/javacpp-1.1.jar:/opt/opendct/lib/ffmpeg-2.8.1-1.1.jar:/opt/opendct/lib/ffmpeg-2.8.1-1.1-linux-x86_64.jar:/opt/opendct/lib/seamless-util-1.1.1.jar:/opt/opendct/lib/seamless-http-1.1.1.jar:/opt/opendct/lib/seamless-xml-1.1.1.jar
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[12] : -Dwrapper.key=B549RjY5IA2uikav
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[13] : -Dwrapper.port=32001
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[14] : -Dwrapper.jvm.port.min=31000
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[15] : -Dwrapper.jvm.port.max=31999
INFO | wrapper | 2018/05/26 00:43:41.659 | Command[16] : -Dwrapper.pid=157
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[17] : -Dwrapper.version=3.2.3
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[18] : -Dwrapper.native_library=wrapper
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[19] : -Dwrapper.cpu.timeout=10
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[20] : -Dwrapper.jvmid=2
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[21] : org.tanukisoftware.wrapper.WrapperSimpleApp
INFO | wrapper | 2018/05/26 00:43:41.660 | Command[22] : opendct.Main
STATUS | wrapper | 2018/05/26 00:43:41.660 | Launching a JVM...
ERROR | wrapper | 2018/05/26 00:44:09.592 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR | wrapper | 2018/05/26 00:44:09.692 | JVM did not exit on request, terminated
INFO | wrapper | 2018/05/26 00:44:09.700 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper | 2018/05/26 00:44:09.800 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper | 2018/05/26 00:44:13.906 | Reloading Wrapper configuration...
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[0] : /usr/bin/java
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[1] : -Dopendct_log_root=/var/log/opendct
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[2] : -Dconfig_dir=/etc/opendct/conf
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[3] : -Ddaemon_mode=true
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[4] : -XX:ErrorFile=/var/log/opendct/hs_err_pid%p.log
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[5] : -verbose:gc
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[6] : -XX:+UseG1GC
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[7] : -Xms128m
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[8] : -Xmx768m
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[9] : -Djava.library.path=/opt/opendct/jsw/lib:/opt/opendct/lib
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[10] : -classpath
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[11] : /opt/opendct/jsw/lib/wrapper.jar:/opt/opendct/lib/opendct-0.5.28.jar:/opt/opendct/lib/cling-core-2.1.1.jar:/opt/opendct/lib/log4j-api-2.5.jar:/opt/opendct/lib/log4j-core-2.5.jar:/opt/opendct/lib/jna-4.2.1.jar:/opt/opendct/lib/jna-platform-4.2.1.jar:/opt/opendct/lib/nanohttpd-2.3.0.jar:/opt/opendct/lib/nanohttpd-nanolets-2.3.0.jar:/opt/opendct/lib/gson-2.8.0.jar:/opt/opendct/lib/javacpp-1.1.jar:/opt/opendct/lib/ffmpeg-2.8.1-1.1.jar:/opt/opendct/lib/ffmpeg-2.8.1-1.1-linux-x86_64.jar:/opt/opendct/lib/seamless-util-1.1.1.jar:/opt/opendct/lib/seamless-http-1.1.1.jar:/opt/opendct/lib/seamless-xml-1.1.1.jar
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[12] : -Dwrapper.key=pS0fbYlUynoQIylm
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[13] : -Dwrapper.port=32001
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[14] : -Dwrapper.jvm.port.min=31000
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[15] : -Dwrapper.jvm.port.max=31999
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[16] : -Dwrapper.pid=157
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[17] : -Dwrapper.version=3.2.3
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[18] : -Dwrapper.native_library=wrapper
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[19] : -Dwrapper.cpu.timeout=10
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[20] : -Dwrapper.jvmid=3
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[21] : org.tanukisoftware.wrapper.WrapperSimpleApp
INFO | wrapper | 2018/05/26 00:44:14.246 | Command[22] : opendct.Main
STATUS | wrapper | 2018/05/26 00:44:14.246 | Launching a JVM...
INFO | jvm 3 | 2018/05/26 00:44:31.268 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO | jvm 3 | 2018/05/26 00:44:31.268 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
INFO | jvm 3 | 2018/05/26 00:44:31.268 |
ERROR | wrapper | 2018/05/26 00:44:42.982 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR | wrapper | 2018/05/26 00:44:47.718 | JVM did not exit on request, terminated
STATUS | wrapper | 2018/05/26 00:44:50.129 | JVM exited in response to signal SIGKILL (9).
ERROR | wrapper | 2018/05/26 00:44:50.129 | Unable to start a JVM
STATUS | wrapper | 2018/05/26 00:44:50.229 | <-- Wrapper Stopped
This only started happening 1-2 months ago, prior to that OpenDCT was running solid.
__________________
Server: MSI Z270 SLI Plus ATX Motherboard, Intel i3-7100T CPU, 16GB Memory, unRAID 6.3.2, SageTV & OpenDCT Dockers
Tuners: 2 x SiliconDust HDHomeRun Prime Cable TV Tuners, 2 x Hauppauge WinTV-HVR-2250 Dual TV Tuner Boards
Clients: Multiple HD300 Extenders
Miscellaneous: Multiple Sony RM-VLZ620 Universal Remote Controls
Reply With Quote
  #2353  
Old 05-26-2018, 05:22 AM
KeithAbbott KeithAbbott is offline
Sage Icon
 
Join Date: Oct 2009
Location: Southeastern Michigan
Posts: 1,026
Looks like jbuszkie had a similar problem last year: https://forums.sagetv.com/forums/showthread.php?t=64848
__________________
Server: MSI Z270 SLI Plus ATX Motherboard, Intel i3-7100T CPU, 16GB Memory, unRAID 6.3.2, SageTV & OpenDCT Dockers
Tuners: 2 x SiliconDust HDHomeRun Prime Cable TV Tuners, 2 x Hauppauge WinTV-HVR-2250 Dual TV Tuner Boards
Clients: Multiple HD300 Extenders
Miscellaneous: Multiple Sony RM-VLZ620 Universal Remote Controls
Reply With Quote
  #2354  
Old 05-26-2018, 09:25 AM
nyplayer nyplayer is offline
SageTVaholic
 
Join Date: Sep 2005
Posts: 4,054
Will this work running one instance of OPENDCT and have several Servers using it by using the IP of the OPENDCT Server ? My guess is that it would work. Pooling will be enabled.

Edit ....

It worked cut down on my NetWork activity from my office upstairs to the basement where all my storage and main server is.
__________________
Windows 10 I3 Dual Core 3.0 Server, SageTV9... OpenDCT with 2 HDHRPrimes and 4 HDHRconnects for a total of 14 Tuners.

Last edited by nyplayer; 05-26-2018 at 10:12 AM.
Reply With Quote
  #2355  
Old 06-06-2018, 09:13 PM
reggie14 reggie14 is offline
SageTVaholic
 
Join Date: Aug 2003
Location: Maryland
Posts: 2,759
My HDMI encoder stopped working yesterday. Restarting my SageTV server seemed to initially fix it, but maybe I didn't test it enough because it's broken today.

Upon further inspection of the OpenDCT.log, it appears that OpenDCT doesn't think the HDMI encoder exists anymore. And sure enough, it doesn't appear in the OpenDCT.properties file anymore.

What's the right way to fix this? I have an old backup of the OpenDCT.properties file. Do I just put it back and go on my merry way?

Why did it happen in the first place? My only clue is that my OpenDCT folder has a file named opendct.properties.upgrade-0. It's blank, but the time it was created was right around when I restarted the server after I noticed it was initially broken.
Reply With Quote
  #2356  
Old 06-08-2018, 04:58 PM
tomdomm tomdomm is offline
Sage User
 
Join Date: Jun 2011
Location: Ohio, USA
Posts: 49
Fixed problem by loading old version of Java. Disabled auto java update and problem has not returned.
Reply With Quote
  #2357  
Old 07-01-2018, 03:31 PM
Deacon Crusher Deacon Crusher is offline
Sage Expert
 
Join Date: Aug 2004
Location: Berkeley, CA
Posts: 503
Is sage or open dct the issue, can't tell, but sage suddenly unuseable

Long time user, never had a problem like this before. Can't figure if problem is initiating within sage or within opendct, so going to break rules and cross-post for a bit, putting this here and will post in opendct thread as well.

I've tried shutting down entire network as well as sage server and bringing stuff up slowly.

I've updated Java (in the right way with sage shutdown) no help.

Starting around 7:15 last night sage starting throwing the errors I'll list below and after a while (15-30) minutes the sage service is at 95%+ CPU usage and everything stops working. Clients are disconnected and shows start failing to record.

Restart after updates etc. stuff works for 15-30 minutes and then starts to repeat problem.

FYI, many references to network issues, but when sage isn't running the computer it's running on has zero problems including continuous pings and large file copies.

Here are what look like the interesting log passages from opendct and sage.

These are likely just symptoms but damned if I can figure out the cause.

Actually, I'll start with this from the Windows System Log

{Delayed Write Failed} Windows was unable to save all the data for the file \Sage\MSNBCLivewithDavidGura-48618664-0.ts; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere.

SAGEtv_0.txt log section right as problem starts
Sun 7/1 13:14:29.167 [Seeker@38ae5f] MARK 1 currRecord=FA[stationID=35975 Speed time=Sun 7/1 12:44:00.000 dur=2:02:00] enc=Hauppauge HD PVR Capture Device clients=[] ir=false
Sun 7/1 13:14:29.175 [Seeker@38ae5f] Seeker in AUTOMATIC mode nextRecord=A[48677476,48520221,"Last Week Tonight With John Oliver",19566@0701.23:00,31,T] nextTTA=35131195
Sun 7/1 13:14:29.183 [Seeker@38ae5f] newRecord=FA[stationID=35975 Speed time=Sun 7/1 12:44:00.000 dur=2:02:00]
Sun 7/1 13:14:29.191 [Seeker@38ae5f] Record was enabled on what's already being recorded; update status.
Sun 7/1 13:14:29.198 [Seeker@38ae5f] Keeping record just the way it is.
Sun 7/1 13:14:29.207 [Seeker@38ae5f] RootFile=H:\ fstype=NTFS fileLength=1476509696 file=H:\Sage-h\Speed-48525414-0.ts
Sun 7/1 13:14:29.215 [Seeker@38ae5f] RootFile=\\ds413\sage-ds413 fstype=null fileLength=2917430624 file=\\ds413\sage-ds413\PGATourGolf-QuickenLoansNationalFinalRound-48650588-0.ts
Sun 7/1 13:14:29.224 [Seeker@38ae5f] RootFile=\\ds413\Sage-ds413-V2 fstype=null fileLength=403777376 file=\\ds413\Sage-ds413-V2\Sage\MSNBCLivewithYasminVossoughian-48618665-0.ts
Sun 7/1 13:14:29.232 [Seeker@38ae5f] RootFile=\\ds413\Sage-ds413-V2 fstype=null fileLength=459065168 file=\\ds413\Sage-ds413-V2\Sage\MLBBaseball-SanFranciscoGiantsatArizonaDiamondbacks-48519375-0.ts
Sun 7/1 13:14:29.241 [VideoFrame-001d6a4bfb0f@1a32879] VF processing job null nPlayin=true
Sun 7/1 13:14:29.249 [Seeker@38ae5f] Checking video directories for new files
Sun 7/1 13:14:29.258 [VideoFrame-001d6a4bfb0f@1a32879] isRec=true rd=868575 base=11973 eos=false
Sun 7/1 13:14:29.266 [Seeker@38ae5f] Diskspace checking is running
Sun 7/1 13:14:29.275 [VideoFrame-001d6a4bfb0f@1a32879] VF thread is now waiting for 0:59:47.102
Sun 7/1 13:14:29.283 [Seeker@38ae5f] Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Sun 7/1 13:14:29.467 [Seeker@38ae5f] Enforcing keep at most limits for the files...
Sun 7/1 13:14:29.480 [Seeker@38ae5f] DONE enforcing keep at most limits for the files.
Sun 7/1 13:14:29.488 [Seeker@38ae5f] Seeker clearing unwanted and partial files...
Sun 7/1 13:14:29.509 [Seeker@38ae5f] DONE clearing unwanted and partial files.
Sun 7/1 13:14:29.645 [Seeker@38ae5f] needFreeSize = 2.025 GB currFreeSize=1038.389954048 GB
Sun 7/1 13:14:29.654 [Seeker@38ae5f] needFreeSize = 2.025 GB currFreeSize=1529.387747328 GB
Sun 7/1 13:14:29.674 [Seeker@38ae5f] needFreeSize = 4.05 GB currFreeSize=3111.840792576 GB
Sun 7/1 13:14:29.681 [Seeker@38ae5f] Seeker waiting for 40 mins.
Sun 7/1 13:16:21.488 [MediaServerConnection@19f] Error in MediaServerConnection of :java.io.IOException: An unexpected network error occurred
Sun 7/1 13:16:21.497 [Pusher@abb708] Error with MiniPlayer, closing UI: java.io.IOException: An unexpected network error occurred
Sun 7/1 13:16:21.511 [MediaServerConnection@1cf3d77] Error in MediaServerConnection of :java.io.IOException: An unexpected network error occurred
Sun 7/1 13:16:21.520 [MediaServerConnection@9e9de2] Error in MediaServerConnection of :java.io.IOException: An unexpected network error occurred
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] java.io.IOException: An unexpected network error occurred
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.FileDispatcherImpl.pwrite0(Native Method)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.FileDispatcherImpl.pwrite(Unknown Source)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.IOUtil.write(Unknown Source)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.FileChannelImpl.writeInternal(Unknown Source)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sun.nio.ch.FileChannelImpl.write(Unknown Source)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sage.MediaServer$Connection.transferDataUpload(MediaServer.java:960)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sage.MediaServer$Connection.writeFile(MediaServer.java:907)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sage.MediaServer$Connection.run(MediaServer.java:1198)
Sun 7/1 13:16:21.528 [MediaServerConnection@1cf3d77] at sage.Pooler$PooledThread.run(Pooler.java:254)
Sun 7/1 13:16:21.529 [MCSRReconnect@1afd3fa] Preparing the media player for a reload...
Sun 7/1 13:16:21.537 [Pusher@abb708] pushBuffer call failed; terminating push loop

opendct.log as problem starts to happen
13:16:06.611 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN SeekableCircularBufferNIO - The buffer has 7863912 bytes left to be read, has only 409 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
13:16:20.717 [NIOHTTPProducerImpl-450CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN SeekableCircularBufferNIO - The buffer has 7863100 bytes left to be read, has only 1221 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
13:16:21.548 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] INFO NIOSageTVMediaServer - Sending 'CLOSE' to SageTV server...
13:16:21.549 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] DEBUG FFmpegTransSageTVConsumerImpl - Error cleaning up broken connection => {}An established connection was aborted by the software in your host machine
13:16:21.549 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] INFO NIOSageTVMediaServer - Connecting to SageTV server on socket /127.0.0.1:7818...
13:16:21.549 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO NIOSageTVMediaServer - Sending 'CLOSE' to SageTV server...
13:16:21.549 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] DEBUG FFmpegTransSageTVConsumerImpl - Error cleaning up broken connection => {}An established connection was aborted by the software in your host machine
13:16:21.549 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO NIOSageTVMediaServer - Connecting to SageTV server on socket /127.0.0.1:7818...
13:16:21.549 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] INFO NIOSageTVMediaServer - Sending 'WRITEOPEN \\ds413\Sage-ds413-V2\Sage\MSNBCLivewithYasminVossoughian-48618665-0.ts 154505568' to SageTV server...
13:16:21.549 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO NIOSageTVMediaServer - Sending 'WRITEOPEN \\ds413\sage-ds413\PGATourGolf-QuickenLoansNationalFinalRound-48650588-0.ts 2038711829' to SageTV server...
13:16:21.561 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] INFO NIOSageTVMediaServer - Sending 'CLOSE' to SageTV server...
13:16:21.561 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] DEBUG FFmpegTransSageTVConsumerImpl - Error cleaning up broken connection => {}An established connection was aborted by the software in your host machine
13:16:21.561 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] INFO NIOSageTVMediaServer - Connecting to SageTV server on socket /127.0.0.1:7818...
13:16:21.562 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] INFO NIOSageTVMediaServer - Sending 'WRITEOPEN \\ds413\Sage-ds413-V2\Sage\MLBBaseball-SanFranciscoGiantsatArizonaDiamondbacks-48519375-0.ts 748271409' to SageTV server...
13:16:22.852 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN SeekableCircularBufferNIO - The buffer has 7863912 bytes left to be read, has only 409 bytes left for writing and 1316 bytes cannot be added. The queue buffer is full at 31457664 bytes.
13:16:22.880 [NIOHTTPProducerImpl-241CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN SeekableCircularBufferNIO - The buffer has 7863100 bytes left to be read, has only 1221 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
13:16:23.486 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN mpegts - Repeated 66 times: [395c83c0] PES packet size mismatch.
13:16:23.486 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN mpegts - [37f3ec80] PES packet size mismatch
13:16:23.492 [NIOHTTPProducerImpl-241CT-HDHomeRun Prime Tuner 131EDBD6-0] INFO SeekableCircularBufferNIO - Recovered 55272 bytes from the queue buffer.
13:16:23.508 [NIOHTTPProducerImpl-450CT-HDHomeRun Prime Tuner 131EDBD6-1] INFO SeekableCircularBufferNIO - Recovered 167132 bytes from the queue buffer.
13:16:23.697 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO SeekableCircularBufferNIO - Recovered 656684 bytes from the queue buffer.
13:16:23.697 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO SeekableCircularBufferNIO - Lost 1504188 bytes that could not be queued in the queue buffer.
13:16:28.983 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN mpegts - Repeated 4 times: [37f3ec80] PES packet size mismatch.
13:16:28.983 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN mpegts - [395c83c0] PES packet size mismatch
13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'WRITE 3160195888 122840' because the socket has not been initialized.
13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] DEBUG FFmpegTransSageTVConsumerImpl - Error cleaning up broken connection => {}The socket is not available.
13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO NIOSageTVMediaServer - Connecting to SageTV server on socket /127.0.0.1:7818...
13:16:36.566 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] INFO NIOSageTVMediaServer - Sending 'WRITEOPEN \\ds413\sage-ds413\PGATourGolf-QuickenLoansNationalFinalRound-48650588-0.ts 2038711829' to SageTV server...

wrapper.log as problem starts

INFO | jvm 1 | 2018/07/01 13:16:06.696 | 13:16:06.611 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN SeekableCircularBufferNIO - The buffer has 7863912 bytes left to be read, has only 409 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
INFO | jvm 1 | 2018/07/01 13:16:20.741 | 13:16:20.717 [NIOHTTPProducerImpl-450CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN SeekableCircularBufferNIO - The buffer has 7863100 bytes left to be read, has only 1221 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
INFO | jvm 1 | 2018/07/01 13:16:22.868 | 13:16:22.852 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN SeekableCircularBufferNIO - The buffer has 7863912 bytes left to be read, has only 409 bytes left for writing and 1316 bytes cannot be added. The queue buffer is full at 31457664 bytes.
INFO | jvm 1 | 2018/07/01 13:16:22.969 | 13:16:22.880 [NIOHTTPProducerImpl-241CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN SeekableCircularBufferNIO - The buffer has 7863100 bytes left to be read, has only 1221 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
INFO | jvm 1 | 2018/07/01 13:16:23.575 | 13:16:23.486 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN mpegts - Repeated 66 times: [395c83c0] PES packet size mismatch.
INFO | jvm 1 | 2018/07/01 13:16:23.575 | 13:16:23.486 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN mpegts - [37f3ec80] PES packet size mismatch
INFO | jvm 1 | 2018/07/01 13:16:29.036 | 13:16:28.983 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN mpegts - Repeated 4 times: [37f3ec80] PES packet size mismatch.
INFO | jvm 1 | 2018/07/01 13:16:29.036 | 13:16:28.983 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN mpegts - [395c83c0] PES packet size mismatch
INFO | jvm 1 | 2018/07/01 13:16:36.618 | 13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'WRITE 3160195888 122840' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:36.618 | 13:16:36.565 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:36.719 | 13:16:36.697 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN NIOSageTVMediaServer - Unable to send 'WRITE 463086864 83096' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:36.719 | 13:16:36.697 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:36.921 | 13:16:36.830 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN NIOSageTVMediaServer - Unable to send 'WRITE 527576128 92308' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:36.921 | 13:16:36.830 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.775 | 13:16:51.748 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN NIOSageTVMediaServer - Unable to send 'WRITE 470100204 67680' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.775 | 13:16:51.748 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.876 | 13:16:51.783 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'WRITE 3189696284 127352' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.876 | 13:16:51.783 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.977 | 13:16:51.876 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN NIOSageTVMediaServer - Unable to send 'WRITE 535694156 68996' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:16:51.977 | 13:16:51.876 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:17:06.830 | 13:17:06.749 [FFmpegTransSageTVConsumerImpl-243CT-HDHomeRun Prime Tuner 131EDBD6-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:17:06.830 | 13:17:06.784 [FFmpegTransSageTVConsumerImpl-258:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:17:06.931 | 13:17:06.869 [NIOHTTPProducerImpl-256:HDHomeRun HDHR4-2US Tuner 10437101-0] WARN SeekableCircularBufferNIO - The buffer has 7863100 bytes left to be read, has only 1221 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.
INFO | jvm 1 | 2018/07/01 13:17:06.931 | 13:17:06.877 [FFmpegTransSageTVConsumerImpl-452CT-HDHomeRun Prime Tuner 131EDBD6-1] WARN NIOSageTVMediaServer - Unable to send 'CLOSE' because the socket has not been initialized.
INFO | jvm 1 | 2018/07/01 13:17:08.654 | [GC pause (G1 Evacuation Pause) (young) 83M->13M(128M), 0.0022229 secs]

Any thoughts or help will be greatly appreciated.

thanks
__________________
Server: PhenomII X4 810, 16GB, 4850, C: 256GB Samsung SSD, D: HGST 3TB, E: HGST 4TB, H: 3T Seagate, 1.5 TB on NAS via UNC, Win 10 x64,
Sage 9 Cable provider is Comcast, Schedules Direct
Tuners: 4 ATSC - 2 seperate HD Homeruns all via Channel Master CM2016 on roof, 6 cable via 2 hdhomerun primes (opendct), 1 HD-PVR (in tuner priority order)
Clients: Wired: HD300, HD200, HD200 running Squeeze Slave, Placeshifters, HD200 (via wireless N bridge)
Reply With Quote
  #2358  
Old 07-01-2018, 07:19 PM
waynedunham waynedunham is offline
Sage Icon
 
Join Date: Sep 2004
Posts: 1,362
You don't say what you upgraded Java to. Many plugins especially won't work with the latest versions of Java. I'm not sure how well SageTV itself plays with the later versions of Java.

I have 2 servers and both are running 7.0.79 (7u79 for Windows).

I do know from reading here (and trying it myself when I upgraded to SageTV V9) that version 8 of Java breaks many plugins so I had to back out to 7.0.79 which has worked fine for me.
__________________
Wayne Dunham
Reply With Quote
  #2359  
Old 07-02-2018, 10:42 AM
Deacon Crusher Deacon Crusher is offline
Sage Expert
 
Join Date: Aug 2004
Location: Berkeley, CA
Posts: 503
Hey Wayne

Thanks for bringing this up. I've been running Java 8 for a while (months) as it seemed to make memory issues slightly better. The only thing it "broke" for me was the sagetv website landing page (on my server), all the sub pages work fine.

As part of troubleshooting I upgraded to latest version of 8. Seemed to help a tiny bit, but that was likely just perception.

I'll try going back to last version of 7 and see if that helps, I have my doubts, but at this point open to anything.

Thanks
__________________
Server: PhenomII X4 810, 16GB, 4850, C: 256GB Samsung SSD, D: HGST 3TB, E: HGST 4TB, H: 3T Seagate, 1.5 TB on NAS via UNC, Win 10 x64,
Sage 9 Cable provider is Comcast, Schedules Direct
Tuners: 4 ATSC - 2 seperate HD Homeruns all via Channel Master CM2016 on roof, 6 cable via 2 hdhomerun primes (opendct), 1 HD-PVR (in tuner priority order)
Clients: Wired: HD300, HD200, HD200 running Squeeze Slave, Placeshifters, HD200 (via wireless N bridge)
Reply With Quote
  #2360  
Old 07-02-2018, 10:46 AM
Deacon Crusher Deacon Crusher is offline
Sage Expert
 
Join Date: Aug 2004
Location: Berkeley, CA
Posts: 503
hmmm, I'm wondering if Windows firewall could have had some rules changed (or defender is doing something new/different.)

Maybe MS pushed out some definition/behavior changes.

All the "network" issues in the logs feel like I should look at the network, but the external/physical network seems fine, but maybe it's the "internal" network on that computer some firewall or internal opendct to sage routing that's triggering something.

I'm going to turn off the firewall to and see if that helps.

Will report back.

Thanks
__________________
Server: PhenomII X4 810, 16GB, 4850, C: 256GB Samsung SSD, D: HGST 3TB, E: HGST 4TB, H: 3T Seagate, 1.5 TB on NAS via UNC, Win 10 x64,
Sage 9 Cable provider is Comcast, Schedules Direct
Tuners: 4 ATSC - 2 seperate HD Homeruns all via Channel Master CM2016 on roof, 6 cable via 2 hdhomerun primes (opendct), 1 HD-PVR (in tuner priority order)
Clients: Wired: HD300, HD200, HD200 running Squeeze Slave, Placeshifters, HD200 (via wireless N bridge)
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 2 (1 members and 1 guests)
graywolf
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ATI TV Wonder Digital Cable Tuner & SageTV nyle Hardware Support 4 02-17-2009 10:12 PM
ATI TV Wonder Digital Cable Tuner rajczi Hardware Support 4 01-14-2008 08:24 PM
ATI TV Wonder™ Digital Cable Tuner dadams Hardware Support 4 01-09-2007 10:55 AM
Digital Cable - one guide - need HD on one tuner reg tv on other Kimper SageTV Beta Test Software 14 11-27-2006 08:15 PM
Multi-tuner Digital Cable mlbdude SageTV Software 0 06-26-2003 01:08 PM


All times are GMT -6. The time now is 10:02 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.