similar to: sub-directory 'hung' ...

Displaying 20 results from an estimated 200 matches similar to: "sub-directory 'hung' ..."

2019 Dec 16
5
Local lmtp proxy on backend server
Hi Aki, If I adapt this configuration on svr1 like this[0], should the mail not be delivered at svr2 passdb { driver = pam # [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=<n>] # [cache_key=<key>] [<service name>] #args = dovecot default_fields = proxy=y host=svr2 } passdb { driver = passwd skip = authenticated default_fields = proxy=y
2019 Dec 17
1
Local lmtp proxy on backend server
Hi Aki, you have some ingenious remark that could help? -----Original Message----- To: aki.tuomi; dovecot Subject: RE: Local lmtp proxy on backend server I am staring constantly at the same logs, this is what I get from dovecot[1]. Sendmail[2] is sending with test at svr1 maybe this overrides lmtp proxying? This is a test with a special-userdb passwd-file also having host=svr2 [1] Dec
2019 Dec 15
3
Local lmtp proxy on backend server
I receive a local mail when I do a 'mail test' on a backend svr1 with this[0] configuration. However when I just add only one configuration change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect this email to still be delivered locally, should this be working or do I misunderstand the lmtp proxy functionality? [0] passdb { args = auth_verbose = default
2019 Dec 16
1
Local lmtp proxy on backend server
I added this: passdb { driver = passwd skip = authenticated } Which enables indeed local delivery, I also noticed this. Maybe the password field check shoud not be done, when you enable skip authentication? Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test): lookup Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid password field '*'
2012 Apr 20
1
Upgrading from V3.0 production system to V3.3
Before I undertake this upgrade I thought I would see if anyone has any advice on how to do this on a production system. Maybe someone has already "fought this dragon". Current config Gluster V3.0.0. This has been in production for over 16 months: 2 servers with 8 x 2TB hard drives (bricks) replicated svr1:vol1 <-> srv2:vol1 -> rbrick1 svr1:vol2 <-> srv2:vol2 ->
2018 Oct 03
2
Non-matching linkedid on CDR Records [SEC=UNCLASSIFIED]
Hi asterisk-users, We have recently moved to the 13.x branch of Asterisk from 11.x, and we're trying to correlate CDR records from multiple-legs for billing purposes. As part of this change we have added 'linkedid' to our CDR table schema in an attempt to join the multiple records into one billable record. The call path can be simplified as (transport types in brackets): SIP
2017 Feb 17
7
RFC: Setting MachineInstr flags through storeRegToStackSlot
## Problem description One of the responsibilities of a target's implementation of TargetFrameLowering::emitPrologue is to set the frame pointer (if needed). Typically, the frame pointer will be stored to the stack just like the other callee-saved registers, and emitPrologue must insert the instruction to change its value after it was stored to the stack. Mips does this by looking at the
2016 Jun 12
4
scp via another server
On 06/12/2016 05:21 PM, J Martin Rushton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > $ scp svr2:/path/to/source svr1:/path/to/dest > > You'll get twice the network traffic since the copy is running on your > workstattoin (or whatever). > > On 12/06/16 15:40, H wrote: >> I normally use ssh to log into a remote server, change directory >>
2016 Jun 12
3
scp via another server
I normally use ssh to log into a remote server, change directory and then use scp from there to copy files from another remote server to the first one. Now the first server has been hit by continuous error correction messages from the ECC controller, all of which are corrected, and I am unable to get a command line to issue the required commands to change directory and then run scp from the other
2005 Oct 17
1
Redhat 9 Samba + LDAP PDC ./smbldap-populate issue
Hello Guys, I have configured samba & ldap as a domain controller before, but never on a redhat 9 system. I have updated samba & ldap as far as i can tell to the latest. Firstly I have a smaller issue (I think) I get this error when trying to restart ldap, as usual I have followed the samba howto; however it's not the documentation that is the problem more so an unusal problem or
2019 Nov 12
2
proxy dual server setup clarification
I want to migrate mail users to a new environment. If I setup a new server next to the old server, and enable proxy on both. Is this then enough to migrate user by user with the passdb host=newsvr option to the new environment? Eg. I do not need to configure a director setup? I only need to enable proxy for imap and lmtp on both servers? (messages on the oldsvr will be proxied to the
2016 Jun 12
1
scp via another server
> On Jun 12, 2016, at 11:21 AM, J Martin Rushton <martinrushton56 at btinternet.com> wrote: > > $ scp svr2:/path/to/source svr1:/path/to/dest > > You'll get twice the network traffic since the copy is running on your > workstattoin (or whatever). You probably meant: $ scp -3 svr2:/path/to/source svr1:/path/to/dest -- Jonathan Billings <billings at
2019 Dec 03
2
Live migrate with virsh migrate
When I migrate a guest from svr1 to svr2 and shutdown the guest on svr2. I cannot start it anymore because the xml is not there. How can I make sure this xml is automatically stored so I can start the guest again on svr2?
2014 Nov 22
1
usbhid-ups causes hang/crash in ohci driver
I'm experiencing a rather serious issue with the usbhid-ups driver on two different Linux systems. The symptoms on both systems are the same: After anything from a few hours to a day or two, upsd is no longer able to communicate with the UPS. upsd initially starts complaining about "data from UPS <such-and-such> is stale - check driver", then upsmon reports a loss of
2016 Jun 13
2
scp via another server
On June 12, 2016 8:51:42 PM CEST, cpolish at surewest.net wrote: >On 2016-06-12 19:07, H wrote: >> On 06/12/2016 05:21 PM, J Martin Rushton wrote: >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > $ scp svr2:/path/to/source svr1:/path/to/dest >> > >> > You'll get twice the network traffic since the copy is running
2006 Nov 16
3
STATUS_INVALID_LOCK_SEQUENCE when writing to a file....
[Note to moderator, I couldn't remember which email account I subscribed to this list from. Sorry...] Hi All, Have any of you seen this little darling of an error on writing to a file? The sequence of events goes something like this: 1) File is opened for reading on a Samba server with oplocks disabled. Open request is requesting a batch oplock. 2) File open SUCCEEDS. (Should this have
2019 Nov 30
1
dovecot: auth: Error: DNS lookup for xxx failed: Name does not resolve
I am sure resolving works fine. I tested this in a running mesos container, but also in docker run[1]. I need to have the search local option in resolve.conf. It was actually working, until I started adding the proxy for managesieve, but when I reverted, it still does not work. I think the building from cache mislead me. I suspect this is a different problem, that at some point is giving
2019 Nov 30
2
Domain XML Multicast Tunnel
Hello I found under networking in the Domain XML 'Multcast tunnel'. My question is does anyone know what is the intended use of multicast tunnel networking?What are the potential pitfalls of using such a configuration other than what's highlighted in the domain xml. eg: can it suffer from throughput issues? Can the tunnel be accessed from outside Libvirt? I'm struggling to find any
2019 Nov 30
2
dovecot: auth: Error: DNS lookup for xxx failed: Name does not resolve
I had a working container with dovecot configured as proxy. And all of a sudden I am getting these messages 'dovecot: auth: Error: DNS lookup for roosit03 failed: Name does not resolve' Pinging/nslookup these hostnames is ok
1999 Sep 01
2
sudden loss of password validation
The problem: Strangely, the PDC rejects user password challenges from Samba. The user account gets locked. After unlocking the account, everything is back to normal. This happens several times a day to different users and from different Samba servers. All Samba servers have the same [global] configuration. Is this a Samba problem? Is samba perhaps not passing along the correct password? If I add