Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On August 23, 2013 01:44:12 PM Timur Birsh wrote: On Thu, Aug 22, 2013 at 08:54 -0500, Steve M. Robbins wrote: Perhaps I should put create_cache_dir() call in 'restart' command. Perhaps you can code it so that restart just calls stop and then start? That seems to be a fairly common idiom. Yep, 'restart' calls 'stop' and then 'start' which are implemented as ordinary functions, do_stop() and do_start(). But create_cache_dir() is called outside of the do_start(). I guess do_start() could call create_cache_dir(). Ok. If you agree I'll close the bug. Yes: moving the call to create_cache_dir() inside do_start() would fix the issue. Thanks! -Steve signature.asc Description: This is a digitally signed message part.
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Thu, Aug 22, 2013 at 08:54 -0500, Steve M. Robbins wrote: Perhaps I should put create_cache_dir() call in 'restart' command. Perhaps you can code it so that restart just calls stop and then start? That seems to be a fairly common idiom. Yep, 'restart' calls 'stop' and then 'start' which are implemented as ordinary functions, do_stop() and do_start(). But create_cache_dir() is called outside of the do_start(). I guess do_start() could call create_cache_dir(). Ok. If you agree I'll close the bug. Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Wed, Aug 21, 2013 at 23:25 -0500, Steve M. Robbins wrote:
root@riemann{~}ls -la /run/inadyn
ls: cannot access /run/inadyn: No such file or directory
root@riemann{~}ls -la /var/log/inadyn
total 16
drwxr-xr-x 2 debian-inadyn debian-inadyn 4096 Aug 10 10:08 .
drwxr-xr-x 27 root root 12288 Aug 21 23:09 ..
root@riemann{~}ls -l /etc/inadyn.conf
-rw-r- 1 root debian-inadyn 787 Aug 9 02:24 /etc/inadyn.conf
As I can see, postinst script ran ok: log dir and config have correct owner.
I edited /et/default/inadyn, and /etc/inadyn.conf, then:
root@riemann{~}/etc/init.d/inadyn restart
Why 'restart'? :) 'start' command in init script has create_cache_dir() call,
which creates /run/inadyn dir. So, if you invoke init script with 'start'
command,
it will create run dir with the correct owner.
Perhaps I should put create_cache_dir() call in 'restart' command.
--
Timur
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On August 22, 2013 03:27:56 PM Timur Birsh wrote:
On Wed, Aug 21, 2013 at 23:25 -0500, Steve M. Robbins wrote:
root@riemann{~}ls -la /run/inadyn
ls: cannot access /run/inadyn: No such file or directory
root@riemann{~}ls -la /var/log/inadyn
total 16
drwxr-xr-x 2 debian-inadyn debian-inadyn 4096 Aug 10 10:08 .
drwxr-xr-x 27 root root 12288 Aug 21 23:09 ..
root@riemann{~}ls -l /etc/inadyn.conf
-rw-r- 1 root debian-inadyn 787 Aug 9 02:24 /etc/inadyn.conf
As I can see, postinst script ran ok: log dir and config have correct owner.
I edited /et/default/inadyn, and /etc/inadyn.conf, then:
root@riemann{~}/etc/init.d/inadyn restart
Why 'restart'? :) 'start' command in init script has create_cache_dir()
call, which creates /run/inadyn dir. So, if you invoke init script with
'start' command, it will create run dir with the correct owner.
Habit. I generally assume restart == stop + start, and therefore that
restart is the same as start if the daemon is not running.
Perhaps I should put create_cache_dir() call in 'restart' command.
Perhaps you can code it so that restart just calls stop and then start?
That seems to be a fairly common idiom.
-Steve
signature.asc
Description: This is a digitally signed message part.
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On August 20, 2013 02:58:27 PM Timur Birsh wrote:
The package had installed w/o any errors?
I don't recall seeing any install errors.
Would you please uninstall the package completely (w/ run/log dirs, config)
and install it again.
OK.
Right after install please run following commands,
and show its output.
$ ls -la /run/inadyn (there should be error)
$ ls -la /var/log/inadyn
$ ls -l /etc/inadyn.conf
root@riemann{~}ls -la /run/inadyn
ls: cannot access /run/inadyn: No such file or directory
root@riemann{~}ls -la /var/log/inadyn
total 16
drwxr-xr-x 2 debian-inadyn debian-inadyn 4096 Aug 10 10:08 .
drwxr-xr-x 27 root root 12288 Aug 21 23:09 ..
root@riemann{~}ls -l /etc/inadyn.conf
-rw-r- 1 root debian-inadyn 787 Aug 9 02:24 /etc/inadyn.conf
I edited /et/default/inadyn, and /etc/inadyn.conf, then:
root@riemann{~}/etc/init.d/inadyn restart
root@riemann{~}sudo ls -la /var/run/inadyn/
total 0
drwxr-xr-x 2 root root 40 Aug 21 23:13 .
drwxr-xr-x 41 root root 1540 Aug 21 23:13 ..
-Steve
signature.asc
Description: This is a digitally signed message part.
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Mon, Aug 19, 2013 at 12:33 -0500, Steve M. Robbins wrote: Attached in file typescript. Note that /run/inadyn was originally owned by root. As you see in the log file, the daemon failed to run. I manually changed the owner, then re-started the daemon using sudo /etc/init.d/inadyn restart. It's running fine now. The package had installed w/o any errors? Would you please uninstall the package completely (w/ run/log dirs, config) and install it again. Right after install please run following commands, and show its output. $ ls -la /run/inadyn (there should be error) $ ls -la /var/log/inadyn $ ls -l /etc/inadyn.conf Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
Hi, Thanks for your report. On Sun, Aug 18, 2013 at 17:45 -0500, Steve M. Robbins wrote: Package: inadyn Version: 1.99.4-1 Followup-For: Bug #711226 Hi, I ran into this problem on a new install of 1.99.4-1. Would you please show log messages and output of the following commands: $ ls -la /run/inadyn $ ls -la /var/log/inadyn $ getent passwd debian-inadyn $ getent group debian-inadyn Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Mon, Aug 19, 2013 at 02:09:48PM +0600, Timur Birsh wrote: Would you please show log messages Attached in file inadyn.log. and output of the following commands: $ ls -la /run/inadyn $ ls -la /var/log/inadyn $ getent passwd debian-inadyn $ getent group debian-inadyn Attached in file typescript. Note that /run/inadyn was originally owned by root. As you see in the log file, the daemon failed to run. I manually changed the owner, then re-started the daemon using sudo /etc/init.d/inadyn restart. It's running fine now. Regards, -Steve Sun Aug 18 17:35:41 2013: Failed opening pidfile /run/inadyn/inadyn.pid for writing: Permission denied Sun Aug 18 17:35:41 2013: Failed starting daemon: RC_ERROR Sun Aug 18 17:38:42 2013: Inadyn version 1.99.4 -- Dynamic DNS update client. Sun Aug 18 17:38:42 2013: Resolving hostname sumost.no-ip.biz = IP# 24.79.69.180 Sun Aug 18 17:38:42 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 17:38:42 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 17:43:42 2013: . Sun Aug 18 17:43:42 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 17:43:42 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 17:48:42 2013: . Sun Aug 18 17:48:42 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 17:48:42 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 17:53:42 2013: . Sun Aug 18 17:53:42 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 17:53:43 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 17:58:43 2013: . Sun Aug 18 17:58:43 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 17:58:43 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:03:43 2013: . Sun Aug 18 18:03:43 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:03:43 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:08:43 2013: . Sun Aug 18 18:08:43 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:08:43 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:13:43 2013: . Sun Aug 18 18:13:43 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:13:43 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:18:43 2013: . Sun Aug 18 18:18:43 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:18:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:23:44 2013: . Sun Aug 18 18:23:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:23:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:28:44 2013: . Sun Aug 18 18:28:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:28:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:33:44 2013: . Sun Aug 18 18:33:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:33:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:38:44 2013: . Sun Aug 18 18:38:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:38:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:43:44 2013: . Sun Aug 18 18:43:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:43:44 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:48:44 2013: . Sun Aug 18 18:48:44 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:48:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:53:45 2013: . Sun Aug 18 18:53:45 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:53:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 18:58:45 2013: . Sun Aug 18 18:58:45 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 18:58:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 19:03:45 2013: . Sun Aug 18 19:03:45 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 19:03:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 19:08:45 2013: . Sun Aug 18 19:08:45 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 19:08:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 19:13:45 2013: . Sun Aug 18 19:13:45 2013: Checking for IP# change, connecting to ip1.dynupdate.no-ip.com(8.23.224.121) Sun Aug 18 19:13:45 2013: No IP# change detected, still at 24.79.69.180 Sun Aug 18 19:18:45 2013: . Sun Aug 18 19:18:45 2013: Checking
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
Package: inadyn Version: 1.99.4-1 Followup-For: Bug #711226 Hi, I ran into this problem on a new install of 1.99.4-1. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages inadyn depends on: ii adduser 3.113+nmu3 ii libc62.17-92 inadyn recommends no packages. inadyn suggests no packages. -- Configuration Files: /etc/default/inadyn changed: RUN_DAEMON=yes RUN_IPUP=no USER=debian-inadyn GROUP=debian-inadyn /etc/inadyn.conf [Errno 13] Permission denied: u'/etc/inadyn.conf' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Thu, Jul 18, 2013 at 18:31 +0200, Bzzz wrote: O_o, there's quite a bug in the latest pkg!: # chown root:inadyn /run/inadyn/ chown: invalid group: `root:inadyn' # chown inadyn:root /run/inadyn/ chown: invalid user: `inadyn:root' Hmm, inadyn's user/group are debian-inadyn. Would you please completely remove the package (w/ config, run dir and logs), install version 1.96.2-1, create /etc/inadyn.conf, start/stop the daemon to create run dir and logs. And then upgrade it to 1.99.3-1? Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
Hi, On Fri, Jun 07, 2013 at 18:47 +0200, Bzzz wrote: That I did, unfortunately: # dpkg -i inadyn_1.98.1+git20130517-3_i386.deb Selecting previously unselected package inadyn. (Reading database ... 388562 files and directories currently installed.) Unpacking inadyn (from inadyn_1.98.1+git20130517-3_i386.deb) ... Setting up inadyn (1.98.1+git20130517-3) ... dpkg: error processing inadyn (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: inadyn I'm sorry for a big delay. It was very busy weeks. Would you pretty please test updated package? http://mentors.debian.net/debian/pool/main/i/inadyn/inadyn_1.99.3-1.dsc Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Thu, Jun 06, 2013 at 11:46 +0200, Bzzz wrote: Did you start inadyn using /etc/init.d/inadyn script? Now that you ask, I'm not so sure… So, I just purge the pkg and reinstall it; bug is confirmed: tail /var/log/inadyn/inadyn.log Thu Jun 6 11:31:34 2013: Failed opening pidfile /run/inadyn/inadyn.pid for writing: Permission denied Thu Jun 6 11:31:34 2013: Failed starting daemon: RC_ERROR la /run drwxr-xr-x 2 root root 40 juin 6 11:31 inadyn This is a pre|postinstall issue as the /etc/init.d/inadyn script contain what is needed to correctly recreate the faulty directory; however as this directory is already created with the wrong rights 'create_cache_dir()' does nothing. 2 poss. solts: 1- install script give the good rights (+) (and 'create_cache_dir()' is not useful anymore) 2- install script don't create this directory (-) I've uploaded updated package to mentors. Would you please test it? http://mentors.debian.net/package/inadyn Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
On Fri, Jun 07, 2013 at 15:41 +0200, Bzzz wrote: On Fri, 7 Jun 2013 14:38:54 +0600 Huu, I never used mentors and all what I see on it is a link to a .dsc source package. I already saw such an extension when compiling regular packages, but I don't have any clue about how to do that directly with this one. Could you enlighten me, please? Please follow these: $ dget http://mentors.debian.net/debian/pool/main/i/inadyn/inadyn_1.98.1+git20130517-3.dsc $ dpkg-source -x inadyn_1.98.1+git20130517-3.dsc $ cd inadyn-1.98.1+git20130517 $ dpkg-buildpackage -rfakeroot -us -uc $ dpkg -i ../inadyn_1.98.1+git20130517-3_i386.deb Please ignore that gpg cannot verify signature. build-essential, devscripts, fakeroot packages should be installed. Or I can upload binary package (i386) somewhere. Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
Package: inadyn Version: 1.98.1+git20130517-2 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, * What led up to the situation? Installing configuring inadyn and trying to start it. * What exactly did you do (or not do) that was effective (or ineffective)? It won't start. * What was the outcome of this action? A glance at the log file shows that inadyn is unable to write to /run/inadyn; a check confirmed that /run/inadyn has 755 root:root, an owner changer fixed that: 755 debian-inadyn:debian-inadyn. This joins the 709391 bug report (however, OP didn't fix the issue properly by changing dir rights to 777). * What outcome did you expect instead? /run/inadyn rights to be OK -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.8-2-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages inadyn depends on: ii adduser 3.113+nmu3 ii libc62.17-3 inadyn recommends no packages. inadyn suggests no packages. -- Configuration Files: /etc/default/inadyn changed [not included] /etc/inadyn.conf [Errno 13] Permission denied: u'/etc/inadyn.conf' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711226: inadyn: Can't start because of wrong owner of /run/inadyn
Hi, Thanks for your report. On Wed, Jun 05, 2013 at 19:08 +0200, Bzzz wrote: A glance at the log file shows that inadyn is unable to write to /run/inadyn; a check confirmed that /run/inadyn has 755 root:root, an owner changer fixed that: 755 debian-inadyn:debian-inadyn. This joins the 709391 bug report (however, OP didn't fix the issue properly by changing dir rights to 777). Did you start inadyn using /etc/init.d/inadyn script? Thanks. -- Timur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
