最新版はこちら。 突っ込みは各日付の BBS エントリのほか、 メール (nakano@st.seikei.ac.jp) や フォーム からどうぞ。 なおスパム除けのため、BBS 機能には 緩い認証を入れて います。 検索エンジンから来た方は、エンジンの方のキャッシュを見るか、 下の簡易検索を試してみてください。
|
Namazu for hns による簡易全文検索 詳しくは 詳細指定/ヘルプを参照して下さい |
|||||||||||||||||||||||||||||||||||||||||||||||
babaserv:/etc/apt# apt-get install apt
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apt: Depends: libc6 (>= 2.7-1) but 2.3.6.ds1-13etch9 is to be installed
Depends: libstdc++6 (>= 4.2.1) but it is not going to be installed
kernel-package: Depends: gcc but it is not going to be installed or
c-compiler
でいきなり躓く。
# apt-get install apt libc6 libstdc++6で通った。ええんかな。 その後 upgrade → dist-upgrade までは順調。ただし texlive-*-doc がデカくて強烈にウザい。 さきに --download-only してから始めるべきだった。
smbldap-useradd -a -u UID -g users -G "Domein Users" -d /home/UNAME UNAMEというような感じで追加しておく。
コンパネ→管理ツール→コンピュータの管理→ローカルユーザーとグループ→グループより "Power Users" のプロパティを開け、"BABALAB\Domain Users" を追加してあげると、だいたい良い感じになるっぽい。 なお "Administrators" には、もともと "BABALAB\Domain Admins" が登録されてるので、 samba サーバで
smbldap-groupmod -G "Domain Admins" UNAMEをしてあげれば、そのユーザはドメインの全マシンで管理者権限となる模様。 これは危険だが。
smbldap-usermod -d /home/2008home/USER USERという感じで。あと 2007 年度の人達への転送を /etc/postfix/rcpt_restrictions を編集して停止した。
ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_check. If you are unable to mount the filesystem, then use the xfs_repair -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.というメッセージ。
mount /home umount /homeしたら、カーネルログが
Apr 2 14:35:56 babaserv kernel: [95317.298208] XFS mounting filesystem sdb1
Apr 2 14:35:56 babaserv kernel: [95317.469678] Starting XFS recovery on filesystem: sdb1 (logdev: internal)
Apr 2 14:35:56 babaserv kernel: [95317.959008] Ending XFS recovery on filesystem: sdb1 (logdev: internal)
Apr 2 14:37:02 babaserv kernel: [95387.450012] mptscsih: ioc0: attempting task abort! (sc=ffff81002c66b840)
Apr 2 14:37:02 babaserv kernel: [95387.450012] sd 0:0:1:0: [sdb] CDB: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00
Apr 2 14:37:07 babaserv kernel: [95391.808635] mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000)
Apr 2 14:37:07 babaserv kernel: [95391.808917] mptsas: ioc0: removing sata device, channel 0, id 1, phy 1
Apr 2 14:37:07 babaserv kernel: [95391.808948] port-0:1: mptsas: ioc0: delete port (1)
Apr 2 14:37:07 babaserv kernel: [95392.058727] mptscsih: ioc0: task abort: SUCCESS (sc=ffff81002c66b840)
Apr 2 14:37:07 babaserv kernel: [95392.058805] mptscsih: ioc0: attempting target reset! (sc=ffff81002c66b840)
Apr 2 14:37:07 babaserv kernel: [95392.058837] sd 0:0:1:0: [sdb] CDB: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00
Apr 2 14:37:07 babaserv kernel: [95392.314726] mptscsih: ioc0: target reset: SUCCESS (sc=ffff81002c66b840)
Apr 2 14:37:07 babaserv kernel: [95392.314826] mptscsih: ioc0: attempting bus reset! (sc=ffff81002c66b840)
Apr 2 14:37:07 babaserv kernel: [95392.314857] sd 0:0:1:0: [sdb] CDB: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00
Apr 2 14:37:11 babaserv kernel: [95395.642725] mptscsih: ioc0: bus reset: SUCCESS (sc=ffff81002c66b840)
Apr 2 14:37:21 babaserv kernel: [95405.648291] mptscsih: ioc0: attempting host reset! (sc=ffff81002c66b840)
Apr 2 14:37:21 babaserv kernel: [95405.648327] mptbase: ioc0: Initiating recovery
Apr 2 14:38:17 babaserv kernel: [95462.461015] mptscsih: ioc0: host reset: SUCCESS (sc=ffff81002c66b840)
Apr 2 14:38:17 babaserv kernel: [95462.461055] sd 0:0:1:0: Device offlined - not ready after error recovery
Apr 2 14:38:17 babaserv kernel: [95462.461094] end_request: I/O error, dev sdb, sector 488491052
Apr 2 14:38:17 babaserv kernel: [95462.461156] I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x1d1dc7ed ("xlog_iodone") error 5 buf count 1024
Apr 2 14:38:17 babaserv kernel: [95462.461210] xfs_force_shutdown(sdb1,0x2) called from line 1026 of file fs/xfs/xfs_log.c. Return address = 0xffffffffa01abe31
Apr 2 14:38:17 babaserv kernel: [95462.461278] Filesystem "sdb1": Log I/O Error Detected. Shutting down filesystem: sdb1
Apr 2 14:38:17 babaserv kernel: [95462.461332] Please umount the filesystem, and rectify the problem(s)
Apr 2 14:38:17 babaserv kernel: [95462.465003] end_request: I/O error, dev sdb, sector 0
Apr 2 14:38:17 babaserv kernel: [95462.465003] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
Apr 2 14:38:17 babaserv kernel: [95462.465003] sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 2 14:40:41 babaserv kernel: [95616.042289] mptsas: ioc0: attaching sata device, channel 0, id 1, phy 1
Apr 2 14:40:41 babaserv kernel: [95616.049643] scsi 0:0:4:0: Direct-Access ATA WDC WD5000YS-01M 2E09 PQ: 0 ANSI: 5
Apr 2 14:40:41 babaserv kernel: [95616.050683] sd 0:0:4:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
Apr 2 14:40:41 babaserv kernel: [95616.072866] sd 0:0:4:0: [sdb] Write Protect is off
Apr 2 14:40:41 babaserv kernel: [95616.072896] sd 0:0:4:0: [sdb] Mode Sense: 73 00 00 08
Apr 2 14:40:41 babaserv kernel: [95616.074841] sd 0:0:4:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 2 14:40:41 babaserv kernel: [95616.075183] sd 0:0:4:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
Apr 2 14:40:41 babaserv kernel: [95616.084119] sd 0:0:4:0: [sdb] Write Protect is off
Apr 2 14:40:41 babaserv kernel: [95616.084146] sd 0:0:4:0: [sdb] Mode Sense: 73 00 00 08
Apr 2 14:40:41 babaserv kernel: [95616.086658] sd 0:0:4:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 2 14:40:41 babaserv kernel: [95616.086707] sdb: sdb1
Apr 2 14:40:41 babaserv kernel: [95616.108866] sd 0:0:4:0: [sdb] Attached SCSI disk
この後再び xfs_check したら同じエラーが出たので、xfs_repair してみる。
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
xfs_repair: libxfs_device_zero write failed: 入力/出力エラーです
そして sdb1 が再び見えなくなった。というわけでやっぱだめ？
Apr 2 14:56:08 babaserv kernel: [96592.004201] mptscsih: ioc0: attempting task abort! (sc=ffff81003122dd40)
Apr 2 14:56:08 babaserv kernel: [96592.004237] sd 0:0:4:0: [sdb] CDB: Write(10): 2a 00 1d 1d a2 5f 00 01 3d 00
Apr 2 14:56:13 babaserv kernel: [96596.533856] mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000)
Apr 2 14:56:13 babaserv kernel: [96596.534176] mptsas: ioc0: removing sata device, channel 0, id 1, phy 1
Apr 2 14:56:13 babaserv kernel: [96596.534208] port-0:4: mptsas: ioc0: delete port (4)
Apr 2 14:56:13 babaserv kernel: [96596.534516] sd 0:0:4:0: [sdb] Synchronizing SCSI cache
Apr 2 14:56:13 babaserv kernel: [96596.677061] mptscsih: ioc0: task abort: SUCCESS (sc=ffff81003122dd40)
Apr 2 14:56:13 babaserv kernel: [96596.677100] mptscsih: ioc0: attempting task abort! (sc=ffff81003122d840)
Apr 2 14:56:13 babaserv kernel: [96596.677130] sd 0:0:4:0: [sdb] CDB: Write(10): 2a 00 1d 1d a3 9c 00 00 c3 00
Apr 2 14:56:13 babaserv kernel: [96596.677186] mptscsih: ioc0: task abort: SUCCESS (sc=ffff81003122d840)
Apr 2 14:56:13 babaserv kernel: [96596.677222] mptscsih: ioc0: attempting target reset! (sc=ffff81003122dd40)
Apr 2 14:56:13 babaserv kernel: [96596.677251] sd 0:0:4:0: [sdb] CDB: Write(10): 2a 00 1d 1d a2 5f 00 01 3d 00
Apr 2 14:56:13 babaserv kernel: [96596.932511] mptscsih: ioc0: target reset: SUCCESS (sc=ffff81003122dd40)
Apr 2 14:56:13 babaserv kernel: [96596.932547] mptscsih: ioc0: attempting bus reset! (sc=ffff81003122dd40)
Apr 2 14:56:13 babaserv kernel: [96596.932576] sd 0:0:4:0: [sdb] CDB: Write(10): 2a 00 1d 1d a2 5f 00 01 3d 00
Apr 2 14:56:16 babaserv kernel: [96600.259770] mptscsih: ioc0: bus reset: SUCCESS (sc=ffff81003122dd40)
Apr 2 14:56:26 babaserv kernel: [96610.264858] mptscsih: ioc0: attempting host reset! (sc=ffff81003122dd40)
Apr 2 14:56:26 babaserv kernel: [96610.264894] mptbase: ioc0: Initiating recovery
Apr 2 14:56:54 babaserv kernel: [96638.083510] mptscsih: ioc0: host reset: SUCCESS (sc=ffff81003122dd40)
Apr 2 14:56:54 babaserv kernel: [96638.083550] sd 0:0:4:0: Device offlined - not ready after error recovery
Apr 2 14:56:54 babaserv kernel: [96638.083580] sd 0:0:4:0: Device offlined - not ready after error recovery
Apr 2 14:56:54 babaserv kernel: [96638.083666] sd 0:0:4:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 2 14:56:54 babaserv kernel: [96638.083726] end_request: I/O error, dev sdb, sector 488481692
Apr 2 14:56:54 babaserv kernel: [96638.083758] sd 0:0:4:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 2 14:56:54 babaserv kernel: [96638.083810] end_request: I/O error, dev sdb, sector 488481375
Apr 2 14:56:54 babaserv kernel: [96638.088833] sd 0:0:4:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
@include common-auth @include common-accountにした。今回はちゃんと ldap を見に行ってるみたいで、 ログにも変なエントリは出なくなった。
Apr 3 10:05:21 babaserv named[2828]: too many timeouts resolving 'XXXX.com/A' (in 'com'?): disabling EDNSというような大量のログが出ていたので、 こちら にあるように
server FOR.WAR.DER.SIP {
edns no;
};
を named.conf に追加した (リンク元では } の後の ; が抜けていて一度嵌まった)。
# echo 1 > /proc/sys/net/ipv4/ip_forwardにて対応。しかし openvpn 経由ではちゃんと繋がるんだな。ふーん。
# find -gid 501 /home -print 0 | xargs -0 chgrp staffというような感じで付け直し。
smbldap-usermod -C "\\babaserv\usrhome" -D "U:" -E (USER).bat (USER)というような感じで。