April 5, 20179 yr Hi guys ! I have some severe problems after updating to 6.3.3. my Plex Docker APP (Limetech) became unreachable (timed out)- worked perfectly before update.... what I tried: Complete remove of docker image and appdata of ALL Docker apps...didnt helped... downgrade to 6.3.2 didnt help installed "an other Plex" from binhex source..... nothing Now... my "old" VM win 10 runs perfectly. I wanted to install another win10 VM and it hangs up after the blue win icon is displayed just right after hitting any key to proceed installation. it shows 75% usage of cores applied to the VM but after long waiting nothing happens. Linux VM runs perfectly. here some logs PLEX Quote Apr 05, 2017 20:08:15.576 [0x7f9ba6736700] INFO - Plex Media Server v1.5.3.3580-4b377d295 - ubuntu PC x86_64 - build: linux-ubuntu-x86_64 ubuntu - GMT 02:00 Apr 05, 2017 20:08:15.576 [0x7f9ba6736700] INFO - Linux version: 4.9.19-unRAID (#1 SMP PREEMPT Thu Mar 30 08:32:28 PDT 2017), language: en-US Apr 05, 2017 20:08:15.576 [0x7f9ba6736700] INFO - Processor Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz Apr 05, 2017 20:08:15.576 [0x7f9ba6736700] INFO - ./Plex Media Server Apr 05, 2017 20:08:15.574 [0x7f9bb25c9840] DEBUG - BPQ: [Idle] -> [Starting] Apr 05, 2017 20:08:15.575 [0x7f9bb25c9840] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.13.0, threadsafe=1 Apr 05, 2017 20:08:15.576 [0x7f9bb25c9840] ERROR - SQLITE3:0x10, 5386, os_unix.c:33579: (19) mmap(/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm) - No such device Apr 05, 2017 20:08:15.576 [0x7f9bb25c9840] ERROR - SQLITE3:0x10, 5386, disk I/O error Apr 05, 2017 20:08:15.577 [0x7f9bb25c9840] ERROR - Database corruption: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 Apr 05, 2017 20:08:15.577 [0x7f9bb25c9840] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE) it seemes like Plex cannot start ?? as you can see.... "DL" was the VM I wanted to set up. Also i tried to use some other templates... and different ISOs(latest included) As Quote 2017-04-05 17:25:38.299+0000: 6496: info : libvirt version: 2.4.02017-04-05 17:25:38.299+0000: 6496: info : hostname: Tower2017-04-05 17:25:38.299+0000: 6496: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows 10' uuid=819bf3ed-fd0c-6195-c759-3e35ea354287 is tainted: high-privileges2017-04-05 17:25:38.299+0000: 6496: warning : qemuDomainObjTaint:3885 : Domain id=1 name='Windows 10' uuid=819bf3ed-fd0c-6195-c759-3e35ea354287 is tainted: host-cpu2017-04-05 17:25:41.922+0000: 6496: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:25:41.922+0000: 6496: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:25:42.141+0000: 6496: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Ubuntu' uuid=691d0bfb-c066-4e09-eb5e-d3e2a6448616 is tainted: high-privileges2017-04-05 17:25:42.141+0000: 6496: warning : qemuDomainObjTaint:3885 : Domain id=2 name='Ubuntu' uuid=691d0bfb-c066-4e09-eb5e-d3e2a6448616 is tainted: host-cpu2017-04-05 17:29:11.539+0000: 6484: warning : qemuDomainObjTaint:3885 : Domain id=3 name='DL' uuid=dceaeb4d-6e84-4b92-9a4c-df2da84f5daf is tainted: high-privileges2017-04-05 17:29:11.539+0000: 6484: warning : qemuDomainObjTaint:3885 : Domain id=3 name='DL' uuid=dceaeb4d-6e84-4b92-9a4c-df2da84f5daf is tainted: host-cpu2017-04-05 17:29:11.721+0000: 6484: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:29:11.721+0000: 6484: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:42:16.576+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=4 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: high-privileges2017-04-05 17:42:16.576+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=4 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: host-cpu2017-04-05 17:42:16.709+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:42:16.709+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:42:48.686+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=5 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: high-privileges2017-04-05 17:42:48.686+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=5 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: host-cpu2017-04-05 17:42:48.814+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:42:48.814+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:46:31.662+0000: 6485: warning : qemuDomainObjTaint:3885 : Domain id=6 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: high-privileges2017-04-05 17:46:31.662+0000: 6485: warning : qemuDomainObjTaint:3885 : Domain id=6 name='DL' uuid=53a03793-aeb4-3b0d-fb40-bc97a08882fe is tainted: host-cpu2017-04-05 17:46:31.852+0000: 6485: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:46:31.852+0000: 6485: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:48:26.732+0000: 6482: warning : qemuDomainObjTaint:3885 : Domain id=7 name='mint test' uuid=076bac74-aca8-7fb0-bb97-8d2fbaa2c3a7 is tainted: high-privileges2017-04-05 17:48:26.732+0000: 6482: warning : qemuDomainObjTaint:3885 : Domain id=7 name='mint test' uuid=076bac74-aca8-7fb0-bb97-8d2fbaa2c3a7 is tainted: host-cpu2017-04-05 17:49:17.711+0000: 6484: warning : qemuDomainObjTaint:3885 : Domain id=8 name='Linux' uuid=4c1bc23e-bed2-66b0-9206-a55ded041e49 is tainted: high-privileges2017-04-05 17:49:17.711+0000: 6484: warning : qemuDomainObjTaint:3885 : Domain id=8 name='Linux' uuid=4c1bc23e-bed2-66b0-9206-a55ded041e49 is tainted: host-cpu2017-04-05 17:50:36.988+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=9 name='Windows 8.1' uuid=acd15d92-4310-5836-3762-b5a942e9c0e0 is tainted: high-privileges2017-04-05 17:50:36.988+0000: 6481: warning : qemuDomainObjTaint:3885 : Domain id=9 name='Windows 8.1' uuid=acd15d92-4310-5836-3762-b5a942e9c0e0 is tainted: host-cpu2017-04-05 17:50:37.094+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:50:37.094+0000: 6481: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id2017-04-05 17:54:22.136+0000: 6483: warning : qemuDomainObjTaint:3885 : Domain id=10 name='Windows 8.1' uuid=acd15d92-4310-5836-3762-b5a942e9c0e0 is tainted: high-privileges2017-04-05 17:54:22.245+0000: 6483: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks2017-04-05 17:54:22.245+0000: 6483: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id I ran out of ideas.... Please help me to love my server again Greetings from Berlin. Michael
April 5, 20179 yr Community Expert It seems to be quite normal that when installing Windows 10 that you need to limit the VM to using a single core. After installation has completed you can increase the number. Why this I have no idea but it seems to be a common issue.
April 7, 20179 yr Author On 5.4.2017 at 9:35 PM, itimpi said: It seems to be quite normal that when installing Windows 10 that you need to limit the VM to using a single core. After installation has completed you can increase the number. Why this I have no idea but it seems to be a common issue. THIS HELPED....!!! THANK YOU !!! Now i still can not figure out whats the matter with PLEX all other Docker apps behave well. Plex is still unreachable....
April 12, 20179 yr On 4/7/2017 at 10:33 AM, ratz9999 said: Plex is still unreachable.... Hi. This might not work however I recently had a issue with Plex. I'm using the Docker provided by Limetech. When I click to go to the WebUI via the Docker panel I get this error on Chrome. This page isn’t working 192.168.0.8 didn’t send any data. ERR_EMPTY_RESPONSE I removed the docker and re-added and the same thing. It also does it on other browsers. I actually updated PMS today but it was doing the same before I did the update. Turns out the default path was incorrect. Unraid 6.2.4 URL is http://192.168.0.8:32400/web/index.html I needed to add the S to make it secure, now I get to the Logon https://192.168.0.8:32400/web/index.html
April 12, 20179 yr Author @Vishlander Tried your idea.... but nope im more worried about this line in the Log like i wrote before: Quote Apr 05, 2017 20:08:15.577 [0x7f9bb25c9840] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE) Im no expert but for me it seems like the server/Plex cannot be started.
April 21, 20179 yr Author the recent update of plex did not help... i think i will have to set up my server again
Archived
This topic is now archived and is closed to further replies.