User avatar
jbeale
Posts: 3500
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: PiKrellCam: motion vector detect + OSD web interface

Sat Feb 13, 2016 12:21 am

I had earlier recommended the automatic archive/cleaup bash script including the below code:

Code: Select all

if [[ ( "$_USED_SPACE" > "$_USED_SPACE_LIMIT" ) ]] ; then
 echo -e "used space over $_USED_SPACE_LIMIT%, deleting old files..."
It turns out that this is a STRING comparison and "100" < "90" because 1 is less than 9 and so if the disk becomes completely full, files are never deleted and the problem is never fixed. Improved code below uses the numerical comparison -gt and note it is needed to properly specify _VOLUME if you aren't storing media on external drive "/dev/sda1"

Code: Select all

#!/bin/bash

_ARCHIVE_OLDER_DAYS="-1 Days"  # how many days old for media before archiving
_VOLUME="/dev/sda1"     # volume to check for disk space usage
_USED_SPACE_LIMIT=90    # percent disk space used over which files are deleted

# Move _ARCHIVE_OLDER_DAYS stills and video to that date's archive folder
echo "archive_still day `date --date="$_ARCHIVE_OLDER_DAYS" +'%F'`"  > /home/pi/pikrellcam/www/FIFO
echo "archive_video day `date --date="$_ARCHIVE_OLDER_DAYS" +'%F'`"  > /home/pi/pikrellcam/www/FIFO

# if used space is over threshold, delete old files and directories to save storage space until threshold reached
# this keeps as much as possible files present
_USED_SPACE=`df  | grep $_VOLUME | awk '{print $5}' |  sed -e "s/\%//g"`
echo "used space: $_USED_SPACE"
echo "used space limit: $_USED_SPACE_LIMIT"


if [[ ( "$_USED_SPACE" -gt "$_USED_SPACE_LIMIT" ) ]] ; then
 echo -e "used space over $_USED_SPACE_LIMIT%, deleting old files..."

 _LOOP=0;

 while [[ ( "$_USED_SPACE" -gt "$_USED_SPACE_LIMIT" )  && ( "$_LOOP" < "100" ) ]] ; do
  _OLDEST=`find /home/pi/pikrellcam/media/archive/ -type f -printf '%T+ %p\n' | sort | head -n 1 | cut -d "+" -f 1 | sed -e "s/\-/\//g"`
  echo "oldest files:$_OLDEST"

  echo "delete oldest folder:/home/pi/pikrellcam/media/archive/$_OLDEST"
  rm -rfv "/home/pi/pikrellcam/media/archive/$_OLDEST"
  sync

  _USED_SPACE=`df  | grep $_VOLUME | awk '{print $5}' |  sed -e "s/\%//g"`
  echo "used space now: $_USED_SPACE%"
  _LOOP=$((_LOOP + 1))
 done

 echo "done"
 df
else
 echo -e "used space below $_USED_SPACE_LIMIT%, nothing to do!"
fi

tomtgrp
Posts: 41
Joined: Thu Jul 09, 2015 8:35 am

Re: PiKrellCam: motion vector detect + OSD web interface

Mon Feb 15, 2016 4:51 pm

jdupa wrote:EDIT: I found the problem, I had to install gst-rtsp-server-1.4.4 as pet Thomas' instructions...

Thank you ALL for your fantastic work!!!

I am having problems installing the streamer. I followed Thomas' instructions on Jessy and:

Code: Select all

[[email protected]:~]# gst-launch-1.0 --version
gst-launch-1.0 version 1.4.4
GStreamer 1.4.4
http://packages.qa.debian.org/gstreamer1.0
[[email protected]:~]# gst-inspect-1.0 | grep omx
omx:  omxmpeg2videodec: OpenMAX MPEG2 Video Decoder
omx:  omxmpeg4videodec: OpenMAX MPEG4 Video Decoder
omx:  omxh263dec: OpenMAX H.263 Video Decoder
omx:  omxh264dec: OpenMAX H.264 Video Decoder
omx:  omxtheoradec: OpenMAX Theora Video Decoder
omx:  omxvp8dec: OpenMAX VP8 Video Decoder
omx:  omxmjpegdec: OpenMAX MJPEG Video Decoder
omx:  omxvc1dec: OpenMAX WMV Video Decoder
omx:  omxh264enc: OpenMAX H.264 Video Encoder
[[email protected]:~]# git clone https://github.com/Gateworks/gst-gateworks-apps.git
Cloning into 'gst-gateworks-apps'...
remote: Counting objects: 73, done.
remote: Total 73 (delta 0), reused 0 (delta 0), pack-reused 73
Unpacking objects: 100% (73/73), done.
Checking connectivity... done.
[[email protected]:~]# cd gst-gateworks-apps
[[email protected]:~/gst-gateworks-apps]# make
Package gstreamer-rtsp-server-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gstreamer-rtsp-server-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gstreamer-rtsp-server-1.0' found
Package gstreamer-rtsp-server-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gstreamer-rtsp-server-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gstreamer-rtsp-server-1.0' found
compiling file: src/gst-variable-rtsp-server.c
src/gst-variable-rtsp-server.c:41:21: fatal error: gst/gst.h: No such file or directory
 #include <gst/gst.h>
                     ^
compilation terminated.
Makefile:108: recipe for target 'obj/gst-variable-rtsp-server.o' failed
make: *** [obj/gst-variable-rtsp-server.o] Error 1
Include files are gone from the repository, can they be posted here?

Thanks,
J


Try Installing this part, then repeat the failing step, maybe this is not optional as I thought:

Code: Select all

#optional,install gst-rtsp-server:
#here you can play with steaming & auth, look at test-auth in examples
wget http://gstreamer.freedesktop.org/src/gst-rtsp/gst-rtsp-server-1.4.4.tar.xz
tar xfvv gst-rtsp-server-1.4.4.tar.xz
cd gst-rtsp-server-1.4.4
./configure
make -j 4
make install
ldconfig
Edit 2015-02-16:
I checked on a fresh 2015-11-21-raspbian-jessie-lite.img, you have to install gst-rtsp-server first, it's not optional.
It's a prereq for building gst-gateworks-apps.
Updated the Instructions.


Tom

jdupa
Posts: 3
Joined: Mon May 18, 2015 10:52 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Wed Feb 17, 2016 5:09 pm

