Hey @cahern7 I took a look at the logs you sent in a DM.
The server logs look reasonable, with only a few errors about permissions on some audio files. Check the paths, subdirectories, and files for the correct read access in these:
/bot/Music/Flying Lotus/Cosmogramma (2010
/bot/Music/Michael Mayer/Immer (2002)
The two things that stood at when glancing over your server logs for common problems were:
- IPv6 is enabled in your PMS Network Show Advanced settings, but it’s mostly likely not needed and it’s known to cause problems with Plex unless you have a perfect LAN.
- I see docker is involved or being scanned.
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - Network interfaces:
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - * 2 enp2s0 (192.168.1.40) (loopback: 0)
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - * 5 docker0 (172.17.0.1) (loopback: 0)
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - * 1 lo (::1) (loopback: 1)
Dec 23, 2019 15:33:38.716 [0x7f3e5b747b80] DEBUG - * 2 enp2s0 (fe80::672:41bc:22bf:7d61%enp2s0) (loopback: 0)
Though PMS is detecting a docker, it’s looking like you’ve avoided the problem of putting PMS inside that docker, because PMS is correctly deciding to use both the loopback and 192.168.1.0 address space:
Dec 23, 2019 15:33:38.716 [0x7f3deaffd700] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Dec 23, 2019 15:33:38.716 [0x7f3deaffd700] DEBUG - NetworkService: Browsing on interface 192.168.1.40 on broadcast address 192.168.1.255 (index: 1)
Dec 23, 2019 15:33:38.716 [0x7f3deaffd700] DEBUG - NetworkService: Browsing on interface 127.0.0.1 on broadcast address 127.255.255.255 (index: 0)
Dec 23, 2019 15:33:38.716 [0x7f3deaffd700] DEBUG - NetworkService: Browsing on interface 192.168.1.40 on broadcast address 192.168.1.255 (index: 1)
Dec 23, 2019 15:33:40.716 [0x7f3deaffd700] DEBUG - NetworkService: Browsing on interface 192.168.1.40 on broadcast address 239.255.255.250 (index: 0)
So I’m going to say for now disable IPv6 inside of PMS settings and Save Changes.
Then I’d shutdown PMS, restart it, and give it another 6min to do housekeeping. After that, continue music testing.
You may just be running into the usual Android mobil music problems I’ve been chasing for months in a number of loooooooong threads. Since the summer, music playback on Android mobil has been erratic, and countless attempts by me to get people to debug it for the devs has gone nowhere.
Essentially, if it’s the Android Mobil issue, I can’t test that because I don’t own one. What the developers consistently ask users for is this:
- Sign up in the forums here for access to Android Mobil beta testing.
- In 7-10 days your sign up will be approved.
- Each week the dev team releases a new Android Mobil build.
- Delete the current Android App completely from the phone.
- Power cycle the phone and the PMS computer hardware.
- Install the latest Android Mobil Beta from the forum links.
- Make sure both the Player and Server are in Debug mode and not Verbose mode.
- Playback some MP3s until it fails. Use public MP3s the developers can download.
- Grab the player log using the Android app.
- Download the server logs in
Settings - Troublehsooting - Download Logs - Zip up the player log file and the server folder of logs.
- Post a new topic in the Players Beta forum for each beta you test
- In your topic, provide the logs, your hardware details, and links to a few songs you are testing with. The devs will want to test the same music files you use.
While that seems like a lot of work, it’s really just
- new topic for each beta you test
- include a sample file
- logs
- steps to reproduce
I’ll look some more at your logs now. Unless I follow up with new information, you have the usual Android problems the devs haven’t had enumerated correctly for them.
If you want to commiserate with others,
Ok good luck!
