[resolu] probleme proftpd, connection local/distant impossible

rhaamo · Le 03/01/2007, à 13:39

Bonjour a tous.
J'ai instalé ubuntu 6.10 sur ma dedibox mais j'ai toujour le meme probleme meme apres reinstalation.

Lorsque je tente de me conecter a mon serveur ftp tournant sous proftpd et instalé via http://howtoforge.com/proftpd_mysql_virtual_hosting
je me heurt au meme probleme:

Etat :	Connexion à 88.191.**.** ...
Etat :	Connecté à 88.191.**.**. Attente du message d'accueil...
Erreur :	Déconnecté du serveur
Erreur :	Impossible de se connecter !
Etat :	Attente de relance... (encore 5 tentatives)

mon /var/log/proftpd/proftpd.log me retourne
Jul 17 23:40:41 tux-atome proftpd[3350] sd-****.dedibox.fr (********.ipt.aol.com[172.***.***.***]): FTP session closed.
J'ai relancer proftpd via reload ou force-reload et meme restarté ma dedi via la console mais rien n'y fait
J'ai deja reusi ce tuto sur une debian et une ubuntu de la meme version mais la je ne comprend pas

Voici mon proftpd.conf

#
# /etc/proftpd/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes reload proftpd after modifications.
# 

# Includes DSO modules
Include /etc/proftpd/modules.conf

ServerName			"tux-atome"
ServerType			standalone
DeferWelcome			off

IdentLookups off
UseReverseDNS off

MultilineRFC2228		on
DefaultServer			on
ShowSymlinks			on

TimeoutNoTransfer		600
TimeoutStalled			600
TimeoutIdle			1200

DisplayLogin                    welcome.msg
DisplayFirstChdir               .message
ListOptions                	"-l"

DenyFilter			\*.*/

# Port 21 is the standard FTP port.
Port				21

# In some cases you have to specify passive ports range to by-pass
# firewall limitations. Ephemeral ports can be used for that, but
# feel free to use a more narrow range.
# PassivePorts                    49152 65534

# 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				proftpd
Group				nogroup

# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask				022  022
# Normally, we want files to be overwriteable.
AllowOverwrite			on

# Uncomment this if you are using NIS or LDAP to retrieve passwords:
# PersistentPasswd		off

# Be warned: use of this directive impacts CPU average load!
#
# Uncomment this if you like to see progress and transfer rate with ftpwho
# in downloads. That is not needed for uploads rates.
# UseSendFile			off

TransferLog /var/log/proftpd/xferlog
SystemLog   /var/log/proftpd/proftpd.log

<IfModule mod_tls.c>
TLSEngine off
</IfModule>

<IfModule mod_quota.c>
QuotaEngine on
</IfModule>

<IfModule mod_ratio.c>
Ratios on
</IfModule>


# Delay engine reduces impact of the so-called Timing Attack described in
# http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02
# It is on by default. 
<IfModule mod_delay.c>
DelayEngine on
</IfModule>

<IfModule mod_ctrls.c>
ControlsEngine        on
ControlsMaxClients    10
ControlsLog           /var/log/proftpd/controls.log
ControlsInterval      5
ControlsSocket        /var/run/proftpd/proftpd.sock
</IfModule>

<IfModule mod_ctrls_admin.c>
AdminControlsEngine on
</IfModule>

# A basic anonymous configuration, no upload directories.

# <Anonymous ~ftp>
#   User				ftp
#   Group				nogroup
#   # We want clients to be able to login with "anonymous" as well as "ftp"
#   UserAlias			anonymous ftp
#   # Cosmetic changes, all files belongs to ftp user
#   DirFakeUser	on ftp
#   DirFakeGroup on ftp
# 
#   RequireValidShell		off
# 
#   # 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
#   <Directory *>
#     <Limit WRITE>
#       DenyAll
#     </Limit>
#   </Directory>
# 
#   # Uncomment this if you're brave.
#   # <Directory incoming>
#   #   # Umask 022 is a good standard umask to prevent new files and dirs
#   #   # (second parm) from being group and world writable.
#   #   Umask				022  022
#   #            <Limit READ WRITE>
#   #            DenyAll
#   #            </Limit>
#   #            <Limit STOR>
#   #            AllowAll
#   #            </Limit>
#   # </Directory>
# 
# </Anonymous>

DefaultRoot ~


# The passwords in MySQL are encrypted using CRYPT
SQLAuthTypes            Plaintext Crypt
SQLAuthenticate         users* groups*


# used to connect to the database
# databasename@host database_user user_password
SQLConnectInfo  ftp@localhost proftpd *******


# Here we tell ProFTPd the names of the database columns in the "usertable"
# we want it to interact with. Match the names with those in the db
SQLUserInfo     ftpuser userid passwd uid gid homedir shell

# Here we tell ProFTPd the names of the database columns in the "grouptable"
# we want it to interact with. Again the names match with those in the db
SQLGroupInfo    ftpgroup groupname gid members

# set min UID and GID - otherwise these are 999 each
SQLMinID        500

# create a user's home directory on demand if it doesn't exist
SQLHomedirOnDemand on

# Update count every time user logs in
SQLLog PASS updatecount
SQLNamedQuery updatecount UPDATE "count=count+1, accessed=now() WHERE userid='%u'" ftpuser

# Update modified everytime user uploads or deletes a file
SQLLog  STOR,DELE modified
SQLNamedQuery modified UPDATE "modified=now() WHERE userid='%u'" ftpuser

# User quotas
# ===========
QuotaEngine on
QuotaDirectoryTally on
QuotaDisplayUnits Mb
QuotaShowQuotas on

SQLNamedQuery get-quota-limit SELECT "name, quota_type, per_session, limit_type, bytes_in_avail, bytes_out_avail, bytes_xfer_avail, files_in_avail, files_out_avail, files_xfer_avail FROM ftpquotalimits WHERE name = '%{0}' AND quota_type = '%{1}'"

SQLNamedQuery get-quota-tally SELECT "name, quota_type, bytes_in_used, bytes_out_used, bytes_xfer_used, files_in_used, files_out_used, files_xfer_used FROM ftpquotatallies WHERE name = '%{0}' AND quota_type = '%{1}'"

SQLNamedQuery update-quota-tally UPDATE "bytes_in_used = bytes_in_used + %{0}, bytes_out_used = bytes_out_used + %{1}, bytes_xfer_used = bytes_xfer_used + %{2}, files_in_used = files_in_used + %{3}, files_out_used = files_out_used + %{4}, files_xfer_used = files_xfer_used + %{5} WHERE name = '%{6}' AND quota_type = '%{7}'" ftpquotatallies

SQLNamedQuery insert-quota-tally INSERT "%{0}, %{1}, %{2}, %{3}, %{4}, %{5}, %{6}, %{7}" ftpquotatallies

SQLNamedQuery gettally  SELECT "ROUND((bytes_in_used/1048576),2) FROM ftpquotatallies WHERE name='%u'"
SQLNamedQuery getlimit  SELECT "ROUND((bytes_in_avail/1048576),2) FROM ftpquotalimits WHERE name='%u'"
SQLNamedQuery getfree   SELECT "ROUND(((ftpquotalimits.bytes_in_avail-ftpquotatallies.bytes_in_used)/1048576),2) FROM ftpquotalimits,ftpquotatallies WHERE ftpquotalimits.name = '%u' AND ftpquotatallies.name = '%u'"

SQLShowInfo   LIST    "226" "Used %{gettally}MB from %{getlimit}MB. You have %{getfree}MB available space."

QuotaLimitTable sql:/get-quota-limit
QuotaTallyTable sql:/get-quota-tally/update-quota-tally/insert-quota-tally

RootLogin off
RequireValidShell off

Si quelqun pouvait m'aider sa serais cool
Merchi.

Dernière modification par rhaamo (Le 03/01/2007, à 15:46)

dexinou · Le 03/01/2007, à 14:10

il y a une incohérence ici :

