PutFile - Component was busy while disconnected by the server. FTW
804 views
Skip to first unread message
markus giesen
Jul 13, 2010, 3:03:13 AM7/13/10
to RedDot CMS Users
Hey folks,
did anyone of you ever had this error message while publishing:
-------------------------------------------------------
Language variant: English
Project variant: HTML_Public_Site
Errors:
PutFile: Failed to transfer /media/images/,
Component was busy while disconnected by the server.
-------------------------------------------------------
Any ideas what this could be?
Cheers,
Markus
did anyone of you ever had this error message while publishing:
-------------------------------------------------------
Language variant: English
Project variant: HTML_Public_Site
Errors:
PutFile: Failed to transfer /media/images/,
Component was busy while disconnected by the server.
-------------------------------------------------------
Any ideas what this could be?
Cheers,
Markus
Henry Lu a.k.a. Javahand
Jul 13, 2010, 10:00:32 AM7/13/10
to reddot-c...@googlegroups.com
Markus--
Not specifically. But if I am to attempt a guess, it is due to a binary file transfer failure in your ftp process. It could be a file lock or corrupted binary file in the src folder.
But you can take the process out of RedDot by directly ftp (or sftp) from the folder to your target box and see if you can reproduce the error and find the culprit.
Henry
--
646-807-8683
Not specifically. But if I am to attempt a guess, it is due to a binary file transfer failure in your ftp process. It could be a file lock or corrupted binary file in the src folder.
But you can take the process out of RedDot by directly ftp (or sftp) from the folder to your target box and see if you can reproduce the error and find the culprit.
Henry
--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
--
646-807-8683
Rob Palmer
Jul 14, 2010, 2:18:42 PM7/14/10
to RedDot CMS Users
Markus:
That looks like the sort of error message we get with the wrong FTP
setting (active vs. passive). Try changing that in the [Administer
Publication -> Project -> Edit General Settings] zone.
-Rob.
That looks like the sort of error message we get with the wrong FTP
setting (active vs. passive). Try changing that in the [Administer
Publication -> Project -> Edit General Settings] zone.
-Rob.
markus giesen
Jul 15, 2010, 7:29:30 PM7/15/10
to RedDot CMS Users
The weird thing is, that it is not a permanent error.
It shows up every now and then.
It shows up every now and then.
RustyLogic
Jul 16, 2010, 3:48:22 AM7/16/10
to RedDot CMS Users
We get it all the time... its due to files being locked / accessed on
the webserver which the ftp is occurring.
the webserver which the ftp is occurring.
Gav
Aug 12, 2010, 5:59:18 AM8/12/10
to RedDot CMS Users
We thought that too, but our ftp area is not being used to display the
files, its just a publication point that later on is picked up by a
Liveserver import job. The only thing connected to the ftp site is the
publication job itself. Its happened forever this one, but it doesnt
actually seem to affect the published files, like a false positive...
Does it even more with soap pubilshing and a similar error.
> > > > Markus- Hide quoted text -
>
> - Show quoted text -
files, its just a publication point that later on is picked up by a
Liveserver import job. The only thing connected to the ftp site is the
publication job itself. Its happened forever this one, but it doesnt
actually seem to affect the published files, like a false positive...
Does it even more with soap pubilshing and a similar error.
>
> - Show quoted text -
mreddot
Aug 13, 2010, 7:31:09 AM8/13/10
to RedDot CMS Users
Just stumbled upon this error, too.
Here's the way which helps in my test scenario:
- try to change the publication options regarding FTP: active/passive
transfer and/or relative path
- clear the pagecache
- clear the reference folder
-->project->publishing targets
- restart the Management Server
- restart DeliveryServer
- start a new publication
Here's the way which helps in my test scenario:
- try to change the publication options regarding FTP: active/passive
transfer and/or relative path
- clear the pagecache
- clear the reference folder
-->project->publishing targets
- restart the Management Server
- restart DeliveryServer
- start a new publication
Reply all
Reply to author
Forward
0 new messages