Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

2015-10-12 Thread Ara Keary
Many thanks for the very fast solution!
Updating from 227-1 to 227-2 solves
• unmounting of partitions at boot
• ssh rsa/dsa-key authentification issue that occurred if partitions were
manually mounted (with: mount -a) and gdm manually started under version
227-1

Best,
Ara



On 9 October 2015 at 14:08, Martin Pitt  wrote:

> Control: tag -1 pending
>
> I found the offending commit, reverted it, and currently run tests.
> I'll upload 227-2 within the hour.
>
> Ara Keary [2015-10-09 12:55 +0200]:
> > Other symptom, if helpful: trying to log with rsa/dsa key fails on every
> > machine i can access to.
> > Could all this mess be related to a (pam) *system-wise authentification
> > problem*?
>
> Might be #801354?
>
> > Maintainers: i really truly appreciate ∞ly your work, but do you test
> > updates before uploading? ...
>
> We do of course, with both automated and manual tests, but #801354 is
> a race condition which doesn't happen everywhere, and this bug doesn't
> actually surface at all until you look at the logs (for non-root
> logins it's just cosmetical). I added a test case for this now,
> though.
>
> Sorry, but sh** happens :-/
>
> Martin
>
> --
> Martin Pitt| http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
>


Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

2015-10-09 Thread Ara Keary
Hi,

same here: no proper boot after 227-1 → 226-4 systemd update.

/var/log/syslog show attempts to unount EVERY partition ; only the
unmounting of / fails (fortunately...).

Under amd64 multiarch, downgrading
 systemd libpam-systemd libsystemd libsystemd:i386
to 226-4 solves the problem

Before downgrading, solved manually by mounting manually all partitions
from root console
 mount -a
and restarting gdm
 service gdm restart

Other symptom, if helpful: trying to log with rsa/dsa key fails on every
machine i can access to.
Could all this mess be related to a (pam) *system-wise authentification
problem*?

On fresh testing → unstable 1 day old update: same symptoms. Thus seems
unrelated to old .conf file problem.

Maintainers: i really truly appreciate ∞ly your work, but do you test
updates before uploading? ...

Best log decrypting,

Ara

PS Severity should be critical


Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

2015-10-09 Thread Ara Keary
PS, downgrading (under amd64)
 systemd libpam-systemd libsystemd libsystemd:i386
to 226-4 on source and destination systems also solves the rsa/dsa ssh key
logging problem (it works again).
Tell me if any log file is needed

On 9 October 2015 at 12:55, Ara Keary  wrote:

> Hi,
>
> same here: no proper boot after 227-1 → 226-4 systemd update.
>
> /var/log/syslog show attempts to unount EVERY partition ; only the
> unmounting of / fails (fortunately...).
>
> Under amd64 multiarch, downgrading
>  systemd libpam-systemd libsystemd libsystemd:i386
> to 226-4 solves the problem
>
> Before downgrading, solved manually by mounting manually all partitions
> from root console
>  mount -a
> and restarting gdm
>  service gdm restart
>
> Other symptom, if helpful: trying to log with rsa/dsa key fails on every
> machine i can access to.
> Could all this mess be related to a (pam) *system-wise authentification
> problem*?
>
> On fresh testing → unstable 1 day old update: same symptoms. Thus seems
> unrelated to old .conf file problem.
>
> Maintainers: i really truly appreciate ∞ly your work, but do you test
> updates before uploading? ...
>
> Best log decrypting,
>
> Ara
>
> PS Severity should be critical
>


Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

2015-10-09 Thread Martin Pitt
Control: tag -1 pending

I found the offending commit, reverted it, and currently run tests.
I'll upload 227-2 within the hour.

Ara Keary [2015-10-09 12:55 +0200]:
> Other symptom, if helpful: trying to log with rsa/dsa key fails on every
> machine i can access to.
> Could all this mess be related to a (pam) *system-wise authentification
> problem*?

Might be #801354?

> Maintainers: i really truly appreciate ∞ly your work, but do you test
> updates before uploading? ...

We do of course, with both automated and manual tests, but #801354 is
a race condition which doesn't happen everywhere, and this bug doesn't
actually surface at all until you look at the logs (for non-root
logins it's just cosmetical). I added a test case for this now,
though.

Sorry, but sh** happens :-/

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature


Processed: Re: Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

2015-10-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #801361 [systemd] [systemd] attempts to unmount filesystems at end of boot, 
INCLUDING ROOT
Added tag(s) pending.

-- 
801361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems