| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| File input Node issues in WMB 6.1 after an upgrade to FP11 |
« View previous topic :: View next topic » |
| Author |
Message
|
| rlokesh26 |
 Posted: Fri Nov 22, 2013 6:57 am Post subject: File input Node issues in WMB 6.1 after an upgrade to FP11 |
 |
|
Newbie
Joined: 18 Oct 2013
Posts: 7
|
| We currently run 6.1 version of broker. Soon after applying Fix pack 11 to runtime I started facing this issue. I assumed that the toolkit upgrade also is required and hence upgraded the toolkit as well. But no luck even after rebuilding the message flow in FP11 toolkit Now I have both broker and toolkit running on FP11. |
|
| Back to top |
|
 |
| rlokesh26 |
| Posted: Fri Nov 22, 2013 7:01 am Post subject: |
|
|
Newbie
Joined: 18 Oct 2013
Posts: 7
|
I recreated the configurable service, set the dbparms and restarted the broker. But no luck again.
mqsistop $Brokername
mqsisetdbparms $Brokername -n ftp::mqm_ftp -d
mqsisetdbparms $Brokername -n ftp::mqm_ftp -u mqftp -p ******
mqsistart $Brokername;mqsideleteconfigurableservice $Brokername -c FtpServer -o ftpbroker
mqsicreateconfigurableservice $Brokername -c FtpServer -o ftpbroker -n serverName,connectionType,securityIdentity -v ftpbroker,ACTIVE,mqm_ftp
mqsireportproperties for the FTP server:
ftpbroker
accountInfo=''
cipher=''
compression=''
connectionType='ACTIVE'
knownHostsFile=''
mac=''
preserveRemoteFileDate=''
protocol=''
remoteDirectory=''
scanDelay=''
securityIdentity='mqm_ftp'
serverName='ftpbroker'
strictHostKeyChecking=''
timeoutSec=''
transferMode=''
File input node properties:
inputDirectory="/data01/home/mqm/files/availability"
processedFileAction="moveToArchive"
replaceDuplicateArchives="true"
messageDomainProperty="BLOB"
fileFtp="true"
fileFtpServer="ftpbroker"
fileFtpUser="mqm_ftp"
fileFtpDirectory="../to/safe_xml"
fileFtpTransferMode="ASCII"
scan delay =60
Broker Error:
WebSphere Broker v61011[1887]: (TEST3.BROKER1.default)[51]BIP3381E: File node 'POC_FileInput' in message flow 'POC1' cannot log in to remote 'FTP' server 'ftpbroker' with user name 'mqftp'. Reason: 'PASS =>response: '. : TEST3.BROKER1.8d68a99e-3e01-0000-0080-efb6e951b188: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 742: com.ibm.broker.nodes.filenodes.ComIbmFileInputNode.getRemoteFileManager: :
FTP server logs: (Does not show any weird behaviour)
[pid 32590] CONNECT: Client "broker"
[pid 32590] FTP response: Client "broker", "220 (vsFTPd 2.0.5)"
[pid 32590] FTP command: Client "broker", "USER mqftp"
[pid 32590] [mqftp] FTP response: Client "broker", "331 Please specify the password."
[pid 32590] [mqftp] FTP command: Client "broker", "PASS <password>"
[pid 32589] [mqftp] OK LOGIN: Client "broker"
[pid 32593] [mqftp] FTP response: Client "broker", "230 Login successful."
[pid 32593] [mqftp] FTP command: Client "broker", "QUIT"
[pid 32593] [mqftp] FTP response: Client "broker", "221 Goodbye."
Any suggestion/help here is much appreciated. |
|
| Back to top |
|
|
| rlokesh26 |
| Posted: Fri Nov 22, 2013 7:27 am Post subject: |
|
|
Newbie
Joined: 18 Oct 2013
Posts: 7
|
| Just to add some more information, Broker runs on Redhat and the toolkit on CentOS. "mqm" is the broker user and "mqftp" is the ftp user. |
|
| Back to top |
|
|
| rlokesh26 |
| Posted: Fri Nov 22, 2013 8:52 am Post subject: |
|
|
Newbie
Joined: 18 Oct 2013
Posts: 7
|
Interesting part in the service trace:
| Code: |
2013-11-22 16:06:27.456320 6 { ImbSyslog::writeToSyslog , 6, '(TEST3.BROKER1.default)[6]BIP3381E: File node 'POC_FileInput' in message flow 'POC1' cannot log in to remote 'FTP' server 'ftpbroker' with user name 'mqftp'. Reason: 'PASS =>response: '. : TEST3.BROKER1.8d68a99e-3e01-0000-0080-efb6e951b188: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 742: com.ibm.broker.nodes.filenodes.ComIbmFileInputNode.getRemoteFileManager: : ', true
2013-11-22 16:06:27.456324 6 { ImbSyslog::closeSyslog
2013-11-22 16:06:27.456334 6 } ImbSyslog::closeSyslog
2013-11-22 16:06:27.456336 6 { ImbSyslog::openSyslog
2013-11-22 16:06:27.456340 6 } ImbSyslog::openSyslog
2013-11-22 16:06:27.456400 6 } ImbSyslog::writeToSyslog
2013-11-22 16:06:27.456414 6 com.ibm.broker.nodes.filenodes.ComIbmFileInputNode.getRemoteFileManager file:/build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp line:742 message:3381.BIPv610 '' , 'POC_FileInput', 'POC1', 'ftpbroker', 'mqftp', 'PASS =>response: ', 'FTP'
2013-11-22 16:06:27.456414 6 Error BIP3381E: File node ''POC_FileInput'' in message flow ''POC1'' cannot log in to remote ''FTP'' server ''ftpbroker'' with user name ''mqftp''. Reason: ''PASS =>response: ''.
The FileInput or FileOutput node failed to log in after connecting to a remote server. Possible reasons for this failure are that the user name and password were invalid or not known at the remote system, the SFTP or FTP protocol was not observed by the server, accounting information was required but not supplied in the FtpServer definition, or that the server was too busy to respond.
Ensure that:
- The user name and password defined as the 'securityIdentity' with 'mqsisetdbparms' are correct.
- The 'account information' is specified on the 'acctInfo' property of the FtpServer definition only if it is required by the remote system.
- Local firewall settings do not block access to the remote server.
If you modify an FtpServer configurable service definition, restart the broker to pick up the new settings. For more information, see the "FtpServer configurable service properties" topic in the WebSphere Message Brokers information center.
2013-11-22 16:06:27.456444 6 } ComIbmFileInputNode.getRemoteFileManager , 'remoteFileManager=null'
2013-11-22 16:06:27.456460 6 ComIbmFileInputNode.transferFromRemoteServer() 'RemoteFileManager created: ' , 'remoteFilemanger=null'
2013-11-22 16:06:27.456482 6 } ComIbmFileInputNode.transferFromRemoteServer() , 'null'
2013-11-22 16:06:27.456490 6 } ComIbmFileInputNode.getNextFile , 'null'
2013-11-22 16:06:27.456502 6 } com.ibm.broker.nodes.filenodes.ComIbmFileInputNode@6a906a9.readData , 'READDATA_TIMED_OUT_WAIT_REQUIRED'
2013-11-22 16:06:27.456510 6 { java_lang_String::java_lang_String
|
[/b][/list] |
|
| Back to top |
|
|
| rlokesh26 |
| Posted: Mon Nov 25, 2013 3:54 am Post subject: |
|
|
Newbie
Joined: 18 Oct 2013
Posts: 7
|
The issue is now fixed. The timeoutSec configurable property did the trick.
I was collecting information for the PMR. And read about an FTP configurable service property called timeoutSec that was added as part of FP9. When left to default this is 5000 milli seconds.
Broker used to wait infinitely for a response from the FTP server prior to this patch. And after the patch, this property was left to default (5 seconds) which was not sufficient (the ftp server was taking more than 5 seconds to respond). This property is not available in the node as well.
Now that I have increased it to 25 secs and the issue is fixed. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
