-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic/fatal during imap operation #262
Comments
I'm starting to wonder if it is platform specific, as I'm seeing inconsistent behaviour building mox on the server and on my workstation. Related to that, I note the following: golang/go#35777 Building with Edit: No issues observed yet when running code built with that flag. Further investigation shows there may, in fact, be an issue with Go in certain virtualized environments, first noted in 2020. Furthermore, as the issue affects a number of non-trivial Go applications I've tested, not just mox, and affects I think you can close this or at least ignore it for now; I'm pursuing this with the Go and FreeBSD projects; will update this with any final conclusions or resolution. |
Hi @mwyvr, thanks for reporting and looking into this closer. Will be interesting to learn the cause of this, and which kinds of applications trigger this. |
An update: this is not a mox issue and can be closed, but as running mox on a VM is likely a common deployment strategy, others may run into this. The issue relates to this report on the Go project: golang/go#46272 Digging into the details, it has become clear the issue isn't specific to Go, either. A FreeBSD project contributor wrote a C program that fails memcmp tests on Vultr's VM infrastructure when running a FreeBSD guest. It does not fail on FreeBSD running on bare metal, nor on another commercial FreeBSD VMs running on typical KVM/QEMU platform. From the Go discussion:
A Reddit comment points to a possible configuration choice that Vultr, a fairly sizable commercial VM provider, may have made.
Regardless of what happens with FreeBSD on Vultr, I'm going to move my mox instance to the other FreeBSD provider late today and run it for a few days; will update with results. |
Environment: FreeBSD 14.2-RELEASE (also occurred on 14.1-RELEASE p6)
Since moving my mox installation from Linux to FreeBSD a couple weeks ago I've been noting non-fatal panics in mox logs relating to IMAP
error: invalid memory address or nil pointer dereference" pkg=imapserver cmd="uid fetch"
; the system has continued to function. I don't recall seeing these non-fatal panics before but don't have logs to verify.Over the past week the mox daemon has been killed by fatal SIGSEGV panics a number of times; they are preceded by an IMAP connection(s) that don't make it to fetch.
While I've not seen these panics on Linux; the change in platforms may be a red herring or related to moving the data. I did a backup, verifydata, backup again, etc, prior to firing up the system on the new platform.
First, a typical non-fatal panic:
And then a fatal SIGSEGV panic; this is preceded by two IMAP connections; this happens to be my device, and I have two mail accounts serviced by this mox instance:
The text was updated successfully, but these errors were encountered: