Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 9 of 9
  1. #1
    Junior Member
    Join Date
    Feb 2021
    Posts
    11

    pCP Noticeably Slower and Auto Restart Fails

    I'm on pCP Version: 8.2.0 - 1627922070

    -Browsing through music and Tidal is progressively getting slower.
    -Rebooting no longer auto restarts Squeezelite and LMS. I have to start them manually.

    Anyone else having theses issues and know how to fix?

    This is on an Rpi 4B.

  2. #2
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,501
    That is an LMS version number. Get the pCP version from the pCP web interface. Boot logs would be useful
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #3
    Junior Member
    Join Date
    Feb 2021
    Posts
    11
    piCorePlayer v7.0.1 | www v00015 | linux 5.4.83-pcpCore-v7l | piCore v12.0pCP | Squeezelite v1.9.9-1386-pCP

    Boot Log...

    Starting piCorePlayer v7.0.1 startup...
    Starting rngd using /dev/hwrng... Done.
    Checking for boot files on mmcblk0p1...
    Trying to mount /dev/mmcblk0p1.
    ssh file found on mmcblk0p1.
    newpcp.cfg not found on mmcblk0p1.
    Setting default piCorePlayer repository...
    Generating sound card drop-down list...
    Starting wifi...
    Starting WiFi on wlan0...
    udhcpc: started, v1.31.1
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: no lease, forking to background
    Done.
    Loading configuration file... Done.
    Loading pcp-lms-functions... Done.
    Waiting for soundcard USB to populate. Done (1).
    Waiting for network........................................... .. Done (45).
    Starting Openssh server... Done.
    Mounting USB Drives...
    Mounting USB Drive: 568a754b-65a4-491d-8107-ba626e34eb2c...
    mount: /dev/mmcblk0p3 mounted on /mnt/data.
    Disk Mounted at /mnt/data.
    Done.
    Mounting Network Drive...
    mount: /mnt/volume1: mount(2) system call failed: No route to host.
    Disk Mount Error, Retrying 2 more times...sleeping 10 seconds.
    mount: /mnt/volume1: mount(2) system call failed: No route to host.
    Disk Mount Error, Retrying 1 more times...sleeping 10 seconds.
    mount: /mnt/volume1: mount(2) system call failed: No route to host.
    Disabling network mount from server at 192.168.1.246.
    Done.
    LMS data disk failed mount, LMS and squeezelite will not start.
    Starting httpd web server... Done.
    Starting to Advertise picoreplayer.local... Done.
    Setting CPU scaling governor to ondemand... Done.
    Creating static footer... Done.

    Finished piCorePlayer v7.0.1 startup.

    To setup piCorePlayer, use the web interface via a browser:
    - http://x.x.x.x

    Press [Enter] to access console.

    In the background, ntpd is syncing time between piCorePlayer and the internet.
    A large offset between 1970 and now is normal.

  4. #4
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,501
    Your network is not connected, what have you changed with WiFi.

    On a side note, running you LMS server on WiFi, is not recommended.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  5. #5
    Junior Member
    Join Date
    Feb 2021
    Posts
    11
    Network is connected and is working fine. Been using WiFi ever since and just recently auto start is not working. Everything still works fine it's just after reboot I have to manually start squeezlite then LMS.

    Unfortunately, my AP is in a location that is not possible to connect to it via ethernet.

    Maybe I'll try Volumio if this becomes too annoying

    Thanks anyway.

  6. #6
    Junior Member
    Join Date
    Feb 2021
    Posts
    11

    Fixed!

    Well sort of. Logs showed my NFS disk was failing to mount. So not sure why the heck it's not mounting.

    Unchecked this and LMS and Squeezelite is auto restarting again.

    So have to now figure out what the problem is with my NAS.

  7. #7
    Senior Member
    Join Date
    Feb 2011
    Location
    Cheshire, UK
    Posts
    6,234
    Quote Originally Posted by scslite View Post
    Well sort of. Logs showed my NFS disk was failing to mount. So not sure why the heck it's not mounting.

    Unchecked this and LMS and Squeezelite is auto restarting again.

    So have to now figure out what the problem is with my NAS.
    Running LMS on WiFi isn't recommended.
    Running LMS on WifFi with an NFS mount to a NAS even less so.
    If there is any delay in WiFi connection the mount is likely to fail. I doubt there is anything wrong with your NAS - it will all be network related.
    Jim
    https://jukeradio.double6.net


    VB2.4 storage QNAP TS419p (NFS)
    Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
    Office Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s
    Dining Room SB Radio
    Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
    Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
    Guest Room Joggler > Topping Amp -> Wharfedale Modus Cubes

  8. #8
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,501
    Clearly shows the network not getting a valid address fast enough. This is very common in WiFi systems.

    Code:
    Starting WiFi on wlan0...
    udhcpc: started, v1.31.1
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: no lease, forking to background
    pCP 8 has a setting that allows you to change the amount of time to wait for a valid DHCP address.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  9. #9
    Junior Member
    Join Date
    Feb 2021
    Posts
    11
    Quote Originally Posted by paul- View Post
    Clearly shows the network not getting a valid address fast enough. This is very common in WiFi systems.

    Code:
    Starting WiFi on wlan0...
    udhcpc: started, v1.31.1
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: no lease, forking to background
    pCP 8 has a setting that allows you to change the amount of time to wait for a valid DHCP address.
    Thanks will check this out. All is well for now and it was just the IP on the NAS.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •