hi,
last week I installed proftpd 1.2.8 from sources in
4 solaris servers. All the installations are identical..
But now I have a problem in 1 server, I couldn�t
list directory contents for root filesystem.( / ).
This error only occurs in 1 server, and only in
root filesystem. I�m looking for errors in proftpd.conf,
and in / but I can�t find any error.

this is a trace of the ftp session:

Status: Connecting to 172.28.1.5:26 ...
Status: Connected with 172.28.1.5:26. Waiting for welcome message...
Response: 220 Ftp Service ready.
Command: USER root
Response: 331 Password required for root.
Command: PASS ******
Response: 230 User root logged in.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: PORT 172,28,0,31,18,3
Response: 200 PORT command successful
Command: TYPE A
Response: 200 Type set to A
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Error: Timeout detected!
Error: Could not retrieve directory listing

can anybody help???

Nacho Bermejo <foo@foo.com> wrote:
>   hi,

	Hi! Exciteablenestingduckies!!!

>   last week I installed proftpd 1.2.8 from sources in
>   4 solaris servers. All the installations are identical..
>   But now I have a problem in 1 server, I couldn�t
>   list directory contents for root filesystem.( / ).
>   This error only occurs in 1 server, and only in
>   root filesystem. I�m looking for errors in proftpd.conf,
>   and in / but I can�t find any error.

	How about posting more detail, such as this luser did:

	http://groups.google.com/groups?q=ftp+port++proftpd+%22Timeout+detected%22&hl=en&lr=lang_en&ie=UTF-8&safe=off&scoring=d&selm=d73a9de0.0302060845.6862887c%40posting.google.com&rnum=2

	And tell us about any firewalling stuff, and whether the exact same
	client fails on the other boxen and whether they are on the same
	subnet as each other or the client.

-am	� 2003

"Anthony Mandic" <ad@hotmail.com> escribi� en el mensaje
news:bim5j6$atb3t$2@ID-200644.news.uni-berlin.de...
> Nacho Bermejo <foo@foo.com> wrote:
> >   hi,
>
> Hi! Exciteablenestingduckies!!!
>
> >   last week I installed proftpd 1.2.8 from sources in
> >   4 solaris servers. All the installations are identical..
> >   But now I have a problem in 1 server, I couldnt
> >   list directory contents for root filesystem.( / ).
> >   This error only occurs in 1 server, and only in
> >   root filesystem. Im looking for errors in proftpd.conf,
> >   and in / but I cant find any error.
>
> How about posting more detail, such as this luser did:
>
>
http://groups.google.com/groups?q=ftp+port++proftpd+%22Timeout+detected%22&hl=en&lr=lang_en&ie=UTF-8&safe=off&scoring=d&selm=d73a9de0.0302060845.6862887c%40posting.google.com&rnum=2
>
> And tell us about any firewalling stuff, and whether the exact same
> client fails on the other boxen and whether they are on the same
> subnet as each other or the client.
>
> -am 2003

- All clients and servers are on the same subnet.
- There is no firewall
- Clients: filezilla 2.1.9a,  Solaris 8 and solaris 9 ftp client, windows xp
ftp client.
- I�ve tryed standard ports and nonstandar ports, Active and passive ftp,
standalone and inetd...
This is my proftpd.conf:

ServerIdent                     on "Ftp Service ready."
ServerType                      inetd
DefaultServer                   on
RootLogin                       on
ExtendedLog                     /var/adm/ftplog.extended ALL
SystemLog                       /var/adm/ftplog
SyslogLevel                     debug

# Port 21 is the standard FTP port.
Port                            21
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask                           022

# To prevent DoS attacks, set the maximum number of child processes
# to 30.  If you need to allow more than 30 concurrent connections
# at once, simply increase this value.  Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances                    30

# Set the user and group that the server normally runs at.
User                            nobody
Group                           nogroup

