Re: ProFTP Glitch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Ed Greshko wrote:
> Mike Dwiggins wrote:
>   
>> Ed Greshko wrote:
>>   
>>     
>>> Mike Dwiggins wrote:
>>>   
>>>     
>>>       
>>>> Trying to start from usr/sbin/proftpd  I egt
>>>>
>>>> - warning: unable to determine IP address of 'laptop.localnet'
>>>> -error: no valid servers configured
>>>> -Fatal: error orocessing configuration file '/etc/proftpd.conf'
>>>>
>>>> and there is nothing in /var/log/messages.  That is whats bugging me, 
>>>> should that not reflect in the system messages file?
>>>>
>>>>   
>>>>     
>>>>       
>>>>         
>>> Well, there then is the problem.
>>>
>>> "unable to determine IP address of 'laptop.localnet' "
>>>
>>> doesn't have an IP address associated with it.  I'm assuming that
>>> "hostname" returns I wouldn't worry at this point about messages not
>>> appearing in /var/log/messages.  
>>>
>>> If I change my hostname I get the same error as you do....
>>>
>>> [root@f12 ~]# hostname f17.greshko.com
>>> [root@f12 ~]# hostname
>>> f17.greshko.com
>>>
>>> [root@f12 ~]# /usr/sbin/proftpd
>>>  - warning: unable to determine IP address of 'f17.greshko.com'
>>>  - error: no valid servers configured
>>>  - Fatal: error processing configuration file '/etc/proftpd.conf'
>>>
>>> But then....
>>>
>>> [root@f12 ~]# hostname f12.greshko.com
>>> [root@f12 ~]# hostname
>>> f12.greshko.com
>>> [root@f12 ~]# service proftpd start
>>> Starting proftpd:                                          [  OK  ]
>>>
>>> So, it is most likely that 'laptop.localnet' does not exist in your
>>> /etc/hosts file.
>>>
>>> Ed
>>>
>>>
>>>
>>>
>>>   
>>>     
>>>       
>> Tried that trick with the same results on my end.  Even tried changing 
>> the machine ID to end with .com and the same happened.  I am wondering 
>> if it has to do with this machine being DHCP client vice static address.
>>
>> I will try that tonight when the rest of the house goes to bed.
>>
>>   
>>     
> OK.... Now that it is actually morning I was able to try one more thing
> that should fix your problem....
>
> edit your /etc/hosts file and add laptop.localnet to the line starting
> with 127.0.0.1
>
>
>   

Magic fix:

Set Static IP
Edit hosts file
reboot

If not done in that order wash/rinse/repeat!

Thank you Sir!  I was beating my forehead flat.

Mike

--

Excessive Virtue is a Vice unto itself!
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux