baselayout : SSHD does not start at boot

[thorheimdall]

Since the last baselayout updates (now baselayout 1.12.4-r7), sshd does not start at boot anymore (/etc/init.d/sshd status -> status: stopped, no error in logs about sshd). It is in the default runlevel though:

Code: Select all

rc-update show default
...
sshd | default
...

and I can successfully start it manually :

Code: Select all

/etc/init.d/sshd start
* Service sshd starting
* Starting sshd ...
* Service sshd started

I have this problem since the multiple baselayout updates we had in previous weeks. I ran etc-update after each update of baselayout.

There are two network interfaces (eth0 = wired network, eth1 = wireless network, net.eth0 and net.eth1 are symbolic links to net.lo in /etc/init.d/), and there is always one of them "connected" at boot. Here is my rc.conf (note that I use RC_PARALLEL_STARTUP="yes" and RC_NET_STRICT_CHECKING="no"):

Code: Select all

RC_TTY_NUMBER=11

RC_PARALLEL_STARTUP="yes"
RC_INTERACTIVE="no"

RC_HOTPLUG="yes"
RC_COLDPLUG="yes"

RC_PLUG_SERVICES="!net.*"
RC_NET_STRICT_CHECKING="no"

RC_DOWN_INTERFACE="yes"
RC_VOLUME_ORDER="raid evms lvm dm"

RC_VERBOSE="yes"
RC_BOOTLOG="yes"

RC_BOOTCHART="no"
RC_USE_FSTAB="no"

RC_USE_CONFIG_PROFILE="yes"
RC_FORCE_AUTO="no"
RC_DEVICES="auto"

RC_DEVICE_TARBALL="no"
RC_SWAP_ERASE="no"

RC_RETRY_KILL="yes"
RC_RETRY_TIMEOUT=1
RC_RETRY_COUNT=5
RC_FAIL_ON_ZOMBIE="no"
RC_KILL_CHILDREN="no"
RC_WAIT_ON_START="0.1"

Idea anyone?

[garlik42]

I just tried the same combo of RC_PARALLEL_STARTUP="yes" and RC_NET_STRICT_CHECKING="no"
And things started just fine, this is a VERY slow system, and possibly there is some form of timing loop.

I would set RC_NET_STRICT_CHECKING="yes", because of the dual network interface issue.

[thorheimdall]

I would set RC_NET_STRICT_CHECKING="yes", because of the dual network interface issue.

In the "rc" file, this is what they say about the meaning of the possible values of RC_NET_STRICT_CHECKING:

Code: Select all

no - This basically means that at least one net.* service besides net.lo must be up.  This can be used by notebook users that have a wifi and a static nic, and only wants one up at any given time to have the 'net' service seen as up.

yes - For this ALL network interfaces MUST be up for the 'net' service to be considered up.

As I said, I only have one of the two interfaces connected at any given time (my computer is a laptop, either connected to a wired network or a wireless network), so it sounds to me I should use "no" for RC_NET_STRICT_CHECKING.

I use DHCP for both interfaces, so it may take some time before the connected interface is actually up. Maybe the sshd init script doesn't wait at all for the interface to be up? If it is the case, is there a way to make it wait until one interface is up (has got its IP address)? This is strange because it was working before the baselayout updates.

Someone has an idea?

[garlik42]

What happened when you tried RC_NET_STRICT_CHECKING="yes" ?

[thorheimdall]

What happened when you tried RC_NET_STRICT_CHECKING="yes" ?

It doesn't work either! I realized recently that this problem occurs for other services : netmount and ddclient. The problem seems related to this topic : [topic=494381]XDM breaks net based services in boot[/topic]

For now, I use RC_PARALLEL_STARTUP="no" (all services start properly), but I'd really like this problem solved and use parallel startup!

[thorheimdall]

bump

[desultory]

Has RC_NET_STRICT_CHECKING="none" been tried in this case?

[aries]

Hello thorheimdall

Same problem over here - baselayout-1.12.5-r2 -:
- same config as you: net.eth0 wired and .eth1 wired network.
- ntpd and sshd do not start when I use the wireless
- they both start when I use the wired network
- I can start both of them by hand
- both are added to runlevel default

In the past I had the same problem, it was solved by upgrading to baselayout-1.12.1 although I am not 100% sure it was the result of only this upgrade. (http://forums.gentoo.org/viewtopic-t-43 ... ight-.html)

I tried baselayout-1.12.4-r8 but without a positive result.

edit
Believe or not.
After this I made a reboot, it took a long time before I loggin in.
So the wireless network was up before I logged in and... ntpd and sshd were running!

It looks likes ntpd runs only if the wireless is up before login, but to be sure about this I have to run more tests
/edit

[thorheimdall]

desultory:

Has RC_NET_STRICT_CHECKING="none" been tried in this case?

All net based services start when this option is set. But it should work with the options RC_NET_STRICT_CHECKING="no" and RC_PARALLEL_STARTUP="yes" (as before the updates of baselayout)

aries:

It looks likes ntpd runs only if the wireless is up before login, but to be sure about this I have to run more tests

It seems our problem is closely related to this topic: [topic=494381]XDM breaks net based services in boot[/topic]. For some people, if XDM is in the default runlevel and parallel startup is activated (RC_PARALLEL_STARTUP="yes"), then net based services (as sshd and ntpd) don't start even if there is one network interface up and running (for RC_NET_STRICT_CHECKING="no"). I check that thread everyday in the hope they find a solution!