| 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.
|  | | 
03-17-2006, 11:44 AM
| | Intermediate Member | |
Posts: 17
| | Invisible Messages Running the Open Source version of the server. I have a user who uses a single e-mail address from two machines, POP3 clients running Outlook Express. He is complaining about recieving duplicate messages on the two machines. Of course I asked him to check to see whether one of the clients was set to leave mail on the server.
In the meantime I logged into his account via the web client. The Inbox shows 18 new messages but only 3 are actually showing. I have changed the view from conversation to message, I have run various searches. The top mailbox shows 1-3 as if their are only three messages in the box.
So is this merely a visual artifact that I am dealing with or are these messages that the client keeps recieving duplicates of somehow stuck out in some sort of limbo? Is their a way for me to clear the mailbox contents or look at them from the shell? Has anyone else seen this? Forum searches are turning up nothing.
Thanks much
Steve | 
03-17-2006, 12:16 PM
| | Zimbra Employee | |
Posts: 4,792
| | Unread counts are cached.. You can clear this with a tomcat restart. If you can reproduce this problem that would be a big help. We've had a couple reports of unread counts being off. Most user's who report this are using POP and either the web client or another POP/IMAP client at the same or near the same time. | 
03-17-2006, 02:06 PM
| | Intermediate Member | |
Posts: 17
| | Invisible messages...begone Ok. Restarting Tomcat did fix the unread mail listing for this client, though oddly enough it seems to have created a different problem. Now when I right-click from the Admin UI on an account and select View Mail it does not work. It transfers me to the page https://myservername/zimbra/auth/ I get an "unable to connect" error.
I will contact the user and see if the duplicate message problem has been corrected as well. | 
03-17-2006, 04:02 PM
| | Intermediate Member | |
Posts: 17
| | Server now dead OK. It looks like I made a mistake when restarting tomcat because now the whole thing is dead.
Mailbox and logger will not start.
zmmailboxctl status seems to indicate that Tomcat and MySql are not running.
Not sure what would cause both the logger and the mailbox to fail.
This is a live production server though, so I need for things to be back up.
Can someone anyone tell me where to look? | 
03-17-2006, 04:15 PM
| | Zimbra Employee | |
Posts: 4,792
| | Anything in zimbra.log? What happens when you try to start it? | 
03-17-2006, 04:33 PM
| | Intermediate Member | |
Posts: 17
| | server problem Indeed....but I am not sure what it means:
2006-03-17 16:40:50,073 INFO [main] [] soap - Servlet SoapServlet starting up
2006-03-17 16:40:50,126 INFO [main] [] soap - Adding service AccountService to SoapServlet
2006-03-17 16:40:50,233 INFO [main] [] soap - Adding service MailService to SoapServlet
2006-03-17 16:40:50,428 INFO [main] [] soap - Adding service IMService to SoapServlet
2006-03-17 16:40:50,437 INFO [main] [] misc - version=3.0.0_GA_156.RHEL4 release=20060206122144 builddate=20060206-1222 buildhost=build.liquidsys.com
2006-03-17 16:40:50,440 INFO [main] [] misc - LANG environment is set to: en_US.UTF-8
2006-03-17 16:40:50,514 INFO [main] [] DbPool - Setting mysql connector property: maxActive=10
2006-03-17 16:40:50,514 INFO [main] [] misc - Setting mysql connection pool size to 10
2006-03-17 16:40:54,799 FATAL [main] [] system - Config initialization failed
com.zimbra.cs.service.ServiceException: system failure: getting database connection
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:131)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 281)
at com.zimbra.cs.util.Config.init(Config.java:69)
at com.zimbra.cs.util.Config.initConfig(Config.java:9 6)
at com.zimbra.cs.util.Config.getString(Config.java:10 8)
at com.zimbra.cs.db.Versions.checkDBVersion(Versions. java:87)
at com.zimbra.cs.db.Versions.checkVersions(Versions.j ava:82)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:89)
at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 118)
at javax.servlet.GenericServlet.init(GenericServlet.j ava:211)
at org.apache.catalina.core.StandardWrapper.loadServl et(StandardWrapper.java:1068)
at org.apache.catalina.core.StandardWrapper.load(Stan dardWrapper.java:900)
at org.apache.catalina.core.ContainerBase.addChild(Co ntainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(Sta ndardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDirec tory(HostConfig.java:909)
at org.apache.catalina.startup.HostConfig.deployDirec tories(HostConfig.java:872)
at org.apache.catalina.startup.HostConfig.deployApps( HostConfig.java:474)
at org.apache.catalina.startup.HostConfig.start(HostC onfig.java:1106)
at org.apache.catalina.startup.HostConfig.lifecycleEv ent(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLife cycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1019)
at org.apache.catalina.core.StandardHost.start(Standa rdHost.java:718)
at org.apache.catalina.core.ContainerBase.start(Conta inerBase.java:1011)
at org.apache.catalina.core.StandardEngine.start(Stan dardEngine.java:440)
at org.apache.catalina.core.StandardService.start(Sta ndardService.java:450)
at org.apache.catalina.core.StandardServer.start(Stan dardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalin a.java:537)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootst rap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:409)
Caused by: java.sql.SQLException: Server connection failure during transaction. Due to underlying exception: 'java.net.SocketException: java.net.ConnectException: Connection refused'.
** BEGIN NESTED EXCEPTION ** | 
03-17-2006, 04:39 PM
| | Intermediate Member | |
Posts: 17
| | Strange First...Kevin thanks for any help.
Ok...a little freaked out now....while typing this I did a zmcontrol status and now the mailbox is running.
Logger is still not running. zmloggerctl start yields the following:
[zimbra@membermail bin]$ ./zmloggerctl start
chmod: changing permissions of `/tmp/logswatch.out': Operation not permitted
[zimbra@membermail bin]$ Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
/opt/zimbra/logger/mysql/bin/mysqld_safe: line 332: /opt/zimbra/log/logger_mysqld.log: Permission denied
/opt/zimbra/logger/mysql/bin/mysqld_safe: line 340: /opt/zimbra/log/logger_mysqld.log: Permission denied
STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
tee: /opt/zimbra/log/logger_mysqld.log: Permission denied
060317 17:37:45 mysqld ended
tee: /opt/zimbra/log/logger_mysqld.log: Permission denied
Perhaps a clue in all that | 
03-17-2006, 04:41 PM
| | Zimbra Employee | |
Posts: 2,103
| | Why not try
zmcontrol stop
zmcontrol start | 
03-17-2006, 04:53 PM
| | Intermediate Member | |
Posts: 17
| | I have...several times. I kept getting the same result mailbox and logger would be stopped.
At this point my customers are running again, so I am wary of stopping it until the weekend officially arrives, which is a couple of more hours for you guys in California.
I get this though, if it helps, when I check zmlogger status: [zimbra@membermail bin]$ ./zmlogger status
DBI connect('database=zimbra_logger;mysql_read_default _file=/opt/zimbra/conf/my.logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock','zimbra',...) failed: Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2) at ./zmlogger line 44
DB: Can't connect to dbi:mysql:database=zimbra_logger;mysql_read_defaul t_file=/opt/zimbra/conf/my.logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock: Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)
Cannot connect to local MySql server through socket?
I am cool now as the mailbox has come back to life. But I would prefer that the logger be running, though the zimbra.log is updating. I also feel moderately queasy about the fact that I revived the mailbox but don't know how I did it. Unanswered questions are always scary. | 
03-20-2006, 09:02 AM
| | Intermediate Member | |
Posts: 17
| | Ok...with the logger still not running I tried zmcontrol stop and start. The logger still is not running.
More frightening is the fact that suddenly just this morning the MTA and Mailbox stopped working. Zmcontrol stop and start brought them back to life but it is really disturbing that they are dropping in and out of active state. I cannot watch this 24 hours a day.
The genesis of all this was me stopping and restarting Tomcat. I did that by going to /opt/zimbra/bin and executing:
tomcat stop
tomcat start
One potential problem though, I did this as root, not as zimbra.
So could that have fouled things up for me?
Also what if anything is the drawback of running without the logger? Logs seem to be being written.
Please...point me in the right direction and I will do what I can.
Thanks
Steve | | Thread Tools | Search this Thread | | | | | Display Modes | Linear Mode | | Why Join? Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.  |