# Normally, we want files to be overwriteable.
<Directory /*>
  AllowOverwrite                on
</Directory>

# A basic anonymous configuration, no upload directories.
<Anonymous /interface/logs>
  User                          ftp
  Group                         ftp
  # We want clients to be able to login with "anonymous" as well as "ftp"
  UserAlias                     anonymous ftp

  # Limit the maximum number of anonymous logins
  MaxClients                    10

  # We want 'welcome.msg' displayed at login, and '.message' displayed
  # in each newly chdired directory.
  DisplayLogin                  welcome.msg
  DisplayFirstChdir             .message

  # Limit WRITE everywhere in the anonymous chroot
  <Limit WRITE>
    DenyAll
  </Limit>

</Anonymous>

"Nacho Bermejo" <foo@foo.com> schreef in bericht
news:bil2uc$afned$1@ID-143134.news.uni-berlin.de...
> hi,
> last week I installed proftpd 1.2.8 from sources in
> 4 solaris servers. All the installations are identical..
> But now I have a problem in 1 server, I couldn�t
> list directory contents for root filesystem.( / ).
> This error only occurs in 1 server, and only in
> root filesystem. I�m looking for errors in proftpd.conf,
> and in / but I can�t find any error.
>
> this is a trace of the ftp session:


A trace at server-site is much more interesting. Include a "DebugLevel = 9"
in your config-file to see what the server is doing before the time-out
occurs.

Stefan

"Nacho Bermejo" <foo@foo.com> schreef in bericht
news:bincj2$ba3fh$1@ID-143134.news.uni-berlin.de...

> > A trace at server-site is much more interesting. Include a "DebugLevel =
9"
> > in your config-file to see what the server is doing before the time-out
> > occurs.

The messages of the last part of the logging (simplyfied);

: in dir_check_full(): path = '/export', fullpath = '/export'.
: FS: using system stat()
: FS: using system stat()
: FS: using system stat()
: dispatching auth request "uid_name" to module mod_auth_file
: dispatching auth request "uid_name" to module mod_auth_unix
: dispatching auth request "gid_name" to module mod_auth_file
: dispatching auth request "gid_name" to module mod_auth_unix
: FS: using system lstat()
: in dir_check_full(): path = '/home', fullpath = '/home'.
: FS: using system stat()
: FS: using system stat()

Seems to me the ProFTPd server is busy/hangs on a stat()  on /home. You can
mimic that using an "ls -ld /home". That will probably time-out too and
possibly with an error message. If not, check your syslog / messages files.
Because the server trips on /home, I'd say it has got something to do with
automount (or a NFS share). Look further in that area.

Stefan

"Stefan" <someone@somewhere.nl> escribi� en el mensaje
news:3f4f4560$0$76263$e4fe514c@dreader9.news.xs4all.nl...
> "Nacho Bermejo" <foo@foo.com> schreef in bericht
> news:bincj2$ba3fh$1@ID-143134.news.uni-berlin.de...
>
> > > A trace at server-site is much more interesting. Include a "DebugLevel
=
> 9"
> > > in your config-file to see what the server is doing before the
time-out
> > > occurs.
>
> The messages of the last part of the logging (simplyfied);
>
> : in dir_check_full(): path = '/export', fullpath = '/export'.
> : FS: using system stat()
> : FS: using system stat()
> : FS: using system stat()
> : dispatching auth request "uid_name" to module mod_auth_file
> : dispatching auth request "uid_name" to module mod_auth_unix
> : dispatching auth request "gid_name" to module mod_auth_file
> : dispatching auth request "gid_name" to module mod_auth_unix
> : FS: using system lstat()
> : in dir_check_full(): path = '/home', fullpath = '/home'.
> : FS: using system stat()
> : FS: using system stat()
>
> Seems to me the ProFTPd server is busy/hangs on a stat()  on /home. You
can
> mimic that using an "ls -ld /home". That will probably time-out too and
> possibly with an error message. If not, check your syslog / messages
files.
> Because the server trips on /home, I'd say it has got something to do with
> automount (or a NFS share). Look further in that area.
>
> Stefan
>
>


Yes, you are right.
I can�t stat /home.
The problem was automountd...
Thanks.