Author Topic: Backup failure over FTP since security update applied  (Read 1717 times)

Offline synthesis

  • Jr. Member
  • **
  • Posts: 74
  • Country: za
  • Karma: +1/-0
    • View Profile
Backup failure over FTP since security update applied
« on: March 22, 2021, 05:15:52 AM »
Backups over FTP use to work until a security update was applied. Now the backups fail and when looking at the network traffic between the Mitel 3300 ICP and FTP server (Filezilla), there is a "550 Permission denied" from the server. Looking at the logs on the Mitel 3300 ICP, I also see "Could not put the backup file to FTP server: <ftp_server_IP>" and "Permission denied".

I never made any configuration changes to the FTP server since the security update and even gave full rights to the Everyone user on the backup destination folder to test it, but still getting permission denied error. Why is this happening? Is it a bug?


Offline Dogbreath

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 389
  • Country: gb
  • Karma: +18/-0
    • View Profile
Re: Backup failure over FTP since security update applied
« Reply #1 on: March 22, 2021, 06:28:24 AM »
What did you apply the security update to?
Look at the Filezilla logs. Replicate what the Mitel is doing, upload a file of a similar size to the same location as the same user. Does it work.
FWIW, I am backing up tens of customer's MiVB systems to a Filezilla server without issue.

Offline synthesis

  • Jr. Member
  • **
  • Posts: 74
  • Country: za
  • Karma: +1/-0
    • View Profile
Re: Backup failure over FTP since security update applied
« Reply #2 on: March 22, 2021, 10:09:53 AM »
What did you apply the security update to?

The security update was applied to the Mitel 3300 ICP.

Look at the Filezilla logs. Replicate what the Mitel is doing, upload a file of a similar size to the same location as the same user. Does it work.
FWIW, I am backing up tens of customer's MiVB systems to a Filezilla server without issue.

Tried replicating it with the same user on another computer and the computer was able to successfully upload the file to the same location on the FTP server.

Below are the Filezilla logs:

Code: [Select]
Connected on port 2020, sending welcome message...
220-FileZilla Server 0.9.60 beta
220-written by Tim Kosse (tim.kosse@filezilla-project.org)
220 Please visit https://filezilla-project.org/
USER user
331 Password required for user
PASS *********
230 Logged on
TYPE I
200 Type set to I
CWD /
250 CWD successful. "/" is current directory.
SIZE /backup_dbsave_mitel_14.0.3.37_20210322155818.tar.tmp
213 66528
PASV
227 Entering Passive Mode (10,1,1,10,220,224)
REST 66528
350 Rest supported. Restarting at 66528
STOR /backup_dbsave_mitel_14.0.3.37_20210322155818.tar.tmp
550 Permission denied
QUIT
221 Goodbye

As can be seen near the bottom of the log, there is a "550 Permission denied" so it seems the issue is with the Mitel 3300 ICP.

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4064
  • Country: us
  • Karma: +129/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: Backup failure over FTP since security update applied
« Reply #3 on: March 22, 2021, 11:54:36 AM »
You are reading it wrong, the ### responses are from Filezilla... The 3300 is trying to backup the database:

STOR /backup_dbsave_mitel_14.0.3.37_20210322155818.tar.tmp

But Filezilla is returning an error:

550 Permission denied

Then the Mitel quits because it doesn't have permission:

QUIT

And then Filezilla responds with a confirmation:

221 Goodbye

It appears your issue is in your FTP server...
« Last Edit: March 22, 2021, 12:17:18 PM by acejavelin »

Offline Dogbreath

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 389
  • Country: gb
  • Karma: +18/-0
    • View Profile
Re: Backup failure over FTP since security update applied
« Reply #4 on: March 24, 2021, 09:49:57 AM »
Working transaction for comparison:
Code: [Select]
(000943)23/03/2021 23:58:07 - (not logged in) (1.2.3.4)> 331 Password required for the ftp username
(000943)23/03/2021 23:58:07 - (not logged in) (1.2.3.4)> PASS ******
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> 230 Logged on
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> TYPE I
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> 200 Type set to I
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> PWD
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> 257 "/" is current directory.
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> PASV
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> 227 Entering Passive Mode (192,168,123,123,243,60)
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> STOR /backups/customer/backup_dbsave_customer_13.2.1.27_20210323235508.tar.tmp
(000943)23/03/2021 23:58:07 - the ftp username (1.2.3.4)> 150 Opening data channel for file upload to server of "/backups/customer/backup_dbsave_customer_13.2.1.27_20210323235508.tar.tmp"
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> 226 Successfully transferred "/backups/customer/backup_dbsave_customer_13.2.1.27_20210323235508.tar.tmp"
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> RNFR /backups/customer/backup_dbsave_customer_13.2.1.27_20210323235508.tar.tmp
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> 350 File exists, ready for destination name.
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> RNTO /backups/customer/backup_dbsave_customer_13.2.1.27_20210323235508.tar
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> 250 file renamed successfully
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> QUIT
(000943)23/03/2021 23:58:45 - the ftp username (1.2.3.4)> 221 Goodbye

What's going on with that "restart" command? Is the connection timing out? No timestamps in your log, hard to tell.
Try creating a scheduled FTP export of one of the smaller forms, see if that works.


 

Sitemap 1 2 3 4 5 6 7 8 9 10