SOLVED FTP not startable after update/reboot

[russoj88]

I just ran the updates (9.3-STABLE-201502142001) and rebooted the machine. When it comes up, it says FTP is running in the services tab, but it is not.

Trying to start FTP from the interface just gives the error that it could not start.

I then did

Code:

service ftpd start

in the web shell. This said I could not because ftpd_enable was "NO". I added "YES" to rc.conf and then was able to start FTP.

1. I'm not sure really where to start to diagnose this. I read in the manual that proftpd is supposed to be used and not ftpd. Was this the "correct" course of action?
2. I'm assuming this is not the best fix. Should "YES" be in rc.conf? Is there a better way to fix this?

 

[cyberjock]

Yeah.. not the best fix by a longshot. What you need to do is see what is in /var/log/messages after you try to start it (and it fails). We need more info than "gives the error that it could not start" to troubleshoot the issue.

Forcing "YES" may make the service start, but I can promise you that there is much more to it than just that service ftpd start to get ftpd to work properly. So we still need to figure out what the problem actually is.

 

[russoj88]

Thanks for the quick reply. By "gives the error that it could not start", I meant the error in the web GUI.

I removed what I added to rc.conf and then tailed the messages file while starting FTP:

Code:

Feb 20 01:27:00 freenas notifier: Starting proftpd.                                                                                
Feb 20 01:27:01 freenas notifier: 2015-02-20 01:27:01,019 freenas.local proftpd[6445]: warning: unable to determine IP address of 'freenas.local'                                                                                                                      
Feb 20 01:27:01 freenas notifier: 2015-02-20 01:27:01,019 freenas.local proftpd[6445]: error: no valid servers configured          
Feb 20 01:27:01 freenas notifier: 2015-02-20 01:27:01,019 freenas.local proftpd[6445]: fatal: error processing configuration file '/usr/local/etc/proftpd.conf'                
Feb 20 01:27:01 freenas root: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd                          
Feb 20 01:27:01 freenas notifier: /usr/local/etc/rc.d/proftpd: WARNING: failed to start proftpd

Not sure why it could originally determine the IP, but now can't. Thanks for the help and time. It is appreciated.

 

[cyberjock]

What's your hardware?

 

[russoj88]

SUPERMICRO MBD-X9SCM-F-O
Xeon E3-1230 V2
16GB Kingston ECC RAM
6x WD Scorpio Blue WD5000LPVT 500GB 5400 RPM 8MB Cache SATA 3.0Gb/s 2.5"
RAIDZ2 connected through a HighPoint RocketRAID 2720SGL

The system is an "in-between" setup before I get 6x WD reds.

 

[enemy85]

Don't want to hijack the thread, but I have the same problem but with a fresh instal of FreeNAS-9.3-STABLE-201502162250.
I'm using my old test rig with just 4gb RAM, but i don't think it's that the problem because it's a brand new install without no data or plugins and it worked with the 9.2.1.x
I'll see how @russoj88 will fix his problem and try to fix mine too

 

[enemy85]

@russoj88 i solved my problem:
adding the local IP address of my FreeNAS Server to the 'Host Name Database' in Network > Global Configuration followed by the host name
example (x.x.x.x freenas.local)

try and see if it works for you too

 

[dlavigne]

Note that there is a fix for this in the next SU: https://bugs.freenas.org/issues/8073.

 

[russoj88]

@enemy85 yes, that worked for me too. Thank you.
@dlavigne thanks for the fix!