Edit 2015-02-16:
I checked on a fresh 2015-11-21-raspbian-jessie-lite.img, you have to install gst-rtsp-server first, it's not optional.
It's a prereq for building gst-gateworks-apps.
Updated the Instructions.
Yes, that helped, thanks Tom!!

Nestboxtech
Posts: 71
Joined: Fri Apr 11, 2014 9:45 pm
Contact: Website

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 21, 2016 5:57 pm

I'm running PiKrellcam on an A+ Raspi. I've want to add a network share as archive location, and cannot seem to figure out the permissions for Pikrellkam to create the folders / write to them or something.

I'm mounting a password & user restricted share on a networked windows PC via cifs in fstab:

Code: Select all

//192.XXX.X.X/SHARE/ModelA /mnt/SHARE/ cifs username=networkUserName,password=networkUserpwd,uid=1000,gid=1000,_netdev,x-systemd.automount 0 0
_netdev,x-systemd.automount is added otherwise it wont mount automatically at boot. I've checked an the share is mounted properly. I've also added the archive folder already as /mnt/SHARE/pikrellcam/media/archive

ls -lh of the mount point is as follows:

Code: Select all

[email protected]:/mnt $ ls -lh
total 4.0K
drwxr-xr-x 2 pi pi 4.0K Feb 21 07:35 SHARE
In the log of Pikrellcam, I get the following error message:

Code: Select all

========================================================
2016-02-21 17:00:16 ===== PiKrellCam 2.1.13 started =====
========================================================
using FIFO: /home/pi/pikrellcam/www/FIFO
using mjpeg: /run/pikrellcam/mjpeg.jpg
17:00:16 : execl:[sudo mkdir -p /mnt/SHARE/pikrellcam/media/archive]
Make directory failed: /mnt/SHARE/pikrellcam/media/archive
archive is indicated in .pikrellcam/pikrellcam.conf as follows:

Code: Select all

archive_dir /mnt/SHARE/pikrellcam/media/archive
Any help as to what I'm doing wrong would be appreciated,

Thanks,
Chris
http://nestboxtech.blogspot.co.uk/

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 21, 2016 8:04 pm

Nestboxtech wrote: I'm mounting a password & user restricted share on a networked windows PC via cifs in fstab:

Code: Select all

//192.XXX.X.X/SHARE/ModelA /mnt/SHARE/ cifs username=networkUserName,password=networkUserpwd,uid=1000,gid=1000,_netdev,x-systemd.automount 0 0
_netdev,x-systemd.automount is added otherwise it wont mount automatically at boot. I've checked an the share is mounted properly. I've also added the archive folder already as /mnt/SHARE/pikrellcam/media/archive

ls -lh of the mount point is as follows:

Code: Select all

[email protected]:/mnt $ ls -lh
total 4.0K
drwxr-xr-x 2 pi pi 4.0K Feb 21 07:35 SHARE
You need more write permission and with Windows filesystems you have to specify that at mount time.
In the fstab entry, try adding umask=0002 to the options field: ...uid=1000,gid=1000,umask=0002...

Nestboxtech
Posts: 71
Joined: Fri Apr 11, 2014 9:45 pm
Contact: Website

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 21, 2016 11:04 pm

I cant seem to get umask to work with mount.cifs. Oddly, if I just echo a string to a file in the mounted folder directory, there is no issue. Looking at 'top' pikrellcam is running under the 'pi' user, so I'm a bit stumped at what is going on.
http://nestboxtech.blogspot.co.uk/

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 21, 2016 11:28 pm

Nestboxtech wrote:I cant seem to get umask to work with mount.cifs. Oddly, if I just echo a string to a file in the mounted folder directory, there is no issue. Looking at 'top' pikrellcam is running under the 'pi' user, so I'm a bit stumped at what is going on.
The mkdir is done with sudo so it's root trying to set up directories. Can you "sudo echo ..." to a file?
You could manually make the archive directory and the video saving might work. because that is done
as user pi. From the web page the video viewing/deleting is done as user www-data, so reads might
work, but deleting an archived video probably wouldn't.

Or, I'm not really familiar with cifs, but I just stumbled on some web pages mentioning dir_mode and
maybe you could try using dir_mode=0777,file_mode=0666.
Do a search on "cifs dir_mode", I found:
http://superuser.com/questions/456243/m ... e-writable

Note that if you set gid, it should be the www-data gid 33.

User avatar
jbeale
Posts: 3500
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

reported disk space slightly off?

Mon Feb 22, 2016 12:16 am

I just changed my media directory to an external USB stick by uncommenting the MOUNT_DISK=sda1
line in ~/pikrellcam/scripts/startup. It works OK, but I notice the reported disk space used on the thumbs page (5.4%) does not quite agree with 'df' running on the machine (1%). I wonder why the web page reports 3.3 GB in use, when 'du' can find only 120 MB of files on /home/pi/pikrellcam/media/

Code: Select all

http://rp22/media-archive.php?mode=media&type=thumbs
Disk: 61.0GB   Free: 57.7GB   Used: 3.3GB (5.4 %)

[email protected] ~ $ df /dev/sda1
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/sda1       59569284 173596  56346680   1% /home/pi/pikrellcam/media
EDIT: nevermind, I guess it is something like the difference between total space and usable space (maybe due to formatting overhead?)

Code: Select all

[email protected] ~ $ df -h /dev/sda1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        57G  260M   54G   1% /home/pi/pikrellcam/media

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: reported disk space slightly off?

Mon Feb 22, 2016 12:57 am

jbeale wrote: EDIT: nevermind, I guess it is something like the difference between total space and usable space (maybe due to formatting overhead?)

Code: Select all

[email protected] ~ $ df -h /dev/sda1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        57G  260M   54G   1% /home/pi/pikrellcam/media
I think the df command used disk space may be the space used by files and does not include
all space actually used as you suggest. So maybe its formula is something like
total = free + used-by-user + filesystem-overhead
On the web page I just calculate used = total - free where total and free are from PHP functions.
So probably my used space calculation is naive and maybe I should just be reporting total, free and
free percent and not try to report used. I'll look more into it to be sure.

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sat Feb 27, 2016 10:51 am

Hello
This installscript is not working....

Code: Select all

