LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-07-2016, 12:22 PM   #1
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,403

Rep: Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018
NFS/NIS: startup hangs at "Starting system message bus..." after switching server hardware


Hi,

I'm currently facing a really annoying problem. Our local school just bought two brand-new HP servers, in replacement of the old Dell servers we had here. Servers are running Slackware64 14.1, all desktop clients are running Slackware 14.1 32-bit.

On the old main server, I had a NIS+NFS setup with central authentication, which has been working flawlessly for a few years. I just replaced the hardware, reinstalled the server and copied over the exact same configuration. Same hostname, same network configuration, everything is exactly the same. Only when I start a client, startup get stuck a very long time at this message:

Code:
Starting system message bus..."
After a very long time, it eventually resumes booting, but I can't really login. Well, I can (sort of) log in as root, which takes almost a minute to get to a password prompt, that is, if it doesn't time out.

I'm completely clueless as to what can cause this error. Plus, I'm in a mild panic, because the whole network should be up again tomorrow morning, so I'm facing a bit of a countdown.

Any suggestions?

Niki
 
Old 06-07-2016, 12:27 PM   #2
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,000

Rep: Reputation: Disabled
when I had similar issues they were always related by:
- non-working/reachable nfs mounts in /etc/fstab
- nis server not responding
it can be also related by a network misconfiguration of the client/server.

this might help.

Last edited by ponce; 06-07-2016 at 12:37 PM.
 
1 members found this post helpful.
Old 06-07-2016, 03:51 PM   #3
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,403

Original Poster
Rep: Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018
I tried various scenarios, but to no avail. It's a mystery, and I'm pulling my hair out.
 
Old 06-07-2016, 04:00 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,464

Rep: Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808Reputation: 1808
ethtool on the interfaces. There may be a mismatch between what the interfaces believe they should use to talk to each other. You'll get tons of dropped packets that way.
 
Old 06-08-2016, 04:35 AM   #5
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Brú na Bóinne, IE
Distribution: Slackware, NetBSD
Posts: 1,620

Rep: Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119Reputation: 1119
Did you update the NICs in your iptables script?

Edit: sorry - ignore that. Wasn't thinking.

Last edited by Gerard Lally; 06-08-2016 at 07:31 AM.
 
Old 06-08-2016, 09:00 AM   #6
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Tumbleweed, Fedora, Slackware64-current
Posts: 489

Rep: Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743
Looks like your NIS doesn't work. D-Bus hangs because it switches to messagebus user and nss tries to connect the yp server.

On the new server check again if the stuff in /etc/ and /var/yp is identical to the old server (passwd shadow etc..). Did you run the makefile in /var/yp. May be you forgot /etc/defaultdomain. Is /etc/rc.d/rc.yp executable.

On a client replace /etc/nsswich.conf by the default no-NIS. This will allow you to login as root without delay.

Can you ping your server from your client

Cheers
 
1 members found this post helpful.
Old 06-08-2016, 09:17 AM   #7
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,403

Original Poster
Rep: Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018
Quote:
Originally Posted by ivandi View Post
Looks like your NIS doesn't work. D-Bus hangs because it switches to messagebus user and nss tries to connect the yp server.

On the new server check again if the stuff in /etc/ and /var/yp is identical to the old server (passwd shadow etc..). Did you run the makefile in /var/yp. May be you forgot /etc/defaultdomain. Is /etc/rc.d/rc.yp executable.

On a client replace /etc/nsswich.conf by the default no-NIS. This will allow you to login as root without delay.

Can you ping your server from your client

Cheers
Thanks for your detailed suggestions. This morning I started everything from scratch with a clean head, and everything works perfectly now.

Cheers,

Niki
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora 16 hangs during startup during "Started NFS file locking service" CGBS Linux - Newbie 1 02-29-2012 07:03 PM
Starting system message bus :dbus --ldap client hangs at this stage sarajevo Linux - Server 1 02-05-2010 01:03 PM
NFS Locking problem: starting "rpc.statd " gives error message opmetc Linux - Networking 2 11-16-2009 02:58 AM
FC5- System Stops at "Starting System Message BUS " athreyavc Linux - Hardware 5 08-19-2007 11:46 AM
"Detecting new hardware" on verbose startup and then hangs LinuxLola Linux - Newbie 1 09-04-2005 09:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration