View previous topic :: View next topic |
Author |
Message |
chidrob n00b
Joined: 07 Aug 2002 Posts: 17
|
Posted: Wed Aug 07, 2002 2:58 am Post subject: pure-ftpd error on startup but ok if manually started |
|
|
pure-ftpd starts on boot, but I can not ftp (connection refused).
I must do
"/etc/init.d/pure-ftpd zap" and "/etc/init.d/pure-ftpd start"
and then it works ok, until the next reboot.
Both "/etc/init.d/pure-ftpd restart" and "/etc/init.d/pure-ftpd stop"
don't work because there is no pid file.
Looking at /mnt/init.d/ and it says pure-ftpd is started, but ps -x shows nothing (so the "zap" required previus to the start).
Perhaps I am executing the rc-script too early in the boot process.
I have tested with sleep operand, disabling some rc-scripts and other more silly things, without success.
I can post whichever information you think can help to look harder at the problem.
What is the next to look at?
Thanks. |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Wed Aug 07, 2002 3:33 am Post subject: |
|
|
Did you rc-update add it to boot or default? _________________ I don't believe in witty sigs. |
|
Back to top |
|
|
chidrob n00b
Joined: 07 Aug 2002 Posts: 17
|
Posted: Wed Aug 07, 2002 5:33 am Post subject: |
|
|
default.
alsasound -> /etc/init.d/alsasound
cupsd -> /etc/init.d/cupsd
dhcp -> /etc/init.d/dhcp
gpm -> /etc/init.d/gpm
iptables -> /etc/init.d/iptables
local -> /etc/init.d/local
named -> /etc/init.d/named
net.eth0 -> /etc/init.d/net.eth0
net.eth1 -> /etc/init.d/net.eth1
net.eth2 -> /etc/init.d/net.eth2
netmount -> /etc/init.d/netmount
pure-ftpd -> /etc/init.d/pure-ftpd
sshd -> /etc/init.d/sshd
syslog-ng -> /etc/init.d/syslog-ng
vcron -> /etc/init.d/vcron
vmware -> /etc/init.d/vmware
wwwoffled -> /etc/init.d/wwwoffled
wwwoffled-online -> /etc/init.d/wwwoffled-online
xfs -> /etc/init.d/xfs |
|
Back to top |
|
|
mgirard n00b
Joined: 30 Jul 2002 Posts: 64
|
Posted: Wed Aug 07, 2002 12:43 pm Post subject: |
|
|
Perhaps the configuration file is screwed up? I would definitely double check those settings. If you can't do a start/restart/stop from the commandline than the configurations is certainly suspect.
-Mg |
|
Back to top |
|
|
chidrob n00b
Joined: 07 Aug 2002 Posts: 17
|
Posted: Wed Aug 07, 2002 11:15 pm Post subject: |
|
|
I found the problem.
1 - I was starting pure-ftpd before the interface with the ip address (wmnet).
2 - A missconfiguration in syslog-ng did that I lost the error message from pure-ftpd.
It seems that, if pure-ftpd starts with an unassigned ip address, the error is no t catched by the script in /etc/init.d/, and pure-ftpd is registered as started ok.
All in all, a silly error. |
|
Back to top |
|
|
|