NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
6.8.0 breaks FTP
After upgrading to OS6 6.8.0, scans from my Lexmark MX410de multi-function scanner fail if the .pdf file being written to is not altered within about 3 seconds. This is a new failure that did not exi...
We traced the cause of the issue, and have posted our findings to the ProFTPD bugzilla report. We should be able to get it fixed for the next 6.9.0 Beta.
Both the NAS and the scanner are on the same local, wired network, both receiving a reserved IP address from the DHCP server.
Even low resolution scans fail when they are multiple page and the ADF is not used (the pause between placing the next page triggers the failure).
I set up a temporary FTP server on a Windows 10 Pro computer and the scanner scans to it just fine.
There is no FTP rate limit set. Permissions should not be an issue, as scans without a delay between pages work fine.
I will PM the logs.
Below are three entries from the proftpd.log file just created:
Entry 1 shows a successful scan to the FTP server.
Entries 2 and 3 are a failed scan and the error.
Does anyone know what the last character (c or i) in the first two entries represents?
Mon Sep 18 09:38:50 2017 6 192.168.2.125 1166589 /var/ftp/shared_files/Documents/Online_Statements/_From_Scanner/Scanned_2017-09-18-103840.pdf b _ i r dtesluk ftp 0 * c
Mon Sep 18 09:39:11 2017 14 192.168.2.125 1048609 /var/ftp/shared_files/Documents/Online_Statements/_From_Scanner/Scanned_2017-09-18-103853.pdf b _ i r dtesluk ftp 0 * i
2017-09-18 09:39:15,690 rnpro proftpd[4729] 127.0.0.2 (192.168.2.125[192.168.2.125]): notice: user dtesluk: aborting transfer: Interrupted system call
Logs reveal that the OS on this ReadyNAS was updated to 6.8.0 on 2017-Aug-18.
Logs also reveal that the ProFTPD service on this ReadyNAS changed from 1.3.5b (maint) to 1.3.6 (stable) on 2017-08-18 (presumably by the firmware update).
It looks to me that the issue started from and is related to these linked updates.
Hello chainlinc,
It does appear that there is a bond set on the NIC cards what bonding/teaming is setup on the NAS? Have you try disconnecting the bond and just use a single ethernet port and then check the connection? Is the NAS connected to a Netgear switch?I have notice there are lot of logs listed below that I may need to check this with others who can probably assist us and get back to you as soon as possible.
Thanks for your cooperation!
Sep 18 09:52:08 rnpro proftpd[23603]: pam_unix(ftp:session): session opened for user admin by (uid=0)
Sep 18 09:52:08 rnpro proftpd[23603]: pam_unix(ftp:session): session closed for user admin
Sep 18 09:52:09 rnpro kernel: bond0: An illegal loopback occurred on adapter (eth0)Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
Sep 18 09:52:09 rnpro kernel: bond0: An illegal loopback occurred on adapter (eth1)Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
Regards,
Marty_M
NETGEAR Community Team
Marty_M wrote:Hello chainlinc,
It does appear that there is a bond set on the NIC cards what bonding/teaming is setup on the NAS? Have you try disconnecting the bond and just use a single ethernet port and then check the connection? Is the NAS connected to a Netgear switch?I have notice there are lot of logs listed below that I may need to check this with others who can probably assist us and get back to you as soon as possible.
Thanks for your cooperation!
Sep 18 09:52:08 rnpro proftpd[23603]: pam_unix(ftp:session): session opened for user admin by (uid=0)
Sep 18 09:52:08 rnpro proftpd[23603]: pam_unix(ftp:session): session closed for user admin
Sep 18 09:52:09 rnpro kernel: bond0: An illegal loopback occurred on adapter (eth0)Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
Sep 18 09:52:09 rnpro kernel: bond0: An illegal loopback occurred on adapter (eth1)Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports
Regards,
Marty_M
NETGEAR Community TeamMarty_M,
I did try disconnecting the bond and just used a single ethernet port and then checked the connection - the problem persists.
Bond on ReadyNASBonding/teaming is setup on the NAS as a LACP team connected to a Netgear JGS524PE - 24-Port Gigabit ProSAFE Plus Switch through ports 13 and 15. The LAG was disabled on the switch and is now enabled. Switch has firmware 2.0.1.40. I am now going to try with the bond removed and use a single ethernet port on the switch (not 13 nor 15).
Bond on ReadyNASOn Netgear switch
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
