question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot enable video support

See original GitHub issue

Describe the bug I cannot see or play videos. I open the IP of the server, login, and see the message:

 Server error
Video support error, switching off..
Details: "Error: Error accessing ffmpeg, cant find executable: Error: ffmpeg was killed with signal SIGSEGV" 

I go to the pigallery2 web settings, try to disable/enable the video support, but get the same error.

In the terminal of the server I see:

<timestamp>[WARN] Handled error:
ErrorDTO {
  code: 13,
  message: 'Settings error: Error: Error accessing ffmpeg, cant find executable: Error: ffmpeg was killed with signal SIGSEGV',
  details: Error: Error accessing ffmpeg, cant find executable: Error: ffmpeg was killed with signal SIGSEGV
      at /home/pi/pigallery2/backend/model/diagnostics/ConfigDiagnostics.js:84:43
      at /home/pi/pigallery2/node_modules/fluent-ffmpeg/lib/capabilities.js:360:16
      at handleExit (/home/pi/pigallery2/node_modules/fluent-ffmpeg/lib/processor.js:170:11)
      at Socket.<anonymous> (/home/pi/pigallery2/node_modules/fluent-ffmpeg/lib/processor.js:197:11)
      at Socket.emit (events.js:215:7)
      at Pipe.<anonymous> (net.js:659:12)
}

Extra info I can execute ffmpeg and ffprobe in the terminal of the server. During npm install, I noticed the following lines, but I cannot spot an arm variant (maybe it pass too fast):

extract:@ffprobe-installer/win32-x64
extract:@ffprobe-installer/win32-ia32
extract:@ffmpeg-installer/win32-x64
extract:@ffmpeg-installer/win32-ia32

and at the end of npm install I see:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffmpeg-installer/darwin-x64@4.1.0 (node_modules/@ffmpeg-installer/darwin-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffmpeg-installer/darwin-x64@4.1.0: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffmpeg-installer/linux-ia32@4.1.0 (node_modules/@ffmpeg-installer/linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffmpeg-installer/linux-ia32@4.1.0: wanted {"os":"linux","arch":"ia32"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffmpeg-installer/linux-x64@4.1.0 (node_modules/@ffmpeg-installer/linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffmpeg-installer/linux-x64@4.1.0: wanted {"os":"linux","arch":"x64"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffmpeg-installer/win32-ia32@4.1.0 (node_modules/@ffmpeg-installer/win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffmpeg-installer/win32-ia32@4.1.0: wanted {"os":"win32","arch":"ia32"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffmpeg-installer/win32-x64@4.1.0 (node_modules/@ffmpeg-installer/win32-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffmpeg-installer/win32-x64@4.1.0: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffprobe-installer/darwin-x64@4.1.0 (node_modules/@ffprobe-installer/darwin-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffprobe-installer/darwin-x64@4.1.0: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffprobe-installer/linux-ia32@4.1.0 (node_modules/@ffprobe-installer/linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffprobe-installer/linux-ia32@4.1.0: wanted {"os":"linux","arch":"ia32"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffprobe-installer/linux-x64@4.1.0 (node_modules/@ffprobe-installer/linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffprobe-installer/linux-x64@4.1.0: wanted {"os":"linux","arch":"x64"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffprobe-installer/win32-ia32@4.1.0 (node_modules/@ffprobe-installer/win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffprobe-installer/win32-ia32@4.1.0: wanted {"os":"win32","arch":"ia32"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @ffprobe-installer/win32-x64@4.1.0 (node_modules/@ffprobe-installer/win32-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @ffprobe-installer/win32-x64@4.1.0: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"arm"})

Environment:

  • HW: Raspberry Pi 3 B+
  • OS: clean installation of “Raspbian Buster with desktop”, release 2019-09-26. Updated to the date of the post.
  • Browser: locally with Chromium, and from another PC of the network with Firefox.

Used app version:

  • from release v1.70, following the installation instructions of the repository.

Thanks.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
jabr1884commented, Jan 1, 2020

I’m happy to report that I’m fully operational with the Docker setup using nginx and https, and that video is working. Thanks again for your help!

The issue I had with nginx initially is that it would start on boot and then again with docker-compose. I had to use the following to prevent nginx from starting on boot: sudo update-rc.d -f nginx disable

1reaction
onlycparracommented, Jan 2, 2020

Hi, two things: (1) I tried the docker version: it runs smoodly. The video support works perfect. I will need to ffmpeg all my videos to mp4, but that’s part of the deal. (2) Regarding to the sudo thing, I just changed the port, and rebooted the machine. Also, at some point I did a recursive

chown -R pi:pi .

to all in the pigallery2 folder, but I cannot recall if it was before or after. With that said, I highly recommend to go for the docker option. It’s simple, it is easily configurable to run automatically on raspberry pi (RPI) reboot, and it is easy to update.

Once again, Thanks bpatrik. I’m away from my home, and this little project will allow my family to nicely see our family photos.

Read more comments on GitHub >

github_iconTop Results From Across the Web

My camera isn't working in Teams - Microsoft Support
Go to Settings > Privacy and Security > Site Settings > View permissions and data stored across sites. From here, enter “teams.microsoft.com” in...
Read more >
Use your camera & microphone - Google Chrome Help
Fix problems with your camera · Step 1: Check your site permissions in Chrome · Step 2: Check your system settings · Step...
Read more >
If you can't make or receive a FaceTime call on your iPhone or ...
A FaceTime call can't be switched into a phone call or a FaceTime audio call. To do this, end the current call and...
Read more >
How To Fix Voice & Video Call Not Working In Android
Let's get your Android voice and video call working again in this quick and easy guide. ... Your browser can't play this video....
Read more >
Troubleshooting Zoom video crashes
Restart your computer. Uninstall the Zoom client and reinstall the latest version from our Download Center. Visit your device's support and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found