IFS Cloud - Document Management

Hi,

I m having a IFS cloud customer with IFS Cloud 21.1, SU4 claiming that the issue  he had  in SU2 is still occurring for ftp repository.

Quoting from the customer: 

“When viewing an existing document which was stored in the ftp repository long time ago, the error message is:
{"error":{"code":"ODATA_PROVIDER_ERROR","message":"Ein interner Serverfehler ist aufgetreten. Wenden Sie sich an den Administrator.","details":[{"code":"PROJECTION_IMPL_EXCEPTION","message":"Error when reading the file: Error while downloading the file. Failed to connect to FTP server: IFS-FTP-REP-PROD: System error"}]}}

If you create a new document, no error is shown but the file is not stored in the repository.”

When he first reported at SU2, we have asked him to wait till SU4. 

Any views on this? 

Thank you all in advance. :) 
Dhananji

Dear all,
just want to share for others here, the issue was found in K8s cluster and fix is coming with 21R2SU3. Having SU3 installed, it works fine then.
Thank you @Mathias Dahl for all your support.
Jan

Hi Mathias,
thanks for update, I will post the update to the case too.
No new info/findings have arrived on this via case, so I appreciate to get any.
You are most probably right with the FTP server. So let’s see the finding you have.
Thanks Jan

Hi Mathias,
yesterday we were trying to monitor the network traffic from linux box to FTP server with using tcpdump  and we were trying to see the difference between upload and download.
We recognized there is no traffic initiated to FTP server on the port where the download is supposed to happen.
While you are investigating we can also try to use another FTP server (with newer OS then WS2012) whether we see the same behavior.  
BR Jan
 

Hi Mathias,
pls. find new document attachment to the case with my findings. I used curl to retrieve the pdf file from FTP. I run the command from:
1. MTS Ubuntu OS - works fine, ending with status 226
2. oData container in K8s - does not work, ending with status 550, despite K8s firewall disabled

I would like to highlight also screenshot with FTP log for both scenarios, for scenario #2 it seems the Data Channel is closed with status 258. And I noticed that  the IP address of the client is missing on these lines. It seems the Data Channel communication is not somehow routed back to K8s cluster. Or any other idea?
Thanks Jan

@Mathias Dahl 
just a quick update, I did not manage to run FTP from odata container, but I was testing from linux box and I think I found the issue. The FTP server is by default using quite wide range of ports for passive mode and from security reasons not all of them are opened from the linux box. I will share more details with findings and testing results later today/tomorrow.
 

Thanks alot! Although it might not look like it, I think there are errors in the FTP log file 🙃 Have a look at my latest comment on the case in Service Now.

Hi @Mathias Dahl ,
I have uploaded following to the case.

• document with screenshots from my further testing
• FTP log - but no errors found with there
• dump from IFS application server

Unf. not too much error messages around, if needed we can have a screen sharing session to look at this together.
Thanks Jan

I am sometimes very paranoid when it comes to what information I get using technical investigations like these :-) so I must ask: how do you see that the file has been uploaded correctly? If you look “in the FTP server”, then it’s fine. If you trusted Docman that the upload went well, because there were no errors, well, then it is not always the case that it went well :-p

Yep, I used WinSCP FTP client to connect to FTP server and I can see the file there. Pls. see screenshot in the last attachment. 

Hi @Mathias Dahl , let me reply on question #1 n the attached document, I will be coming with the rest of the points during the day. Jan

Ref. 1. we use FTP with IIS on Windows Server 2012, passive mode supported, proved with FTP client WinSCP in passive mode. Yes we use IP address for the repository.

Document with screenshots was attached to the case.
Ticket Form for Case - IFS Customer Support

@ORFJAN 

Hi again, I have tested FTP repositories now, in our internal environment:

• Latest IFS Cloud 21R2 (this is in our development environment)

• FileZilla FTP server (64 bit) installed on a Windows Server 2012 R2, username = guest, password = guest, virtual path = / mapped to c:\docman\ftp, with full read and write access

• I used the machine name and not the IP in the repository setup in Docman. Set / as path there. No port set (will default to 21 on the server).

Upload AND download works. In the FTP server log we can see both the upload and download that is done from the IFS Odata container working well.

The only problem is after the download is finished, the client aborts the connection and this shows as an error in the FTP server. The file downloads though, without any visible error on the client side.

If you try to download with the Aurena Agent enabled, do you get any detailed error message showing up in the toast in the lower right corner? By using the Document Revision page you should be able to see any server error. The client errors pasted earlier in this post does not give any clues unfortunately (this is often the case, that we want to see the server errors since the client error is sometimes just a side effect of the server error).

Some questions as well:

1. Which FTP server do you use?
2. Are there any logs you can look at there?
3. Have you enabled support for passive FTP on the server and in your firewall? IFS uses passive nowadays, while we used active before (a change we had to make due to moving into containers).

Thanks!

Hi Mathias,
thanks for sharing, we will check the option further however seeing how many issues/gaps/redesigns is connected with the upgrade from IFS10 to IFS Cloud it’s another effort and complexity we adding here and not sure we have capacity for. If you see feasible to have FTP issue fixed with SU4 I would prefer to go that way.

Thanks Jan