May 24 21:15:01 node99 syslog-ng[2120]: Error resolving user; user='news'

May 24 21:15:01 node99 syslog-ng[2120]: Error resolving group; group='news'

May 24 21:15:01 node99 syslog-ng[2120]: Error resolving user; user='news'

May 24 21:15:01 node99 syslog-ng[2120]: Error resolving group; group='news'

May 24 21:15:01 node99 syslog-ng[2120]: Error resolving user; user='news'

May 24 21:15:01 node99 syslog-ng[2120]: Error resolving group; group='news'

May 24 21:15:01 node99 syslog-ng[2120]: New configuration initialized;

May 24 21:15:04 node99 logrotate: ALERT exited abnormally with [1]

May 24 21:15:04 node99 logrotate: error: fetchmail:10 unknown user 'fetchmai
l'

May 24 21:15:04 node99 logrotate: error: found error in /var/log/fetchmail ,
skipping

May 24 21:15:04 node99 logrotate: error: icecream:9 unknown user 'icecream'

May 24 21:15:04 node99 logrotate: error: found error in /var/log/iceccd /var
/log/icecc_scheduler , skipping

May 24 21:15:04 node99 logrotate: error: squid:2 unknown group 'nogroup'

May 24 21:15:04 node99 logrotate: error: found error in file squid, skipping


May 24 21:15:04 node99 logrotate: error: syslog:52 unknown user 'news'

May 24 21:15:04 node99 logrotate: error: found error in file syslog, skippin
g

May 24 21:15:04 node99 logrotate: error: "/var/lib/mysql" has insecure permi
ssions. It must be owned and be writable by root only to avoid security prob
lems. Set the "su" directive in the config file to tell logrotate which user
/group should be used for rotation.

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/zebra.log f
ailed: Permission denied

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/bgpd.log fa
iled: Permission denied

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/ospfd.log f
ailed: Permission denied

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/ospf6d.log
failed: Permission denied

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/ripd.log fa
iled: Permission denied

May 24 21:15:04 node99 logrotate: error: stat of /var/log/quagga/ripngd.log
failed: Permission denied

May 24 21:15:04 node99 logrotate: error: "/var/log/squid" has insecure permi
ssions. It must be owned and be writable by root only to avoid security prob
lems. Set the "su" directive in the config file to tell logrotate which user
/group should be used for rotation.

May 24 21:15:04 node99 logrotate: error: stat of /var/log/squid/cache.log fa
iled: No such file or directory

May 24 21:15:04 node99 logrotate: error: "/var/log/news" has insecure permis
sions. It must be owned and be writable by root only to avoid security probl
ems. Set the "su" directive in the config file to tell logrotate which user/
group should be used for rotation.

May 24 21:15:04 node99 logrotate: error: "/var/log/news" has insecure permis
sions. It must be owned and be writable by root only to avoid security probl
ems. Set the "su" directive in the config file to tell logrotate which user/
group should be used for rotation.

May 24 21:15:04 node99 logrotate: error: "/var/log/news" has insecure permis
sions. It must be owned and be writable by root only to avoid security probl
ems. Set the "su" directive in the config file to tell logrotate which user/
group should be used for rotation.


会不会被黑了？
--
FROM 1.192.36.*

想起来了，估计是我更改passwd导致的
谢谢


【 在 JulyClyde 的大作中提到: 】
: 看看nsswitch.conf和passwd文件有没有猫病
--
FROM 218.29.119.*

我直接把红帽子的覆盖了SLES的？。。。。。

一着急给忘了，两个服务器同步账户

幸亏之前保留过一份passwd，但现在发现有些账户的id是一样的，比如man账户，Redha
t里没有，SLES的有，id是13，但是Redhat里也有一个id为13的账户。

要恢复的话得重建一下各自的500一下的账户。



【 在 JulyClyde 的大作中提到: 】
: 你咋改的？
--
FROM 218.29.119.*

因为SLES那个E就是enterprise啊
【 在 iconquer 的大作中提到: 】
: 为啥SLES在企业里用的这么多。。。
--
FROM 113.108.77.*

我也很好奇
suse好像“从来没有”强势过
【 在 iconquer 的大作中提到: 】
: 这我当然知道啊，就是说选Suse的居然还不少
--
FROM 113.108.77.*