Running 11.4 x64, I’ve tried everything I can think of (which is not saying
a lot) but I can’t get sshd started on boot. Running /etc/init.d/sshd
starts the service manually with no problem but I really need it started on
boot.
I can’t find anything different when comparing this instance with other
similar instances where sshd does start but this instance is an update from
11.3 where sshd was not enabled and the others are all clean installs where
sshd was enabled during installation, if that makes any difference.
show?
Did you enable it with yast -> runlevels to start in runlevel 3 and 5?
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.3 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
ION | 3GB Ram
> Have you set it to start in the System Services (Runlevel)?
Set to runlevels 3 and 5. On reboot, this shows the correct runlevels but
the “running” entry is “yes*” - not started. No mention of sshd in any logs
except for those shown for when I manually start the service and when a
login is attempted.
This is getting frustrating! I’m about ready to start inserting debug
messages into the start-up scripts in /etc/init.d just see if they are even
being run.
> This is getting frustrating! I’m about ready to start inserting debug
> messages into the start-up scripts in /etc/init.d just see if they are even
> being run.
Disable run parallel for the scripts. If it works, known bug.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
> On 2011-05-21 23:43, Will Honea wrote:
>
>> This is getting frustrating! I’m about ready to start inserting debug
>> messages into the start-up scripts in /etc/init.d just see if they are
>> even being run.
>
> Disable run parallel for the scripts. If it works, known bug.
Give the man a cigar! That worked. Where do you see these little gems you
keep coming up with?
Funny that a clone installation on another drive doesn’t have the problem…
On 2011-05-22 02:17, Will Honea wrote:
> Carlos E. R. wrote:
>> Disable run parallel for the scripts. If it works, known bug.
>
> Give the man a cigar! That worked. Where do you see these little gems you
> keep coming up with?
X’-)
It happens to be a bug in which I am interested. There are many posts here
and in the mail lists, it took many people and many tests to find that trick.
However, using that trick makes boot/halt much slower.
It is “Bug 642289 - System does not boot correctly with
sysvinit-tools-2.88-15.1.x86_64.rpm or newer (blogd issue)”, which is
listed as solved.
Are you sure you installed all the updates?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
> On 2011-05-22 02:17, Will Honea wrote:
>> Carlos E. R. wrote:
>
>>> Disable run parallel for the scripts. If it works, known bug.
>>
>> Give the man a cigar! That worked. Where do you see these little gems
>> you keep coming up with?
>
> X’-)
>
> It happens to be a bug in which I am interested. There are many posts here
> and in the mail lists, it took many people and many tests to find that
> trick.
>
> However, using that trick makes boot/halt much slower.
>
>
> It is “Bug 642289 - System does not boot correctly with
> sysvinit-tools-2.88-15.1.x86_64.rpm or newer (blogd issue)”, which is
> listed as solved.
>
> Are you sure you installed all the updates?
Yep. I think I remember seeing sysvinit update come in. I’ll keep playing
and see if I may have skipped it or just not gotten it yet…
Hmmmmm I show sysvinit-tools-2.88.37.45.1 installed from the update repo.
Wonder if there was a regression? If I can confirm the behavior I’ll re-
open the bug.
On 2011-05-22 04:02, Will Honea wrote:
> Hmmmmm I show sysvinit-tools-2.88.37.45.1 installed from the update repo.
> Wonder if there was a regression? If I can confirm the behavior I’ll re-
> open the bug.
Keep us informed…
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
>
> I see no issues here in 11.4
>
>> I show sysvinit-tools-2.88.37.45.1 installed from the updateMe too
I only see it on one particular installation - that’s why I was getting so
darned frustrated trying to fix it. Just one more gremlin for Murphy’s sake
I guess. I’ve chased enough race conditions that I’m not surprised now that
Carlos pointed out the fix and I don’t reboot often enough to be bothered by
a few more seconds.