Jump to content
Sebas798

ANSWERED Media scan fail with error: Value cannot be null. Parameter name: path

Recommended Posts

Sebas798

Greetings,

 

I had my emby server worked flawlessly under Ubuntu 14.04 LTS. When I upgraded to 16.04 LTS, the package was removed. I reinstalled it from the official PPA and since, I get the following error whenever a media scan is initiated. I cannot figure out why.

2016-08-14 05:38:40.7216 Error TaskManager: Error
    *** Error Report ***
    Version: 3.0.6060.0
    Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
    Operating system: Unix 4.4.0.34
    Processor count: 8
    64-Bit OS: True
    64-Bit Process: True
    Program data path: /var/lib/emby-server
    Mono: 4.2.1 (Debian 4.2.1.102+dfsg2-7ubuntu4)
    Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe
    Value cannot be null.
    Parameter name: path
    System.ArgumentNullException

The error does not say much about the problematic path.  Regarding this bad / useless error message, I already opened issue #2056.  Still, I would like to fix the problem.  Anybody can provide some help with this?  What actual parameter in what file is missing / misconfigured according to you?

 

Thank you in advance,
Sebas.

Share this post


Link to post
Share on other sites
Luke

Thanks for the report.

Share this post


Link to post
Share on other sites
Sebas798

Your are welcome.  However, now it has been 3 weeks I have not Emby working anymore.  Anybody can help me with my issues?  At this point, I have to consider switching to another media system since currently, I have none that works.

Share this post


Link to post
Share on other sites
Luke

Try installing the latest version of emby server.

Share this post


Link to post
Share on other sites
mastrmind11

Your are welcome.  However, now it has been 3 weeks I have not Emby working anymore.  Anybody can help me with my issues?  At this point, I have to consider switching to another media system since currently, I have none that works.

An upgrade should not have removed Emby.  If it did, it likely didn't do it cleanly and there may be remnants of the previous install lurking around.  Does the Emby path still exist?  If so, back up your library and do a proper uninstall of Emby and then a proper reinstall.  Then copy over your backed up library.

Share this post


Link to post
Share on other sites
Sebas798

I have installed emby-server-dev and it failed to start, with no logs nor traces showing up.  I reverted to emby-server and now it does not work anymore; same problem.  I ran "apt purge emby-server" and reinstalled it to no vail.  No logs under /var/lib/emby-server/logs.  Below, what shows up in syslog.  Nothing works anymore, with no log nor traces.  Help!

Sep  7 04:37:09 server systemd[1]: Started Emby Media Server.
Sep  7 04:37:10 server systemd[1]: Created slice User Slice of emby.
Sep  7 04:37:10 server systemd[1]: Starting User Manager for UID 124...
Sep  7 04:37:10 server systemd[1]: Started Session c13 of user emby.
Sep  7 04:37:10 server systemd[9863]: Reached target Timers.
Sep  7 04:37:10 server systemd[9863]: Reached target Paths.
Sep  7 04:37:10 server systemd[9863]: Reached target Sockets.
Sep  7 04:37:10 server systemd[9863]: Reached target Basic System.
Sep  7 04:37:10 server systemd[9863]: Starting Run Click user-level hooks...
Sep  7 04:37:10 server click[9876]: Nothing to install.
Sep  7 04:37:10 server click[9876]: Nothing to update.
Sep  7 04:37:10 server click[9876]: Nothing to delete.
Sep  7 04:37:10 server systemd[9863]: Started Run Click user-level hooks.
Sep  7 04:37:10 server systemd[9863]: Reached target Default.
Sep  7 04:37:10 server systemd[9863]: Startup finished in 454ms.
Sep  7 04:37:10 server systemd[1]: Started User Manager for UID 124.
Sep  7 04:37:10 server console-kit-daemon[5919]: console-kit-daemon[5919]: GLib-CRITICAL: Source ID 684 was not found when attempting to remove it
Sep  7 04:37:10 server console-kit-daemon[5920]: GLib-CRITICAL: Source ID 684 was not found when attempting to remove it
Sep  7 04:37:10 server systemd[1]: Stopping User Manager for UID 124...
Sep  7 04:37:10 server systemd[9863]: Stopped target Default.
Sep  7 04:37:10 server systemd[9863]: Stopped Run Click user-level hooks.
Sep  7 04:37:10 server systemd[9863]: Reached target Shutdown.
Sep  7 04:37:10 server systemd[9863]: Starting Exit the Session...
Sep  7 04:37:10 server systemd[9863]: Stopped target Basic System.
Sep  7 04:37:10 server systemd[9863]: Stopped target Timers.
Sep  7 04:37:10 server systemd[9863]: Stopped target Sockets.
Sep  7 04:37:10 server systemd[9863]: Stopped target Paths.
Sep  7 04:37:10 server systemd[9863]: Received SIGRTMIN+24 from PID 9919 (kill).
Sep  7 04:37:10 server systemd[1]: Stopped User Manager for UID 124.
Sep  7 04:37:10 server systemd[1]: Removed slice User Slice of emby.

Share this post


Link to post
Share on other sites
Sebas798

Well, I just got a new update from the PPA, and suddenly, emby-server just started to work.  I had to go through the reconfiguration wizard, but now all my movies are scanned.  Somehow, the latest stable emby-server 3.0.7100-71.1 fixed the issue of the previous release.

 

Case closed, except, of course, for the bug report #2056 I opened;  the log message must be improved.

Share this post


Link to post
Share on other sites
Luke

Thanks for confirming. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...