.
.
.
nginx (1.2.1-2.2+wheezy4) wird eingerichtet ...
php5 (5.4.45-0+deb7u2) wird eingerichtet ...
./install-pikrellcam.sh: Zeile 135: realpath: Kommando nicht gefunden.
Replacing /usr/local/bin/pikrellcam link
Adding a pikrellcam autostart command to /etc/rc.local:
su pi -c '(sleep 5; /home/pi/pikrellcam/pikrellcam) &'
Adding to /etc/sudoers.d: www-data permission to run pikrellcam as user pi:
Installing /etc/nginx/sites-available/pikrellcam
    nginx web server port: 80
    nginx web server root: /home/pi/pikrellcam/www
./install-pikrellcam.sh: Zeile 270: realpath: Kommando nicht gefunden.
Changing /etc/nginx/sites-enabled/default link to pikrellcam
Restarting nginx: nginx: [emerg] open() "/etc/nginx/snippets/fastcgi-php.conf" failed (2: No such file or directory) in /etc/nginx/sites-enabled/default:48
nginx: configuration file /etc/nginx/nginx.conf test failed

Install finished.
This install script does not automatically start pikrellcam.
To start pikrellcam, open a browser page to:
    http://your_pi
and click on the "System" panel and then the "Start PiKrellCam" button.
PiKrellCam can also be run from a Pi terminal for testing purposes.
Automatic pikrellcam starting at boot is enabled.

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sat Feb 27, 2016 3:31 pm

0lly wrote:Hello
This installscript is not working....

Code: Select all

.
.
.
nginx (1.2.1-2.2+wheezy4) wird eingerichtet ...
php5 (5.4.45-0+deb7u2) wird eingerichtet ...
./install-pikrellcam.sh: Zeile 135: realpath: Kommando nicht gefunden.
Replacing /usr/local/bin/pikrellcam link
Adding a pikrellcam autostart command to /etc/rc.local:
su pi -c '(sleep 5; /home/pi/pikrellcam/pikrellcam) &'
Adding to /etc/sudoers.d: www-data permission to run pikrellcam as user pi:
Installing /etc/nginx/sites-available/pikrellcam
    nginx web server port: 80
    nginx web server root: /home/pi/pikrellcam/www
./install-pikrellcam.sh: Zeile 270: realpath: Kommando nicht gefunden.
Changing /etc/nginx/sites-enabled/default link to pikrellcam
Restarting nginx: nginx: [emerg] open() "/etc/nginx/snippets/fastcgi-php.conf" failed (2: No such file or directory) in /etc/nginx/sites-enabled/default:48
nginx: configuration file /etc/nginx/nginx.conf test failed

Install finished.
This install script does not automatically start pikrellcam.
To start pikrellcam, open a browser page to:
    http://your_pi
and click on the "System" panel and then the "Start PiKrellCam" button.
PiKrellCam can also be run from a Pi terminal for testing purposes.
Automatic pikrellcam starting at boot is enabled.
Realpath was not installed - looks like a script bug for wheezy installs. Try installing realpath:

Code: Select all

sudo apt-get install realpath
and rerun the install script.

User avatar
jbeale
Posts: 3500
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: PiKrellCam: motion vector detect + OSD web interface

Sat Feb 27, 2016 7:11 pm

[Edit: Solved - see following post.] Had a problem today with PiKrellCam motion recording 1080p to a USB stick (/dev/sda1) while also displaying vectors and regions on the web page. Something seems to have become confused. I can ssh in ok, but USB disk now appears to be empty, and I can't reboot the device or unmount the disk. MP4Box was stuck at 100% cpu before I killed that process. Any ideas?

Code: Select all

[email protected] ~ $ sudo umount -f /dev/sda1
umount2: Device or resource busy
umount: /home/pi/pikrellcam/media: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy

Code: Select all

10:44:50 : Video record: /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.44.50_108.mp4.h264 ...
10:44:50 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:50 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:52 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:52 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:52 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:52 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:44:58 : Video motion record stopped. Header size: 29  h264 file size: 8033382
10:44:58 :     first detect: direction  totals - direction: 19  burst: 0  max burst count: 0
10:44:58 : execl:[(MP4Box -quiet -tmp /tmp -fps 24 -add /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.44.50_108.mp4.h264 /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.44.50_108.mp4 2> /dev/null && rm /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.44.50_108.mp4.h264 )]
10:44:58 : execl:[/home/pi/pikrellcam/scripts-dist/_thumb /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg /home/pi/pikrellcam/media /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 60 73 262 78]
  convert /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg -crop 73x73+226+42 -resize 150x150\! /home/pi/pikrellcam/media/thumbs/motion_2016-02-27_10.44.50_108.th.jpg
10:44:58 : event_preview_dispose(); removing /run/pikrellcam/motion_2016-02-27_10.44.50_108.jpg
10:45:18 : command_process: motion show_regions toggle
10:45:18 : command_process: motion show_vectors toggle
10:45:19 : Video record: /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.19_109.mp4.h264 ...
10:45:19 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.19_109.jpg
10:45:20 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.19_109.jpg
10:45:24 : Video motion record stopped. Header size: 29  h264 file size: 5785774
10:45:24 :     first detect: direction  totals - direction: 2  burst: 0  max burst count: 0
10:45:24 : execl:[(MP4Box -quiet -tmp /tmp -fps 24 -add /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.19_109.mp4.h264 /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.19_109.mp4 2> /dev/null && rm /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.19_109.mp4.h264 )]
10:45:24 : execl:[/home/pi/pikrellcam/scripts-dist/_thumb /run/pikrellcam/motion_2016-02-27_10.45.19_109.jpg /home/pi/pikrellcam/media /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 152 62 161 62]
  convert /run/pikrellcam/motion_2016-02-27_10.45.19_109.jpg -crop 152x152+85+0 -resize 150x150\! /home/pi/pikrellcam/media/thumbs/motion_2016-02-27_10.45.19_109.th.jpg
10:45:24 : event_preview_dispose(); removing /run/pikrellcam/motion_2016-02-27_10.45.19_109.jpg
10:45:24 : Video record: /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.24_110.mp4.h264 ...
10:45:24 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg
10:45:25 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg
10:45:25 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg
10:45:29 : Video motion record stopped. Header size: 29  h264 file size: 5337852
10:45:29 :     first detect: direction  totals - direction: 4  burst: 0  max burst count: 0
10:45:29 : execl:[(MP4Box -quiet -tmp /tmp -fps 24 -add /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.24_110.mp4.h264 /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.24_110.mp4 2> /dev/null && rm /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.24_110.mp4.h264 )]
10:45:29 : execl:[/home/pi/pikrellcam/scripts-dist/_thumb /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg /home/pi/pikrellcam/media /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 190 83 160 62]
  convert /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg -crop 190x190+65+0 -resize 150x150\! /home/pi/pikrellcam/media/thumbs/motion_2016-02-27_10.45.24_110.th.jpg
