Jump to content

Search the Community

Showing results for tags 'init.d'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. thatoneguy99

    Emby-Server upgrade

    Good morning. I do not use an init.d script to run Emby. I use a systemd script to autostart my server. The problem is during an upgrade. Post installation script for Emby tries to run update-rc.d but since I do not have an startup script in the init.d folder I get an error that the install failed. How can i make the post installation script complete? Is there a way to turn off this functionality of the upgrade process? Any information is helpful! Thank you!
  2. ilikerolls

    New Emby init.d script Not Working?

    Has anyone tried the init.d script on Ubuntu 14.04 yet? I don't think I have ever gotten one of these init.d scripts to work without modifications, but this new one changed a lot. And from the command prompt I just get and of course PID 3783 will not exist afterwords sudo emby-server start emby-server start/running, process 3783​ This is all I get in the syslog Aug 13 13:03:13 CRACKHEADGDK /proc/self/fd/9: DEBUG: EMBYSERVER='/usr/lib/emby-server/emby-server'#012EMBY_BIN='/usr/lib/emby-server/MediaBrowser.Server.Mono.exe'#012EMBY_DATA='/var/lib/emby-server'#012EMBY_PATH='/usr/lib/emby-server'#012EMBY_PIDFILE='/var/run/emby-server.pid'#012EMBY_USER='emby'#012IFS=' #011#012'#012OPTIND='1'#012PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin'#012PPID='1'#012PS1='# '#012PS2='> '#012PS4='+ '#012PWD='/'#012TERM='linux'#012UPSTART_INSTANCE=''#012UPSTART_JOB='emby-server' Aug 13 13:03:13 CRACKHEADGDK kernel: [ 2690.725826] init: emby-server main process (3719) terminated with status 127 Aug 13 13:03:13 CRACKHEADGDK kernel: [ 2690.725836] init: emby-server main process ended, respawning Aug 13 13:03:13 CRACKHEADGDK kernel: [ 2690.728713] init: emby-server post-stop process (3724) terminated with status 127​
×
×
  • Create New...