Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Abrupt Failure upon Apt upgrade to RPi2B (sidestep99)
2. Difficulty starting motion on VPN (TOCOLIN)
----------------------------------------------------------------------
Message: 1
Date: Sun, 14 Feb 2021 15:34:36 +0000
From: sidestep99 <sideste...@protonmail.com>
To: "motion-user@lists.sourceforge.net"
<motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Abrupt Failure upon Apt upgrade to RPi2B
Message-ID:
<3ldj3WMnD1Kntia81EOnA3CT0zpJWUnOzsjIeDvZ9xwweXW26dNeF_p-1YvKp1UUmWdhVrFT5GBqbYADQsDUlZbwudRL3fdOW5Jkw7ST1UA=@protonmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks to everyone who contacted me with insight. Always appreciated. I cleared
up the mess. Here's the summary of what I found:
It didn't matter what pixel format I used. Numerous changes all resulted in the
same types of log messages. I eventually left "v4l2_palette 9" as I was only
requiring jpeg output for the project.
I was inaccurately blaming the sudden failure of the setup on an apt
update/upgrade. But what I forgot to consider was the 128Gb Sandisk formatted
as ext4 that I had plugged into a USB port. Yes, I had installed the two ext4
utility packages just after the major apt update/upgrade, and those made it
possible to mount the USB stick, but those packages didn't seem to be the issue.
Bottom line: if the USB stick was plugged in, Motion complained about the two
items mentioned in my initial post, and would eventually croak. If the USB
stick was not plugged in, Motion ran like a champion.
I reformatted the Sandisk to fat32 (vfat), and no longer had any issues
whatsoever. Not sure what the deeper issue is, but I've read the old Model 2 B
units have some sort of bug with USB drives. After changing the format of the
USB stick, I was then able to redirect jpeg file output to the USB stick, and
the project configuration was finally done.
I appreciate the help I received from members monitoring these posts. As a
software engineer, I've only posted twice in about 30 years to any list, and
your replies/attention to this issue was the shot of adrenaline I needed to
keep pushing. I am humbled and encouraged.
> On Sat, Feb 13, 2021, 18:27 x via Motion-user
> <motion-user@lists.sourceforge.net> wrote:
>
>> I don't know if anyone else is writing about this, but my most recent weekly
>> update/upgrade to a test Raspberry Pi with Pi camera running Motion (which
>> was installed from apt) has abruptly ceased to function.
>>
>> A bit more background: Fully functioning, weekly updated/upgraded Raspberry
>> Pi with motion.conf simply taking a photo upon identifying the default
>> amount of motion. After my upgrade yesterday, motion no longer likes the
>> config. I didn't change anything in motion.conf. It all just stopped working
>> immediately after my weekly apt update/upgrade of this Pi.
>>
>> ~ tail motion.log:
>> v4l2_select_input: Device does not support specifying PAL/NTSC norm
>> followed by:
>> v4l2_do_set_pix_format: Error setting pixel format
>>
>> Anybody have any idea what changed causing this simple setup to no longer
>> work?
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sun, 14 Feb 2021 20:58:21 +0000
From: TOCOLIN <tocolinsd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Difficulty starting motion on VPN
Message-ID:
<CAMCWue9FJ-F9E+npt+X9teEc=r4cgrxztm1316ctyogox6f...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all
I've recently installed Motion and having only managed to output connection
refusal screens so far would appreciate any help;
Installed via 'sudo apt-get install motion'
Using VPN at 77.68.127.159 ,
login Putty
(saved the motion.conf file with localhost OFF)
Started app:
root@localhost:~# sudo motion
SSH output just reads-
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
/etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to file
(/var/log/motion/motion.log)
(I'm not sure if this is normally the only output at SSH terminal)
Then using Chrome,
http://<my VPN ip>:8081 , browser states <my VPN ip> refused to connect
I've also tried on Putty- root@localhost:~# nc -zvw3 <my VPN ip> 8081
which results- nc: connect to <my VPN ip> port 8081 (tcp) failed:
Connection refused
(Tried disabling Firewall too & the Motion log seems to indicate repeated
attempts to connect to Cameras which I've not connected yet as my
understanding is that there should at least be a grey blank display in any
case)
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 176, Issue 25
********************************************
