ftp causing invalid syntax

Well I tried the mkdir Public/myFakeNAs and it worked this time! I have no idea as to why it didn't before.

Presently the NASname = os.path.join("/mnt/CCTV/PiZero" , fname)

After running the script and a picture shows up on the monitor, it does not get saved to the /CCTV/PiZero directory, nor on my NAS box.

I realise there is something else I have to do but not sure what.

I think this was answered before, but as there are many posts on this thread, I can't find it just now.

Thanks

I found the post I was after and I added //NAS at the beginning of the line

pi@raspberrypi:~ $ sudo mount //NAS/CCTV/PiZero /mnt/CCTV/PiZero Password for root@//NAS/CCTV/PiZero: ********* mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Here I used the PiZero password.

Then I tried this:

pi@raspberrypi:~ $ sudo mount -t cifs -o username=root,password=****** //NAS/CCTV/PiZero /mnt/CCTV/PiZero mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) pi@raspberrypi:~ $

Here I used both password and username for my NAS box

I did have a look at that page and to be hones, I am no wiser.

this seems close to what you want. BUT //NAS ? can you reach the nas from the PI via the nasme 'NAS'?

try ping NAS

if it comes back saying it does not recognize the name then try to swap NAS for its ip-address

pi@raspberrypi:~ $ sudo mount -t cifs -o username=root,password=****** //192.168.1.22/CCTV/PiZero /mnt/CCTV/PiZero ^^^^^^^^^^^^

or whatever the ip of the nas is

The ip address here is not mine but some other somewhere.

pi@raspberrypi:~ $ ping NAS PING NAS (92.242.132.24) 56(84) bytes of data.

--- NAS ping statistics ---

This my NAS box and pinging the correct IP address Actually the real name of my NAS box is FreeNAS, but using that did not make difference to the above

pi@raspberrypi:~ $ ping 192.168.0.22 PING 192.168.0.22 (192.168.0.22) 56(84) bytes of data.

--- 192.168.0.22 ping statistics ---

On Sat, 19 May 2018 09:39:50 +0100, RobH declaimed the following:

"/CCTV/PiZero" is not the same directory as "/mnt/CCTV/PiZero"

With the script as I provided it, the first place the video file should appear is that "shared memory" RAM; it should then be copied (the shutil line) to "/mnt/CCTV/PiZero"

It will only appear on the NAS box if you've managed a successful "mount ..." command.

Put a # in front of the os.unlink() line; that will keep it from deleting the RAM copy.

