Breezy->dapper upgrade missing /var/run/sshd

Bug #38921 reported by Dave Gilbert
14
Affects Status Importance Assigned to Milestone
openssh (Ubuntu)
Invalid
Medium
Scott James Remnant (Canonical)

Bug Description

Hi,
  I did a dist-upgrade from breezy to dapper-pre (update at about 5pm BST 9th April);
The openssh-server upgrade failed complaining that
  missing privelidge separation directory: /var/run/sshd
  restart failed
(typed from notes with bonus spelling mistakes)

I should note I had some other issues during the upgrade (I hit the pcmcia
hang and had to hit reset), so it is possible that it lost it during that - but lets see if anyone else sees it.

(I fixed it by purging and then reinstalling openssh-server).

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 38921] Breezy->dapper upgrade missing /var/run/sshd

Did you let it write its new configuration files during upgrade or did
you choose to keep the old ones?

Revision history for this message
Colin Watson (cjwatson) wrote :

For the record I don't think Dennis' question is relevant here; nothing interesting with respect to this bug has changed in the default configuration.

I'm wondering if something is wonky in the sysvinit upgrade process such that /var/run goes missing for a while.

Revision history for this message
Colin Watson (cjwatson) wrote :

Marking as Confirmed; this seems like a real issue to me, since I've now had several reports of it.

Changed in openssh:
status: Unconfirmed → Confirmed
Changed in openssh:
assignee: nobody → keybuk
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I'm fairly sure it never actually asked me about config file versions for this package

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please attach the /etc/init.d/ssh file from your machine

Changed in openssh:
status: Confirmed → Needs Info
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote : /etc/init.d/ssh

as requested:
  /etc/init.d/ssh

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

I just realised that you've purged and reinstalled openssh-server

Unfortunately this means all the evidence we need has been lost, so there's nothing else I can but reject this bug until someone else has the problem (we've not heard of a single one yet) simply because it's untraceable

Changed in openssh:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.