All,
After installing the new cert from Comodo in my MS2012 server, my FTPS connections from my RHEL6 server are failing with "gnutls_handshake" error. We moved from Verisign signed to Comodo. I went through the different "set" commands but still unable to connect successfully. Can you please help? Thanks a bunch..
lx1234$ lftp
lftp :~> open -u uname ftps://server
Password:
lftp uname#server:~> set ftps:initial-prot ""
lftp uname#server:~> set ftp:ssl-force true
lftp uname#server:~> set ftp:ssl-protect-data true
lftp uname#server:~> set ssl:verify-certificate "yes"
lftp uname#server:~>debug 99999999
ls
FileCopy(0x15c4e80) enters state INITIAL
FileCopy(0x15c4e80) enters state DO_COPY
---- dns cache hit
---- Connecting to server port 990
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_RSA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_RSA_CAMELLIA_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_RSA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_RSA_CAMELLIA_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_RSA_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_CAMELLIA_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_CAMELLIA_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: DHE_PSK_SHA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: DHE_PSK_SHA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: DHE_PSK_SHA_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: DHE_PSK_SHA_ARCFOUR_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_RSA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_RSA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_RSA_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_DSS_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_DSS_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_DSS_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_CAMELLIA_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_CAMELLIA_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_ARCFOUR_SHA1
GNUTLS: HSK[0x19c5d40]: Keeping ciphersuite: RSA_ARCFOUR_MD5
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: PSK_SHA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: PSK_SHA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: PSK_SHA_3DES_EDE_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: PSK_SHA_ARCFOUR_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_AES_128_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_AES_256_CBC_SHA1
GNUTLS: HSK[0x19c5d40]: Removing ciphersuite: SRP_SHA_3DES_EDE_CBC_SHA1
GNUTLS: EXT[0x19c5d40]: Sending extension CERT_TYPE
GNUTLS: EXT[0x19c5d40]: Sending extension SAFE_RENEGOTIATION
GNUTLS: HSK[0x19c5d40]: CLIENT HELLO was sent [93 bytes]
GNUTLS: REC[0x19c5d40]: Sending Packet[0] Handshake(22) with length: 93
GNUTLS: REC[0x19c5d40]: Sent Packet[1] Handshake(22) with length: 98
GNUTLS: ASSERT: gnutls_buffers.c:599
GNUTLS: XXX[]: ret: 0 Success.
GNUTLS: XXX2[]: ret: 0 Success.
GNUTLS: ASSERT: gnutls_record.c:921
GNUTLS: ASSERT: gnutls_buffers.c:1032
GNUTLS: ASSERT: gnutls_handshake.c:2700
**** gnutls_handshake: A TLS packet with unexpected length was received.
---- Closing control socket
ls: Fatal error: gnutls_handshake: A TLS packet with unexpected length was
received.
Most probably you have set up ftp server so that the connection is plain text.
try connecting with ftp:// like this:
$ lftp
lftp :~> open -u uname ftp://server
lftp uname#server:~> set ftp:ssl-force yes
lftp uname#server:~> ls
Related
I have downloaded confluent kafka in windows machine. Zookeeper is running successfully while running kafka server i am getting below exception.
INFO Opening socket connection to server localhost/<unresolved>:2181. Will not attempt to
authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn)
WARN Session 0x0 for server localhost/<unresolved>:2181, unexpected error, closing socket
connection and attempting reconnect (org.apache.zookeeper.ClientCnxn)
java.nio.channels.UnresolvedAddressException
at java.base/sun.nio.ch.Net.checkAddress(Net.java:149)
at java.base/sun.nio.ch.Net.checkAddress(Net.java:157)
at java.base/sun.nio.ch.SocketChannelImpl.checkRemote(SocketChannelImpl.java:815)
at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:837)
at org.apache.zookeeper.ClientCnxnSocketNIO.registerAndConnect(ClientCnxnSocketNIO.java:277)
at org.apache.zookeeper.ClientCnxnSocketNIO.connect(ClientCnxnSocketNIO.java:287)
at org.apache.zookeeper.ClientCnxn$SendThread.startConnect(ClientCnxn.java:1021)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1064)
Below options i tried to solve the issue but it didn't work.
1.Added listeners=PLAINTEXT://127.0.0.1:9092,advertised.listeners=PLAINTEXT://127.0.0.1:9092
in server.properties file
2.Added localhost ip address in hosts file
Below are properties in server.properties file
num.network.threads=3
num.io.threads=8
socket.send.buffer.bytes=102400
socket.receive.buffer.bytes=102400
socket.request.max.bytes=104857600
log.dirs=C:\KafkaLog
num.partitions=1
num.recovery.threads.per.data.dir=1
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1
log.retention.hours=168
log.segment.bytes=1073741824
log.retention.check.interval.ms=300000
zookeeper.connect=localhost:2181
zookeeper.connection.timeout.ms=6000
confluent.support.metrics.enable=true
confluent.support.customer.id=anonymous
group.initial.rebalance.delay.ms=0
Zookeeper properties are
dataDir=C:\ZookeeperLog
clientPort=2181
maxClientCnxns=0
I have a problem in connecting to cassandra via clqsh. I've deployed a cluster consisting of 3 nodes on CentOS7. I could see that nodes are connecting with each other. nodetool status output is bellow:
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN ${SEED2} 226.47 KiB 1 60,3% <hash> rack1
UN ${SEED} 190.77 KiB 1 50,9% <hash> rack1
UN ${IP} 157.62 KiB 1 88,7% <hash> rack1
But connecting via cqlsh doesn't work. I've tried connection to localhost and to node IP. Here is the output of cqlsh command:
[root#node02 default.conf]# cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1':
error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error:
Connection refused")})
[root#node02 default.conf]# cqlsh ${IP}
connection error: ('Unable to connect to any servers', {'${IP}':
ConnectionShutdown('Connection to ${IP} was closed',)})
It's not such obvious for me why 'Connection to ... was closed' is printed if connecting to rpc_address but 'Connectiong refused' when connecting to the localhost.
Does anyone know the cause of such problem?
cassandra.yaml file is bellow:
# Cassandra storage config YAML
cluster_name: '${NAME}'
hinted_handoff_enabled: true
authenticator: org.apache.cassandra.auth.AllowAllAuthenticator
data_file_directories:
- /var/lib/cassandra/data
commitlog_directory: /var/lib/cassandra/commitlog
hints_directory: /var/lib/cassandra/hints
key_cache_size_in_mb: 2
key_cache_save_period: 14400
row_cache_size_in_mb: 0
row_cache_save_period: 0
saved_caches_directory: /var/lib/cassandra/saved_caches
commitlog_sync: periodic
commitlog_sync_period_in_ms: 10000
concurrent_reads: 32
concurrent_writes: 32
storage_port: 7000
ssl_storage_port: 7001
rpc_port: 9042
start_rpc: true
rpc_keepalive: true
rpc_server_type: sync
request_scheduler: org.apache.cassandra.scheduler.NoScheduler
index_interval: 128
listen_address: ${IP}
rpc_address: ${IP}
seed_provider:
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
- seeds: ${IP},${SEED}
Found the issue. You set rpc_port to 9042. I think you're confusing rpc with native (cql). Rpc is the old interface that is deprecated in later releases. I would recommend setting start_rpc to false and set rpc_port back to it's default value: 9160.
I am using VMware player (version 7.1.0build2496824) and I had installed mac os X lion 10.7 as a virtual os.
When I start VMware player and login on the mac os X lion I get the following error:
Unexpected Signal - vcpu(0) error
Here is my log file
2015-03-25T11:29:50.472+05:45| vmx| I120: Vix: [20849 mainDispatch.c:1187]: VMAutomationPowerOff: Powering off.
2015-03-25T11:29:50.472+05:45| vmx| W110: /home/amit/vmware/Lion/Lion.vmx: Cannot remove symlink /var/run/vmware/amit_1001/1427262279779574_20849/configFile: No such file or directory
2015-03-25T11:29:50.472+05:45| vmx| I120: Policy_SavePolicyFile: invalid arguments to function.
2015-03-25T11:29:50.472+05:45| vmx| I120: PolicyVMX_Exit: Could not write out policies: 15.
2015-03-25T11:29:50.472+05:45| vmx| I120: WORKER: asyncOps=4 maxActiveOps=2 maxPending=0 maxCompleted=0
2015-03-25T11:29:50.491+05:45| vmx| I120: Vix: [20849 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2015-03-25T11:29:50.494+05:45| vmx| I120: Vix: [20849 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2015-03-25T11:29:50.494+05:45| vmx| I120: Transitioned vmx/execState/val to poweredOff
2015-03-25T11:29:50.494+05:45| vmx| I120: Vix: [20849 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
2015-03-25T11:29:50.494+05:45| vmx| I120: Vix: [20849 mainDispatch.c:4330]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
2015-03-25T11:29:50.495+05:45| vmx| I120: Vix: [20849 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2015-03-25T11:29:50.495+05:45| vmx| I120: Transitioned vmx/execState/val to poweredOff
2015-03-25T11:29:50.495+05:45| vmx| I120: VMIOP: Exit
2015-03-25T11:29:50.524+05:45| vmx| I120: Vix: [20849 mainDispatch.c:842]: VMAutomation_LateShutdown()
2015-03-25T11:29:50.524+05:45| vmx| I120: Vix: [20849 mainDispatch.c:792]: VMAutomationCloseListenerSocket. Closing listener socket.
2015-03-25T11:29:50.524+05:45| vmx| I120: Flushing VMX VMDB connections
2015-03-25T11:29:50.524+05:45| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2015-03-25T11:29:50.524+05:45| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2015-03-25T11:29:50.525+05:45| vmx| I120: VigorTransport_ServerDestroy: server destroyed.
2015-03-25T11:29:50.530+05:45| vmx| I120: VMX exit (0).
2015-03-25T11:29:50.530+05:45| vmx| I120: AIOMGR-S : stat o=5 r=15 w=0 i=0 br=245760 bw=0
2015-03-25T11:29:50.541+05:45| vmx| I120: OBJLIB-LIB: ObjLib cleanup done.
2015-03-25T11:29:50.541+05:45| vmx| I120: FileTrack_Exit: done
Could anyone help me solving this error please?
Try troubleshooting using following instructions if after too issue prevails get support request from vmware :
Confirm that the folder or directory is still accessible by the user
creating the virtual machine.
If the virtual machine contains any non-preallocated disks, verify
that the volume storing the disks did not run out of free space.
Perform a repair of the virtual disk.
Verify there are no problems with the host's file system by
performing a disk check on your hard drives.
Verify that you are running the latest version of the VMware product
in use.
Completely reinstall the VMware product. If you are using an older
version of the product, install the latest version.
Memory defects at host can cause failures or unexpected software
behavior.
Ensure that the graphic drivers are up to date on the host physical
machine.
Confirm that a resource, such as the disk, is not too busy to
respond, thus causing the problem.
In some circumstances, you can experience these errors when the
system is very low on resources.
Confirm that no other virtualization software is running
simultaneously.
This is the info they gave me for the DB
HOST: <ip>
PORT: <port>
DB NAME: <name>
DB USER : <user>
DB PASSWORD: <password>
SERVICE: <service name>
CHARSET: WE8MSWIN1252
My parameters.yml looks like this
parameters:
database_driver: oci8
database_host: <ip>
database_port: <port>
database_name: <name>
database_user: <user>
database_password: <password>
database_service: true
database_charset: WE8MSWIN1252
My guess is that I'm missing the service name, but I don't know how to set it up since database_service only accepts boolean.
Thank you in advance!
Checkout getEasyConnectionString method (it was called differently in previous versions od doctrine as far as I know.). According to this you have two options:
Configure connection using separate parameters.
Your parameters.yml file is missing database_servicename parameter you got.
So complete parameters.yml file:
parameters:
database_driver: oci8
database_host: <ip>
database_port: <port>
database_name: <name>
database_user: <user>
database_password: <password>
database_service: true
database_servicename: <servicename>
database_charset: WE8MSWIN1252
You need to modify your config.yml because it probably doesn't have all parameters set there.
config.yml:
# Doctrine Configuration
doctrine:
dbal:
driver: %database_driver%
host: %database_host%
port: %database_port%
dbname: %database_name%
user: %database_user%
password: %database_password%
charset: %database_charset%
service: %database_service% #this you don't have probably
servicename: %database_servicename% #this you don't have probably
Pass whole dsn string as a dbname parameter
Your parameters.yml file:
parameters:
database_driver: oci8
database_user: <user>
database_password: <password>
database_charset: WE8MSWIN1252
database_name: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host>)(PORT=<port>))(CONNECT_DATA=(SERVICE_NAME=<service_name>)))
I have the PostgreSQL server running on my Mac OS X 10.7.2. Sometimes the random query, especially the
CREATE OR REPLACE TEMPORARY VIEW <Name> AS SELECT * FROM <Table>;
failed with code PGRES_FATAL_ERROR = 7 and message
ERROR: invalid page header in block 4169 of relation "pg_type"
After 2-5 attempts the query is finished OK with no errors.
I think the problem caused by the low free space on the system drive because the application works fine without database errors on mac with a lot of free space on system drive.
How could I specify the error causes the query failed?
UPDATE: Added a logs
sh-3.2# cat postgres_LOG.1324986905
LOG: database system was shut down at 2011-12-27 15:54:32 MSK
LOG: checkpoint record is at 1/EEE1161C
LOG: redo record is at 1/EEE1161C; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 1814900; next OID: 808694
LOG: next MultiXactId: 1; next MultiXactOffset: 0
LOG: database system is ready
LOG: transaction ID wrap limit is 1073763426, limited by database "my_db"
LOG: connection received: host=::1 port=49159
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49161
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49162
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49263
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49264
LOG: connection authorized: user=my_db database=my_db
ERROR: invalid page header in block 4169 of relation "pg_type"
LOG: connection received: host=::1 port=49266
LOG: connection authorized: user=my_db database=my_db
ERROR: invalid page header in block 4169 of relation "pg_type"
LOG: connection received: host=::1 port=49273
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49274
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49276
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49277
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49362
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=49363
LOG: connection authorized: user=my_db database=my_db
LOG: connection received: host=::1 port=50293
LOG: connection authorized: user=my_db database=my_db
sh-3.2#
Sounds very much like disk/filesystem corruption. I'd suggest you do a dump/reload cycle on the database as soon as you can - as well as a filesystem and disk hardware check if possible.
Shouldn't be related to the free disk space - that would give you a different error.
More likely some system tables are damaged. At least pg_type. And since pg_type is usually quite small (a dozen pages/blocks) but your number (4169) is quite large, there might be other problems lurking like to few vacuuming.