作者 主題: Centos v4.6 ldap啟動問題  (閱讀 6569 次)

0 會員 與 1 訪客 正在閱讀本文。

aerocat

  • 可愛的小學生
  • *
  • 文章數: 23
    • 檢視個人資料
Centos v4.6 ldap啟動問題
« 於: 2008-01-10 21:44 »
最近準備升到Centos v4.6 所以先裝了一台起來測試,

發現如果啟動openldap後,再加上Authentication Configuration 中 "User Information" enable "Use LDAP,
 
代碼: [選擇]
 
│                     
 |  [ ] Cache Information   [*] Use MD5 Passwords          │                     
│  [ ] Use Hesiod             [*] Use Shadow Passwords      │                     
│  [*] Use LDAP              [*] Use LDAP Authentication    │                     
│  [ ] Use NIS                 [ ] Use Kerberos                     │                     
│  [ ] Use Winbind            [ ] Use SMB Authentication      │                     
│                                  [ ] Use Winbind Authentication   │                     
│                                  [*] Local authorization is sufficient  │                     
│                                                                 │ 


boot過程中在兩個程序會花很多時間,
一個是NFS statd ----3min以上
一個是slapd ----- 3min以上, 主要是checking the configuration file for slapd 花很久時間。

(註)若僅右邊Authentication enable 不會這樣。

進入系統後,ldap運作是正常的,但是如果手動stop ldap 再啟動也是一樣在checking the configuration file for slapd 會停很久。

上線中的電腦 Centos v4.5 則沒有這種現象,
Centos v4.5
openldap-servers-sql-2.2.13-7.4E
openldap-2.2.13-7.4E
openldap-clients-2.2.13-7.4E
openldap-devel-2.2.13-7.4E
openldap-servers-2.2.13-7.4E

Centos v4.6 (已經更新到最新patch,可能非原v4.6 package)
compat-openldap-2.1.30-8.el4_6.2       
openldap-2.2.13-8.el4_6.2               
openldap-clients-2.2.13-8.el4_6.2     
openldap-devel-2.2.13-8.el4_6.2               
openldap-servers-2.2.13-8.el4_6.2         
openldap-servers-sql-2.2.13-8.el4_6.2


有人知道問題出在哪裡嗎?
« 上次編輯: 2008-01-10 21:49 由 aerocat »

aerocat

  • 可愛的小學生
  • *
  • 文章數: 23
    • 檢視個人資料
回覆: Centos v4.6 ldap啟動問題
« 回覆 #1 於: 2008-01-12 18:46 »
debug 2天,找不到原因,
上centos網站,好像也沒人反映有類似問題,
只知道v4.6 的 openldap跟samba 搭配有問題,
但我沒有使用samba,也檢查過所有設定,看不出哪裡有問題。



補上 boot.log
Jan 12 17:56:44 linux syslog: syslogd startup succeeded
Jan 12 17:56:44 linux syslog: klogd startup succeeded
Jan 12 17:56:44 linux irqbalance: Can't balance irqs on a uniprocessor system:  failed
Jan 12 17:56:44 linux portmap: portmap startup succeeded
Jan 13 01:56:00 linux rc.sysinit: -e
Jan 12 17:55:58 linux date: Sat Jan 12 17:55:58 CST 2008
Jan 12 17:55:58 linux rc.sysinit: Setting clock  (localtime): Sat Jan 12 17:55:58 CST 2008 succeeded
Jan 12 17:56:01 linux start_udev: Starting udev:  succeeded
Jan 12 17:56:13 linux rc.sysinit: -e
Jan 12 17:56:25 linux sysctl: net.ipv4.ip_forward = 0
Jan 12 17:56:25 linux sysctl: net.ipv4.conf.default.rp_filter = 1
Jan 12 17:56:25 linux sysctl: net.ipv4.conf.default.accept_source_route = 0
Jan 12 17:56:25 linux sysctl: kernel.sysrq = 0
Jan 12 17:56:25 linux sysctl: kernel.core_uses_pid = 1
Jan 12 17:56:25 linux rc.sysinit: Configuring kernel parameters:  succeeded
Jan 12 17:56:25 linux rc.sysinit: Loading default keymap succeeded
Jan 12 17:56:25 linux rc.sysinit: Setting hostname linux:  succeeded
Jan 12 17:56:25 linux rc.sysinit: Checking root filesystem succeeded
Jan 12 17:56:25 linux rc.sysinit: Remounting root filesystem in read-write mode:  succeeded
Jan 12 17:56:26 linux lvm.static:   2 logical volume(s) in volume group VolGroup00 now active
Jan 12 17:56:26 linux rc.sysinit: Setting up Logical Volume Management: succeeded
Jan 12 17:56:26 linux rc.sysinit: Checking filesystems succeeded
Jan 12 17:56:26 linux rc.sysinit: Mounting local filesystems:  succeeded
Jan 12 17:56:26 linux rc.sysinit: Enabling local filesystem quotas:  succeeded
Jan 12 17:56:27 linux rc.sysinit: Enabling swap space:  succeeded
Jan 12 17:56:27 linux microcode_ctl: microcode_ctl startup succeeded
Jan 12 17:56:28 linux vgchange:   2 logical volume(s) in volume group "VolGroup00" monitored
Jan 12 17:56:28 linux lvm2-monitor: Starting monitoring for VG VolGroup00: succeeded
Jan 12 17:56:28 linux readahead_early: Starting background readahead:
Jan 12 17:56:28 linux rc: Starting readahead_early:  succeeded
Jan 12 17:56:38 linux kudzu:  succeeded
Jan 12 17:56:38 linux rc: Starting openibd:  succeeded
Jan 12 17:56:39 linux rc: Starting pcmcia:  succeeded
Jan 12 17:56:39 linux sysctl: net.ipv4.ip_forward = 0
Jan 12 17:56:39 linux sysctl: net.ipv4.conf.default.rp_filter = 1
Jan 12 17:56:39 linux sysctl: net.ipv4.conf.default.accept_source_route = 0
Jan 12 17:56:39 linux sysctl: kernel.sysrq = 0
Jan 12 17:56:39 linux sysctl: kernel.core_uses_pid = 1
Jan 12 17:56:39 linux network: Setting network parameters:  succeeded
Jan 12 17:56:39 linux network: Bringing up loopback interface:  succeeded
Jan 12 17:56:44 linux network: Bringing up interface eth0:  succeeded
Jan 12 17:58:44 linux nfslock: rpc.statd startup succeeded

