Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-05-2005, 08:29 PM
aws aws is offline
Junior Member
 
Posts: 9
Default FC3 Install and no zimbra ?

We have a fresh install of FC3 with no extras installed. Turned off sendmail also. Did a no problem install of zibra from rpms. Reboot shows:

Oct 4 20:42:08 sesame zimbra: Calling startup (sesame.wdm.com)
Oct 4 20:42:08 sesame zimbra:
Oct 4 20:42:21 sesame zimbra: perl /opt/zimbra/bin/zmmon &
Oct 4 20:42:21 sesame zimbra:
Oct 4 20:42:41 sesame zimbra: RESPONSE: (Zimbra::Mon::serviceInfo)
Oct 4 20:42:41 sesame zimbra: host
Oct 4 20:42:41 sesame zimbra: ip 209.112.191.12
Oct 4 20:42:41 sesame zimbra: name sesame.wdm.com
Oct 4 20:42:49 sesame rc: Starting zimbra: succeeded
Oct 5 18:00:54 sesame syslog: syslogd startup succeeded
Oct 5 18:00:54 sesame syslog: klogd startup succeeded
Oct 5 18:00:54 sesame irqbalance: irqbalance startup succeeded
Oct 5 18:00:55 sesame autofs: automount startup succeeded
Oct 5 18:00:56 sesame sshd: succeeded
Oct 5 18:00:56 sesame xinetd: xinetd startup succeeded
Oct 5 18:00:56 sesame crond: crond startup succeeded
Oct 5 18:00:57 sesame anacron: anacron startup succeeded
Oct 5 18:00:57 sesame atd: atd startup succeeded
Oct 5 18:00:58 sesame haldaemon: haldaemon startup succeeded
Oct 5 18:01:07 sesame zimbra: Calling startup (sesame.wdm.com)
Oct 5 18:01:07 sesame zimbra:
Oct 5 18:01:20 sesame zimbra: perl /opt/zimbra/bin/zmmon &
Oct 5 18:01:20 sesame zimbra:
Oct 5 18:01:41 sesame zimbra: RESPONSE: (Zimbra::Mon::serviceInfo)
Oct 5 18:01:41 sesame zimbra: host
Oct 5 18:01:41 sesame zimbra: ip 209.112.191.12
Oct 5 18:01:41 sesame zimbra: name sesame.wdm.com
Oct 5 18:01:51 sesame rc: Starting zimbra: succeeded
------------------------------------------------------------------------------------
If I try to post more info the forum does strike throughs :-(

Any ideas on what do next ?

-Dee

Last edited by aws; 10-05-2005 at 08:31 PM.. Reason: strike through text
Reply With Quote
  #2 (permalink)  
Old 10-05-2005, 08:51 PM
aws aws is offline
Junior Member
 
Posts: 9
Default Smtp

I forgot to post this also:

root@sesame conf]# netstat -a | grep smtp
[root@sesame conf]#

So no postfix gets started.

-Dee
Reply With Quote
  #3 (permalink)  
Old 10-05-2005, 08:56 PM
Zimbra Employee
 
Posts: 4,792
Default

Use the [CODE\] [/CODE\] (without the \) tags around log posts. It will prevent them from being altered. If you run
Code:
ps -ef
what do you get?
Reply With Quote
  #4 (permalink)  
Old 10-05-2005, 09:48 PM
aws aws is offline
Junior Member
 
Posts: 9
Default

