GDM导致远程登录服务器冻结。 (超过5,000名用户)

Modified on: Sat, 09 Jun 2018 14:59:23 +0800

我在我工作的公司运行一个ubuntu FTP服务器,最近我们将超过5,000个客户迁移到它。我为每个客户创建了一个被监禁的用户/主文件夹,一切都运行顺畅,直到我安装的其中一个软件包需要重新启动系统......然后一切都崩溃了。

gui现在在登录屏幕之前冻结。我能够通过putty远程SSH到服务器,因此尝试通过命令隐藏用户:

sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type Boolean --set /apps/gdm/simple-greeter/disable_user_list True

然后再次重启服务器,但无济于事。

我们现在落后客户记录2天了,我急需帮助!我的生活(和工作)取决于这个严重问题的解决方案......

P.S。 - 我已经考虑过只是启动bash,但是我的老板告诉我,如果他想进入服务器手动进行任何更改,我需要提供GUI,所以很遗憾bash-boot是不是一种选择。


其他信息:

  

来自:cat /var/log/apt/history.log

Start-Date: 2011-05-16  15:51:35
Install: sysinfo (0.7-3ubuntu1)
End-Date: 2011-05-16  15:51:41

Start-Date: 2011-05-16  15:52:20
Remove: sysinfo (0.7-3ubuntu1)
End-Date: 2011-05-16  15:52:22

Start-Date: 2011-05-18  07:51:42
Upgrade: apturl-common (0.4.1ubuntu4, 0.4.1ubuntu4.1), apturl (0.4.1ubuntu4, 0.4.1ubuntu4.1)
End-Date: 2011-05-18  07:51:53

Start-Date: 2011-05-18  10:19:47
Install: linux-headers-2.6.32-31 (2.6.32-31.61), linux-headers-2.6.32-31-generic (2.6.32-31.61), linux-image-2.6.32-31-generic (2.6.32-31.61)
Upgrade: linux-headers-generic (2.6.32.30.36, 2.6.32.31.37), eclipse-rcp (3.5.2-2ubuntu4.2, 3.5.2-2ubuntu4.3), linux-image-generic (2.6.32.30.36, 2.6.32.31.37), apt-transport-https (0.7.25.3ubuntu9.3, 0.7.25.3ubuntu9.4), eclipse-platform-data (3.5.2-2ubuntu4.2, 3.5.2-2ubuntu4.3), apt-utils (0.7.25.3ubuntu9.3, 0.7.25.3ubuntu9.4), apt (0.7.25.3ubuntu9.3, 0.7.25.3ubuntu9.4), libequinox-osgi-java (3.5.2-2ubuntu4.2, 3.5.2-2ubuntu4.3), gdm (2.30.2.is.2.30.0-0ubuntu5.1, 2.30.2.is.2.30.0-0ubuntu5.2), xdg-utils (1.0.2-6.1ubuntu3, 1.0.2-6.1ubuntu3.1), eclipse-platform (3.5.2-2ubuntu4.2, 3.5.2-2ubuntu4.3), linux-generic (2.6.32.30.36, 2.6.32.31.37)
  

操作系统类型:

Linux FTP 2.6.32-31-generic #61-Ubuntu SMP Fri Apr 8 18:24:35 UTC 2011 i686 GNU/Linux
  

奇怪的错误:

Buffer I/O error on device sdb, logical block 96
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: BMDMA stat 0x25
ata4.00: failed comand: READ DMA
ata4.00: cmd c8/00:08:00:03:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:08:03:00/00:00:00:00:00/e0 Emask 0x9 (media error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
end_request: I/O error, dev sdb, sector 784
作者:,Jason

最佳答案

哇,这对我来说是新的。我并不确定GUI实际上能为您提供任何使用文本模式登录无法获得的功能(与普遍认为相反,您不需要学习vi.Nano非常容易使用)。所以,我建议从服务器中删除GUI作为一个简单的修复。然而,这无疑是一个有趣的问题。

1)您应该将此报告为gdm中的错误。它是一个边缘情况,但GDM应该处理得好。我可以想象一个大学共享工作站,系统有10,000个可能的用户.. gdm应该不显示选择器。运行'ubuntu-bug gdm'打开错误报告。

2)编辑/etc/gdm/gdm.schemas并更改

<schema> <key>greeter/IncludeAll</key> <signature>b</signature> <default>true</default> </schema>

<schema> <key>greeter/IncludeAll</key> <signature>b</signature> <default>false</default> </schema>

然后,如果您仍想为本地用户选择

<schema> <key>greeter/Include</key> <signature>s</signature> <default></default> </schema>

<schema> <key>greeter/Include</key> <signature>s</signature> <default>user1,user2,user3</default> </schema>

作者:SpamapS

相关问答

添加新评论