Jan 12 17:58:45 linux rpcidmapd: rpc.idmapd startup succeeded
Jan 12 17:58:45 linux netfs: Mounting other filesystems:  succeeded
Jan 12 17:58:45 linux autofs5: Load autofs4 succeeded
Jan 12 17:58:45 linux autofs5: automount5 startup failed
Jan 12 18:00:46 linux runuser: config file testing succeeded
Jan 12 18:00:46 linux ldap: Checking configuration files for slapd:  succeeded
Jan 12 18:02:46 linux ldap: slapd startup succeeded

Jan 12 18:02:47 linux smartd: smartd startup succeeded
Jan 12 18:02:47 linux acpid: acpid startup succeeded
Jan 12 18:02:49 linux cups: cupsd startup succeeded
Jan 12 18:02:49 linux sshd:  succeeded
Jan 12 18:02:49 linux xinetd: xinetd startup succeeded
Jan 12 18:02:49 linux vsftpd: vsftpd vsftpd succeeded
Jan 12 18:02:51 linux mysqld: Starting MySQL:  succeeded
Jan 12 18:02:52 linux cyrus-imapd: cyrus-master startup succeeded
Jan 12 18:02:52 linux dovecot: dovecot startup succeeded
Jan 12 18:02:53 linux gpm: gpm startup succeeded
Jan 12 18:02:54 linux httpd: httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Jan 12 18:02:55 linux httpd: httpd startup succeeded
Jan 12 18:02:55 linux crond: crond startup succeeded
Jan 12 18:02:57 linux xfs: xfs startup succeeded
Jan 12 18:02:57 linux anacron: anacron startup succeeded
Jan 12 18:02:57 linux atd: atd startup succeeded
Jan 12 18:02:57 linux saslauthd: saslauthd startup succeeded
Jan 12 18:02:57 linux readahead: Starting background readahead:
Jan 12 18:02:57 linux rc: Starting readahead:  succeeded
Jan 12 18:02:58 linux messagebus: messagebus startup succeeded
Jan 12 18:02:58 linux cups-config-daemon: cups-config-daemon startup succeeded
Jan 12 18:02:58 linux haldaemon: haldaemon startup succeeded
« 上次編輯: 2008-01-12 21:12 由 aerocat »

apage

  • 活潑的大學生
  • ***
  • 文章數: 337
    • 檢視個人資料
回覆: Centos v4.6 ldap啟動問題
« 回覆 #2 於: 2008-02-22 10:30 »
先假設你硬體條件相同,與軟體安裝習慣都相同,網路環境也相同

那麼就檢查一下 /etc/resolv.conf 看看
這是根據本人經驗才這樣想的,解名字解不到常常會很久沒錯.
(因為你最後還是開機成功了)

你也可以在 /etc/init.d/nfs 內適當的安插一段指令如:
ping ldap-server address or 查詢 hostname 之類的
方便找出問題的原因
我的筆記
啊,就我的筆記阿...
-----以下兩個是屍體-----
AegisHK
Aegis
eAthena屍體
eathena