Meltemi's questions

在Mac OS X 10.8 (Mountain Lion) 下运行的VirtualBox / Vagrant中安装 GuestAdditions 时遇到问题。我之前没有使用过 VB/Vagrant，也没有使用过 Linux，所以正在寻找一些指导......

错误！无法在 /lib/modules/2.6.32-38-server/build 或 /lib/modules/2.6.32-38-server/source 中找到内核 2.6.32-38-server 的内核头文件。

该错误可以在 shell 输出底部的上下文中找到（如下）

vagrant@lucid64:~$ sudo apt-get install dkms -y
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  fakeroot make patch
Suggested packages:
  make-doc diffutils-doc
The following NEW packages will be installed:
  dkms fakeroot make patch
0 upgraded, 4 newly installed, 0 to remove and 23 not upgraded.
Need to get 458kB of archives.
After this operation, 2,359kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main make 3.81-7ubuntu1 [166kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid/main patch 2.6-2ubuntu1 [121kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main dkms 2.1.1.2-2ubuntu1 [70.8kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ lucid/main fakeroot 1.14.4-1ubuntu1 [101kB]
Fetched 458kB in 1s (337kB/s) 
Selecting previously deselected package make.
(Reading database ... 44864 files and directories currently installed.)
Unpacking make (from .../make_3.81-7ubuntu1_amd64.deb) ...
Selecting previously deselected package patch.
Unpacking patch (from .../patch_2.6-2ubuntu1_amd64.deb) ...
Selecting previously deselected package dkms.
Unpacking dkms (from .../dkms_2.1.1.2-2ubuntu1_all.deb) ...
Selecting previously deselected package fakeroot.
Unpacking fakeroot (from .../fakeroot_1.14.4-1ubuntu1_amd64.deb) ...
Processing triggers for man-db ...
Setting up make (3.81-7ubuntu1) ...
Setting up patch (2.6-2ubuntu1) ...
Setting up dkms (2.1.1.2-2ubuntu1) ...

Setting up fakeroot (1.14.4-1ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.

vagrant@lucid64:~$ sudo vbox/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.1.18 Guest Additions for Linux.........
VirtualBox Guest Additions installer
Removing installed version 4.1.16 of VirtualBox Guest Additions...
tar: Record size = 16 blocks
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.

Building the main Guest Additions module ...fail!
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions ...done.
Installing the Window System drivers ...fail!
(Could not find the X.Org or XFree86 Window System.)

查看/var/log/vboxadd-install.log：

vagrant@lucid64:~$ cat /var/log/vboxadd-install.log
Uninstalling modules from DKMS
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxguest/4.1.18/source ->
                 /usr/src/vboxguest-4.1.18

DKMS: add Completed.

Error! Your kernel headers for kernel 2.6.32-38-server cannot be found at
/lib/modules/2.6.32-38-server/build or /lib/modules/2.6.32-38-server/source.
You can use the --kernelsourcedir option to tell DKMS where it's located, or you could install the linux-headers-2.6.32-38-server package.
Failed to install using DKMS, attempting to install without
/tmp/vbox.0/Makefile.include.header:97: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.

只是尝试 VirtualBox & Vagrant 和我的初始lucid64VM 无法解析us.archive.ubuntu.com但可以解析security.ubuntu.com，google.com和www.apple.com（但不是没有apple.com？www！？！）。

运行 VM的主机可以很好地解析us.archive.ubuntu.com以及所有其他域。

不知道发生了什么事？！？

vagrant@lucid64:~$ sudo apt-get install dkms -y
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  fakeroot make patch
Suggested packages:
  make-doc diffutils-doc
The following NEW packages will be installed:
  dkms fakeroot make patch
0 upgraded, 4 newly installed, 0 to remove and 23 not upgraded.
Need to get 458kB of archives.
After this operation, 2,359kB of additional disk space will be used.
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main make 3.81-7ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main patch 2.6-2ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main dkms 2.1.1.2-2ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Err http://us.archive.ubuntu.com/ubuntu/ lucid/main fakeroot 1.14.4-1ubuntu1
  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/m/make-dfsg/make_3.81-7ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.6-2ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/d/dkms/dkms_2.1.1.2-2ubuntu1_all.deb  Could not resolve 'us.archive.ubuntu.com'
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/f/fakeroot/fakeroot_1.14.4-1ubuntu1_amd64.deb  Could not resolve 'us.archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

香草安装。我的第一次尝试。按照部署 Rails 书中的说明进行操作。

编辑：添加/etc/resolv.conf：

vagrant@lucid64:~$ cat /etc/resolv.conf 
nameserver 10.0.2.3
domain mydomain.com
search mydomain.com

还有一些挖掘信息：

vagrant@lucid64:~$ dig us.archive.ubuntu.com
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.7.0-P1 <<>> us.archive.ubuntu.com
;; global options: +cmd
;; connection timed out; no servers could be reached

+trace但它似乎在使用标志时解析域名？！？（或者我读错了吗？）

vagrant@lucid64:~$ dig us.archive.ubuntu.com +trace

; <<>> DiG 9.7.0-P1 <<>> us.archive.ubuntu.com +trace
;; global options: +cmd
.           199183  IN  NS  d.root-servers.net.
.           199183  IN  NS  k.root-servers.net.
.           199183  IN  NS  m.root-servers.net.
.           199183  IN  NS  a.root-servers.net.
.           199183  IN  NS  j.root-servers.net.
.           199183  IN  NS  e.root-servers.net.
.           199183  IN  NS  l.root-servers.net.
.           199183  IN  NS  b.root-servers.net.
.           199183  IN  NS  f.root-servers.net.
.           199183  IN  NS  g.root-servers.net.
.           199183  IN  NS  h.root-servers.net.
.           199183  IN  NS  i.root-servers.net.
.           199183  IN  NS  c.root-servers.net.
;; Received 256 bytes from 10.0.2.3#53(10.0.2.3) in 1 ms

com.            172800  IN  NS  a.gtld-servers.net.
com.            172800  IN  NS  b.gtld-servers.net.
com.            172800  IN  NS  c.gtld-servers.net.
com.            172800  IN  NS  d.gtld-servers.net.
com.            172800  IN  NS  e.gtld-servers.net.
com.            172800  IN  NS  f.gtld-servers.net.
com.            172800  IN  NS  g.gtld-servers.net.
com.            172800  IN  NS  h.gtld-servers.net.
com.            172800  IN  NS  i.gtld-servers.net.
com.            172800  IN  NS  j.gtld-servers.net.
com.            172800  IN  NS  k.gtld-servers.net.
com.            172800  IN  NS  l.gtld-servers.net.
com.            172800  IN  NS  m.gtld-servers.net.
;; Received 499 bytes from 193.0.14.129#53(k.root-servers.net) in 191 ms

ubuntu.com.     172800  IN  NS  ns1.canonical.com.
ubuntu.com.     172800  IN  NS  ns2.canonical.com.
ubuntu.com.     172800  IN  NS  ns3.canonical.com.
;; Received 151 bytes from 192.42.93.30#53(g.gtld-servers.net) in 46 ms

us.archive.ubuntu.com.  600 IN  A   91.189.92.192
us.archive.ubuntu.com.  600 IN  A   91.189.92.193
us.archive.ubuntu.com.  600 IN  A   91.189.91.13
us.archive.ubuntu.com.  600 IN  A   91.189.91.23
us.archive.ubuntu.com.  600 IN  A   91.189.91.24
us.archive.ubuntu.com.  600 IN  A   91.189.91.25
us.archive.ubuntu.com.  600 IN  A   91.189.92.151
us.archive.ubuntu.com.  600 IN  A   91.189.92.152
us.archive.ubuntu.com.  600 IN  A   91.189.92.153
us.archive.ubuntu.com.  600 IN  A   91.189.92.154
us.archive.ubuntu.com.  600 IN  A   91.189.92.155
us.archive.ubuntu.com.  600 IN  A   91.189.92.176
us.archive.ubuntu.com.  600 IN  A   91.189.92.177
us.archive.ubuntu.com.  600 IN  A   91.189.92.179
us.archive.ubuntu.com.  600 IN  A   91.189.92.180
us.archive.ubuntu.com.  600 IN  A   91.189.92.181
us.archive.ubuntu.com.  600 IN  A   91.189.92.182
us.archive.ubuntu.com.  600 IN  A   91.189.92.183
us.archive.ubuntu.com.  600 IN  A   91.189.92.184
ubuntu.com.     172800  IN  NS  ns2.canonical.com.
ubuntu.com.     172800  IN  NS  ns3.canonical.com.
ubuntu.com.     172800  IN  NS  ns1.canonical.com.
;; Received 455 bytes from 91.189.95.3#53(ns2.canonical.com) in 183 ms

Edit2 - 更多挖掘：

vagrant@lucid64:~$ dig @10.0.2.3 security.ubuntu.com +short
91.189.92.181
91.189.92.184
91.189.92.151
91.189.92.166
vagrant@lucid64:~$ dig @10.0.2.3 us.archive.ubuntu.com
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.7.0-P1 <<>> @10.0.2.3 us.archive.ubuntu.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

有什么方法可以禁用 Lion Server 的 Wiki Server 中的 wiki？

删除一个很容易，但是如何暂时禁用一个以便以后可以复活？

我们的 Leopard Server 队列中有邮件累积，但不知道具体原因。这台机器多年来几乎不需要维护，所以我希望这里有人能发现明显的情况并为我们节省一些时间。让我知道还有什么其他信息会有帮助。服务器似乎运行正常，除了“阻塞”队列和与每个“捕获”消息相关的以下错误：

查看队列中的消息，每条消息的状态如下：

Message ID: 4213C3B8B3F
Date:       October 27, 2009 11:33:27 AM
Size:       1824
Sender:     [email protected]
Recipient(s) & Status:
----------------------
[email protected]:
    connect to 127.0.0.1[127.0.0.1]: Connection refused

在设置>中继下，我们检查了仅接受来自这些主机和网络的 SMTP 中继：

127.0.0.0/8
10.0.1.0/24 

队列中的邮件将发送给帐户在此服务器上的用户。客户端上的 Mail.app 似乎运行正常并检查服务器上的检查邮件。前段时间我们确实添加了一个虚拟域，但一段时间以来一切正常……最近才开始发生这种情况……有什么想法吗？

编辑：打开和关闭过滤器服务似乎已经解决了这个问题，除了 2 条剩余的排队消息显示“邮件传输不可用”作为错误！？！

我确定我忽略了一些事情，因为这应该是例行公事......但我想知道管理员如何设置通用帐户，如“[email protected]”和“[email protected]”？使用 OS X Server，您可以在用户的​​邮件帐户中创建别名，这些邮件将自动转发给所述用户......但我想要一个可以由多个客户端监控的单独 IMAP（或 POP）帐户。当我们只需要电子邮件时，我真的需要在我们的系统和 Open Directory 中为每个帐户创建一个完整用户吗？

我最近遇到了一个问题，即我们的 Mac 客户端（10.5 和 10.6）与 OS X 服务器（10.5）的单点登录中断。主机似乎可以在客户端和服务器上解析正向和反向。子网位于防火墙后面并使用 10.0.1.xxx。

nslookup 的初步测试似乎没问题。

我可以使用其他测试/工具吗？外部 DNS 测试网站无济于事，因为它位于防火墙后面……

谢谢

编辑：这是我所做的破坏事情......我手动删除了区域 0.0.10.in-addr.arpa 的下面的代码块。我没有 10.0.0.xxx 子网，ServerAdmin 烦人地不断添加它。没有其他方法可以摆脱它，我遵循了这个线程的建议。我想我现在的问题是 OS X Server 出于某种原因需要 10.0.0.xxx 吗？对于 Kerberos？外径？尽管收到一些服务正在运行的报告，但网络仍然不稳定！？！啊DNS，我多么爱你……

server:/etc/dns me$ more publicView.conf.apple
acl "com.apple.ServerAdmin.DNS.public" {localnets;};

//
// This is the view that is shown in Server Admin
// This is an automatically generated file.
// PLEASE DO NOT MANUALLY MODIFY THIS FILE!
// Please make your changes in the named.conf file
//

view "com.apple.ServerAdmin.DNS.public" {
//GUID=A37562D4-E056-2DA7-B4AD-3C4973C63824;

        allow-recursion {"com.apple.ServerAdmin.DNS.public";};

        zone "0.0.10.in-addr.arpa." {
                type master;
                file "db.0.0.10.in-addr.arpa.";
                allow-transfer {none;};
                allow-update {none;};
        };


        zone "domain1.com." {
                type master;
                file "db.domain1.com.";
                allow-transfer {none;};
                allow-update {none;};
        };


        zone "1.0.10.in-addr.arpa." {
                type master;
                file "db.1.0.10.in-addr.arpa.";
                allow-transfer {none;};
                allow-update {none;};
        };


        zone "domain2.com." {
                type master;
                file "db.domain2.com.";
                allow-transfer {none;};
                allow-update {none;};
        };

        zone "." {
                type hint;
                file "named.ca";
        };
        zone "localhost" IN {
                type master;
                file "localhost.zone";
                allow-update { none; };
        };

        zone "0.0.127.in-addr.arpa" IN {
                type master;
                file "named.local";
                allow-update { none; };
        };

};

用户的登录/帐户信息已被删除，并且不再列在 Mac OS X 客户端系统首选项中的“帐户”下。

他们的主文件夹仍然存在于 /Users/

任何人都知道如果我们只是创建一个具有相同名称的新用户会发生什么？它会假设用户的主文件夹吗？还是会将“1”附加到新帐户名和文件夹？

我们如何才能重新激活该用户？

谢谢您的帮助

尝试对无法从客户端登录到我们服务器的用户进行故障排除。客户端绑定到服务器，其他用户可以进行身份​​验证。

当相关用户尝试从终端登录时，ApplePasswordServer.Server.log 会显示以下内容：

Jul 26 2009 17:42:26    AUTH2: {0x473633ea7bc7fcaa0000000553400871, jeffb} DIGEST-MD5 authentication succeeded.
Jul 26 2009 17:42:26    AUTH2: {0x473633ea7bc7fcaa0000000553400871, jeffb} DIGEST-MD5 authentication succeeded.
Jul 26 2009 17:42:26    GETPOLICY: user {0x473633ea7bc7fcaa0000000553400871, jeffb}.
Jul 26 2009 17:42:31    KERBEROS-LOGIN-CHECK: user {0x473633ea7bc7fcaa0000000553400871, jeffb} is in good standing.
Jul 26 2009 17:42:31    KERBEROS-LOGIN-CHECK: user {0x473633ea7bc7fcaa0000000553400871, jeffb} authentication succeeded.
Jul 26 2009 17:42:31    AUTH2: {0x473633ea7bc7fcaa0000000553400871, jeffb} DIGEST-MD5 authentication succeeded.
Jul 26 2009 17:42:31    AUTH2: {0x473633ea7bc7fcaa0000000553400871, jeffb} DIGEST-MD5 authentication succeeded.

我们立即被踢出一个相当突然的反应：

macx42:~ weston$ ssh jeffb@xserver
Password:
Connection closed by 10.0.1.32

编辑：我们尝试使用 Workgroup Manager 更改用户密码无济于事...

编辑 2：回复评论...我确实看到 /var/log/secure.log 中记录了失败的尝试：

Jul 26 17:42:23 xserver sshd[498]: /etc/sshd_config line 70: Unsupported option KerberosGetAFSToken
Jul 26 17:42:26 xserver com.apple.SecurityServer[34]: checkpw() succeeded, creating credential for user jeffb
Jul 26 17:42:26 xserver com.apple.SecurityServer[34]: checkpw() succeeded, creating shared credential for user jeffb
Jul 26 17:42:26 xserver com.apple.SecurityServer[34]: Succeeded authorizing right system.login.tty by client /usr/sbin/sshd for au
thorization created by /usr/sbin/sshd.
Jul 26 17:42:26 xserver sshd[498]: error: PAM: User account has expired for jeffb from bigmac.demetrioi.com
Jul 26 17:42:31 xserver com.apple.SecurityServer[34]: checkpw() succeeded, creating credential for user jeffb
Jul 26 17:42:31 xserver com.apple.SecurityServer[34]: checkpw() succeeded, creating shared credential for user jeffb
Jul 26 17:42:31 xserver com.apple.SecurityServer[34]: Succeeded authorizing right system.login.tty by client /usr/sbin/sshd for au
thorization created by /usr/sbin/sshd.
Jul 26 17:42:31 xserver sshd[498]: Failed password for jeffb from 10.0.1.201 port 54698 ssh2

编辑 3 - 污垢的结果：

xserver:~ weston$ dirt -u jeffb -p ********
Call to dsGetRecordList returned count = 1 with Status : eDSNoErr : (0)

Call to checkpw(): Success

path: /LDAPv3/127.0.0.1
Username: jeffb
Password: ********
Success

在 Mac OS X Server (10.5.7) 环境中 - 我有一个用户在服务器上的网络主页无法从我们的任何客户端 Mac 登录。

他们甚至无法在本地登录到其主文件夹所在的服务器。目录域中的其他用户可以登录。我尝试使用 WGM 更改密码并确保该用户可以使用访问帐户。

有什么想法吗？