10:45:29 : event_preview_dispose(); removing /run/pikrellcam/motion_2016-02-27_10.45.24_110.jpg
10:45:35 : Video record: /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.35_111.mp4.h264 ...
10:45:35 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:35 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:35 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:37 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:37 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:45:48 : Video motion record stopped. Header size: 29  h264 file size: 11537206
10:45:48 :     first detect: direction  totals - direction: 33  burst: 8  max burst count: 1068
10:45:48 : execl:[(MP4Box -quiet -tmp /tmp -fps 24 -add /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.35_111.mp4.h264 /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.35_111.mp4 2> /dev/null && rm /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.45.35_111.mp4.h264 )]
10:45:48 : execl:[/home/pi/pikrellcam/scripts-dist/_thumb /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg /home/pi/pikrellcam/media /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 426 251 400 156]
  convert /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg -crop 426x426+187+0 -resize 150x150\! /home/pi/pikrellcam/media/thumbs/motion_2016-02-27_10.45.35_111.th.jpg
10:45:48 : event_preview_dispose(); removing /run/pikrellcam/motion_2016-02-27_10.45.35_111.jpg
10:46:00 : Video record: /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.00_112.mp4.h264 ...
10:46:00 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.00_112.jpg
10:46:09 : Video motion record stopped. Header size: 29  h264 file size: 8615112
10:46:09 :     first detect: direction  totals - direction: 12  burst: 0  max burst count: 0
10:46:09 : execl:[(MP4Box -quiet -tmp /tmp -fps 24 -add /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.00_112.mp4.h264 /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.00_112.mp4 2> /dev/null && rm /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.00_112.mp4.h264 )]
10:46:09 : execl:[/home/pi/pikrellcam/scripts-dist/_thumb /run/pikrellcam/motion_2016-02-27_10.46.00_112.jpg /home/pi/pikrellcam/media /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 60 76 247 99]
  convert /run/pikrellcam/motion_2016-02-27_10.46.00_112.jpg -crop 76x76+209+61 -resize 150x150\! /home/pi/pikrellcam/media/thumbs/motion_2016-02-27_10.46.00_112.th.jpg
10:46:09 : event_preview_dispose(); removing /run/pikrellcam/motion_2016-02-27_10.46.00_112.jpg
10:46:33 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.33_113.mp4.h264.  Input/output error
10:46:33 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.33_113.jpg
10:46:33 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.33_114.mp4.h264.  Input/output error
10:46:34 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.33_114.jpg
10:46:34 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.34_115.mp4.h264.  Input/output error
10:46:34 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.34_115.jpg
10:46:34 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.34_116.mp4.h264.  Input/output error
10:46:34 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.34_116.jpg
10:46:35 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.35_117.mp4.h264.  Input/output error
10:46:35 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.35_117.jpg
10:46:35 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.35_118.mp4.h264.  Input/output error
10:46:36 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.35_118.jpg
10:46:37 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.37_119.mp4.h264.  Input/output error
10:46:38 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.37_119.jpg
10:46:38 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.38_120.mp4.h264.  Input/output error
10:46:38 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.38_120.jpg
10:46:38 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.38_121.mp4.h264.  Input/output error
10:46:38 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.38_121.jpg
10:46:38 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.38_122.mp4.h264.  Input/output error
10:46:38 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.38_122.jpg
10:46:39 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.39_123.mp4.h264.  Input/output error
10:46:39 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.39_123.jpg
10:46:39 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.39_124.mp4.h264.  Input/output error
10:46:39 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.39_124.jpg
10:46:40 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.40_125.mp4.h264.  Input/output error
10:46:40 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.40_125.jpg
10:46:47 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.47_126.mp4.h264.  Input/output error
10:46:47 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.47_126.jpg
10:46:47 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.47_127.mp4.h264.  Input/output error
10:46:47 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.47_127.jpg
10:46:47 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.47_128.mp4.h264.  Input/output error
10:46:47 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.47_128.jpg
10:46:47 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.47_129.mp4.h264.  Input/output error
10:46:48 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.47_129.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_130.mp4.h264.  Input/output error
10:46:49 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_130.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_131.mp4.h264.  Input/output error
10:46:49 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_131.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_132.mp4.h264.  Input/output error
10:46:49 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_132.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_133.mp4.h264.  Input/output error
10:46:49 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_133.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_134.mp4.h264.  Input/output error
10:46:49 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_134.jpg
10:46:49 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.46.49_135.mp4.h264.  Input/output error
10:46:50 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.46.49_135.jpg
10:47:02 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.47.02_136.mp4.h264.  Input/output error
10:47:02 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.47.02_136.jpg
10:47:02 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.47.02_137.mp4.h264.  Input/output error
10:47:02 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.47.02_137.jpg
10:47:08 : command_process: motion show_vectors toggle
10:47:11 : command_process: motion show_regions toggle
10:47:53 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.47.53_138.mp4.h264.  Input/output error
10:47:53 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.47.53_138.jpg
10:47:53 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.47.53_139.mp4.h264.  Input/output error
10:47:53 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.47.53_139.jpg
10:47:53 : Could not create video file /home/pi/pikrellcam/media/videos/motion_2016-02-27_10.47.53_140.mp4.h264.  Input/output error
10:47:53 : event preview save: copy /run/pikrellcam/mjpeg.jpg -> /run/pikrellcam/motion_2016-02-27_10.47.53_140.jpg
10:48:00 : command_process: upgrade
10:48:00 : execl:[/home/pi/pikrellcam/scripts-dist/_upgrade /home/pi/pikrellcam /home/pi/pikrellcam/www/FIFO /tmp/pikrellcam.log 2.1.13]
  Upgraded to commit Sat Feb 27 10:00:15 2016 -0600  Latest changes: Fix realpath install on wheezy.
  Version number is unchanged.
10:48:24 : command_process: quit

========================================================
2016-02-27 10:48:26 ===== PiKrellCam 2.1.13 started =====
========================================================
using FIFO: /home/pi/pikrellcam/www/FIFO
using mjpeg: /run/pikrellcam/mjpeg.jpg
10:48:26 : execl:[sudo mkdir -p /home/pi/pikrellcam/media/archive]
Make directory failed: /home/pi/pikrellcam/media/archive

