Quantcast
Channel: iRedMail — iRedMail Support
Viewing all 43333 articles
Browse latest View live
↧

Re: can't start iredadmin service

July 31, 2024, 8:17 pm
$
0
0

Reinstalled with almost entirely default settings (no sogo, kept netdata) and the service still isn't starting.

Other environmental facts:
Proxmox
Ubuntu 24.04 LXC image


This same environment is running another instance of iRedMail from a while back that started on Ubuntu 20.04 (again from a LXC image) and initially installed iRedMail 1.6.0 and upgraded over time to 1.6.8.

Even with different hostnames for the containers, I tried shutting off/removing the existing server (I just restored it on a completely different environment, tested recovery procedures for good measure!) to make sure there wasn't some strange configuration underlying the problem and that doesn't seem to be the case.

↧
Search

Re: can't start iredadmin service

July 31, 2024, 11:51 pm
$
0
0
w0k wrote:

Reinstalled with almost entirely default settings (no sogo, kept netdata) and the service still isn't starting.

Other environmental facts:
Proxmox
Ubuntu 24.04 LXC image


This same environment is running another instance of iRedMail from a while back that started on Ubuntu 20.04 (again from a LXC image) and initially installed iRedMail 1.6.0 and upgraded over time to 1.6.8.

Even with different hostnames for the containers, I tried shutting off/removing the existing server (I just restored it on a completely different environment, tested recovery procedures for good measure!) to make sure there wasn't some strange configuration underlying the problem and that doesn't seem to be the case.

the same issue here as well while ubuntu 22.04 work just fine.

↧
↧

Re: Emails arrive to inbox and then disappear

August 1, 2024, 12:32 am
$
0
0
Cthulhu wrote:
Jul 31 15:43:06 mail dovecot: imap(myUser@myDomain.com)<3607><***>: expunge: box=INBOX, uid=11, msgid=<***>, size=5659, from=email@from.com, subject=***: Arrival, flags=(\Deleted \Recent)

There it CLEARLY states that the expunge command was sent to delete the mail, and that comes from your mail client

I am struggling with a similar problem myself, I think I am lucky that I came across this issue while looking for a solution, your answer helped me.

↧

Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 1, 2024, 9:07 am
$
0
0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.8
- Deployed with iRedMail Easy or the downloadable installer? Downloadable installer
- Linux/BSD distribution name and version: Ubuntu Server 20.04.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
I am wondering why the last release of iRedMail-1.7.0 is not for Ubuntu Server 20.04 ?
As far as I see at the requirements, seems possible to upgrade  iRedMail-1.6.8 ->  iRedMail-1.7.0
No? Why what is incompatible?
Thanks

↧

Re: dovecot log: imap: Error: DETAIL: Key (username, domain) already exis

August 1, 2024, 10:09 am
$
0
0
ZhangHuangbin wrote:

Show me full log under /var/log/dovecot/dovecot.log related to this error.

ZhangHuangbin, here's another log, this time including what I believe is the associated imp log...

imap.log:

Aug  1 16:58:54 mail dovecot: imap-login: Login: user=<myUser@myDomain>, method=PLAIN, rip=clientIP, lip=serverIP, mpid=22577, TLS, TLSv1.2 with cipher cipherID (256/256 bits), session=<mzA8IKIeJfJriWvy>
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Disconnected: Logged out in=36 out=605 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Error: last_login_dict: Failed to write value: dict-server returned failure: sql dict: commit failed: ERROR:  duplicate key value violates unique constraint "last_login_pkey"

dovecot.log

Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Loading modules from directory: /usr/lib/dovecot/modules
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_last_login_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mailbox_alias_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Added userdb setting: mail=maildir:~/Maildir
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Added userdb setting: plugin/master_user=myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=524288000
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Effective uid=2000, gid=2000, home=/var/vmail/vmail1/myDomain/e/v/e/myUser-2024.07.30.18.01.20/
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: Starting transaction
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: Setting 'shared/last-login/imap/myUser@myDomain/myDomain' to '1722531534'
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: conn unix:/run/dovecot/dict: Connecting
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: conn unix:/run/dovecot/dict (pid=614,uid=0): Client connected (fd=8)
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota root: name=user backend=dict args=:proxy::quotadict
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota rule: root=user mailbox=* bytes=524288000 messages=0
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota warning: bytes=524288000 (100%) messages=0 reverse=no command=quota-warning 100 myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota warning: bytes=498073600 (95%) messages=0 reverse=no command=quota-warning 95 myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota warning: bytes=471859200 (90%) messages=0 reverse=no command=quota-warning 90 myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota warning: bytes=445644800 (85%) messages=0 reverse=no command=quota-warning 85 myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Quota grace: root=user bytes=52428800 (10%)
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: quota-dict: user=myUser@myDomain, uri=proxy::quotadict, noenforcing=0
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: maildir++: root=/var/vmail/vmail1/myDomain/e/v/e/myUser-2024.07.30.18.01.20//Maildir, index=, indexpvt=, control=, inbox=/var/vmail/vmail1/myDomain/e/v/e/myUser-2024.07.30.18.01.20//Maildir, alt=
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: initializing backend with data: vfile
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: acl username = myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: owner = 1
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl vfile: Global ACLs disabled
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/Shared/%Ld/%Ln
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: shared: root=/run/dovecot, index=, indexpvt=, control=, inbox=, alt=
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: initializing backend with data: vfile
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: acl username = myUser@myDomain
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl: owner = 0
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: acl vfile: Global ACLs disabled
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: Waiting for dict to finish pending operations
Aug  1 16:58:54 mail dovecot: imap: Error: DETAIL:  Key (username, domain)=(myUser@myDomain, myDomain) already exists. (reply took 0.058 secs (0.014 in dict wait, 0.034 in other ioloops, 0.000 in locks, async-id reply 0.038 secs ago, started on dict-server 0.041 secs ago, took 0.041 secs))
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: Dict transaction finished
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: conn unix:/run/dovecot/dict (pid=614,uid=0): Disconnected: Connection closed (fd=8)
Aug  1 16:58:54 mail dovecot: imap(myUser@myDomain)<22577><mzA8IKIeJfJriWvy>: Debug: dict(proxy)<myUser@myDomain>: Waiting for dict to finish pending operations
↧
↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 1, 2024, 5:17 pm
$
0
0

So, what problem is shown?
Hard to find out without logs

Ubuntu 20.04 is not supported, 24.04 is recommend but 22.04 works aswell

↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 1, 2024, 5:46 pm
↧

Re: dovecot log: imap: Error: DETAIL: Key (username, domain) already exis

August 1, 2024, 5:54 pm
↧
Search

Re: can't start iredadmin service

August 1, 2024, 6:31 pm
$
0
0

iRedAdmin works fine on a normal Ubuntu 24.04 OS.
It reports "socket(): Permission denied [core/socket.c line 82]", not sure whether it's a LXC issue in this case. But i don't have LXC environment for reproducing this issue.

↧
↧

Re: dovecot log: imap: Error: DETAIL: Key (username, domain) already exis

August 1, 2024, 7:35 pm
$
0
0

I cannot reproduce this issue locally (both iRedMail and iRedMail Enterprise Edition).
Is it possible to give me direct ssh access with root privilege, and a testing email account to reproduce the issue?

↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 1, 2024, 9:05 pm
$
0
0
Cthulhu wrote:

So, what problem is shown?
Hard to find out without logs

Ubuntu 20.04 is not supported, 24.04 is recommend but 22.04 works aswell

The problem is, in the announcement of the 1.7.0 release, stated that Ubuntu 20.04 is not supported, SO I ASKED the question. What logs to show? I did not tried yet because of the statement in the release announcement....

↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 1, 2024, 9:09 pm
$
0
0
ZhangHuangbin wrote:

To upgrade current iRedMail-1.6.8 server, please follow our tutorial here:
https://docs.iredmail.org/iredmail.releases.html

Dear Sir,
as four years admin in my iRedMail server installation, I very well know the indicating url for upgrading the existing installation.
My real question is : in the announcement of the 1.7.0 release, stated that Ubuntu 20.04 is not supported so can I upgrade from 1.6.8 => 1.7.0 in my installation (that is 20.04) or not ???

↧

Re: can't start iredadmin service

August 2, 2024, 8:19 am
$
0
0
ZhangHuangbin wrote:

iRedAdmin works fine on a normal Ubuntu 24.04 OS.
It reports "socket(): Permission denied [core/socket.c line 82]", not sure whether it's a LXC issue in this case. But i don't have LXC environment for reproducing this issue.

Testing on Proxmox running ubuntu 24.04 vm, iredadmin service work just fine.

↧
↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 2, 2024, 8:23 am
$
0
0
mikekgr wrote:

The problem is, in the announcement of the 1.7.0 release, stated that Ubuntu 20.04 is not supported

Ubuntu 20.04 is not supported for NEW fresh installation.
Existing Ubuntu 20.04 servers work fine as usual.

↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 2, 2024, 8:24 am
$
0
0
mikekgr wrote:

My real question is : in the announcement of the 1.7.0 release, stated that Ubuntu 20.04 is not supported so can I upgrade from 1.6.8 => 1.7.0 in my installation (that is 20.04) or not ???

Yes you can upgrade to 1.7.0 on Ubuntu 20.04.

↧
Search

Re: can't start iredadmin service

