Displaying 3 results from an estimated 3 matches for "lock_tim".
Did you mean:
lock_time
2012 Jul 09
1
Timeout (180s) while waiting for lock for transaction log file
Hello,
We still have problems with our updated dovecot servers... The problem
now is that we are having errors like:
Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: Timeout
(180s) while waiting for lock for transaction log file
/var/indexes/<user>/.INBOX/dovecot.index.log
Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error:
+4YfCwKS+k9HPAAAmo+UlA:
2013 Jun 07
0
pam_tally2 reset problems with many simultaneous connections
...d with many sftp connections, you'll see
lots of logs even though everything eventually succeeds.
I'm on RHEL 5.5 with openssh-server-4.3p2-41.el5 and pam-0.99.6.2-6.el5_4.1.
I'm using pam_tally2 in the auth and account phases:
#%PAM-1.0
...
auth requisite pam_tally2.so deny=3 lock_time=10 unlock_time=900
...
account required pam_tally2.so
...
I'm guessing the problem is that sshd doesn't call pam_setcred correctly
as stated in the pam_tally2 man page:
"Account phase resets attempts counter if the user is not magic root.
This phase can be used optionally for s...
2013 Oct 08
4
'puppet storeconfigs export' killed
...fc19.noarch
I''m positive the MySQL server receives the query and returns the data,
according to MySQL''s slow-queries.log:
# Time: 131008 17:06:14
# User@Host: puppet[puppet] @ [172.20.59.127]
# Thread_id: 169 Schema: puppet Last_errno: 0 Killed: 0
# Query_time: 189.509563 Lock_time: 0.000136 Rows_sent: 6168111
Rows_examined: 12712154 Rows_affected: 0 Rows_read: 18446744073709551613
# Bytes_sent: 2426331478 Tmp_tables: 0 Tmp_disk_tables: 0
Tmp_table_sizes: 0
# InnoDB_trx_id: A93
SET timestamp=1381244774;
SELECT `hosts`.`id` AS t0_r0, `hosts`.`name` AS t0_r1, `hosts`....