User                proftpd
Group                nogroup

Alors que le tutorial indique que c'est ftpuser et ftpgroup

rhaamo · Le 03/01/2007, à 14:14

Um j'ai jamaismodif sa et sa tournais
je tente en modifiant sa et relancant proftpd

EDIT:
Meme en modifiant comme il faut sa revien au meme

Dernière modification par rhaamo (Le 03/01/2007, à 14:17)

dexinou · Le 03/01/2007, à 14:19

remettez le user:proftpd et le group:nogroup
Faut regarder les logs pour voir ce qu'il se passe mais les logs ne disent pas grand chose.

essayer de décommenter ceci:

# PassivePorts                    49152 65534

pour outrepasser les règles du par-feu

Dernière modification par dexinou (Le 03/01/2007, à 14:23)

rhaamo · Le 03/01/2007, à 14:29

Toujours pareil, je ne comprend pas, sur la meme distrib chez moi sa marchait

proftpd.log si sa peut aider (meme si ya rien qui n'aide )

Jan 03 11:11:11 tux-atome proftpd[10794] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 11:17:25 tux-atome proftpd[10794] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 11:17:25 tux-atome proftpd[10794] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 11:17:27 tux-atome proftpd[10837] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 11:17:47 tux-atome proftpd[10837] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 11:17:47 tux-atome proftpd[10837] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 11:17:49 tux-atome proftpd[10866] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 11:29:22 tux-atome proftpd[10890] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 11:29:33 tux-atome proftpd[10891] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 11:33:22 tux-atome proftpd[10897] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 11:34:22 tux-atome proftpd[10898] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 11:34:32 tux-atome proftpd[10899] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 12:17:40 tux-atome proftpd[10940] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
Jan 03 12:17:47 tux-atome proftpd[10941] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
Jan 03 12:20:52 tux-atome proftpd[10951] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
Jan 03 12:21:09 tux-atome proftpd[10866] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 12:21:09 tux-atome proftpd[10866] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 12:21:12 tux-atome proftpd[10976] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 12:21:14 tux-atome proftpd[10982] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
Jan 03 12:24:20 tux-atome proftpd[10976] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 12:24:20 tux-atome proftpd[10976] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 12:24:22 tux-atome proftpd[11008] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 12:24:25 tux-atome proftpd[11014] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
Jan 03 12:40:54 tux-atome proftpd[11045] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 12:43:23 tux-atome proftpd[11008] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 12:43:23 tux-atome proftpd[11008] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 12:43:25 tux-atome proftpd[11075] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 12:43:31 tux-atome proftpd[11080] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 12:46:43 tux-atome proftpd[11081] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:16:13 tux-atome proftpd[11075] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:16:13 tux-atome proftpd[11075] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:16:15 tux-atome proftpd[12498] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:16:21 tux-atome proftpd[12503] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:16:26 tux-atome proftpd[12504] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:19:06 tux-atome proftpd[12498] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:19:06 tux-atome proftpd[12498] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:19:08 tux-atome proftpd[12532] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:19:13 tux-atome proftpd[12537] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:19:23 tux-atome proftpd[12538] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:20:59 tux-atome proftpd[12532] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:20:59 tux-atome proftpd[12532] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:21:01 tux-atome proftpd[12566] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:21:11 tux-atome proftpd[12575] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:21:39 tux-atome proftpd[12566] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:21:39 tux-atome proftpd[12566] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:21:41 tux-atome proftpd[12600] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:21:45 tux-atome proftpd[12605] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:23:06 tux-atome proftpd[12600] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:23:06 tux-atome proftpd[12600] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:23:08 tux-atome proftpd[12630] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:23:14 tux-atome proftpd[12635] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.
Jan 03 13:26:18 tux-atome proftpd[12630] tux-atome.fr: ProFTPD killed (signal 15)
Jan 03 13:26:18 tux-atome proftpd[12630] tux-atome.fr: ProFTPD 1.3.0 standalone mode SHUTDOWN
Jan 03 13:26:20 tux-atome proftpd[12667] tux-atome.fr: ProFTPD 1.3.0 (stable) (built Wed Nov 29 02:01:20 UTC 2006) standalone mode STARTUP
Jan 03 13:26:23 tux-atome proftpd[12672] tux-atome.fr (********.ipt.aol.com[********.249]): FTP session closed.

mysql.log et mysql.err sont vide donc proftpd arrive bien a se connecter a la bdd ou alors ne s'y connecte pas

dexinou · Le 03/01/2007, à 14:32

Regarder les logs dans /var/log/syslog pour voir s'il est pas un peu plus bavard car un "FTP session closed" ça me dit rien.

Dernière modification par dexinou (Le 03/01/2007, à 14:32)

rhaamo · Le 03/01/2007, à 14:33

dans syslog il n'y a rien qui parle de ftp ou de connection

dexinou · Le 03/01/2007, à 14:36

Je n'ai plus d'idées...
Sinon essayer de vous connecter par ssh directmenet au serveur et tapper:

ftp localhost

Pour voir s'il accepte la connexion en local.

Dernière modification par dexinou (Le 03/01/2007, à 14:38)

rhaamo · Le 03/01/2007, à 14:38

ok, pas grave.
Merci d'avoir voulu m'aider

rhaamo · Le 03/01/2007, à 14:39

heu si tu regarde le log
Jan 03 12:17:40 tux-atome proftpd[10940] tux-atome.fr (localhost[127.0.0.1]): FTP session closed.
meme en local sa ne marche pas

rhaamo · Le 03/01/2007, à 15:47

en rajoutant une ligne dans le fichier de conf de proftpd j'ai reusi a afficher un log des commande sql, j'ai vu que proftpd voulait se conecter a mysql en utilisant postgrey, j'ai donc commenter cette ligne dans modules.conf et tout marche sur des roulettes .

dexinou · Le 03/01/2007, à 16:23

Si j'ai bien compris il chargeait le module postgrey au lieu du module mysql.

Dernière modification par dexinou (Le 03/01/2007, à 16:24)

rhaamo · Le 03/01/2007, à 16:28

Oui c'est sa.

Jan 03 14:07:34 mod_sql/4.2.1[13097]: defaulting to 'postgres' backend
Jan 03 14:07:34 mod_sql/4.2.1[13097]: backend module 'mod_sql_postgres/4.02'
Jan 03 14:07:34 mod_sql/4.2.1[13097]: backend api    'mod_sql_api_v2'

sa c'etait sans le #devant le module postgrey donc sa ne marchait pas et proftpd s'autokillais

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 03/01/2007, à 13:39

[resolu] probleme proftpd, connection local/distant impossible

#2 Le 03/01/2007, à 14:10

Re : [resolu] probleme proftpd, connection local/distant impossible

#3 Le 03/01/2007, à 14:14

Re : [resolu] probleme proftpd, connection local/distant impossible

#4 Le 03/01/2007, à 14:19

Re : [resolu] probleme proftpd, connection local/distant impossible

#5 Le 03/01/2007, à 14:29

Re : [resolu] probleme proftpd, connection local/distant impossible

#6 Le 03/01/2007, à 14:32

Re : [resolu] probleme proftpd, connection local/distant impossible

#7 Le 03/01/2007, à 14:33

Re : [resolu] probleme proftpd, connection local/distant impossible

#8 Le 03/01/2007, à 14:36

Re : [resolu] probleme proftpd, connection local/distant impossible

#9 Le 03/01/2007, à 14:38

Re : [resolu] probleme proftpd, connection local/distant impossible

#10 Le 03/01/2007, à 14:39

Re : [resolu] probleme proftpd, connection local/distant impossible

#11 Le 03/01/2007, à 15:47

Re : [resolu] probleme proftpd, connection local/distant impossible

#12 Le 03/01/2007, à 16:23

Re : [resolu] probleme proftpd, connection local/distant impossible

#13 Le 03/01/2007, à 16:28

Re : [resolu] probleme proftpd, connection local/distant impossible

Pied de page des forums