========================================================
2016-02-27 10:48:42 ===== PiKrellCam 2.1.13 started =====
========================================================
using FIFO: /home/pi/pikrellcam/www/FIFO
using mjpeg: /run/pikrellcam/mjpeg.jpg
10:48:42 : execl:[sudo mkdir -p /home/pi/pikrellcam/media/archive]
Make directory failed: /home/pi/pikrellcam/media/archive

========================================================
2016-02-27 10:48:45 ===== PiKrellCam 2.1.13 started =====
========================================================
using FIFO: /home/pi/pikrellcam/www/FIFO
using mjpeg: /run/pikrellcam/mjpeg.jpg
10:48:45 : execl:[sudo mkdir -p /home/pi/pikrellcam/media/archive]
Make directory failed: /home/pi/pikrellcam/media/archive
EDIT: after doing 'sudo fdisk -l' I found that apparently what was /dev/sda1 is now /dev/sdb1 (!) all the data is still there. Can't unmount /dev/sda1 though. 'dmesg' has a long spew about some kind of kernel fault.

Code: Select all

[   21.085290] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 3147.504049] usb 1-1.3: USB disconnect, device number 5
[ 3147.509656] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883844 (offset 0 size 4096 starting block 11599243)
[ 3147.509710] Buffer I/O error on device sda1, logical block 11598986
[ 3147.510185] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 5505155 (offset 0 size 12288 starting block 22053367)
[ 3147.510232] Buffer I/O error on device sda1, logical block 22053108
[ 3147.510274] Buffer I/O error on device sda1, logical block 22053109
[ 3147.510318] Buffer I/O error on device sda1, logical block 22053110
[ 3147.517487] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133406)
[ 3147.517526] Buffer I/O error on device sda1, logical block 133120
[ 3147.517550] Buffer I/O error on device sda1, logical block 133121
[ 3147.517568] Buffer I/O error on device sda1, logical block 133122
[ 3147.517586] Buffer I/O error on device sda1, logical block 133123
[ 3147.517603] Buffer I/O error on device sda1, logical block 133124
[ 3147.517621] Buffer I/O error on device sda1, logical block 133125
[ 3147.517765] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133436)
[ 3147.517914] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133466)
[ 3147.518060] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133496)
[ 3147.518205] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133526)
[ 3147.518352] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133556)
[ 3147.518499] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133586)
[ 3147.518645] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883845 (offset 0 size 2093056 starting block 133616)
[ 3147.555404] Aborting journal on device sda1-8.
[ 3147.555462] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4839: Journal has aborted
[ 3147.555478] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[ 3147.569135] EXT4-fs error (device sda1) in ext4_free_blocks:4879: Journal has aborted
[ 3147.581853] EXT4-fs (sda1): previous I/O error to superblock detected
[ 3147.582010] EXT4-fs (sda1): Delayed block allocation failed for inode 2883829 at logical offset 783 with max blocks 8 with error 30
[ 3147.598837] EXT4-fs (sda1): previous I/O error to superblock detected
[ 3147.598932] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[ 3147.605647] EXT4-fs (sda1): This should not happen!! Data will be lost
[ 3147.605647]
[ 3147.605679] EXT4-fs error (device sda1) in ext4_writepages:2421: Journal has aborted
[ 3147.605690] EXT4-fs (sda1): previous I/O error to superblock detected
[ 3147.637960]
[ 3147.640354] EXT4-fs (sda1): Remounting filesystem read-only
[ 3147.648247] EXT4-fs (sda1): previous I/O error to superblock detected
[ 3149.561257] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[ 3149.662791] usb 1-1.3: New USB device found, idVendor=0781, idProduct=5583
[ 3149.662843] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3149.662860] usb 1-1.3: Product: Ultra Fit
[ 3149.662876] usb 1-1.3: Manufacturer: SanDisk
[ 3149.662892] usb 1-1.3: SerialNumber: 4C531001361129100342
[ 3149.664291] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 3149.664873] scsi host1: usb-storage 1-1.3:1.0
[ 3150.662466] scsi 1:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[ 3150.664248] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 3150.666663] sd 1:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 3150.668235] sd 1:0:0:0: [sdb] Write Protect is off
[ 3150.668266] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 3150.669267] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3150.686411]  sdb: sdb1
[ 3150.689611] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 3155.078044] EXT4-fs warning: 115 callbacks suppressed
[ 3155.078073] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3155.357653] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #2: comm convert: reading directory lblock 0
[ 3179.867501] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3180.040990] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3180.214013] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3180.735233] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3181.776358] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3181.951957] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3184.034366] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3184.379033] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3184.727267] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3184.903004] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3185.245587] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3185.768542] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3186.810237] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3193.404595] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3193.579105] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3193.752379] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3193.926298] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3195.139773] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3195.313398] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3195.488314] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3195.661416] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3195.835557] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3196.008478] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3208.330285] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3208.503821] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3225.702335] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #2: comm php5-fpm: reading directory lblock 0
[ 3245.621409] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3259.356535] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3259.704048] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3259.879400] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 3363.763531] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
[ 3369.427545] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
[ 3399.169089] Unable to handle kernel paging request at virtual address 35838000
[ 3399.179200] pgd = b325c000
[ 3399.183277] [35838000] *pgd=00000000
[ 3399.188204] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 3399.194847] Modules linked in: ctr ccm snd_bcm2835 snd_pcm snd_seq snd_seq_device snd_timer snd sg arc4 ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211 uio_pdrv_genirq uio rfkill
[ 3399.215517] CPU: 3 PID: 4207 Comm: shutdown Not tainted 4.0.7-v7+ #802
[ 3399.223386] Hardware name: BCM2709
[ 3399.228133] task: b441c800 ti: b45e0000 task.ti: b45e0000
[ 3399.234897] PC is at __percpu_counter_add+0x3c/0x110
[ 3399.241196] LR is at clear_page_dirty_for_io+0xd0/0x12c
[ 3399.247781] pc : [<80309cfc>]    lr : [<800f7d9c>]    psr: 60000093
[ 3399.247781] sp : b45e1db0  ip : 00000001  fp : b45e1dd4
[ 3399.261969] r10: ffffffff  r9 : 00000001  r8 : b5b54d00
[ 3399.268506] r7 : ffffffff  r6 : ffffffff  r5 : b5b54ce0  r4 : 20000013
[ 3399.276327] r3 : 00000000  r2 : 35838000  r1 : 00000018  r0 : b5b54d00
[ 3399.284129] Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
[ 3399.293819] Control: 10c5387d  Table: 3325c06a  DAC: 00000015
[ 3399.300812] Process shutdown (pid: 4207, stack limit = 0xb45e0210)
[ 3399.308250] Stack: (0xb45e1db0 to 0xb45e2000)
[ 3399.313833] 1da0:                                     ffffffff 20000013 b5b54ce0 b45e1e40
[ 3399.324434] 1dc0: b5423564 b45e1ee8 b45e1df4 b45e1dd8 800f7d9c 80309ccc 00000018 b45e1ee8
[ 3399.335141] 1de0: b6766bf0 00000000 b45e1ea4 b45e1df8 800f7fb0 800f7cd8 0000000e 00000003
[ 3399.345888] 1e00: 00000528 00000001 0004ba86 00000001 00000002 800414f4 ffffffff b5423564
[ 3399.356638] 1e20: 800f7550 b45e0000 00000000 00000000 b50fda40 00000001 00000001 00000000
[ 3399.367421] 1e40: b6766bf0 b45e1e50 8054bfec 800ccf80 b45e1e7c b45e1e60 800470c0 8054bfc8
[ 3399.378286] 1e60: 00000000 b50fda40 807e9440 8080a0b0 b45e1ebc b45e1e80 b50a404c b5423564
[ 3399.389219] 1e80: b45e1ee8 00000000 b5423564 8016e108 00000000 b5423564 b45e1ed4 b45e1ea8
[ 3399.400272] 1ea0: 800f8284 800f7e04 b45e1ea8 b45e1ea8 b45e1eb0 b45e1eb0 b45e1eb8 b45e1eb8
[ 3399.411402] 1ec0: ffffffff 7fffffff b45e1ee4 b45e1ed8 800f9bf4 800f8244 b45e1f24 b45e1ee8
[ 3399.422554] 1ee0: 800ef1f0 800f9bcc 7fffffff 00000000 00000000 00000000 ffffffff 7fffffff
[ 3399.433761] 1f00: 00000001 00000000 b5423490 b54234e0 8080a1e0 00000000 b45e1f44 b45e1f28
[ 3399.445049] 1f20: 800ef230 800ef194 ffffffff 7fffffff 00000001 b54234e0 b45e1f54 b45e1f48
[ 3399.456359] 1f40: 8016e128 800ef204 b45e1f84 b45e1f58 80177bc4 8016e114 00000000 00000000
[ 3399.467668] 1f60: 000145b0 00000036 00000024 8000ed48 b45e0000 00000000 b45e1fa4 b45e1f88
[ 3399.478976] 1f80: 8016e494 80177b18 00000000 00000001 8000ec80 00000000 00000000 b45e1fa8
[ 3399.490287] 1fa0: 8000eb40 8016e43c 00000000 000145b0 ffffffff 00000002 00000010 7ef2f500
[ 3399.501596] 1fc0: 00000000 000145b0 00000036 00000024 00014284 00000000 0001427c 00000000
[ 3399.512907] 1fe0: 00000000 7ef2f4d8 0000a9ec 76e6504c 60000010 ffffffff 00000000 00000000
[ 3399.524234] [<80309cfc>] (__percpu_counter_add) from [<800f7d9c>] (clear_page_dirty_for_io+0xd0/0x12c)
[ 3399.536690] [<800f7d9c>] (clear_page_dirty_for_io) from [<800f7fb0>] (write_cache_pages+0x1b8/0x440)
[ 3399.548963] [<800f7fb0>] (write_cache_pages) from [<800f8284>] (generic_writepages+0x4c/0x68)
[ 3399.560621] [<800f8284>] (generic_writepages) from [<800f9bf4>] (do_writepages+0x34/0x48)
[ 3399.571928] [<800f9bf4>] (do_writepages) from [<800ef1f0>] (__filemap_fdatawrite_range+0x68/0x70)
[ 3399.583931] [<800ef1f0>] (__filemap_fdatawrite_range) from [<800ef230>] (filemap_fdatawrite+0x38/0x40)
[ 3399.596388] [<800ef230>] (filemap_fdatawrite) from [<8016e128>] (fdatawrite_one_bdev+0x20/0x24)
[ 3399.608213] [<8016e128>] (fdatawrite_one_bdev) from [<80177bc4>] (iterate_bdevs+0xb8/0xe4)
[ 3399.619595] [<80177bc4>] (iterate_bdevs) from [<8016e494>] (sys_sync+0x64/0xa8)
[ 3399.630011] [<8016e494>] (sys_sync) from [<8000eb40>] (ret_fast_syscall+0x0/0x54)
[ 3399.640603] Code: e1a07003 e59b1004 e5903010 ee1d2f90 (e7920003)
[ 3399.651108] ---[ end trace fb7618a542a15434 ]---
[ 3399.670306] note: shutdown[4207] exited with preempt_count 1
[ 3456.376695] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[ 4960.808963] EXT4-fs warning (device sda1): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
[ 5062.056070] EXT4-fs (sdb1): recovery complete
[ 5062.089221] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Last edited by jbeale on Sun Feb 28, 2016 6:24 pm, edited 1 time in total.

