← Back to team overview

tieto team mailing list archive

[Bug 1003845] Re: Invisible symbols in sssd upstart config causes sssd to not start if /bin/sh is a link to /bin/bash

 

This bug was fixed in the package sssd - 1.8.6-0ubuntu0.2

---------------
sssd (1.8.6-0ubuntu0.2) precise-proposed; urgency=low

  * rules: Really install the new pam-auth-update file for password
    changes. (LP: #1086272)
  * rules: Pass --datadir, so the path in autogenerated python files is
    correctly substituted. (LP: #1079938)

** Changed in: sssd (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Tieto,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1003845

Title:
  Invisible symbols in sssd upstart config causes sssd to not start if
  /bin/sh is a link to /bin/bash

Status in “sssd” package in Ubuntu:
  Fix Released
Status in “sssd” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  prevents the daemon from starting when /bin/sh is bash

  [Test case]
  change /bin/sh to point to bash, run 'start sssd'

  [Regression potential]
  small, it's an obvious packaging bug

  --

  This problem appeared when I changed /bin/sh link to /bin/bash.
  Somehow dash tolerates this bug described below.

  When trying to start sssd I've got:

  root@ubuntu-precise:~# start sssd
  start: Job failed to start

  The only trace in syslog was:

  May 24 11:11:59 ubuntu-precise kernel: [66576.880595] init: sssd pre-
  start process (9782) terminated with status 2

  I've took a look on /etc/init/sssd.conf and everything looks ok, but
  after some play I make it to start, and this is the difference to the
  original:

  root@ubuntu-precise:/etc/init# diff sssd.conf sssd.conf.orig
  19c19
  < 	test -f /etc/sssd/sssd.conf || { stop; exit 0; }
  ---
  > 	test -f /etc/sssd/sssd.conf || { stop; exit 0; }

  This looks bizzare for me, so I tried that:

  root@ubuntu-precise:/etc/init# cat -A sssd.conf|grep test
  ^Itest -f /etc/sssd/sssd.conf || { stop; exit 0; }$
  root@ubuntu-precise:/etc/init# cat -A sssd.conf.orig|grep test
  ^Itest -f /etc/sssd/sssd.conf ||M-BM- { stop; exit 0; }$
  root@ubuntu-precise:/etc/init#

  I have no idea what does "M-BM-" stand for, but I'm sure this is not
  how it should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: sssd 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Thu May 24 11:02:44 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: sssd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.sssd.conf: 2012-05-24T10:54:11.246378

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1003845/+subscriptions