English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
Emails not working after moving to a share location
-
Good day,
We have an issue.
Over the weekend, I moved multiple mailboxes to a shared location in preparation for running in a clustered environment. A few weeks ago, I had moved a small number of mailboxes and everything was working fine, so I decided to proceed with migrating the rest.
However, this morning many of the mailboxes are not working. Outlook is failing to synchronize, and MDaemon overall seems very slow—opening the Account Manager takes longer than usual, and the User page has been stuck loading for over 10 minutes.
Is there a way to resolve this? The shared location is on the same subnet, connected via a VLAN between the servers, and using a 10G connection.Thank you
-
My initial thought is that something is causing the disk reading and writing to be very slow. MDaemon requires a lot of disk activity. If you move the folders back to the local drive does the performance return to normal?
If it does, then you'll have to try to identify the bottle neck. There are tools available that can measure the disk performance. I'd start by measuring the disk performance of the shared location from the MDaemonn server vs the disk performance of the local drives on the MDaemon server.
I'd also suggest looking at the RAID setup of the shared storage device. Typically we see issues with RAID 5 setups not being able to keep up with the disk activity.
-
Hi Arron,
The share location is using zfs in a Debian Dell server with 4 PCIe NVME Dell disks. I followed all the rules to set this up on the server, like no using a RAID controller, etc.
The mailboxes still locally seems to be fine. So you think it's a bottleneck? I will try to move back mailboxes with the issue and seems if that works.
-
That is my theory. If you can capture a series of hang dumps for mdaemon.exe while the issue is occurring, we should be able to take a look at them and verify.
Instructions for collecting the dumps can be found at https://knowledge.mdaemon.com/how-to-collect-hang-dumps. Or just open task manager, right click on MDaemon.exe and select Create Dump, wait a minute, and repeat. Please collect 3 or 4 memory dumps about 1 minute apart.
Once you have the dump files, please zip them and upload them to us at https://mdaemon.sharefile.com/r-rc3922c1eed334d4dbf5e34f0bd04ccd6
-
Arron, the system is too slow, and it's impossible to revert the changes and put the mailboxes back on the local disk. The web remote administrator is just loading, there are like 600 emails in the local queue, the account manager is stuck in updating every time I try to change a mailbox.. I do not know what to do. Should I stop all the email services, disconnect the network, and try locally from the server if I can change the users mailboxes? I could change a few, but right now is not responding. I restarted the server a few times already.
-
- Collect hang dumps so we can confirm try to confirm that MDaemon is being held up trying to read/write data.
- Stop MDaemon (They should move faster once MDaemon is trying to read/write data to the network location).
- Move the mailboxes from the network location back to the local disk using Windows Explorer or whatever tool you prefer for moving the data
- Restore a copy of the userlist.dat file from before you changed to storing the mailboxes on the network. If you don't have a backup, first make a backup of the file. Then you can edit the userlist.dat file and change the maildir values using a tool such as notepad.exe or your favorite text editor. The userlist.dat file is space delimited, you must very careful to maintain the correct spacing. Here is an article that documents the format of the file.
https://knowledge.mdaemon.com/mdaemon-userlist-database-format
Here is an example of what it will look like:
Here is an example of what it should look like after changing the Arron account back to the local drive.
Notice that even though the length of the maildir value changed for Arron the spacing is maintained. Every column needs to line up, if it doesn't, add/remove spaces where necessary.
Until you are comfortable with it, I'd suggest editing each line individually so that you can see the spacing is correct and the columns for the row you are editing line up with the columns of the rows you have not altered. If you do a find and replace on everything and the spacing is not correct, it will be harder to get everything back into the correct location.
Once you've made the changes and moved the mailboxes restart MDaemon.
-
Hello Arron,
I was able to revert the changes and move the mailboxes back to the server using the userlist.dat file. Everything seems to be working again.
Unfortunately, the server deleted the dump files. I had created six, but they were gone after the reboot. There also appears to be a bottleneck with the shared folders — I’ll investigate further to identify the source.By the way, we paid for priority support yesterday, but no one answered the phone. After five minutes, a recording stated that no one was available. We also haven’t received any email response from MDaemon support.
I really appreciate your quick help on this matter.
Thank you!
-
I'm glad you were able to revert the changes and get everything working again.
Sorry, sometimes our support team gets busy. If everyone is on a call you should be given the option to leave a voicemail, so that we can call you back. Were you given an option to leave a voicemail? Did you?
Our CRM solution shows the support team responded to your email yesterday. Please check your spam folder and mail server logs. It is possible delivery was delayed our routed to a backup MX if your server was offline.
-
Yes, I got the option to leave a voicemail, but I did not leave anything, hoping I would be reached by someone else.
I saw that Tyler sent me an email; it arrived at 3:00 pm, probably because of the email issues.
Thank you
-
Sorry, we typically do not try to return calls that don't leave a voicemail. We'll look into making adjustments to our systems to help in the future.
Thank you!