August 2, 2024, 9:01 am
$
0
0

但是我通过浏览器无法访问
报错：internal server error

↧

Re: Why iRedMail-1.7.0 does not run (upgrade) from iRedMail-1.6.8 (20.04)?

August 2, 2024, 11:01 am
$
0
0
ZhangHuangbin wrote:
mikekgr wrote:

My real question is : in the announcement of the 1.7.0 release, stated that Ubuntu 20.04 is not supported so can I upgrade from 1.6.8 => 1.7.0 in my installation (that is 20.04) or not ???

Yes you can upgrade to 1.7.0 on Ubuntu 20.04.

Many thanks !  I will upgrade tomorrow.

↧
↧

netdata connection refused after upgrade to iredmail 1.6.3

August 2, 2024, 11:10 am
$
0
0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.1
- Deployed with iRedMail Easy or the downloadable installer? not sure, just ran upgrade
- Linux/BSD distribution name and version: Debian 12.6 bookworm
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): Mariadb
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I followed the tutorial to upgrade from 1.6.1 to 1.6.3. The only error I saw during the upgrade related to iRedAdmin, however iRedAdmin is working. I upgraded to the latest available versions of netdata and Roundcube because the versions listed in the tutorial were not available.

Now when I attempt to load https://mail.my.domain I get an error 502 Bad Gateway. The nginx error.log shows this:

2024/08/02 11:56:15 [error] 701#701: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: mail.my.domain, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "127.0.0.1"

2024/08/02 11:57:00 [error] 701#701: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 104.37.148.71, server: mail.my.domain, request: "GET /mail/?_task=mail&_mbox=INBOX HTTP/2.0", upstream: "fastcgi://127.0.0.1:9999", host: "mail.my.domain", referrer: "[url]https://mail.my.domain/mail/?_task=mail&_mbox=INBOX[/url]"

2024/08/02 11:59:03 [error] 701#701: *11 connect() failed (111: Connection refused) while connecting to upstream, client: 104.37.148.71, server: mail.my.domain, request: "GET /mail/ HTTP/2.0", upstream: "fastcgi://127.0.0.1:9999", host: "mail.my.domain"

It looks to me like netdata is refusing connections on port 9999, however netstat shows otherwise:

# netstat -lntp|grep 9999
tcp        0      0 127.0.0.1:19999         0.0.0.0:*               LISTEN      580/netdata

/opt/netdata/etc/netdata.conf looks like this:

# Get config from [url]http://127.0.0.1[/url]:<netdata_port>/netdata.conf
[registry]
    # Disable public central registry and become registry locally
    enabled = yes

    # Register to internal server instead
    registry to announce = [url]http://127.0.0.1:19999[/url]

[global]
    # The number of entries the netdata daemon will by default keep in memory
    # for each chart dimension. This setting can also be configured per chart.
    history = 172800

    # memory mode
    # - `save` is the default mode, data are maintained in memory and saved to
    #          disk when netdata exits.
    # - `ram` data are exclusively on memory and never saved on disk.
    # - `map` like swap, files are mapped to memory on demand.
    #
    #         WARNING: We suggest not to use this mode on nodes that run other
    #                  applications.
    #
    # - `none` no local database (used when data are streamed to a remote netdata).
    # - `dbengine`: data are in database files.
    #               The Database Engine works like a traditional database.
    memory mode = dbengine

    #
    # dbengine.
    #
    # determines the amount of RAM in MiB that is dedicated to caching netdata
    # metric values themselves.
    page cache size = 32

    # determines the amount of disk space in MiB that is dedicated to storing
    # netdata metric values and all related metadata describing them.
    dbengine disk space = 256

    # Bind to 127.0.0.1 by default.
    bind to = 127.0.0.1
    # Bind to all available network interfaces, but allow access from specified
    # IP addresses or networks.
    #bind to = *
    #allow connections from =

    run as user = netdata
    default port = 19999

    # The frequency in seconds, for data collection.
    update every = 3

    # Log files
    # Nginx logs access log, netdata no need to log it again.
    access log = none
    #error log = syslog
    #debug log = syslog

[plugin:proc]
    # Disable IPVS check since iRedMail doesn't use ipvs by default
    /proc/net/ip_vs/stats = no

    # inbound packets dropped
    /proc/net/dev = no
↧

Re: netdata connection refused after upgrade to iredmail 1.6.3

August 2, 2024, 6:59 pm
↧

Re: can't start iredadmin service

August 2, 2024, 7:01 pm
$
0
0
welsper.jer wrote:

但是我通过浏览器无法访问
报错：internal server error

访问出错时，这几个日志文件里有什么相关错误？

/var/log/maillog
/var/log/syslog
/var/log/messages

↧
Viewing all 43333 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>