majstang Posted March 19, 2013 Share Posted March 19, 2013 There seem to be something that resembles a bug in 1.24 and 1.25 (didn't see this with earlier versions). It has happened three times now. Two with 1.24 and just now with 1.25. If having several recordings going at once (4) and two of them executes an after recording task in form of comskip commercial removing when finshed. The task executes most of the script but gets interrupted somewhere at the end and renders the webserver unresponsive. It impossible to connect to the webinterface from here on. The recording engine seem to functioning alright though cuz the two remaining files in recording are growing in size, so RS hasn't crashed (yet). Streaming to client works fine as well. Don't know if the recent WebAPI changes could have anything to do with it? Some logs: 19.03.13 22:02:00.206 TRecording D:\TV\Recording Service\20130319_20-59-04_SVT1 HD_Veckans brott - S06E10 10.ts Discontinuities: 0 - Total size: 7,44 GB - Device:7231 BDA DVBC Tuner (1) 19.03.13 22:02:00.761 TRecording Release 7231 BDA DVBC Tuner (1) 19.03.13 22:02:00.964 CreateProcessW 2032 19.03.13 22:02:01.188 TRecordingEngine Releasereference TRecording: 3 19.03.13 22:02:01.199 TProcessTimer Process Params 19.03.13 22:02:01.995 TProcessTimer Proctimer started 19.03.13 22:02:01.995 TRecordingEngine AddReference TProcessTimer: 4 19.03.13 22:02:02.101 TRecording D:\TV\Recording Service\20130319_20-59-03_Sjuan_Mannen som talar med hundar - S07E07 20.ts Discontinuities: 3 - Total size: 2,85 GB - Device:7231 BDA DVBC Tuner (7) 19.03.13 22:02:06.996 TRecording Release 7231 BDA DVBC Tuner (7) 19.03.13 22:02:06.996 TRecording Destroy 7231 BDA DVBC Tuner (7) 19.03.13 22:02:07.164 TRecording Destroyed 7231 BDA DVBC Tuner (7) 19.03.13 22:02:07.164 TRecording hamDeleted 7231 BDA DVBC Tuner (7) 19.03.13 22:02:07.201 Createthumb WM_DATACOPY 19.03.13 22:02:07.201 Createthumb success 19.03.13 22:02:07.231 TRecordingEngine Releasereference TRecording: 3 19.03.13 22:02:07.254 TProcessTimer Process Params 19.03.13 22:02:07.387 TProcessTimer Proctimer started 19.03.13 22:02:07.387 TRecordingEngine AddReference TProcessTimer: 4 19.03.13 22:02:31.940 CreateProcessW 3780 19.03.13 22:03:18.372 TProcessTimer Proctimer finished 19.03.13 22:03:18.372 TRecordingEngine Releasereference TProcessTimer: 3 19.03.13 22:03:44.735 TProcessTimer Proctimer finished 19.03.13 22:03:44.735 TRecordingEngine Releasereference TProcessTimer: 2 Link to comment
Lars_MQ Posted March 19, 2013 Share Posted March 19, 2013 No the wep API is independend. The log extract seems fine to me. Link to comment
majstang Posted March 19, 2013 Author Share Posted March 19, 2013 Hm, yes and according to the log the process timers did finish ok. However the script did not and the webinterface crashed. The script content hasn't changed for over a year and has worked alright during that period. The script do talk to the WebAPI though, that's why I asked. If webserver crashes the script can't retrieve any status information from RS and won't operate ok. Wonder what can cause a webservercrash and everything else works fine? Never heard that a script can crash the webserver. Only recent change in my personal settings from v.1.24 and now is I did enable the CreateThumbs. I'll disable it again and see if problem disappears. Link to comment
majstang Posted March 20, 2013 Author Share Posted March 20, 2013 Hm, more trouble! I usually leave DVBViewer client running when hibernating PC at night. Today DVBViewer resumed alright from hibernation two times, the third streaming from RS to DVBViewer wasn't working. To get it working RS has to be stopped and restarted. This has happened a couple of times now. Once with RS 1.24 and once with RS 1.25. Never occured with earlier RS versions. According to log RS seems to try retuning but something goes wrong. No fun with these kind of troubles, I'll revert to last working RS. I'll post a support.zip though if devs wanna have a look support.zip Link to comment
majstang Posted March 20, 2013 Author Share Posted March 20, 2013 Hm again...webinterface crashes with RS 1.23.1 as well, which it didnt before. Starting to suspect a major chrome bug here. Chrome automatic update in all its glory Last update done March 13 and that coincides with the time when I first saw this issue. Time to give IE a chance... Link to comment
Lars_MQ Posted March 20, 2013 Share Posted March 20, 2013 I use firefox and I have no problems with the RS web interface Maybe something else interferes? Most anti virus programs have some kind of "web/link protection" Link to comment
majstang Posted March 20, 2013 Author Share Posted March 20, 2013 Yes, you're right! This may very well be AV related. F-secure, which I'm using, did large changes in their latest update some weeks ago. Before I could disable the Windows firewall altogether and the F-secure firewall took care of everything. After latest update F-secure are forcing us to have the windows firewall enabled and there's no way to disable it as long as using their software. Haven't made any windows firewall settings at all. Perhaps it's time to check the windows firewall option in the RS installer and things will go smoother?! In fact the issue resembles the config file wipeout issue I had earlier (which sometimes happens still) that was confirmed being caused by the F-secure firewall. The common thing is it works most of the times and suddenly it goes bad without any forewarning. No visible logic to why it happens at all. Link to comment
majstang Posted March 23, 2013 Author Share Posted March 23, 2013 (edited) Ok, now thing's back up and running as normal. Turns out the madmen on F-Secure (Internet Security 2013) has skipped their own basic firewall functionality and started to use Windows Firewall for that functionality. This without any warning and there's no way of disable F-Secure automatic updates. Once FSIS 2013 has been installed Windows Firewall can not be disabled. For everything to work as usual you have to tweak the settings in several places. I do believe it's time to choose an another Internet Security software and let F-Secure know this crap won't simply do. http://community.f-secure.com/fsecured/attachments/fsecured/Protection/4114/1/New%20Firewall%20Functionality%20in%20F-Secure%20Internet%20Security%202013.pdf The crashing RS webinterface with failing after recording tasks as consequence was fixed by checking the: "Allow LOCAL network in the Windows firewall for the Recording Service" checkbox option in 4th splashscreen in RS installer. To fix the DVBViewer client sometimes not resuming ok from hibernation I had to configure the Windows Firewall manually. Allowing DVBViewer Pro application communicating through the Windows firewall. The DVBViewer Pro app wasn't allowed, but several old DVBViewer Pro Beta were. Could be why it worked most of the times resuming from hibernation and sometimes not. Deleted them and configurated a new DVBViewer Pro item in allowed list. Edited March 23, 2013 by majstang Link to comment
Recommended Posts