Quote:
Originally Posted by KevinH
Use the [CODE\] [/CODE\] (without the \) tags around log posts. It will prevent them from being altered. If you run
Code:
ps -ef
what do you get?
[root@sesame zcs]# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 19:10 ? 00:00:01 init [3]
root 2 1 0 19:10 ? 00:00:00 [ksoftirqd/0]
root 3 1 0 19:10 ? 00:00:00 [events/0]
root 4 3 0 19:10 ? 00:00:00 [khelper]
root 5 3 0 19:10 ? 00:00:00 [kacpid]
root 20 3 0 19:10 ? 00:00:00 [kblockd/0]
root 21 1 0 19:10 ? 00:00:00 [khubd]
root 33 3 0 19:10 ? 00:00:00 [aio/0]
root 32 1 0 19:10 ? 00:00:00 [kswapd0]
root 105 1 0 19:10 ? 00:00:00 [kseriod]
root 172 1 0 17:59 ? 00:00:00 [scsi_eh_0]
root 173 1 0 17:59 ? 00:00:00 [ahc_dv_0]
root 185 1 0 17:59 ? 00:00:00 [scsi_eh_1]
root 186 1 0 17:59 ? 00:00:00 [ahc_dv_1]
root 193 1 0 18:00 ? 00:00:00 [kjournald]
root 1204 1 0 18:00 ? 00:00:00 udevd
root 1434 1 0 18:00 ? 00:00:00 [kjournald]
root 1435 1 0 18:00 ? 00:00:00 [kjournald]
root 1921 1 0 18:00 ? 00:00:00 syslogd -m 0
root 1925 1 0 18:00 ? 00:00:00 klogd -x
root 1978 1 0 18:00 ? 00:00:00 /usr/sbin/sshd
root 1989 1 0 18:00 ? 00:00:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
root 1999 1 0 18:00 ? 00:00:00 crond
daemon 2035 1 0 18:00 ? 00:00:00 /usr/sbin/atd
zimbra 2153 1 0 18:01 ? 00:00:00 /opt/zimbra/openldap/libexec/slapd -4 -u zimbra -h ldap://:7389/ -f /opt/zimbra/conf/slapd.conf
root 2684 1 0 18:01 ? 00:00:00 login -- root
root 2689 1 0 18:01 tty2 00:00:00 /sbin/mingetty tty2
root 2690 1 0 18:01 tty3 00:00:00 /sbin/mingetty tty3
root 2691 1 0 18:01 tty4 00:00:00 /sbin/mingetty tty4
root 2692 1 0 18:01 tty5 00:00:00 /sbin/mingetty tty5
root 2693 1 0 18:01 tty6 00:00:00 /sbin/mingetty tty6
root 3185 2684 0 18:02 tty1 00:00:00 -bash
root 3629 1978 0 18:04 ? 00:00:00 sshd: deem [priv]
deem 3631 3629 0 18:04 ? 00:00:00 sshd: deem@pts/0
deem 3632 3631 0 18:04 pts/0 00:00:00 -bash
root 3658 3632 0 18:04 pts/0 00:00:00 su
root 3659 3658 0 18:04 pts/0 00:00:00 bash
root 11119 3 0 19:38 ? 00:00:00 [pdflush]
root 11516 3 0 19:39 ? 00:00:00 [pdflush]
zimbra 11781 1 0 19:39 pts/0 00:00:00 /bin/sh /opt/zimbra/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.cnf --ledir=/opt/zimbra/
zimbra 11813 11781 0 19:39 pts/0 00:00:02 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11814 11813 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11815 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11816 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11817 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11818 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11844 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11845 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11846 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11847 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 11848 11814 0 19:39 pts/0 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --dat
zimbra 14246 1 0 19:44 pts/0 00:00:00 perl /opt/zimbra/bin/zmmon
zimbra 14265 14246 0 19:44 pts/0 00:00:00 perl /opt/zimbra/bin/zmmon
zimbra 14266 14246 0 19:44 pts/0 00:00:00 perl /opt/zimbra/bin/zmmon
root 15549 3659 0 19:46 pts/0 00:00:00 ps -ef
[root@sesame zcs]#

I saw this error also as I just did /install.sh -u and then ./install.sh :

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])

Is this the reason everything is not working correctly?

-Dee
Reply With Quote
  #5 (permalink)  
Old 10-06-2005, 07:54 AM
Zimbra Employee
 