User avatar
jbeale
Posts: 3500
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

SOLVED: USB stick glitch actually power supply problem

Sat Feb 27, 2016 8:00 pm

Happened 2x more. It seems to simply be that this particular 128 GB Sandisk USB drive is not reliable, or is not compatible with RPi. Has an error, then gets remounted as /dev/sdb1 and chaos ensues.

Code: Select all

[   21.405919] EXT4-fs (sda1): recovery complete
[   21.427475] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[  669.499297] usb 1-1.3: USB disconnect, device number 5
[  669.501903] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[  669.501942] sd 0:0:0:0: [sda] CDB: opcode=0x2a 2a 00 05 84 73 68 00 00 08 00
[  669.501962] blk_update_request: I/O error, dev sda, sector 92566376
[  669.501990] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883922 (offset 0 size 4096 starting block 1                      1570798)
[  669.502018] Buffer I/O error on device sda1, logical block 11570541
[  669.502114] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745711)
[  669.502134] Buffer I/O error on device sda1, logical block 11745425
[  669.502156] Buffer I/O error on device sda1, logical block 11745426
[  669.502175] Buffer I/O error on device sda1, logical block 11745427
[  669.502194] Buffer I/O error on device sda1, logical block 11745428
[  669.502212] Buffer I/O error on device sda1, logical block 11745429
[  669.502230] Buffer I/O error on device sda1, logical block 11745430
[  669.502248] Buffer I/O error on device sda1, logical block 11745431
[  669.502266] Buffer I/O error on device sda1, logical block 11745432
[  669.502284] Buffer I/O error on device sda1, logical block 11745433
[  669.502422] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745741)
[  669.502588] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745771)
[  669.502753] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745801)
[  669.502922] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745831)
[  669.503091] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745861)
[  669.503257] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745891)
[  669.503417] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745921)
[  669.503575] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 2883923 (offset 0 size 6623232 starting bloc                      k 11745951)
[  669.509726] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[  669.509775] sd 0:0:0:0: [sda] CDB: opcode=0x2a 2a 00 0a 84 11 f0 00 00 10 00
[  669.509807] blk_update_request: I/O error, dev sda, sector 176427504
[  669.537568] Aborting journal on device sda1-8.
[  669.537678] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  669.559068] EXT4-fs (sda1): previous I/O error to superblock detected
[  669.559257] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[  669.573381] EXT4-fs (sda1): Remounting filesystem read-only
[  669.581421] EXT4-fs (sda1): previous I/O error to superblock detected
[  669.776358] EXT4-fs error (device sda1): ext4_wait_block_bitmap:494: comm vc.ril.video_en: Cannot read block bitmap - block_group = 4,                       block_bitmap = 1029
[  669.794932] EXT4-fs error (device sda1): ext4_discard_preallocations:4004: comm vc.ril.video_en: Error reading block bitmap for 4
[  670.034896] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #2: comm convert: reading directory lblock 0
[  670.608531] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[  670.711419] usb 1-1.3: New USB device found, idVendor=0781, idProduct=5583
[  670.711476] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  670.711494] usb 1-1.3: Product: Ultra Fit
[  670.711510] usb 1-1.3: Manufacturer: SanDisk
[  670.711526] usb 1-1.3: SerialNumber: 4C531001361129100342
[  670.714097] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[  670.714776] scsi host1: usb-storage 1-1.3:1.0
[  671.712972] scsi 1:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[  671.716603] sd 1:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[  671.717910] sd 1:0:0:0: Attached scsi generic sg0 type 0
[  671.720065] sd 1:0:0:0: [sdb] Write Protect is off
[  671.720113] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  671.721109] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  671.742068]  sdb: sdb1
[  671.746431] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[  683.836821] EXT4-fs warning: 132 callbacks suppressed
[  683.836858] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[  684.007221] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
[  684.703431] EXT4-fs warning (device sda1): __ext4_read_dirblock:674: error -5 reading directory block (ino 2883585, block 0)
EDIT: SOLVED. Bad power supply (1A, maybe actually less) doesn't support RP2, camera, wifi, and newer 128GB USB stick which runs hotter than old parts. Changed to 2A power supply and it's all good.
Last edited by jbeale on Sun Feb 28, 2016 6:23 pm, edited 1 time in total.

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 28, 2016 12:42 am

