It appears that I have solved the problem related to permissions for
/var/run/motion. Further investigation shows that Motion seems to start
OK and then crashes. This crash does not appear to be related to this
bug 294852. I am running 2 cameras so it may be related to bug 604169.
When I confi
I have server version 12.04 installed with the same bug. I tried the
fix in Post 4 and got the following results. Motion is started but then
dies.
darren@alpha:~$ pgrep motion
darren@alpha:~$ sudo /etc/init.d/motion restart
[sudo] password for darren:
* Restarting motion...
12.04 64 bit, seeing the same thing. At first I thought I was working
around the issue by giving myself permission to /var/run/motion, until I
realized it seems to disappear on itself.
I've also noticed if I run sudo /etc/init.d/motion restart, once motion
is detected, the process disappears and n
This bug was still present for me in 11.10 and the fix #4 worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/294852
Title:
motion fails to start because /var/run/motion is missing
To manage noti
Also occurring in Maverick 10.10. Torglut's solution #4 works for me (I
use a slightly modified form in Bug #675694)
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification because you are a member of Ubuntu
Bugs, whic
The bug also exists in Lucid 10.04.
By doing what torglut suggests in the comment #4 above everything works fine.
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This does work around the issue, but why does /var/run/motion disappear
in the first place?
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug still exists in 9.10
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu 9.10"
This bug seams to be nearly the same as the one described here (for another
package) :
https://bugs.launchpad.net/ubuntu/+source/zabbix/+bug/17277
** Changed in: motion (Ubuntu)
Status: New => Confirmed
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Still present on Hardy-amd64 - I also had to fiddle out a workaround, a
bit different, but same root cause:
motion (as daemon) runs as user=motion, group=motion which is correkt from
point of security.
But this prohibits to place its PIDFILE in /var/run cause lack of permission.
--
motion fail
The same problem on Ubuntu 9.04 Jaunty 32bit, my work around is to launch like
this:
sudo mkdir /var/run/motion ; motion
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification because you are a member of Ubuntu
Bugs,
The -b flag to start-stop-daemon really causes problems and should be
removed. When motion believes it is running in the foreground it does
not write a PID file
--
motion fails to start because /var/run/motion is missing
https://bugs.launchpad.net/bugs/294852
You received this bug notification be
12 matches
Mail list logo