Posts: 4,792
Default

Is that output from ps -ef *after* running install.sh -u but before running install.sh? If so you need to kill all the processes running as Zimbra. So some reason they are not stopping and will cause problems when you re-install.
Reply With Quote
  #6 (permalink)  
Old 10-06-2005, 08:49 AM
aws aws is offline
Junior Member
 
Posts: 9
Default

Quote:
Originally Posted by KevinH
Is that output from ps -ef *after* running install.sh -u but before running install.sh? If so you need to kill all the processes running as Zimbra. So some reason they are not stopping and will cause problems when you re-install.
OK, I'll try again later and then let you know. My anniversay is tomorrow so I'll out of pocket for a couple days. :-)

-Dee
Reply With Quote
  #7 (permalink)  
Old 10-06-2005, 03:20 PM
aws aws is offline
Junior Member
 
Posts: 9
Default

I killed all related processes and un-installed zimbra. The upon the fresh re-install:

nstalling packages

zimbra-core......zimbra-core-3.0.M1_21.FC3-20050920155949_.i386.rpm...done
zimbra-ldap......zimbra-ldap-3.0.M1_21.FC3-20050920155949_.i386.rpm...done
zimbra-mta......zimbra-mta-3.0.M1_21.FC3-20050920155949_.i386.rpm...done
zimbra-snmp......zimbra-snmp-3.0.M1_21.FC3-20050920155949_.i386.rpm...done
zimbra-store......zimbra-store-3.0.M1_21.FC3-20050920155949_.i386.rpm...done

Post installation configuration

Creating db...done
Setting the hostname to sesame.wdm.com...done
Setting the LDAP host to sesame.wdm.com...done
Initializing ldap...done
Creating server sesame.wdm.com...done
Creating domain sesame.wdm.com...done
Creating admin account admin@sesame.wdm.com...done
Setting smtp host to sesame.wdm.com...done
Adding sesame.wdm.com to zimbraMailHostPool in default COS...done
Initializing mta config...done
Configuring SNMP...done
Setting services on sesame.wdm.com...done
Setting up SSL...done
Starting servers...Calling GetServiceInfoRequest (sesame.wdm.com)

RESPONSE: (Zimbra::Mon::serviceInfo)
antispam
status Running
antivirus
status Running
ldap
status Running
mailbox
status Running
mta
status Running
snmp
status Stopped
host
ip 209.112.191.12
name sesame.wdm.com
done

Installation complete!

Operations logged to /tmp/install.log.11332

[root@sesame zcs]#
--------------------------------------------------------------------------------------------------
Reply With Quote
  #8 (permalink)  
Old 10-06-2005, 09:29 PM
Zimbra Employee
 
Posts: 4,792
Default

Cool! Looks like you got it. Let us know if you have any feedback or ideas for improvment.
Reply With Quote
  #9 (permalink)  
Old 10-08-2005, 07:21 PM
aws aws is offline
Junior Member
 
Posts: 9
Default

Quote:
Originally Posted by KevinH
Cool! Looks like you got it. Let us know if you have any feedback or ideas for improvment.
Thanks! I really like this package. Now I need to know if the rrdtools package is hosed.

/opt/zimbra/conf/swatchrc
[zimbra@sesame ~]$ zmcontrol status
Calling GetServiceInfoRequest (sesame.wdm.com)

RESPONSE: (Zimbra::Mon::serviceInfo)
antispam
status Running
antivirus
status Running
ldap
status Running
mailbox
status Running
mta
status Running
snmp
status Stopped
[root@sesame deem]# /tmp/swatch.out
/tmp/swatch.out: line 2: syntax error near unexpected token `('
/tmp/swatch.out: line 2: `*** swatch version 3.1.1 (pid:14431) started at Thu Oct 6 13:14:56 AKDT 2005'

I see this after a fresh re-boot:

