MQ server Exception - exception

While I am trying to connect to MQ server, getting the below exception.
Could anybody tell me how to resolve it.
MQJE001: Completion Code '2', Reason '2195'.
A WebSphere MQ Error occured : Completion Code 2 Reason Code 2195
An MQException occurred trying to connect to the QManager.
Thanks and Regards,
K.Teja.

Did you try to telnet your remote queue manager server and port ? it may be firewall settings
telnet -d <MQ host IP or hostname> <channel port>

Related

CentOS 7 vsftpd keeps rejecting PhpStorm FTP Connection

I recently installed vsftpd on a server at my home for local development utilizing CentOS7. I went through the setup, and enabled passive mode, set up my ports, put my port forwarding on in my router, and then when I go to connect through PhpStorm, it rejects the connection.
I'm not sure what's going on, I've tried enabling Anonymous login, using a user, root. Nothing seems to work. Please let me know any information I can add.
The result from Test Connection is as follows:
Connection to '10.0.0.110' failed.
Connection to FTP server on "10.0.0.110" rejected.
Here are results from a FileZilla attempt.
Status: Connecting to 10.0.0.110:40000...
Status: Connection established, waiting for welcome message...
Response: 500 OOPS: failed to open xferlog log
ile:/var/log/vsftpd/vsftpd.log
Error: Critical error: Could not connect to server
Alright, so here is the answer, after looking in to what #LazyOne posted. I needed to change permissions as the first step. chmod 644 / 755 for files / dirs.
After that, I added in a listen_port=40000 to my vsftpd.conf file.
Then, I added in port_enable, pasv_address=<my internal ip address for my server> and lastly, pasv_addr_resolve=NO, as I have a static IP on my server.
I also added additional ports to the passive settings 40000-40500, as I've read this will allow multiple connections and will solve another error I was having.
After all of this, I opened up the ports in my server firewall-cmd --add-port=40000-40500/tcp --permanent, and added port forwarding in my router to allow this.
After all was said and done, I was finally able to connect to my FTP.
Hopefully this will help someone.

Connection from sails in ec2 to MySQL in rds giving handshake inactivity timeout error

I deployed my sails app in ec2 and I have mysql database in rds.
when I use mysql in rds from my local, it worked absolutely fine. But when I connect myswl in rds from the ec2 it is giving me this error:
error: A hook (`orm`) failed to load!
error: Error (E_UNKNOWN) :: Encountered an unexpected error
: Could not connect to MySQL:
Error: Handshake inactivity timeout
Please help me solve this issue. Should I configure my ec2 instance to connect to rds?
When adding inbound connection in the security options, don't use anywhere. As you can imagine, this is not secure at all. Instead use the security group associated with your instance. Of course, if you want to connect to your database remotely, add only your external IP address to the rules. "Anywhere" is like an invitation to the whole world saying: "Try to hack me!"
I figured it out. Added a inbound connection in security options with anywhere option.

OBIEE Agent to send mail doesn't mail

I am trying to set up via an OBIEE agent. I did the configuration of the smtp server in the EM and tested it via telnet. So this should be okay, but if I am running my agent I get this:
Eventually succeeded, but encountered and resolved errors...
Number of skipped deliveries: 2 of 3
AgentID: /users/weblogic/testagent
[nQSError: 75027] Failed to open connection to SMTP Server (host localhost; port 25).
It says 'localhost' and I don't get why it doesn't connect to my mailserver. What can I do to solve this?
Thanks!
My instanceconfig.xml:
<Alerts>
<ScheduleServer ssl="false">localhost:9705</ScheduleServer>
<OfflinePresentationServicesURL>http://10.232.18.95:9704/analytics/saw.dll</OfflinePresentationServicesURL>
</Alerts>
<ActionFramework>
<WorkflowServer>http://10.232.18.95:9704</WorkflowServer>
<WorkflowService>ANALYTICS</WorkflowService>
<WorkflowSystem>obiaftests</WorkflowSystem>
</ActionFramework>
My schedulerconfig.xml:
<From>Oracle Delivers</From>
<SMTP_Port>25</SMTP_Port>
<SMTP_Server>localhost</SMTP_Server>
<Sender>no-reply#oracle.com</Sender>
There are three steps in doing this:
configuring the SMTP server in Oracle EM
creating an agent in OBIEE
amending the schedulerconfig.xml file (located at OBI_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBISCH)
I didn't do step 3 so OBIEE was trying to send over localhost. You should put the same server in here as configured in the EM.

Cannot connect to Remote SQL DB with Dreamfactory

I am attempting to connect to a remote MySQL database using DreamFactory app.
This is what I am doing:
http://i.imgur.com/S9WHZ5i.png
And this is the error I see in the Dreamfactory app log:
[2014-06-14 09:47:53] app.ERROR: REST Exception #500 > Failed to
launch service "myservice": CDbConnection failed to open the DB
connection.
{"host":"myaddress","request_uri":"/rest/myapp","source_ip":"...","sapi_name":"apache2handler"}
[] [2014-06-14 09:47:53] app.ERROR: SQLSTATE[HY000] [2003] Can't
connect to MySQL server on '...' (111) [] []
I checked on my MySQL machine for any access attempts and I see none.
I think I configured something wrong in the Dreamfactory Admin screens.
Please help!
Many thanks!
User has answered his own question. Had to enable incoming connections within his Amazon EC2 instance. Just a heads up to others having the same issue out there.
Thanks,
Mark

Openshift DB connection issue

I'm trying to connect mysql db in openshift from my application as below ,
new DriverManagerDataSource("jdbc:mysql://localhost/dbXXXX?autoReconnect=true", "usernameXXX", "pwdXXX");
However an error was thrown as
om.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Any idea , whats the reasonn
If this is a scaled application, then you need to also supply the port, as it won't be 3306. Otherwise try restarting the mysql cartridge, or try sshing into your gear, and use the "mysql" command to see if you can connect, also try using the environment variables for your connection instead of the actual values. Also, localhost is wrong, ssh into your gear and run "env | grep MYSQL" and you will see the values that you should use.