~15 seconds after you see a preview, execute (at the console prompt -- you may want to open a second console connection so the script can run in one console while you explore using the second): ls /run/shm {Hmmm, Debian Stretch in a virtual instance is using /dev/shm rather than /run/shm -- I shouldn't spend the time but I'm going to dig out my RPi to check.

wulfraed@stretch:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 1015088 0 1015088 0% /dev tmpfs 205264 11224 194040 6% /run /dev/sda1 31210380 13389136 16212796 46% / tmpfs 1026320 0 1026320 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 1026320 0 1026320 0% /sys/fs/cgroup VB_Shared 1952096584 457233388 1494863196 24% /media/sf_VB_Shared tmpfs 205264 4 205260 1% /run/user/111 tmpfs 205264 20 205244 1% /run/user/1000 wulfraed@stretch:~$ uname -a Linux stretch 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux

pi@raspberrypi:~$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 13064524 6465240 5912592 53% / devtmpfs 468088 0 468088 0% /dev tmpfs 472696 0 472696 0% /dev/shm tmpfs 472696 12244 460452 3% /run tmpfs 5120 4 5116 1% /run/lock tmpfs 472696 0 472696 0% /sys/fs/cgroup /dev/mmcblk0p6 66528 22137 44392 34% /boot tmpfs 94536 0 94536 0% /run/user/1000 /dev/mmcblk0p5 30701 398 28010 2% /media/pi/SETTINGS pi@raspberrypi:~$ uname -a Linux raspberrypi 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux pi@raspberrypi:~$

debian@beaglebone:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 219512 0 219512 0% /dev tmpfs 49576 5164 44412 11% /run /dev/mmcblk1p1 3704040 2893736 602432 83% / tmpfs 247876 0 247876 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 247876 0 247876 0% /sys/fs/cgroup tmpfs 49572 4 49568 1% /run/user/1000 debian@beaglebone:~$ uname -a Linux beaglebone 4.9.78-ti-r94 #1 SMP PREEMPT Fri Jan 26 21:26:24 UTC 2018 armv7l GNU/Linux debian@beaglebone:~$

Okay -- Debian Stretch 64-bit in VirtualBox (on Windows), RPi-3 "Raspbian", and Beaglebone Black Debian are ALL using /dev/shm

root@ElusiveUnicorn:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 1952096584 458150456 1493946128 24% / root 1952096584 458150456 1493946128 24% /root home 1952096584 458150456 1493946128 24% /home data 1952096584 458150456 1493946128 24% /data cache 1952096584 458150456 1493946128 24% /cache mnt 1952096584 458150456 1493946128 24% /mnt none 1952096584 458150456 1493946128 24% /dev none 1952096584 458150456 1493946128 24% /run none 1952096584 458150456 1493946128 24% /run/lock none 1952096584 458150456 1493946128 24% /run/shm none 1952096584 458150456 1493946128 24% /run/user C: 1952096584 458150456 1493946128 24% /mnt/c D: 2930134012 993977732 1936156280 34% /mnt/d E: 3906983932 252169040 3654814892 7% /mnt/e Z: 5860519932 3360494188 2500025744 58% /mnt/z root@ElusiveUnicorn:~# uname -a Linux ElusiveUnicorn 4.4.0-17134-Microsoft #48-Microsoft Fri Apr 27

... but the "Ubuntu BASH shell on Windows" is using /run/shm (and not in RAM either). I'm sure someone else on the thread suggested /run/shm; google searches imply that /run/shm is the new standard name, but it appears Debian hasn't changed from /dev/shm yet.

On your RPi, execute: df and look for either /run/shm or /dev/shm

If you find it is /dev/shm change the line in the script from

RAMname = os.path.join("/run/shm", fname)

to

RAMname = os.path.join("/dev/shm", fname)

I'm surprised the script didn't dump a traceback on a non-exist ant path if this is the case... Maybe the camera library is catching the error and just silently not doing the capture.

On Sat, 19 May 2018 10:08:03 +0100, RobH declaimed the following:

This is where you want the IP# of your NAS device, unless you have a DNS system that knows what machine "NAS" refers to...

Suggest rebooting the RPi to clean up any partial mount operations before starting again...

It took me a few attempts but I opened up a directory on my Windows box for network sharing. Had to add my admin account to the share (my user account does not have a password, but the mount command fails if I don't provide one).

Again -- all path names are for MY systems, don't take them literally; I'm doing these just to show functioning examples!

Create mount point directory on local machine pi@raspberrypi:~$ ls /media pi pi@raspberrypi:~$ sudo mkdir /media/Shared

Attempt to mount fails as Windows machine is not in any DNS lookup pi@raspberrypi:~$ sudo mount -t cifs //ElusiveUnicorn/VB_Shared /media/Shared -o username=wulfraed mount error: could not resolve address for ElusiveUnicorn: Unknown error

Using IP address; fails since my user account does not have a password to send pi@raspberrypi:~$ sudo mount -t cifs //192.168.2.109/VB_Shared /media/Shared -o username=wulfraed Password for wulfraed@//192.168.2.109/VB_Shared: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

After adding "root" (my Windows admin account, which does have a password) to the share (on Windows) (without adding that account to the share users I get no-permissions errors) pi@raspberrypi:~$ sudo mount -t cifs //192.168.2.109/VB_Shared /media/Shared -o username=root Password for root@//192.168.2.109/VB_Shared: **********

No error, display the contents of the shared directory pi@raspberrypi:~$ sudo ls /media/Shared/ BabaYagaHut.bmp cache code_1.16.0-1504714880_amd64.deb slrn.rc VB_share_permissions.txt BabaYagaHut.png cache.c myTest.dat so.py pi@raspberrypi:~$

Needed "sudo" since I didn't chown the mount to my RPi user. (Strange

-- the same sequence on my BBB is giving a "host is down" on the attempt to mount)

Password for root@//NAS/CCTV/PiZero: ********* mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Password for root@//NAS/CCTV/PiZero: ********* mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Password for root@//NAS/CCTV/PiZero: ********* mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

First I mounted : pi@raspberrypi:~ $ sudo mount //NAS/CCTV/PiZero /mnt/CCTV/PiZero Password for root@//NAS/CCTV/PiZero: ********* mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Then put a # infront of os.unlink

I then ran the python script:

pi@raspberrypi:~ $ python intruder_recmotion.py Traceback (most recent call last): File "intruder_recmotion.py", line 37, in pi@raspberrypi:~ $ shutil.copyfile(RAMname, NASname) File "/usr/lib/python2.7/shutil.py", line 83, in copyfile with open(dst, 'wb') as fdst: IOError: [Errno 13] Permission denied: '/mnt/CCTV/PiZero/2018-19-19_17.43.42.h264'

Whilst the script was running, ie 15 seconds after the video, I then ran

pi@raspberrypi:~ $ ls /run/shm

As well as pi@raspberrypi:~ $ ls /dev/shm

It very well looks like the files are created, but where to.

so - use 192.168.0.22 - NOT NAS

On Sat, 19 May 2018 17:54:28 +0100, RobH declaimed the following:

Unless you know for certain that the name NAS resolves to YOUR NAS device, you should probably be using YOUR IP# there.

No... You ATTEMPTED to mount it -- the mount did not complete successfully; likely because the name NAS is not pointing to your device but to something defined somewhere else (and how it is visible to your network I have no idea).

Expected if you have a partial mount success -- that is, it thinks it is mounted, but you have no privileges to do anything on that location.... OR: the non-mounted directory is not writable by your user account. Try running

sudo chown pi:pi /mnt/CCTV/PiZero

and maybe for safety also

sudo chown pi:pi /mnt/CCTV

Interesting -- it appears that your system sees /run/shm and /dev/shm as the same location.

Those files are located in a shared RAM(disk) -- which is why you'll want the unlink() statement once the mount works. Though why you show files going back three days if they are in RAM I don't know -- Unless you haven't rebooted the system in all that time, and my script was silently dying on the copyfile() so the unlink() never ran. The unlink() is supposed to delete the temporary file from RAM after it is copied to /mnt/whatever...

Password for root@//192.168.0.22/CCTV/PiZero: ****** pi@raspberrypi:~ $

Ok, I think I am getting somewhere now.

I did sudo chown pi:pi /mnt/CCTV/PiZero and sudo chown pi:pi /mnt/CCTV

Then I: pi@raspberrypi:~ $ sudo mount //192.168.0.22/CCTV/PiZero /mnt/CCTV/PiZero Password for root@//192.168.0.22/CCTV/PiZero: ****** pi@raspberrypi:~ $

No error messages of any kind now, so in the script you provided, where or what should I change to incorporate FreeNAS ip address.

Regarding the files going back 3 days, no I have not rebooted the Pi Zero at all, so that is maybe the reason why.

Thanks

On Sun, 20 May 2018 19:00:49 +0100, RobH declaimed the following:

NOTHING...

The "mount" command is what linked your FreeNAS directory to a directory on the RPI... The RPI only has to put files into what looks to it like just another local directory. And if you haven't changed anything, that should be /mnt/CCTV/PiZero

If the "copyfile" was failing because of the bad mount point, the program wouldn't have executed the unlink() calls.

You might want to clear out that region before you run out of RAM

rm /dev/shm/*.h264 or rm /run/shm/*.h264

since it seems both paths were the same on your system.

Once you see files appear in /mnt/CCTV/PiZero then verify externally that the NAS shows them... Then restore the unlink() statement in the script (and empty /dev/shm again -- if the script is running without problems it should be removing the RAM files after they get copied to the NAS mount point.

I mounted the directory again:

pi@raspberrypi:~ $ sudo mount //192.168.0.22/CCTV/PiZero /mnt/CCTV/PiZero -o username=root,password=******

Then I ran the python script:

pi@raspberrypi:~ $ python intruder_recmotion.pyTraceback (most recent call last): File "intruder_recmotion.py", line 37, in shutil.copyfile(RAMname, NASname) File "/usr/lib/python2.7/shutil.py", line 83, in copyfile with open(dst, 'wb') as fdst: IOError: [Errno 13] Permission denied: '/mnt/CCTV/PiZero/2018-20-20_20.02.21.h264'

Then :

pi@raspberrypi:~ $ rm /run/shm/*.h264 pi@raspberrypi:~ $ rm /dev/shm/*.h264 rm: cannot remove '/dev/shm/*.h264': No such file or directory pi@raspberrypi:~ $

great. before fiddling with the script try this

echo "test" > /mnt/CCTV/PiZero/test.txt

check on you nas if you see the file at CCTC/piZero if you do - then try the script

if you get permission denied, try

sudo echo "test" > /mnt/CCTV/PiZero/test.txt

check again.

if ok (you see in in the nas) remove the file with

sudo rm /mnt/CCTV/PiZero/test.txt

fix permissions sudo chown -R pi:pi /mnt/CCTV/PiZero

(note '-R' for recursive)

and try again

echo "test" > /mnt/CCTV/PiZero/test.txt if ok, try the script

On Sun, 20 May 2018 20:08:55 +0100, RobH declaimed the following:

You might need to do the "sudo chown" stuff to allow the non-root account to write to the mount point.

Sort of expected -- as I mentioned, it seems that /run/shm and /dev/shm both are two paths for the same actual directory.

Ok , things seem to be getting better here.

pi@raspberrypi:~ $ echo "test" > /mnt/CCTV/PiZero/test.txt

-bash: /mnt/CCTV/PiZero/test.txt: Permission denied

So: pi@raspberrypi:~ $ sudo chown /mnt/CCTV/PiZero. chown: missing operand after ?/mnt/CCTV/PiZero? Try 'chown --help' for more information.

pi@raspberrypi:~ $ sudo chown //192.168.0.22/CCTV/PiZero /mnt/CCTV/PiZero chown: invalid user: ?//192.168.0.22/CCTV/PiZero?

I left it for an hour or so, then tried again: pi@raspberrypi:~ $ sudo echo "test" > /mnt/CCTV/PiZero/test.txt

-bash: /mnt/CCTV/PiZero/test.txt: Permission denied

So: pi@raspberrypi:~ $ sudo chown -R pi:pi /mnt/CCTV/PiZero pi@raspberrypi:~ $ sudo rm /mnt/CCTV/PiZero/test.txt

I then looked on my FreeNAS box , in the CCTV/PiZero directory, and to my surprise, I saw files there from yesterday, and also the test.txt file.

The files from yesterday are the ones started by the python script on motion detected, BUT, they are all 0 bytes.

So as I say, some improvment.

I removed the # from infront of os.unlink, and I'm still getting permission denied after this:

pi@raspberrypi:~ $ sudo mount //192.168.0.22/CCTV/PiZero /mnt/CCTV/PiZero -o username=root,password=******

pi@raspberrypi:~ $ python intruder_recmotion.pyTraceback (most recent call last): File "intruder_recmotion.py", line 37, in shutil.copyfile(RAMname, NASname) File "/usr/lib/python2.7/shutil.py", line 83, in copyfile with open(dst, 'wb') as fdst: IOError: [Errno 13] Permission denied: '/mnt/CCTV/PiZero/2018-050-22_11.34.55.h264'

So I tried: sudo chown -R pi:pi /mnt/CCTV/PiZero

then: pi@raspberrypi:~ $ python intruder_recmotion.py Traceback (most recent call last): File "intruder_recmotion.py", line 37, in shutil.copyfile(RAMname, NASname) File "/usr/lib/python2.7/shutil.py", line 83, in copyfile with open(dst, 'wb') as fdst: IOError: [Errno 13] Permission denied: '/mnt/CCTV/PiZero/2018-050-22_11.44.02.h264' pi@raspberrypi:~ $

Again, the files are being created, but are all 0 bytes.

Something is just not quite right.

Clutching at straws here, but does the /etc/fsab file need editing with this:

Thanks

what does ls -la /mnt/CCTV/PiZero say? (run the command and paste its output here)

pi@raspberrypi:~ $ ls -ls /mnt/CCTV/PiZero total 7

You might want to change that root password now you've just posted it.