Oct 8 17:12:47 sesame zimbra: Calling startup (sesame.wdm.com)
Oct 8 17:12:47 sesame zimbra:
Oct 8 17:15:12 sesame zimbra: perl /opt/zimbra/bin/zmmon &
Oct 8 17:15:12 sesame zimbra:
Oct 8 17:15:49 sesame zimbra: RESPONSE: (Zimbra::Mon::serviceInfo)
Oct 8 17:15:49 sesame zimbra: antispam
Oct 8 17:15:49 sesame zimbra: status Running
Oct 8 17:15:49 sesame zimbra: antivirus
Oct 8 17:15:49 sesame zimbra: status Running
Oct 8 17:15:49 sesame zimbra: ldap
Oct 8 17:15:49 sesame zimbra: status Running
Oct 8 17:15:49 sesame zimbra: mailbox
Oct 8 17:15:49 sesame zimbra: status Running
Oct 8 17:15:49 sesame zimbra: mta
Oct 8 17:15:49 sesame zimbra: status Running
Oct 8 17:15:49 sesame zimbra: snmp
Oct 8 17:15:49 sesame zimbra: status Stopped
Oct 8 17:15:49 sesame zimbra: host
Oct 8 17:15:49 sesame zimbra: ip 209.112.191.12
Oct 8 17:15:49 sesame zimbra: name sesame.wdm.com
Oct 8 17:16:02 sesame rc: Starting zimbra: failed
[root@sesame log]#