billw wrote: Realpath was not installed - looks like a script bug for wheezy installs. Try installing realpath:

Code: Select all

sudo apt-get install realpath
and rerun the install script.
that does not help.
there are other errors.

Code: Select all

nginx: configuration file /etc/nginx/nginx.conf test failed
There is no nginx.conf. in /etc/nginx
I've created one and now the installation is running correctly.
But wait, what's going on?

Code: Select all

2016/02/28 00:56:16 [error] 2617#0: *2 "/etc/nginx/html/index.html" is not found (2: No such file or directory), client: 192.168.178.53, server: localhost, request: "GET / HTTP/1.1", host: "192.168.178.34"
2016/02/28 00:56:32 [error] 2617#0: *2 "/etc/nginx/html/index.html" is not found (2: No such file or directory), client: 192.168.178.53, server: localhost, request: "GET / HTTP/1.1", host: "192.168.178.34"
my sites-available
pikrellcam

Code: Select all

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
        listen 81;
        listen [::]:81;

        # SSL configuration
        #
        # listen 443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root /home/pi/pikrellcam/www;
        # auth_basic "Restricted";
        # auth_basic_user_file /home/pi/pikrellcam/www/.htpasswd;

        # Add index.php to the list if you are using PHP
        index index.php index.html index.htm index.nginx-debian.html;

        server_name _;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
        #
        #       # With php5-cgi alone:
        #       fastcgi_pass 127.0.0.1:9000;
        #       # With php5-fpm:
                fastcgi_pass unix:/var/run/php5-fpm.sock;
        }

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #       deny all;
        #}
}
and the link in sites-enabled is correctly

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Sun Feb 28, 2016 5:14 pm

0lly wrote: there are other errors.

Code: Select all

nginx: configuration file /etc/nginx/nginx.conf test failed
There is no nginx.conf. in /etc/nginx
I've created one and now the installation is running correctly.
But wait, what's going on?

Code: Select all

2016/02/28 00:56:16 [error] 2617#0: *2 "/etc/nginx/html/index.html" is not found (2: No such file or directory), client: 192.168.178.53, server: localhost, request: "GET / HTTP/1.1", host: "192.168.178.34"
2016/02/28 00:56:32 [error] 2617#0: *2 "/etc/nginx/html/index.html" is not found (2: No such file or directory), client: 192.168.178.53, server: localhost, request: "GET / HTTP/1.1", host: "192.168.178.34"
my sites-available
pikrellcam

Code: Select all

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
        listen 81;
        listen [::]:81;

        # SSL configuration
        #
        # listen 443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root /home/pi/pikrellcam/www;
        # auth_basic "Restricted";
        # auth_basic_user_file /home/pi/pikrellcam/www/.htpasswd;

        # Add index.php to the list if you are using PHP
        index index.php index.html index.htm index.nginx-debian.html;

        server_name _;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
        #
        #       # With php5-cgi alone:
        #       fastcgi_pass 127.0.0.1:9000;
        #       # With php5-fpm:
                fastcgi_pass unix:/var/run/php5-fpm.sock;
        }

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #       deny all;
        #}
}
and the link in sites-enabled is correctly
nginx.conf should be in the nginx-common package, so maybe something is wrong with your
nginx install. So, I would suggest purging nginx and redoing the install:

Code: Select all

