similar to: Passord change problem. (INTERNAL)

Displaying 20 results from an estimated 7000 matches similar to: "Passord change problem. (INTERNAL)"

2017 Sep 11
1
pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL)
Hi, I switched back to 2.2.27 with the same config that I am using for 2.2.32 and it work fine. Sep 11 11:49:37 imap-login: Info: Login: user=<viboge>, method=PLAIN, rip=88.89.118.45, lip=148.123.160.116, mpid=18709, TLS, session=<v7o22OZYrsdYWXYt> Sep 11 11:49:40 imap(mailuser) Session-ID v7o22OZYrsdYWXYt RemoteIP 88.89.118.45 Maildir /var/nextmail/nfs2.flex14/49/79/841 Info:
2017 Sep 11
1
pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (INTERNAL)
Hi, Here is the gdb output. Arvid GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show
2017 Sep 12
1
dovecot Digest, Vol 173, Issue 28 (INTERNAL)
Hi, I enabled rawlog. Everything seems to be OK but the dovecot-log shows a fatal error and core dump. (created a core file) Arvid Rawlog in <<< STAT >>> <<< LIST >>> <<< UIDL 1 >>> <<< UIDL >>> <<< QUIT >>> Rawlog out <<< +OK Logged in. >>> <<< +OK 22 17589388
2017 Sep 12
1
dovecot Digest, Vol 173, Issue 28 (INTERNAL)
Hi, It is quite easy. I use a client (thunderbird or windows live mail) set it up to use starttls on standard port 110. Logon and just do a list on the mailbox. The fatal error occurred when I logoff. Arvid -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of dovecot-request at dovecot.org Sent: 11. september 2017 14:57 To: dovecot at dovecot.org
2017 Sep 08
1
pop3-login core dump when using TLSSTART on version dovecot-2.2.32 (OPEN)
Hi, Pop3-login are CORE-dumping when I log on with TLSSTART, I believe the same will happen with imap-logon to, but I have not tested it yet. The TLS session is coming up and it works fine until I log off, then it's core dump. Open sslvesrion is openssl-1.0.2k. We ran dovecot-2.2.27 before we upgraded to dovecote-2.2.32, and that seems to work fine. (not core dumping) Arvid LOG Sep 05
2017 Mar 20
1
change passord sssd-client
Hi, I'm trying to migrate to samba4 and had the following issue: I have SSSD configured to authenticate users on linux machines that I get from a samba4 service through LDAP endpoint. Users are successfuly authenticated in the system, but I can't manage to change password of these users from command line. When I try to use passwd command, i got the following: Password change failed.
2002 May 07
2
--passord-file doesn't work
hello, I have this error while using --password-file= option. Any idea. Fran?ois tamtam:/etc# rsync --password-file=/etc/rsyncd.secrets backupcvs@cvs::cvs/ @ERROR: auth failed on module cvs rsync error: partial transfer (code 23) at io.c(143) . All seems OK tamtam:/etc# ls -ltr /etc/rsyncd.secrets -rw------- 1 root root 23 May 7 18:12 /etc/rsyncd.secrets
2007 Dec 18
5
querying status of worker with job_key
Hi, Is it possible to start a worker with job_key and then ask_status of that specific worker with the job_key? MiddleMan.ask_work(:worker => :auth_worker, :job_key=>''1'', :worker_method => :auth) and then MiddleMan.ask_status(:worker => :auth_worker, :job_key=>''1'') >From my testing of the new backgroundrb, asking status using job key
2005 Jun 02
2
Re: Reboots -- lsof and SIGHUP, a combination to know ...
From: Simon Perreault <nomis80 at lqt.ca> > Sure, theoretically it would be possible, but how would you restart this one? > [nomis80 at poste10-153 ~]$ sudo lsof | grep libc | grep init > init 1 root mem REG 253,0 1521500 999437 /lib/tls/libc-2.3.5.so I need to verify the post-install script for the glibc RPM, but I believe it SIGHUPs the process -- and
2013 Jun 08
1
crash/mem violation in auth_worker + 50G logs in 2.1.7
Hi, This morning I discovered what seemed to be a deliberate crash in auth_worker: Jun 7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2) Jun 7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in defaults handling. Program aborted Jun 7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc detected ***
2014 Jan 15
1
rsync -a --update resets status of newer target directories
Hi, this is a question regarding the behavior of the --update option for the recursive replication of directories. rsync 3.0.7-2 shows the following behavior on a Debian squeeze system (ext4): After running the following commands the adjusted ownership of the subdirectory /tmp/dst/sub below the target directory is overwritten and its newer modification time is reset to that of the older
1998 Oct 24
0
INTERNAL ERROR - Sig 11
I've had Samba 1.9.18p3 running on a FreeBSD 2.2.7 box at home for months without problems, but after installing 1.9.18p10 on a 2.2.7 box, with the same smb.conf (except for an IP change in the interfaces config and the Netbios server name), I keep getting the following entry in log.nmb immediately after boot: root@gw# cat log.nmb 1998/10/24 00:36:51 netbios nameserver version 1.9.18p10
2018 Mar 20
0
rsync time machine backup permissions
What is the order that rsync uses to set permissions? Time Machine directories have ACL permissions that basically prohibit making any changes of any kind. In order to make a backup of the directory, you would need to set those permissions after copying everything in the subdirectories. Is rsync smart enough to do it in that order? On 2018-03-19, at 10:44 PM, Andre Althoff via rsync <rsync
2010 Jan 07
1
LDAP_NO_SUCH_OBJECT upon new user creation in s4/OpenLDAP
Hello, on Mon, 07 Dec 2009 01:13:19 -0800 Eric Woltermann posted: > for some weeks now I am trying to set up Samba4 (alpha9) with an OpenLDAP 2.4.17 backend as an AD PDC for my XP/7 clients. It was working for some time with Samba's integrated LDAP facility, however I could not figure out how to use this database e.g. to authenticate my IMAP users against (bind-dn, port etc.). OpenLDAP
2003 Sep 16
1
SIGHUP fails to restart (3.6.1p2 -> 3.7p1)
I have the sshd daemon located at /sbin/ssh_22 in this scenario (because I have more than one daemon with separate executable images). After upgrading from 3.6.1p2 to 3.7p1, with the /sbin/ssh_22 copy replaced by mv (not by writing over the existing image), I do SIGHUP and get this message logged: Sep 16 15:07:36 vega sshd_22[22552]: Received SIGHUP; restarting. Sep 16 15:07:36 vega
2002 Jul 06
0
Samba binding to two IPs, even when specified not to
Hello. I'm running RH 7.1, with Samba 2.2.2. VERY often I get a SIGHUP to smbd and it'll dump the workgroups. I also get a "Discarding datagram from IP 216.202.200.103. Source name ROUTER<00> is one of our names" all the time also. This line FILLS my logs. I don't understand this one, because I have the interfaces line specified in smb.conf to use only the local
2018 Mar 20
4
rsync time machine backup permissions
That doesn’t work too. :-( Last login: Mon Mar 19 19:18:16 on console iMac:~ andre$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk2 on /Volumes/G-DRIVE Thunderbolt 3 (hfs, local, nodev, nosuid, journaled, noowners) iMac:~ andre$
2002 Mar 14
0
sshd signal handling
Hi, I am running into a problem with sshd. sshd is invoked by a process (say X) which sends sighup to it if there is a configuration change automatically. If user changes the configuration in quick succession then sshd gets terminated. I think the problem is that sshd installs its signal handlers after key generation is done. It takes a while for key generation (server key, I am using ssh
2014 Jul 29
2
[LLVMdev] Sanitizer test failure
I can. I've removed every other compilation flags from clang and even used GCC, with the exact same behaviour. cheers, --renato On 29 July 2014 15:15, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > OK, we can switch to SIGHUP. Could you please verify that this SIGUSR1 > behavior is not caused by MSan? > > On Tue, Jul 29, 2014 at 6:09 PM, Renato Golin
2014 Jul 29
2
[LLVMdev] Sanitizer test failure
On 29 July 2014 15:02, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > You mean replacing SIGUSR1 with SIGHUP in the test case? Weird, I > don't see how they are different. So, AFAIK, they should be identical. But I put some printfs and sleeps around and it wasn't a synchronization issue. My man page says that SIGUSR1 should terminate if there isn't a handler for