Re: Publish our first site

We actually did a test using Net::FTP which is what
Bricolage uses and we
were able to put files on the server using the same username
and password we
have set up in Server Profile. If doesn't appear to be a
problem with FTP.
It appears that Bricolage isn't even talking with the ftp
application.




On 3/28/07 2:45 PM, "Beaudet, David P."
<D-BeaudetNGA.GOV> wrote:

> 
> Is your manual FTP client also using active FTP?  If
not, it's not a
> complete test.  Some FTP clients can be set to function
with active or
> passive -- others cannot.
> 
> Active v.s. Passive FTP:
> 
> h
ttp://en.wikipedia.org/wiki/File_Transfer_Protocol
> 
> 
> Active will require that a dynamic port range be opened
in your server's
> firewall configuration.  You could do a quick test by
shutting down your
> firewall and testing again if you think this might be
the problem (e.g.
> "service iptables stop")
> 
> 
> -----Original Message-----
> From: brad2 [mailto:brad2uakron.edu]
> Sent: Wednesday, March 28, 2007 2:36 PM
> To: userslists.bricolage.cc
> Subject: Re: Publish our first site
> 
> Yes we can ftp in manually from the Bricolage server to
the output
> server.
> When you say "bricolage user" do you mean
what we put into the
> destinations
> setup?
> 
> (Server Profile)
> Host Name: 
> OS:
> Document Root:
> Login:
> Password:
> Cookie:
> Active:
> 
> We have hostname, OS, Document Root, Login and Password
filled out. We
> have
> Active checked.
> 
> 
> We are using straight ftp at this point.
> 
> 
> 
> 
> On 3/28/07 1:32 PM, "cdmiller"
<cdmilleradams.edu> wrote:
> 
>> brad2 wrote:
>>> On our first time setup we have a good install.
We are trying to
> publish to
>>> another webserver. We create a story, preview
it o.k., then move it
> to the
>>> publish desk and publish but the files don't
write to the server. We
> have
>>> ftp set as the mover. We have the path correct
to the place we are
> trying to
>>> publish and permissions set wide open to accept
writes. Bricolage
> reports
>>> that the publish was successful.
>>> 
>>> The server is in the dns and we have the dns
name in the hostname box
> of
>>> destinations. We are using the Default Server
as the destination. Are
> there
>>> any configs we need to do to get it to publish
over to that server?
>> 
>> Make sure you can manually ftp as the bricolage
user from server to
> server.
>> 
>> With SFTP you may have to do this once to get past
the "add remote to
>> known_hosts" type of message for the first
login.
>> 
>> - cameron

-- 
Brad Rice
bradriceuakron.edu
Ext. 2481
Web Graphics Designer

So on the jobs screen everything disappears like it has been

published?  Does the bric_queued log have anything unusual?

>We actually did a test using Net::FTP which is what
Bricolage uses and we
>were able to put files on the server using the same
username and password we
>have set up in Server Profile. If doesn't appear to be a
problem with FTP.
>It appears that Bricolage isn't even talking with the
ftp application.
>
>
>
>
>On 3/28/07 2:45 PM, "Beaudet, David P."
<D-BeaudetNGA.GOV> wrote:
>
>>
>>  Is your manual FTP client also using active FTP? 
If not, it's not a
>>  complete test.  Some FTP clients can be set to
function with active or
>>  passive -- others cannot.
>>
>>  Active v.s. Passive FTP:
>>
>>  h
ttp://en.wikipedia.org/wiki/File_Transfer_Protocol
>>
>>
>>  Active will require that a dynamic port range be
opened in your server's
>>  firewall configuration.  You could do a quick test
by shutting down your
>>  firewall and testing again if you think this might
be the problem (e.g.
>>  "service iptables stop")
>>
>>
>>  -----Original Message-----
>>  From: brad2 [mailto:brad2uakron.edu]
>>  Sent: Wednesday, March 28, 2007 2:36 PM
>>  To: userslists.bricolage.cc
>>  Subject: Re: Publish our first site
>>
>>  Yes we can ftp in manually from the Bricolage
server to the output
>>  server.
>>  When you say "bricolage user" do you
mean what we put into the
>>  destinations
>>  setup?
>>
>>  (Server Profile)
>>  Host Name:
>>  OS:
>>  Document Root:
>>  Login:
>>  Password:
>>  Cookie:
>>  Active:
>>
>>  We have hostname, OS, Document Root, Login and
Password filled out. We
>>  have
>>  Active checked.
>>
>>
>>  We are using straight ftp at this point.
>>
>>
>>
>>
>>  On 3/28/07 1:32 PM, "cdmiller"
<cdmilleradams.edu> wrote:
>>
>>>  brad2 wrote:
>>>>  On our first time setup we have a good
install. We are trying to
>>  publish to
>>>>  another webserver. We create a story,
preview it o.k., then move it
>>  to the
>>>>  publish desk and publish but the files
don't write to the server. We
>>  have
>>>>  ftp set as the mover. We have the path
correct to the place we are
>>  trying to
>>>>  publish and permissions set wide open to
accept writes. Bricolage
>>  reports
>>>>  that the publish was successful.
>>>>
>>>>  The server is in the dns and we have the
dns name in the hostname box
>>  of
>>>>  destinations. We are using the Default
Server as the destination. Are
>>  there
>>>>  any configs we need to do to get it to
publish over to that server?
>>>
>>>  Make sure you can manually ftp as the
bricolage user from server to
>>  server.
>>>
>>>  With SFTP you may have to do this once to get
past the "add remote to
>>>  known_hosts" type of message for the
first login.
>>>
>>>  - cameron
>
>--
>Brad Rice
>bradriceuakron.edu
>Ext. 2481
>Web Graphics Designer


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537