apt-get purge nginx nginx-common php5-fpm
But before you try the pikrellcam install again, are you on wheezy or jessie? I thought from your
previous post you are on wheezy but the sites-available version pikrellcam installed is for jessie.
So, do you have the file /etc/debian_version? If so, what's in it. It should be there since it's from
the base-files package.

Also, I don't know if it will give more information, but get the output from

Code: Select all

sudo nginx -t
Run that before you try any nginx reinstall and again after for comparison.

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Mon Feb 29, 2016 12:51 am

billw wrote: Run that before you try any nginx reinstall and again after for comparison.
No thanks.
I have reinstalled Rpi Cam Web Interface and runs without problems.
You should your InstallScript test yourself under wheezy.
it does not work!

Mercedes
Posts: 2
Joined: Tue Feb 09, 2016 7:01 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Mon Feb 29, 2016 3:23 am

No thanks.
I have reinstalled Rpi Cam Web Interface and runs without problems.
You should your InstallScript test yourself under wheezy.
it does not work!
have another beer Olly :lol:

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Mon Feb 29, 2016 6:24 am

Mercedes wrote: have another beer Olly :lol:
Thanks for the beer but I do not drink alcohol. :D

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Wed Mar 02, 2016 12:54 pm

Here are a few errors.
In your installscript line 92 / 93

Code: Select all

WHEEZY=7.8
DEB_VERSION=`cat /etc/debian_version`
My Output

Code: Select all

[email protected] ~ $ cat /etc/debian_version
7.9
And this leads to errors.
Line 117

Code: Select all

IS_WHEEZY=`echo "$DEB_VERSION <= $WHEEZY" | bc`
Edit
From RPi_Cam_Web_Interface_Installer

Code: Select all

# Tedect version
version=$(cat /etc/issue)
if [ "$version" == "Raspbian GNU/Linux 7 \n \l" ]; then
  echo "Raspbian Wheezy";
  wwwroot="/var/www"
elif [ "$version" == "Raspbian GNU/Linux 8 \n \l" ]; then
  echo "Raspbian Jessie";
  wwwroot="/var/www/html"
else
  echo "Unknown"
  wwwroot="/var/www"
fi

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Wed Mar 02, 2016 4:13 pm

0lly wrote:Here are a few errors.
Thanks, the test for wheezy should be fixed now.

0lly
Posts: 77
Joined: Sun Mar 02, 2014 5:07 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Wed Mar 02, 2016 6:53 pm

billw wrote:Thanks, the test for wheezy should be fixed now.
the odyssey is over.
the pikrellcam-installation now runs flawlessly.
Thank you and sorry for the stress. :mrgreen:

Code: Select all

.
.
Adding a pikrellcam autostart command to /etc/rc.local:
su pi -c '(sleep 5; /home/pi/pikrellcam/pikrellcam) &'
Adding to /etc/sudoers.d: www-data permission to run pikrellcam as user pi:
Turning off nginx access_log.
Installing /etc/nginx/sites-available/pikrellcam
    nginx web server port: 81
    nginx web server root: /home/pi/pikrellcam/www
Adding /etc/nginx/sites-enabled/pikrellcam link to sites-available/pikrellcam.
A password for the web page is not set.
Restarting nginx: nginx.

Install finished.
This install script does not automatically start pikrellcam.
To start pikrellcam, open a browser page to:
    http://your_pi:81
and click on the "System" panel and then the "Start PiKrellCam" button.
PiKrellCam can also be run from a Pi terminal for testing purposes.
Automatic pikrellcam starting at boot is enabled.

BerryPicker
Posts: 177
Joined: Tue Oct 16, 2012 3:03 pm
Location: The East of England

Re: PiKrellCam: motion vector detect + OSD web interface

Fri Mar 04, 2016 3:40 pm

billw wrote:So I've written PiKrellCam and I thought I would go ahead and put it out there.
I'm so glad you did. And thank you for making it so easy to come on board. I've done so with a Pi B+ and Jessie light. I just love those thumbnails, located at just the right moment in time, and zoomed in to just the right region of interest. My camera points into the sun, but its remarkable how sensitive the movement detector is, yet amazingly imune to shaddows, wind and reflections.
Two questions.
To shutdown (power off) is the proper way to use SSH?
Are the loaded regions in use even when Regions ON is not displayed?

billw
Posts: 403
Joined: Tue Sep 18, 2012 8:23 pm

Re: PiKrellCam: motion vector detect + OSD web interface

Fri Mar 04, 2016 4:03 pm

BerryPicker wrote:
billw wrote:So I've written PiKrellCam and I thought I would go ahead and put it out there.
I'm so glad you did. And thank you for making it so easy to come on board. I've done so with a Pi B+ and Jessie light. I just love those thumbnails, located at just the right moment in time, and zoomed in to just the right region of interest. My camera points into the sun, but its remarkable how sensitive the movement detector is, yet amazingly imune to shaddows, wind and reflections.
Two questions.
To shutdown (power off) is the proper way to use SSH?
Are the loaded regions in use even when Regions ON is not displayed?
Sure, shutdown over SSH is fine. I've got headless setups and do it all the time. And yes, the regions
are always in effect whether shown or not.

User avatar
jbeale
Posts: 3500
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

PiKrellCam on RPi 3 ?

Mon Mar 07, 2016 5:56 am

My Rpi 3 is still on backorder, so I'm throwing the question out there: can anyone confirm if the RPi 3 allows PiKrellCam to run at 30 fps, instead of being limited to 24 fps? There are some applications where it would be nice if the frame rate synchronized with another camera I have, which runs at 29.97 fps.

Tashman
Posts: 16
Joined: Tue Mar 08, 2016 11:23 am

Re: PiKrellCam: motion vector detect + OSD web interface

Tue Mar 08, 2016 11:57 am

Hi

Running PiKrellCam for a few months now - excellent! Massive thanks to Bill and other contributors.

Just added a USB stick to the pi2 running PiKrellCam and have noticed a couple of annoyances -

1 Videos archived previously onto the sdcard are not showing in the archive calendar now. I can imagine why as the usb stick is now being used for media storage. How can I merge/copy the older sdcard files onto the usb stick please?

2 since the usb stick was added, when browsing the media webpages on PiKrellCam, the sizes for Disk, free & used all show as 0.0? seems that PiKrellCam is not looking at the usb stick to collect the data?, or something's not correct with my usb stick install?
Videos, stills etc are all being saved ok, just the disk details are incorrect....

Thanks in advance
Tashman

Return to “Camera board”