bounguine Posted November 18, 2019 Posted November 18, 2019 (edited) Hi! I have Media Server 2.1.0.4 installed, which acts too strange. (1) When I start PC: - DVBViewer Media Server in Services is not running, - tray icon is grey, - TV is working on clients, - WEB UI is working. (2) When Media Server crashes (happens every day!) and when I start it in Services: - DVBViewer Media Server in Services is running, - tray icon is blue, - TV is not working on clients, - WEB UI is not working. The only thing I can do to restart Media Server is to restart PC to get case (1) Why? NB I exluded svcdebug.log, because there is not enough space for support.zip here. But it looks like : Spoiler Zitat 18.11.19 14:16:39.088 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:16:39.089 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:16:39.090 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:16:39.091 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:16:39.092 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:16:39.092 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:16:40.114 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:16:40.114 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:16:40.114 TBDADigitalDevices SetTuner TType: 1, Freq: 10775, Symrate: 29900, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 1061, VPID: 1060, PMT: 106, SID: 1506, TID: 11300, NID: 318, SatMod: 22, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:16:49.243 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:16:49.244 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:16:49.244 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:16:49.245 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:16:49.246 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:16:49.247 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:16:55.337 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:16:55.337 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:16:55.337 TBDADigitalDevices SetTuner TType: 1, Freq: 10892, Symrate: 27500, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 92, VPID: 163, PMT: 1004, SID: 4804, TID: 11900, NID: 318, SatMod: 22, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:16:59.400 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:16:59.401 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:16:59.402 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:16:59.403 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:16:59.404 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:16:59.404 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:09.557 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:17:09.558 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:17:09.559 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:17:09.560 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:17:09.561 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:17:09.562 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:10.580 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:10.580 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:10.580 TBDADigitalDevices SetTuner TType: 1, Freq: 10930, Symrate: 30000, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 502, VPID: 501, PMT: 4369, SID: 50, TID: 12100, NID: 318, SatMod: 22, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:17:19.713 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:17:19.714 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:17:19.715 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:17:19.716 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:17:19.717 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:17:19.717 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:25.805 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:25.844 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:25.844 TBDADigitalDevices SetTuner TType: 1, Freq: 10971, Symrate: 29700, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 503, VPID: 502, PMT: 501, SID: 17201, TID: 12300, NID: 318, SatMod: 6, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:17:29.870 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:17:29.871 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:17:29.872 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:17:29.873 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:17:29.874 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:17:29.875 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:40.027 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:17:40.028 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:17:40.028 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:17:40.030 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:17:40.030 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:17:40.031 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:41.043 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:41.043 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:41.043 TBDADigitalDevices SetTuner TType: 1, Freq: 11013, Symrate: 29900, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 1811, VPID: 1810, PMT: 1981, SID: 17711, TID: 12500, NID: 318, SatMod: 14, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:17:50.183 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:17:50.187 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:17:50.191 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:17:50.195 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:17:50.199 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:17:50.203 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:17:56.276 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:56.276 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:17:56.276 TBDADigitalDevices SetTuner TType: 1, Freq: 11258, Symrate: 27500, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 112, VPID: 111, PMT: 110, SID: 1901, TID: 300, NID: 318, SatMod: 6, DiseqCVal: 130, Flags: 24, Group: 3 18.11.19 14:18:00.337 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:18:00.338 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:18:00.339 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:18:00.340 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:18:00.341 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:18:00.342 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:18:10.494 TDVBWebserver Connect Could not connect 192.168.1.140:8089 18.11.19 14:18:10.495 TDVBWebserver Connect Could not connect 192.168.1.139:8089 18.11.19 14:18:10.496 TDVBWebserver Connect Could not connect 127.0.0.1:8089 18.11.19 14:18:10.497 TStreamManager InitHttpServer Could not connect 192.168.1.140:7522 18.11.19 14:18:10.497 TStreamManager InitHttpServer Could not connect 192.168.1.139:7522 18.11.19 14:18:10.498 TStreamManager InitHttpServer Could not connect 127.0.0.1:7522 18.11.19 14:18:11.508 TEPGUpdater AllocateHardware Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:18:11.508 TEPGUpdater Release Digital Devices DVB-S2 Tuner 2 (1) 18.11.19 14:18:11.508 TBDADigitalDevices SetTuner TType: 1, Freq: 11373, Symrate: 27500, LOF: 9750, Tone: 0, Pol: 0, DiseqC: 9, FEC: 0, APID: 5012, VPID: 5011, PMT: 5010, SID: 501, TID: 900, NID: 318, SatMod: 6, DiseqCVal: 130, Flags: 24, Group: 3 support.zip Edited November 18, 2019 by Griga spoiler tags added Quote
HaraldL Posted November 18, 2019 Posted November 18, 2019 First of all, your windows firewall ist set to "public firewall" like when you're connected to a insecure public wifi. In this mode the firewall is blocking many things that connect to devices/services outside your pc (from above log I think 192.168.1.139, 192.168.1.140 are such devices). If this is your home network as I think you should set all windows devices on this network to "private" mode so they can communicate. There are many explanations on the web when searching for "windows 10 network private" like this one for example. Regarding space for files here on the forum: You have to delete old files to regain space by clicking on your user icon top right, in the menu you find the option to delete old files. Quote
bounguine Posted November 18, 2019 Author Posted November 18, 2019 (edited) Thanks. I don't have Windows firewall to be configured. 192.168.1.139, 192.168.1.140 are 2 network interfaces of the server where MS is installed. PS I deleted all my previous files before opening the thread, but the space was not enough anyway. PS/2 I rebooted the PC at 16:39 and as I said above now I have case (1) - all is working, but in Services MS is not started and icon is grey. WEB UI can be accessed both by: http://192.168.1.139:8089/ http://192.168.1.140:8089/ I attached the log, which I make shorter to be uploaded normally. The problem appeared when I switched from RS to MS svcdebug.log Edited November 18, 2019 by bounguine Quote
Griga Posted November 19, 2019 Posted November 19, 2019 vor 5 Stunden schrieb bounguine: I don't have Windows firewall to be configured. Of course you have. Every Windows user has it. It's built-in. Obviously your PC is misconfigured in this respect. If it is part of a home network, you need to configure it accordingly. https://www.howtogeek.com/245982/whats-the-difference-between-private-and-public-networks-in-windows/ For correct firewall configuration see the last screenshot on this page. Quote
bounguine Posted November 19, 2019 Author Posted November 19, 2019 (edited) 2 hours ago, Griga said: Of course you have. Every Windows user has it. It's built-in. Obviously your PC is misconfigured in this respect. If it is part of a home network, you need to configure it accordingly. https://www.howtogeek.com/245982/whats-the-difference-between-private-and-public-networks-in-windows/ For correct firewall configuration see the last screenshot on this page. I switched it totally off (for all networks) on the PC with MS as I use Microtik firewall and I have Linux envoronment. https://www.lifewire.com/how-to-disable-the-windows-firewall-2624505 Cannot attached screenshots right now. On other PCs in my network I cannot even configure Windows firewall as they are only Linux, VMWare or Android. For WAN all ports of MS PC are closed by Microtik NAT. Why are you talking about Windows Firewall on PCs in my network then? Anyway firewall is not the answer why: - MS doesn't start as service according to Windows Services.msc whenPC starts, - MS without starting as service works, - upon crash starting MS as service won't help. And I don't understand why you started talking about firewall when seeing my logs upon crash. In them 192.168.1.139, 192.168.1.140 and 127.0.0.1 are network interfaces of the PC where MS is installed. So even if firewall was swithed on, it won't block them. Definitely they show that MS is totally down untill PC's reboot. And you might miss my point that with the same configuration RS didn't have such a problem. Obviously not starting MS as service has nothing todo with firewall Edited November 19, 2019 by bounguine Quote
Griga Posted November 19, 2019 Posted November 19, 2019 vor 3 Stunden schrieb bounguine: Why are you talking about Windows Firewall on PCs in my network then? Because of "Public Firewall Profile is active" in your SystemInfo.txt. This is what the Windows API reports. You didn't report your firewall setup before (what you should have done), but had us guessing. Besides that, a public network configuration is not only a firewall thing, but affects network operations in your PC as a whole. See the link that I've provided above. Anyway, the DMS is encountering a severe network problem in your PC, as you can see in your log excerpts. None of the server units is The Web Server and the Live Streaming Server are not able to set up a listening socket (listening for incoming connections), not even on localhost. They fail altogether. This is not a known DMS issue, so it must be related to your configuration somehow. BTW: Why don't you use the current 2.1.5.2 DMS version? A 2.1.0.4 version has never been released. Where did you get it from? Well, it's a typo. You are using 2.1.4.0, as your SystemInfo.txt reports. It has been released in January. Quote
bounguine Posted November 19, 2019 Author Posted November 19, 2019 The version might be a misprint. So Firewall is guilty? OK. In 2 more houses I have the same configuration and have no issues. OK. That doesn't matter Why then after reboot MS service doesn't start automatically, but works through LAN? Firewall doesn't let it start? If I start it manually, it starts. Firewall does nothing to prevent me from starting it. My question was mainly why service doesn't start automatically, but MS works. Firewall? Quote
Griga Posted November 19, 2019 Posted November 19, 2019 vor einer Stunde schrieb bounguine: Why then after reboot MS service doesn't start automatically, but works through LAN? That's impossible. It can't work without running. Maybe the start isn't signalled correctly. Messages like TDVBWebserver Connect Could not connect 192.168.1.140:8089 can be caused by an already occupied port 8089, maybe because another not completely stopped DMS instance is still active in the background, dunno... What you can try for comparison: Disable the automatic start as service, reboot and see how it works if you start DVBVservice.exe as application in your user account. Just double-click it. A small dummy window will appear that allows to close the DMS again. Please note that this mode entails some restrictions. Particularly the tray tool and the DMS options (scvcoptions.exe) don't recognize that the DMS is running. Before clicking OK in the options, you need to close the DMS manually and start it again afterwards. There will be an enhanced suppport for the application mode in the next release. And you should update to 2.1.5.2. From the change log: Am 7.9.2019 um 18:58 schrieb hackbart: Fix: Channel List: Empty root or category names could let the Media Server crash when loading the channel list on start (see here). Quote
bounguine Posted November 19, 2019 Author Posted November 19, 2019 (edited) I cannot reboot the server now, as my family watches TV. What I did. I stopped DMS in Services. And all is working. See the picture So you misunderstood me. I did't ask why DMS crashes. I asked why DMS starts without starting as a service. And why when it crashes for some reason, I cannot get DMS working simply staring the service. As you see, I can start and stop service, but nothing happens. As for firewall, I opened many connections from clients (I have 13 tuners plus DVBViewer can open up to 6 simultanious connections to DVBLink to get IPTV) and I see no firewall conflict described by you) Edited November 19, 2019 by bounguine not enough info Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.