[SOLVED] weird error in zimbra

[getridoff]

Hi Phoenix,

here is my output of ls -l /etc/syslog*

[root@mail ~]# ls -l /etc/syslog*
-rw-r--r-- 1 root root 1071 Feb 18 2010 /etc/syslog.conf
-rw-r--r-- 1 root root 1071 Feb 18 2010 /etc/syslog.conf.bak
[root@mail ~]#


anyhow i will fix the syslog as per your guide and will inform you about the result in a moment.

Thank you Phoenix.

[getridoff]

Hi Phoenix,

here is my new syslog.conf file configuration :

[root@mail ~]# cat /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;news.none;authpriv.none;cron.none /var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Log all the mail messages in one place.
mail.* -/var/log/maillog


# Log cron stuff
cron.* /var/log/cron

# Everybody gets emergency messages
*.emerg *

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log
local0.* -/var/log/zimbra.log
local1.* -/var/log/zimbra-stats.log
auth.* -/var/log/zimbra.log
mail.* -/var/log/zimbra.log
[root@mail ~]#


and the error is still there if i want to restart the syslog :

[root@mail ~]# /etc/init.d/syslog start
Starting system logger: syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[FAILED]
Starting kernel logger: klogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[FAILED]

and i have tried to yum update :

[root@mail ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* addons: centos.maulvi.net
* base: centos.maulvi.net
* extras: centos.maulvi.net
* updates: centos.maulvi.net
Setting up Update Process
No Packages marked for Update

Thanks Phoenix.

[phoenix]

Are either of the syslog (syslogd & klog) packages running? What does this show:

ps aux | grep log

[getridoff]

Hi Phoenix,

sorry for the late reply. below is the output for :

[root@mail ~]# ps aux | grep log
root 24187 0.0 0.1 3920 668 pts/1 R+ 16:14 0:00 grep log
[root@mail ~]#

i cant see any klog here..

Thank you Phoenix.

[getridoff]

Hi Phoenix,

Is there anything that i can do to overcome this issue ? It has been very very weird issue since last week, as i did not attempt to this in my previous zimbra server as well.

Waiting for your advice.

Thank you Phoenix.

[uxbod]

You could try removing syslogd and re-adding it to see whether it pulls in the necessary dependencies. What does the following show

ldd /sbin/syslogd

and does that library have a link?

ls -l /lib/libc.so.6 
lrwxrwxrwx 1 root root 11 Jan 23 03:19 /lib/libc.so.6 -> libc-2.5.so

[getridoff]

helo uxbod,

kindly apologize for my late reply, as im on leave. kindly to let you know that this problem has been solved. the reason this problem appears is one of my colleague 'stupidly' enable the firewall for the Centos machine, and this cause the error. after i have disable the firewall, all zimbra status and services becomes normal and it is receiving the mails and sending as normal, and almost real time! hats off to zimbra mail!

im hereby would like to apologize for the 'stupidity' of my colleage here, wasting a lot of energy and effors from u guys.

By the way, i just have 1 more question to ask. If i want to setup this same zimbra mail setup, using Centos machine 32 bit or 64 bit,in not NATED environment, which doesnt need to go thru the firewall, how do i go abt this?

thank you guys for all your efforts and ideas and really hats off to u guys and to zimbra as well!

zimbra rocks!!

[weigenmann]

For what it is worth.
I have had the same problem on my CentOS 5.5 x64 with Zimbra 6.05 x64.
Was using rsyslog instead of syslog.
Installed syslog and adjusted syslog.conf as suggested in this thread. Stopped rsyslog in services and also disabled it from restarting. Started syslog in services and made sure it is ticked to restart in future shutdowns.
Restart of Zimbra was then OK.