| 2021-10-08 19:36:00 |
Bruce Duncan |
bug |
|
|
added bug |
| 2023-09-20 19:49:16 |
Launchpad Janitor |
motion (Ubuntu): status |
New |
Confirmed |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
nominated for series |
|
Ubuntu Mantic |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
bug task added |
|
motion (Ubuntu Mantic) |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
nominated for series |
|
Ubuntu Noble |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
bug task added |
|
motion (Ubuntu Noble) |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-29 22:52:04 |
Erich Eickmeyer |
bug task added |
|
motion (Ubuntu Jammy) |
|
| 2024-03-01 23:00:42 |
Sudip Mukherjee |
motion (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2024-03-01 23:00:44 |
Sudip Mukherjee |
motion (Ubuntu Mantic): status |
New |
Confirmed |
|
| 2024-03-01 23:00:49 |
Sudip Mukherjee |
motion (Ubuntu Jammy): assignee |
|
Sudip Mukherjee (sudipmuk) |
|
| 2024-03-01 23:00:51 |
Sudip Mukherjee |
motion (Ubuntu Mantic): assignee |
|
Sudip Mukherjee (sudipmuk) |
|
| 2024-03-01 23:00:54 |
Sudip Mukherjee |
motion (Ubuntu Noble): assignee |
|
Sudip Mukherjee (sudipmuk) |
|
| 2024-03-01 23:00:57 |
Sudip Mukherjee |
motion (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2024-03-01 23:01:00 |
Sudip Mukherjee |
motion (Ubuntu Mantic): status |
Confirmed |
In Progress |
|
| 2024-03-01 23:01:02 |
Sudip Mukherjee |
motion (Ubuntu Noble): status |
Confirmed |
In Progress |
|
| 2024-03-05 22:13:17 |
Sudip Mukherjee |
summary |
motion fails to start after install: Permission denied creating log file |
[SRU] motion fails to start after install: Permission denied creating log file |
|
| 2024-03-05 22:14:15 |
Sudip Mukherjee |
description |
I installed motion for the first time on a reasonably fresh Kubuntu 21.04 release. I installed this system in April 2021. It immediately fails and spams "emergency" log messages all over my terminals. (See dpkg log below)
The problem seems to be that the default config /etc/motion/motion.conf specifies:
log_file /var/log/motion/motion.log
but there is nothing to create that directory. I'm not sure whether this should be a job for postinst, or a systemd ExecStartPre, but I would argue that not logging to a file at all and letting systemd-journald hoover up the stderr/syslog messages would be better.
Indeed, if I remove the log_file line from /etc/motion/motion.conf, motion starts and runs perfectly well, and I get log messages in systemctl status.
Thanks,
Bruce
Dpkg log:
Setting up motion (4.3.2-1) ...
Adding group `motion' (GID 134) ...
Done.
Warning: The home dir /var/lib/motion you specified already exists.
Adding system user `motion' (UID 127) ...
Adding new user `motion' (UID 127) with group `motion' ...
The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'.
adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service.
Processing triggers for man-db (2.9.4-2) ...
Broadcast message from systemd-journald@w7700 (Fri 2021-10-08 01:05:54 BST):
motion[1372993]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied |
[ Impact ]
motion will fail to start after installing with the error:
motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Also, service status will show:
$ systemctl status motion.service
○ motion.service - Motion detection video capture daemon
Loaded: loaded (/usr/lib/systemd/system/motion.service; enabled; preset: enabled)
Active: inactive (dead) since Tue 2024-03-05 21:47:35 GMT; 1min 16s ago
Duration: 91ms
Docs: man:motion(1)
Process: 4536 ExecStart=/usr/bin/motion (code=exited, status=0/SUCCESS)
Main PID: 4536 (code=exited, status=0/SUCCESS)
CPU: 49ms
Mar 05 21:47:34 sudip-pc-i440fx-7-2 systemd[1]: Started motion.service - Motion detection video capture daemon.
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:35 sudip-pc-i440fx-7-2 systemd[1]: motion.service: Deactivated successfully.
Any attempt to start or restart the service will still fail.
$ sudo systemctl start motion.service
Broadcast message from systemd-journald@sudip-pc-i440fx-7-2 (Tue 2024-03-05 21:49:44 GMT):
motion[4621]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
The problem will be there until the /var/log/motion directory is created. A non-technical user will see "motion" is not working.
[ Test Plan ]
1. Install motion
2. Check motion service status and confirm its started
With the fixed package, motion service status will shows it has started.
[ Where problems could occur ]
It does not change any part of the code, only adds in the postinst script to create the log folder if it does not exist. There should not be any regression in the software for this change.
[ Other Info ]
The log folder creation was part of the init scripts at https://git.launchpad.net/ubuntu/+source/motion/tree/debian/motion.init?h=ubuntu/focal#n60
I guess it was missed while updating the package to use systemd services.
The error will not be seen by users upgrading from Focal.
[ Original Bug Description ]
I installed motion for the first time on a reasonably fresh Kubuntu 21.04 release. I installed this system in April 2021. It immediately fails and spams "emergency" log messages all over my terminals. (See dpkg log below)
The problem seems to be that the default config /etc/motion/motion.conf specifies:
log_file /var/log/motion/motion.log
but there is nothing to create that directory. I'm not sure whether this should be a job for postinst, or a systemd ExecStartPre, but I would argue that not logging to a file at all and letting systemd-journald hoover up the stderr/syslog messages would be better.
Indeed, if I remove the log_file line from /etc/motion/motion.conf, motion starts and runs perfectly well, and I get log messages in systemctl status.
Thanks,
Bruce
Dpkg log:
Setting up motion (4.3.2-1) ...
Adding group `motion' (GID 134) ...
Done.
Warning: The home dir /var/lib/motion you specified already exists.
Adding system user `motion' (UID 127) ...
Adding new user `motion' (UID 127) with group `motion' ...
The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'.
adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service.
Processing triggers for man-db (2.9.4-2) ...
Broadcast message from systemd-journald@w7700 (Fri 2021-10-08 01:05:54 BST):
motion[1372993]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied |
|
| 2024-03-05 22:15:23 |
Sudip Mukherjee |
description |
[ Impact ]
motion will fail to start after installing with the error:
motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Also, service status will show:
$ systemctl status motion.service
○ motion.service - Motion detection video capture daemon
Loaded: loaded (/usr/lib/systemd/system/motion.service; enabled; preset: enabled)
Active: inactive (dead) since Tue 2024-03-05 21:47:35 GMT; 1min 16s ago
Duration: 91ms
Docs: man:motion(1)
Process: 4536 ExecStart=/usr/bin/motion (code=exited, status=0/SUCCESS)
Main PID: 4536 (code=exited, status=0/SUCCESS)
CPU: 49ms
Mar 05 21:47:34 sudip-pc-i440fx-7-2 systemd[1]: Started motion.service - Motion detection video capture daemon.
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:35 sudip-pc-i440fx-7-2 systemd[1]: motion.service: Deactivated successfully.
Any attempt to start or restart the service will still fail.
$ sudo systemctl start motion.service
Broadcast message from systemd-journald@sudip-pc-i440fx-7-2 (Tue 2024-03-05 21:49:44 GMT):
motion[4621]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
The problem will be there until the /var/log/motion directory is created. A non-technical user will see "motion" is not working.
[ Test Plan ]
1. Install motion
2. Check motion service status and confirm its started
With the fixed package, motion service status will shows it has started.
[ Where problems could occur ]
It does not change any part of the code, only adds in the postinst script to create the log folder if it does not exist. There should not be any regression in the software for this change.
[ Other Info ]
The log folder creation was part of the init scripts at https://git.launchpad.net/ubuntu/+source/motion/tree/debian/motion.init?h=ubuntu/focal#n60
I guess it was missed while updating the package to use systemd services.
The error will not be seen by users upgrading from Focal.
[ Original Bug Description ]
I installed motion for the first time on a reasonably fresh Kubuntu 21.04 release. I installed this system in April 2021. It immediately fails and spams "emergency" log messages all over my terminals. (See dpkg log below)
The problem seems to be that the default config /etc/motion/motion.conf specifies:
log_file /var/log/motion/motion.log
but there is nothing to create that directory. I'm not sure whether this should be a job for postinst, or a systemd ExecStartPre, but I would argue that not logging to a file at all and letting systemd-journald hoover up the stderr/syslog messages would be better.
Indeed, if I remove the log_file line from /etc/motion/motion.conf, motion starts and runs perfectly well, and I get log messages in systemctl status.
Thanks,
Bruce
Dpkg log:
Setting up motion (4.3.2-1) ...
Adding group `motion' (GID 134) ...
Done.
Warning: The home dir /var/lib/motion you specified already exists.
Adding system user `motion' (UID 127) ...
Adding new user `motion' (UID 127) with group `motion' ...
The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'.
adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service.
Processing triggers for man-db (2.9.4-2) ...
Broadcast message from systemd-journald@w7700 (Fri 2021-10-08 01:05:54 BST):
motion[1372993]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied |
[ Impact ]
motion will fail to start after installing with the error:
motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Also, service status will show:
$ systemctl status motion.service
○ motion.service - Motion detection video capture daemon
Loaded: loaded (/usr/lib/systemd/system/motion.service; enabled; preset: enabled)
Active: inactive (dead) since Tue 2024-03-05 21:47:35 GMT; 1min 16s ago
Duration: 91ms
Docs: man:motion(1)
Process: 4536 ExecStart=/usr/bin/motion (code=exited, status=0/SUCCESS)
Main PID: 4536 (code=exited, status=0/SUCCESS)
CPU: 49ms
Mar 05 21:47:34 sudip-pc-i440fx-7-2 systemd[1]: Started motion.service - Motion detection video capture daemon.
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [ERR] [ALL] mycreate_path: Problem creating directory /var/log/motion: Permission denied
Mar 05 21:47:34 sudip-pc-i440fx-7-2 motion[4536]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
Mar 05 21:47:35 sudip-pc-i440fx-7-2 systemd[1]: motion.service: Deactivated successfully.
Any attempt to start or restart the service will still fail.
$ sudo systemctl start motion.service
Broadcast message from systemd-journald@sudip-pc-i440fx-7-2 (Tue 2024-03-05 21:49:44 GMT):
motion[4621]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied
The problem will be there until the /var/log/motion directory is created. A non-technical user will see "motion" is not working.
[ Test Plan ]
1. Install motion
2. Check motion service status and confirm its started
With the fixed package, motion service status will shows it has started.
[ Where problems could occur ]
It does not change any part of the code, only change is in the postinst script to create the log folder if it does not exist. There should not be any regression in the software for this change.
[ Other Info ]
The log folder creation was part of the init scripts at https://git.launchpad.net/ubuntu/+source/motion/tree/debian/motion.init?h=ubuntu/focal#n60
I guess it was missed while updating the package to use systemd services.
The error will not be seen by users upgrading from Focal.
[ Original Bug Description ]
I installed motion for the first time on a reasonably fresh Kubuntu 21.04 release. I installed this system in April 2021. It immediately fails and spams "emergency" log messages all over my terminals. (See dpkg log below)
The problem seems to be that the default config /etc/motion/motion.conf specifies:
log_file /var/log/motion/motion.log
but there is nothing to create that directory. I'm not sure whether this should be a job for postinst, or a systemd ExecStartPre, but I would argue that not logging to a file at all and letting systemd-journald hoover up the stderr/syslog messages would be better.
Indeed, if I remove the log_file line from /etc/motion/motion.conf, motion starts and runs perfectly well, and I get log messages in systemctl status.
Thanks,
Bruce
Dpkg log:
Setting up motion (4.3.2-1) ...
Adding group `motion' (GID 134) ...
Done.
Warning: The home dir /var/lib/motion you specified already exists.
Adding system user `motion' (UID 127) ...
Adding new user `motion' (UID 127) with group `motion' ...
The home directory `/var/lib/motion' already exists. Not copying from `/etc/skel'.
adduser: Warning: The home directory `/var/lib/motion' does not belong to the user you are currently creating.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service.
Processing triggers for man-db (2.9.4-2) ...
Broadcast message from systemd-journald@w7700 (Fri 2021-10-08 01:05:54 BST):
motion[1372993]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied |
|
| 2024-03-05 22:15:59 |
Sudip Mukherjee |
attachment added |
|
motion_noble.debdiff https://bugs.launchpad.net/ubuntu/+source/motion/+bug/1946521/+attachment/5752986/+files/motion_noble.debdiff |
|
| 2024-03-05 22:16:26 |
Sudip Mukherjee |
attachment added |
|
motion_mantic.debdiff https://bugs.launchpad.net/ubuntu/+source/motion/+bug/1946521/+attachment/5752987/+files/motion_mantic.debdiff |
|
| 2024-03-05 22:16:46 |
Sudip Mukherjee |
attachment added |
|
motion_jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/motion/+bug/1946521/+attachment/5752988/+files/motion_jammy.debdiff |
|
| 2024-03-05 22:17:02 |
Sudip Mukherjee |
motion (Ubuntu Jammy): status |
In Progress |
Confirmed |
|
| 2024-03-05 22:17:04 |
Sudip Mukherjee |
motion (Ubuntu Mantic): status |
In Progress |
Confirmed |
|
| 2024-03-05 22:17:09 |
Sudip Mukherjee |
motion (Ubuntu Noble): status |
In Progress |
Confirmed |
|
| 2024-03-05 22:17:12 |
Sudip Mukherjee |
motion (Ubuntu Jammy): assignee |
Sudip Mukherjee (sudipmuk) |
|
|
| 2024-03-05 22:17:14 |
Sudip Mukherjee |
motion (Ubuntu Mantic): assignee |
Sudip Mukherjee (sudipmuk) |
|
|
| 2024-03-05 22:17:16 |
Sudip Mukherjee |
motion (Ubuntu Noble): assignee |
Sudip Mukherjee (sudipmuk) |
|
|
| 2024-03-05 22:17:20 |
Sudip Mukherjee |
bug |
|
|
added subscriber Sudip Mukherjee |
| 2024-03-05 22:17:32 |
Sudip Mukherjee |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2024-03-05 22:39:20 |
Sudip Mukherjee |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849712 |
|
| 2024-03-05 22:39:20 |
Sudip Mukherjee |
bug task added |
|
motion (Debian) |
|
| 2024-03-06 00:04:49 |
Bug Watch Updater |
motion (Debian): status |
Unknown |
New |
|
| 2024-03-25 14:18:37 |
Dave Jones |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2024-03-25 15:43:17 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Dave Jones |
| 2024-03-28 08:08:18 |
Launchpad Janitor |
motion (Ubuntu Noble): status |
Confirmed |
Fix Released |
|
| 2024-04-05 13:43:58 |
Timo Aaltonen |
motion (Ubuntu Mantic): status |
Confirmed |
Fix Committed |
|
| 2024-04-05 13:44:00 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-04-05 13:44:02 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2024-04-05 13:44:05 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-mantic |
|
| 2024-04-05 13:44:34 |
Timo Aaltonen |
motion (Ubuntu Jammy): status |
Confirmed |
Fix Committed |
|
| 2024-04-05 13:44:38 |
Timo Aaltonen |
tags |
verification-needed verification-needed-mantic |
verification-needed verification-needed-jammy verification-needed-mantic |
|
| 2024-05-04 18:22:43 |
Sudip Mukherjee |
tags |
verification-needed verification-needed-jammy verification-needed-mantic |
verification-done verification-done-jammy verification-done-mantic |
|
| 2024-06-05 08:57:05 |
Launchpad Janitor |
motion (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2024-06-05 08:57:08 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-06-05 08:57:14 |
Launchpad Janitor |
motion (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
