forked-daapd doesn't start, Segmentation fault?

    • OMV 2.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • forked-daapd doesn't start, Segmentation fault?

      Hello there,

      Here is my platform: Raspberry Pi B running OMV 2.x + RTC + USB HDD to hold system and shared data. All updated at the time of this post.

      I have installed the forked-daapd plugin as an intent to offload iTunes music and possibly, podcasts to have these available for when Apple decides they will remove ability to download one's library. I added a shared folder, currently containing one album for testing purposes. If it works properly on all computers, my intent is to download my whole collection, currently hosted on Apple's servers, and finally cut the tie.

      However, the plugin fails to start for some reason.

      Source Code

      1. tail /var/log/syslog
      2. Jun 17 11:47:58 pi-printer monit[2713]: 'forked-daapd' process is not running
      3. Jun 17 11:47:58 pi-printer monit[2713]: 'forked-daapd' trying to restart
      4. Jun 17 11:47:58 pi-printer monit[2713]: 'forked-daapd' start: /etc/init.d/forked-daapd
      5. Jun 17 11:48:32 pi-printer monit[2713]: 'forked-daapd' failed to start
      6. Jun 17 11:49:03 pi-printer monit[2713]: 'localhost' loadavg(5min) of 2.9 matches resource limit [loadavg(5min)>2.0]
      7. Jun 17 11:49:03 pi-printer monit[2713]: 'localhost' 'localhost' loadavg(1min) check succeeded [current loadavg(1min)=1.8]
      8. Jun 17 11:49:03 pi-printer monit[2713]: 'forked-daapd' process is not running
      9. Jun 17 11:49:03 pi-printer monit[2713]: 'forked-daapd' trying to restart
      10. Jun 17 11:49:03 pi-printer monit[2713]: 'forked-daapd' start: /etc/init.d/forked-daapd
      11. Jun 17 11:49:38 pi-printer monit[2713]: 'forked-daapd' failed to start
      Display All


      then I tried

      Source Code

      1. service forked-daapd restart
      2. Restarting DAAP/DACP (iTunes) server, support for AirPlay and Spotify: forked-daapdSegmentation fault
      3. failed!


      Would there be any way to know specifically why it fails?

      Having experienced that with a previous hard drive, I tested the current HDD, and it thankfully didn't show any bad sectors through a read-only test.