Database error: Error: write EPIPE / throw er; // Unhandled 'error' event / Error: spawn ENOENT

[kenetik]

Just did a clean install on Ubuntu 12.04 64Bit with node -v 0.10.22 and npm -v v1.3.14.

I have also chmod -R 777 * within the MediaCenterJS directory.

Launching the application via node server.js results successfuly and the application starts/serves properly. Clicking the Movies icon results with the page partially loading and then throwing the following error:

info: socket.io started
MediacenterJS listening on port: 80
Screen ready...
Database error: Error: write EPIPE
Database error: Error: write EPIPE

events.js:72
        throw er; // Unhandled 'error' event
            ^
Error: spawn ENOENT
    at errnoException (child_process.js:980:11)
    at Process.ChildProcess._handle.onexit (child_process.js:771:34)
Child process exited

[kenetik]

This exact error is also being thrown when I attempt to "Clear 'media' Cache" of any type.

[osteenbergen]

Having the same problem on Ubuntu 13.10

[kenetik]

@osteenbergen

Having the same problem on Ubuntu 13.10

Did you experience this issue on a clean/fresh install?
Did you attempt adding any plugins?
Did you alter any configurations from default files?

---

I am asking, because I started over from scratch and no longer experience this specific issue, however I am experiencing Issue #43

[jansmolders86]

Hej guys,

Thanks for letting me know there are issues on Ubuntu. I currently develop on Windows so I'm grateful you took the time to notify me of these problems. My first thought would be there's a mismatch selecting the binaries, and Ubuntu uses the OXS binaries but I have to debug to be sure. Are you running as root or with sudo?

I'll have a look what is going on.
Thanks again!

[kenetik]

@jansmolders86

Are you running as root or with sudo?

I always run as root, please see my additional comment/reply to @osteenbergen as I was able to get it to perform correctly on the second attempt. I do not know what I changed. However, I am still experiencing Issue #43

Thank you for looking into it! I'll be happy to test and configurations that you setup as I run all Operating Systems except for Windows. =)

[osteenbergen]

I did a clean install, with no plugins and only changed the folders that the setup asked me.

Running as root and used the installing on ubuntu guide including the chmods.

The trace isn't very helpfull, but I will try to debug the issue.

[osteenbergen]

Owh I run using sudo. will try root

[kenetik]

@jansmolders86 I started the server and performed an strace on the process and have made a gist from it. I don't know if it will be of any benefit to you, however you can find it here: https://gist.github.com/kenetik/7518849#file-mcjs-events-js-throw-er

Please let me know how I can be of assistance in helping you resolve this, or any further issues, as I am very excited about this project and willing to help!

[jansmolders86]

Hej Guys,

So yesterday evening I had time to install Ubuntu 13.10 in a virtual box and installed the application. This is what I used:

• No chmod preformed (the server does this automatically, so this should not be needed.)
• Video folder: /home/jan/videos/
• Port: 3000
• Browser: Chromium
• running without sudo or root (Sudo is only needed when using a port below 1000)

And it worked out of the box. I had no errors. Could the browser be the culprit?

[kenetik]

@jansmolders86
Just did another fresh/clean install and I'm receiving the same errors again. I am running Chromium as well. Version 30.0.1599.114 Built on Ubuntu

If your online I can give you SSH access to my server throwing the error?

[jansmolders86]

Hej,

I would love to be able to debug your code! Thank you very much for the opportunity. Could you mail me the login info? And the time when I can take a crack at the code? I'm sure this issue can be resolved swiftly :)

Jan
(jansmolders86@gmail.com)

[jansmolders86]

Hej Kenetik and Osteenbergen,

Thanks to the debugging session yesterday evening I was able to pinpoint the cause of this issue.
for some reason, your Ubuntu distro does not work with the packaged SQLite3 binaries.

To fix this issue I have done two things:

• Updated the binaries to the newest version. (hopefully this is already sufficient)
• If the binaries still cause problems I've added a setting which allows you to tell MCJS you don't want to use the binaries included. (this setting can be found in the settings list)
  This means you have to install SQLite3 (sudo apt-get install sqlite3) yourself which will eliminate the problem all together.

Could you please test this solution as I did not have time to thoroughly test the fix I've committed.

Regards,
Jan