[root@sesame log]# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 17:10 ? 00:00:01 init [3]
root 2 1 0 17:10 ? 00:00:00 [ksoftirqd/0]
root 3 1 0 17:10 ? 00:00:00 [events/0]
root 4 3 0 17:10 ? 00:00:00 [khelper]
root 5 3 0 17:10 ? 00:00:00 [kacpid]
root 20 3 0 17:10 ? 00:00:00 [kblockd/0]
root 21 1 0 17:10 ? 00:00:00 [khubd]
root 30 3 0 17:10 ? 00:00:00 [pdflush]
root 31 3 0 17:10 ? 00:00:00 [pdflush]
root 33 3 0 17:10 ? 00:00:00 [aio/0]
root 32 1 0 17:10 ? 00:00:00 [kswapd0]
root 105 1 0 17:10 ? 00:00:00 [kseriod]
root 172 1 0 17:11 ? 00:00:00 [scsi_eh_0]
root 173 1 0 17:11 ? 00:00:00 [ahc_dv_0]
root 185 1 0 17:11 ? 00:00:00 [scsi_eh_1]
root 186 1 0 17:11 ? 00:00:00 [ahc_dv_1]
root 193 1 0 17:11 ? 00:00:00 [kjournald]
root 1240 1 0 17:12 ? 00:00:00 udevd
root 1397 1 0 17:12 ? 00:00:00 [kjournald]
root 1398 1 0 17:12 ? 00:00:00 [kjournald]
root 1670 1 0 17:12 ? 00:00:00 syslogd -m 0
root 1674 1 0 17:12 ? 00:00:00 klogd -x
root 1727 1 0 17:12 ? 00:00:00 /usr/sbin/sshd
root 1738 1 0 17:12 ? 00:00:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
root 1748 1 0 17:12 ? 00:00:00 crond
daemon 1765 1 0 17:12 ? 00:00:00 /usr/sbin/atd
zimbra 1898 1 0 17:12 ? 00:00:00 /opt/zimbra/openldap/libexec/slapd -4 -u zimbra -h ldap://:7389/ -f /opt/zimbra/conf/slapd.conf
zimbra 2348 1 0 17:13 ? 00:00:00 amavisd (master)
zimbra 2462 2348 0 17:13 ? 00:00:00 amavisd (virgin child)
zimbra 2463 2348 0 17:13 ? 00:00:00 amavisd (virgin child)
zimbra 2464 2348 0 17:13 ? 00:00:00 amavisd (virgin child)
zimbra 2465 2348 0 17:13 ? 00:00:00 amavisd (virgin child)
zimbra 2467 2348 0 17:13 ? 00:00:00 amavisd (virgin child)
zimbra 2688 1 0 17:13 ? 00:00:00 /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf -d --checks=12
zimbra 2697 1 0 17:13 ? 00:00:00 /opt/zimbra/clamav/sbin/clamd --config-file /opt/zimbra/conf/clamd.conf
zimbra 2828 1 0 17:13 ? 00:00:00 /usr/bin/perl /opt/zimbra/bin/zmmtaconfig
zimbra 3017 1 0 17:14 ? 00:00:00 /bin/sh /opt/zimbra/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.cnf --ledir=/opt/zimbra/my
zimbra 3070 3017 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3075 3070 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3076 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3077 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3078 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3079 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3088 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3089 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3090 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3091 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3092 3075 0 17:14 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
zimbra 3199 1 2 17:14 ? 00:00:07 /opt/zimbra/java/bin/java -client -XX:NewRatio=2 -Xms417m -Xmx417m -Djava.library.path=/opt/zimbra/lib -
zimbra 3823 1 0 17:14 ? 00:00:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -a zimbra
zimbra 3824 3823 0 17:14 ? 00:00:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -a zimbra
zimbra 3825 3823 0 17:14 ? 00:00:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -a zimbra
zimbra 3826 3823 0 17:14 ? 00:00:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -a zimbra
zimbra 3827 3823 0 17:14 ? 00:00:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -a zimbra
root 4217 1 0 17:15 ? 00:00:00 /opt/zimbra/postfix-2.2.3/libexec/master
postfix 4218 4217 0 17:15 ? 00:00:00 pickup -l -t fifo -u
postfix 4219 4217 0 17:15 ? 00:00:00 qmgr -l -t fifo -u
postfix 4220 4217 0 17:15 ? 00:00:00 smtpd -n 7075 -t inet -u
postfix 4222 4217 0 17:15 ? 00:00:00 tlsmgr -l -t unix -u
zimbra 4224 1 0 17:15 ? 00:00:00 perl /opt/zimbra/bin/zmmon
zimbra 4244 4224 0 17:15 ? 00:00:00 perl /opt/zimbra/bin/zmmon
zimbra 4245 4224 0 17:15 ? 00:00:00 perl /opt/zimbra/bin/zmmon
zimbra 4557 3075 0 17:15 ? 00:00:00 /opt/zimbra/mysql/bin/mysqld --defaults-file=/opt/zimbra/conf/my.cnf --basedir=/opt/zimbra/mysql --datad
root 5248 1 0 17:16 tty1 00:00:00 /sbin/mingetty tty1
root 5253 1 0 17:16 tty2 00:00:00 /sbin/mingetty tty2
root 5254 1 0 17:16 tty3 00:00:00 /sbin/mingetty tty3
root 5255 1 0 17:16 tty4 00:00:00 /sbin/mingetty tty4
root 5256 1 0 17:16 tty5 00:00:00 /sbin/mingetty tty5
root 5529 1 0 17:16 tty6 00:00:00 /sbin/mingetty tty6
root 5797 1727 0 17:16 ? 00:00:00 sshd: deem [priv]
deem 5799 5797 0 17:16 ? 00:00:00 sshd: deem@pts/0
deem 5800 5799 0 17:16 pts/0 00:00:00 -bash
root 5826 5800 0 17:16 pts/0 00:00:00 su
root 5827 5826 0 17:16 pts/0 00:00:00 bash
root 8557 5827 0 17:20 pts/0 00:00:00 ps -ef
[root@sesame log]#
Reply With Quote
  #10 (permalink)  
Old 10-08-2005, 07:35 PM
Zimbra Employee
 
Posts: 4,792
Default

Is is it just the stats not working? Or do you have other problems after a restart?
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.