I've two JDK's on my CentOS machine, 1.7 and 1.8.
When I set my JAVA_HOME to 1.7 the java -version command still shows 1.8
What's this? And how to fix?
Presto can't handle many concurrent sessions.
what's the maximum number of concurrent sessions per presto and how to set parameter for this ?
and how to handle it's maximum JVM ?
I am facing issue while running ./sqlplus command after installing Oracle Client 11g R2 on RHEL 7
here's is the error:
$ ./sqlplus
./sqlplus: symbol lookup error: /home/oracle/app/oracle/product/11.2.0/client_1/lib/libclntsh.so.11.1: undefined symbol: nnfyboot
I identified LD_LIBRARY_PATH, ORACLE_HOME, PATH
Also, all pre-req. packages have been isntalled.
Look at the below commands as well,
$ ldd
/home/oracle/app/oracle/product/11.2.0/client_1/lib/libclntsh.so.11.1
linux-vdso.so.1 => (0x00007fff60ff9000)
libnnz11.so => /home/oracle/app/oracle/product/11.2.0/client_1/lib/libnnz11.so (0x00007f8f85e62000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f8f85c57000)
libm.so.6 => /lib64/libm.so.6 (0x00007f8f85955000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8f85739000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f8f8551f000)
libc.so.6 => /lib64/libc.so.6 (0x00007f8f8515e000)
libaio.so.1 => /lib64/libaio.so.1 (0x00007f8f84f5c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8f88856000)
and this,
$ ldd sqlplus
linux-vdso.so.1 => (0x00007fff54d4d000)
libsqlplus.so => /home/oracle/app/oracle/product/11.2.0/client_1/lib/libsqlplus.so (0x00007f3d1e403000)
libclntsh.so.11.1 => /home/oracle/app/oracle/product/11.2.0/client_1/lib/libclntsh.so.11.1 (0x00007f3d1bdd7000)
libnnz11.so => /home/oracle/app/oracle/product/11.2.0/client_1/lib/libnnz11.so (0x00007f3d1ba0f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f3d1b805000)
libm.so.6 => /lib64/libm.so.6 (0x00007f3d1b502000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3d1b2e6000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f3d1b0cd000)
libc.so.6 => /lib64/libc.so.6 (0x00007f3d1ad0b000)
libaio.so.1 => /lib64/libaio.so.1 (0x00007f3d1ab09000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3d1e5eb000)
ldconfig completed successfully.
Would you please help ?
We've application fetching messages from mailbox inbox.
Once, application stoppped fetching, then we'd the following in maillog:
Aug 15 11:03:47 server_name postfix/virtual[16743]: 731E258003: to=<mailbox_name>, relay=virtual, delay=0.06, delays=0.04/0/0/0.02, dsn=2.0.0, status=sent (delivered to mailbo
x)
Aug 15 11:03:55 server_name postfix/pipe[3201]: 9CE9658002: to=<mailbox_name>, relay=filter, delay=0.19, delays=0.15/0/0/0.05, dsn=2.0.0, status=sent (delivered via filter ser
vice)
Aug 15 11:03:55 server_namepostfix/virtual[16743]: C6C4958003: to=<mailbox_name>, relay=virtual, delay=0.06, delays=0.05/0/0/0.01, dsn=2.0.0, status=sent (delivered to mailbo
x)
Aug 15 11:06:22 server_name postfix/pipe[6280]: 0CBA058002: to=<mailbox_name>, relay=filter, delay=0.22, delays=0.18/0/0/0.04, dsn=2.0.0, status=sent (delivered via filter ser
vice)
Aug 15 11:06:41 server_name postfix/virtual[11801]: 3CEA058003: to=<mailbox_name>, relay=virtual, delay=19, delays=0.04/0/0/19, dsn=4.2.0, status=deferred (delivery failed to
mailbox unable to lock for exclusive access: Resource temporarily unavailable)
Aug 15 11:09:31 server_name postfix/pipe[6282]: 438CF58002: to=<mailbox_name>, relay=filter, delay=0.15, delays=0.12/0/0/0.03, dsn=2.0.0, status=sent (delivered via filter ser
vice)
Aug 15 11:09:50 server_name postfix/virtual[12526]: 62A7E58004: to=<mailbox_name>, relay=virtual, delay=19, delays=0.04/0/0/19, dsn=4.2.0, status=deferred (delivery failed to
mailbox : unable to lock for exclusive access: Resource temporarily unavailable)
Aug 15 11:13:14 server_name postfix/virtual[12526]: 3CEA058003: to=<mailbox_name>, relay=virtual, delay=412, delays=394/0/0/19, dsn=4.2.0, status=deferred (delivery failed to
mailbox : unable to lock for exclusive access: Resource temporarily unavailable)
Aug 15 11:16:16 server_name postfix/pipe[6280]: D111E58002: to=<mailbox_name>, relay=filter, delay=0.18, delays=0.14/0/0/0.04, dsn=2.0.0, status=sent (delivered via filter ser
vice)
Aug 15 11:16:16 server_name postfix/virtual[12526]: 03C0E58005: to=<mailbox_name>, relay=virtual, delay=0.06, delays=0.04/0/0/0.01, dsn=2.0.0, status=sent (delivered to mailbo
x)
then I had the following in dovecot-info:
dovecot: Aug 15 11:03:48 Info: POP3(mailbox_name): Disconnected: Logged out top=0/0, retr=2/42139, del=2/2, size=42100
dovecot: Aug 15 11:14:23 Info: POP3(mailbox_name): Disconnected for inactivity top=0/0, retr=1/29827, del=0/1, size=29809
dovecot: Aug 15 18:01:28 Info: POP3(mailbox_name): Disconnected: Logged out top=0/0, retr=96/9469449, del=96/96, size=9467620
From the above logs I understood that:
1- mailbox inbox was working good till 11:03:47 and message was fetched as per mentioned in dovecot-info @11:03:48
2-after 11:03:47, no message fetched and @11:06 inbox was locked for exclusive access
3-@11:14: application tried to connect but it was disconnected for inactivity
4-everything went fine again after restarting application service @18:01
My questions are:
-Was application unable to access due to lock ?
-Why application didn't try to access again ?
-if this is issue was for inbox locking due to more than 2 access in the same time, how to avoid such behavior ?
-can I increase postfix parameter for simultaenous access to be more than 2 ?
I've the following error message appeared 3 continuous for the same mailbox
> (delivery failed to mailbox
> /var/spool/postfix/vhosts/<user>/mail/inbox:
>
> unable to lock for exclusive access: Resource temporarily unavailable
I didn't understand what's happenening .. Can you explain for me ?
What Can I do to avoid such error message again ?
Also, I've the below settings:
# used only for creating mbox dotlock files when creation fails for INBOX.
# Rely on O_EXCL to work when creating dotlock files. The default is to use
# hard linking. O_EXCL makes the dotlocking faster, but it doesn't always
#dotlock_use_excl = no
# Locking method for index files. Alternatives are fcntl, flock and dotlock.
# Dotlocking uses some tricks which may create more disk I/O than other locking
# methods. NFS users: flock doesn't work, remember to change mmap_disable.
#lock_method = fcntl
# Which locking methods to use for locking mbox. There are four available:
# dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe
# fcntl : Use this if possible. Works with NFS too if lockd is used.
# flock : May not exist in all systems. Doesn't work with NFS.
# lockf : May not exist in all systems. Doesn't work with NFS.
# You can use multiple locking methods; if you do the order they're declared
# in is important to avoid deadlocks if other MTAs/MUAs are using multiple
# locking methods as well. Some operating systems don't allow using some of
#mbox_read_locks = fcntl
#mbox_write_locks = fcntl
# Maximum time in seconds to wait for lock (all of them) before aborting.
#mbox_lock_timeout = 300
# If dotlock exists but the mailbox isn't modified in any way, override the
# lock file after this many seconds.
#mbox_dotlock_change_timeout = 120
# Keep the mailbox locked for the entire POP3 session.
#pop3_lock_session = no
# blocking passdb and userdb queries (eg. MySQL and PAM). They're
# [blocking=yes] [session=yes] [setcred=yes]
# Setting blocking=yes uses the alternative way: dovecot-auth worker
# [blocking=yes] - See userdb passwd for explanation
# [blocking=yes] - See userdb passwd for explanation
# [blocking=yes] - By default the lookups are done in the main dovecot-auth
# proceses. Useful with remote NSS lookups that may block.
# used either directly or though a dictionary server. The following dict block
I am using Postfix 2.10.2/Dovecot 2.2.5 on RHEL 5.9. I used to create normal virtual mailboxes.
How can i create IMAP mailbox and use it and how to differentiate it from POP3 mailboxes ?
I hope i am asking the right question, if not please correct me.
Thanks !!