[SOLVED] Shairport on OMV - Working

  • Is it possible to run Shairport properly on OMV?


    I have managed to get Shairport working, but the Service only starts on the command: "sudo /etc/init.d/shairport status"


    It doesn't start when booting the System. Any suggestions?

    OMV - 3.2 backport kernel - Intel Atom D525 - Zotac NM10-DTX - 4gb Ram - 3 TB Wd Red

    Einmal editiert, zuletzt von spezialtrick ()

    • Offizieller Beitrag

    Did you try:


    sudo update-rc.d shairport default


    That should make it start when booting.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • It didn't work. Thats the output:


    root@Server:~# /etc/init.d/shairport start
    Starting shairport: .
    root@Server:~# sudo update-rc.d shairport default
    update-rc.d: using dependency based boot sequencing
    usage: update-rc.d [-n] [-f] <basename> remove
    update-rc.d [-n] <basename> defaults [NN | SS KK]
    update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
    update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
    -n: not really
    -f: force


    The disable|enable API is not stable and might change in the future.
    root@Server:~#

    OMV - 3.2 backport kernel - Intel Atom D525 - Zotac NM10-DTX - 4gb Ram - 3 TB Wd Red

    • Offizieller Beitrag

    I forgot an 's' on default. Should be:


    update-rc.d shairport defaults


    By the way... if you are logged in as root, you don't need sudo.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Just get the same output:


    root@Server:~# sudo update-rc.d shairport default
    update-rc.d: using dependency based boot sequencing
    usage: update-rc.d [-n] [-f] <basename> remove
    update-rc.d [-n] <basename> defaults [NN | SS KK]
    update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
    update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
    -n: not really
    -f: force


    The disable|enable API is not stable and might change in the future.
    root@Server:~#


    The second command works, but no start of shairport on booting:


    root@Server:~# service shairport start
    Starting shairport: .
    root@Server:~#

    OMV - 3.2 backport kernel - Intel Atom D525 - Zotac NM10-DTX - 4gb Ram - 3 TB Wd Red

  • Output with the missing 'S' :D :


    root@Server:/# update-rc.d shairport defaults
    update-rc.d: using dependency based boot sequencing
    insserv: warning: current stop runlevel(s) (0) of script `shairport' overwrites defaults (0 1 6).
    root@Server:/#



    Still no start on booting.

    OMV - 3.2 backport kernel - Intel Atom D525 - Zotac NM10-DTX - 4gb Ram - 3 TB Wd Red

    • Offizieller Beitrag

    Not that I want to debug the shairport init script (this is not an omv issue) but what is output of:


    cat /etc/init.d/shairport

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Cheers for your help mate!


    OMV - 3.2 backport kernel - Intel Atom D525 - Zotac NM10-DTX - 4gb Ram - 3 TB Wd Red

    • Offizieller Beitrag

    Not knowing anything about shairport, the init script waits for the network to start but must need something else started (syslog? local filesystem?) before it works. That is why it works when you /etc/init.d/shareport start but not at boot.


    Try changing the following as root:


    nano /etc/init.d/shairport
    change line
    # Required-Start: $network
    to
    # Required-Start: $all
    ctrl-o to save
    ctrl-x to exit

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Good to hear :)

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!