similar to: systemd also listening on imaps port

On 20.08.2018 14:32, Kai Schaetzl wrote: > I noticed that most of the time with dovecot 2.3 I get this output, > showing systemd listening on the port as well: > > lsof -i TCP:993 > systemd 1 root 38u IPv4 3388360574 0t0 TCP *:imaps (LISTEN) > systemd 1 root 41u IPv6 3388360575 0t0 TCP *:imaps (LISTEN) > dovecot 11607 root 5u IPv4 3388360574

------------------------ Dovecot Version: ------------------------ 2.0.13 ------------------------ Output of "dovecot -n": ------------------------ # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.35-28-generic x86_64 Ubuntu 10.10 ext4 mail_location = maildir:/home/%u/Maildir passdb { args = %s driver = pam } protocols = imap pop3 ssl = no userdb { driver = passwd }

# netstat -an | grep LISTEN tcp4 0 0 *.32785 *.* LISTEN tcp4 0 0 130.238.4.133.22 *.* LISTEN What in ?@# is 32785 ?? # lsof ... sshd 11152 root 5u IPv4 0x7003ded8 0t0 TCP *:32785 (LISTEN) sshd 11152 root 6u IPv4 0x7004ded8 0t0 TCP xxx.yyy.zzz.hhh:22 (LISTEN) ... #cat /etc/sshd_config Port 22

Thanks for the information, I am unclear how to implement the winbind 'rid' backend. I've identified that winbindd is not operating on my demo server (fresh installation of Ubuntu 16), and am looking for some assistance if possible. 1] 'apt-get install winbind' informs me that the package is already installed (v4.3.9), yet it is not operating; 2] Lsof -Pnl +M -i4 provides:

Am 26.08.2018 um 20:48 schrieb TE Dukes: >> You see a basic error message "Could not connect to localhost:143". So >> test that without using additional software. Foremost consult the >> maillog, in this case the log content produced by dovecot. And test >> connectivity on the lowest level. >> >> echo QUIT | openssl s_client -connect localhost:143

On 10/14/2015 01:56 PM, Jonathan Billings wrote: > lsof /dev/log Uhmm ... that is not what I expect: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log systemd-j 263 root 5u

Hi there, when I try to start the nmbd -D daemon on my OpenServer5.0.5 box, I'll get the errormessage in log.nmbd: [...] [2002/03/12 19:30:18, 0] nmbd/nmbd.c:(783) Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/03/12 19:30:18, 0] lib/util_sock.c:(789) bind failed on port 137 socket_addr = 0.0.0.0. Error = Address already in use

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hello Rowland, I think avahi-daemon is not installed as standard in ubuntu 14.04.3 LTS Here is in our server : ROOT at SERVER:~# DPKG -L |GREP AVAHI II  LIBAVAHI-CLIENT3:AMD64              0.6.31-4UBUNTU1                  AMD64        AVAHI CLIENT LIBRARY II  LIBAVAHI-COMMON-DATA:AMD64          0.6.31-4UBUNTU1                  AMD64        AVAHI COMMON DATA FILES II 

Hi I rsync from 4 machines to a single destination one, and I am certain the filenames they sync do not overlap. But from time to time rsync from a source machine gets stuck (not always the same source machine). I followed https://rsync.samba.org/issues.html and I gathered strace, lsof and netstat when the freeze occurred. I'd like to ask for any further debug info or ideas! General info

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

I upgraded (NetBSD 2.99 i386) from 1.0rc7 to 1.0rc24 and then tried rc25, and in both cases need to restart Dovecot every day or so (low volume server). It seems to run out of file descriptors. I have now raised the file descriptor limit to 1024, but that is not a long-term solution... ... Mar 5 11:41:38 arioch dovecot: pipe() failed: Too many open files Mar 5 11:42:38 arioch

> Date: Sunday, August 26, 2018 16:25:14 -0400 > From: TE Dukes <tdukes at palmettoshopper.com> > >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of >> Alexander Dalloz >> Sent: Sunday, August 26, 2018 3:46 PM >> >> Am 26.08.2018 um 20:48 schrieb TE Dukes: >> >> You see a basic error

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

> > It's listening on both IPv6 and IPv4. Specifically, why is that a problem? The central problem seems to be that the monitoring host can't hit nrpe on port 5666 UDP. [root at monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H puppet.mydomain.com CHECK_NRPE: Socket timeout after 10 seconds. It is listening on the puppet host on port 5666 [root at puppet:~] #lsof -i :5666

Hi. I have Centos 7 (updated) running as my host, and I?m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn?t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)