Hi, you might be running into bug 29234:
Bug 29234 – Repeated message sending on appointment cancellation
Search found 57 matches
- Mon Oct 13, 2008 6:52 pm
- Forum: Administrators
- Topic: Appointment Cancellation Notices Spam server
- Replies: 2
- Views: 780
- Mon Oct 13, 2008 11:48 am
- Forum: Developers
- Topic: SOAP application causing Alarm/Reminder not to pop up
- Replies: 1
- Views: 707
SOAP application causing Alarm/Reminder not to pop up
Hi, it's not clear without more detail, but my initial guess is that the reminder definition ( element in SOAP) is getting wiped out when your SOAP application makes an update. Do you have a SOAP request/response trace of your app doing an update?
- Mon Sep 08, 2008 12:47 pm
- Forum: Administrators
- Topic: Resource accepts even when busy
- Replies: 14
- Views: 2844
Resource accepts even when busy
This is bug 29350, fixed in ZCS 5.0.8.
- Thu Jul 31, 2008 12:24 pm
- Forum: Administrators
- Topic: Unable to get calendar item notes MIME part
- Replies: 12
- Views: 3367
Unable to get calendar item notes MIME part
You can create a new calendar folder and move all suspect appointments to that calendar. That'll get your main calendar working again. Find the offending appointment, and submit it to the support case.
- Wed Jul 30, 2008 12:16 pm
- Forum: Administrators
- Topic: Unable to get calendar item notes MIME part
- Replies: 12
- Views: 3367
Unable to get calendar item notes MIME part
Let's go for a brute force approach to find and remove the appointment containing the bad data. Get the user's mailbox id with a mysql query: mysql> select id from zimbra.mailbox where comment=''; Then go to /opt/zimbra/store/0//msg directory, and grep all files looking for "Legrand". Some...
- Tue Jul 29, 2008 12:48 pm
- Forum: Installation and Upgrade
- Topic: Failure Upgrading from 4.5.11 to 5.0.6 Open-Source
- Replies: 6
- Views: 1928
Failure Upgrading from 4.5.11 to 5.0.6 Open-Source
Errno 39 is ENOTEMPTY, directory not empty. I think it's saying you have tables in mboxgroup20 database, and you must drop the tables before dropping the database. Try: mysql> use mboxgroup20; mysql> show tables; mysql> drop table [table name]; (for each table) If that still doesn't work, shutdown m...
- Tue Jul 01, 2008 1:25 pm
- Forum: Installation and Upgrade
- Topic: Failure Upgrading from 4.5.11 to 5.0.6 Open-Source
- Replies: 6
- Views: 1928
Failure Upgrading from 4.5.11 to 5.0.6 Open-Source
Hi, the error message says the upgrade script was trying to run some SQL command against mboxgroup41.mail_item table but the table wasn't there. Either the mail_item table is missing or the mboxgroup41 database is missing. Use mysql client to check which is the case. "use mboxgroup41" comm...
- Thu Jun 26, 2008 1:31 am
- Forum: Installation and Upgrade
- Topic: Failed to switch servers
- Replies: 7
- Views: 1557
Failed to switch servers
Is there any useful info in /opt/zimbra/log/mailbox.log? zmrestoreoffline sends most of its log output there.
I believe the "No DB_CONFIG" warning is only a warnin, not a cause for restore failure.
I believe the "No DB_CONFIG" warning is only a warnin, not a cause for restore failure.
- Tue Jun 10, 2008 11:03 am
- Forum: Installation and Upgrade
- Topic: Cannot start cluster on rhel 4 with ZCS 5.0.5
- Replies: 5
- Views: 1241
Cannot start cluster on rhel 4 with ZCS 5.0.5
I'm not much familiar with up2date, but try --channel option to make sure you're refreshing the cluster suite software too. Your kernel may be newer than the kernel modules of RHCS. You can get the latest cluster suite rpms from Red Hat Network site. My test box has kernel 2.6.9-67.ELsmp, which is s...
- Tue Jun 10, 2008 3:37 am
- Forum: Administrators
- Topic: Question about redo logs and disaster recovery
- Replies: 10
- Views: 2859
Question about redo logs and disaster recovery
Then why don't you manually run an incremental backup now? Hopefully enough space will be freed up. If you don't get enough space back and must delete the logs, keep in mind your backups will be missing these logs. Restore will not be able to get all data back. The problem will become irrelevant aft...