Error trying to write picture to my home directory - Raspberry Pi Forums


i experimenting setting pi surveillance camera using christoph buenger 's set http://www.codeproject.com/articles/665 ... nce-camera

have problem don't understand. when boot pi camera led turns on turn off after few seconds. checking /tmp/motion.log file shows errors trying write files home directory. don't understand why should happening.

code: select all

pi@pi-a ~ $ cat /tmp/motion.log [-1242643616] [ntc] [all] [jul 13 15:56:37] motion_startup: using log type (all) log level (wrn) [1] [alr] [vid] [jul 13 15:56:37] mmalcam_start: mmal camera thread starting... camera (vc.ril.camera) of 1024 x 576 @ 2 fps [1] [alr] [vid] [jul 13 15:56:37] mmalcam_start: mmal camera using video capture [1] [err] [enc] [jul 13 15:58:32] ffmpeg_open: url_fopen - error opening file /home/pi/01-20140713155832.avi ... check access rights target directory: [1] [err] [evt] [jul 13 15:58:32] event_ffmpeg_newfile: ffopen_open error creating (new) file [/home/pi/01-20140713155832.avi]: [1] [err] [all] [jul 13 15:58:32] myfopen: error opening file /home/pi/01-20140713155831-01.jpg mode w: [1] [err] [all] [jul 13 15:58:32] put_picture: can't write picture file /home/pi/01-20140713155831-01.jpg - check access rights target directory thread going finish due fatal error: [1] [err] [all] [jul 13 15:58:32] myfopen: error opening file /home/pi/01-20140713155832-00.jpg mode w: [1] [err] [all] [jul 13 15:58:32] put_picture: can't write picture file /home/pi/01-20140713155832-00.jpg - check access rights target directory thread going finish due fatal error: [1] [alr] [vid] [jul 13 15:58:33] mmal camera cleanup
can explain why happening , if possible solution. seems 1 more blog missing necessary set info.



mrengman

what uid/gid motion running with? ownership have on /home/pi?


raspberrypi



Comments

Popular posts from this blog

Convierte tu Raspberry en un NAS. Firmware fvdw-sl 15.3 - Raspberry Pi Forums

How to format a Get Request

avrdude: verification error, first mismatch at byte 0x0000 0x0c != 0x62