| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 81904 | 2007-08-10 07:27:00 | Linux - proftpd wont start | personthingy (1670) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 578972 | 2007-08-10 07:27:00 | meinServer:~# proftpd - IPv4 getaddrinfo 'meinServer' error: Name or service not known - warning: unable to determine IP address of 'meinServer' - error: no valid servers configured - Fatal: error processing configuration file '/etc/proftpd/proftpd.conf' and here's the config file: # This is a basic ProFTPD configuration file (rename it to # 'proftpd.conf' for actual use. It establishes a single server # and a single anonymous login. It assumes that you have a user/group # "nobody" and "ftp" for normal operation and anon. ServerName "meinServer" ServerType standalone DefaultServer on # 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 under which the server will run. User nobody Group nogroup # To cause every FTP user to be "jailed" (chrooted) into their home # directory, uncomment this line. DefaultRoot ~ # Normally, we want files to be overwriteable. <Directory /> AllowOverwrite on </Directory> this DID work, and the only thing i can think that i changed was change the servers name from "server" to "meinServer" |
personthingy (1670) | ||
| 578973 | 2007-08-10 07:51:00 | What name does /etc/hosts show for 127.0.0.1? | Jen (38) | ||
| 578974 | 2007-08-10 08:04:00 | What name does /etc/hosts show for 127.0.0.1?Not a lot. here's /etc/hosts.conf multi on o hang on, you said "hosts" not "host.conf" 127.0.0.1 localhost 203.97.119.70 server.something.net.nz server # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts I think i'll just alter the second line, and see what happens............ |
personthingy (1670) | ||
| 578975 | 2007-08-10 08:11:00 | meinServer:~# proftpd - IPv6 getaddrinfo 'meinServer.something.net.nz' error: Name or service not known that's the error i always used to get, but as it only seemed to effect ipV6, which isn't happening anyway, i've never worried about it........ seems to work now :) Thanks for that! |
personthingy (1670) | ||
| 578976 | 2007-08-10 08:17:00 | Super! :D Have you tried #'ing out the following lines in hosts and seeing what happens? ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Put it back again if you get that error or smoke starts coming out of the server ... :eek: |
Jen (38) | ||
| 578977 | 2007-08-10 08:23:00 | Super! :D Have you tried #'ing out the following lines in hosts and seeing what happens? ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Put it back again if you get that error or smoke starts coming out of the server ... :eek:i'll try that tomorrow, there's people in the chatroom, and it would be bad form to tweak that deep in the system, and reboot the server on them, just to see what happens.......:rolleyes: |
personthingy (1670) | ||
| 578978 | 2007-08-10 09:00:00 | ... reboot the server on them, just to see what happens.......:rolleyes: Should never have to reboot a Linux server for something like this. If your distro is "Redhat like" you should be able to try a line like: service proftpd restart if not then something like: /etc/rc.d/init.d/profptd restart Distributions differ but finding out how this works for your one saves having to reboot. |
johnd (85) | ||
| 578979 | 2007-08-10 09:05:00 | Should never have to reboot a Linux server for something like this. If your distro is "Redhat like" you should be able to try a line like: service proftpd restart if not then something like: /etc/rc.d/init.d/profptd restart Distributions differ but finding out how this works for your one saves having to reboot.But, i'm working on the theory that what i'm doing may effect all sorts of things, so the easiest way to restart everything, i think, is reboot. If i was playing with just the proftpd.conf file i wouldn't dream of it! |
personthingy (1670) | ||
| 578980 | 2007-08-11 01:45:00 | ipv6 has got nothing to do with it . Don't bother changing that . The problem, made clear in the error messages, was that the name of the server couldn't be resolved to an IP address . . Of course it couldn't: you didn't have that alias in that host . conf file . Now it can find the ip address corresponding to meinserver, and it works . That's how it's supposewd to work . "203 . 97 . 119 . 70 server . something . net . nz server" was the culprit . You had server as an alias . Changing that line to: "203 . 97 . 119 . 70 server . something . net . nz server meinserver" would do the trick . No rebooting needed, just restarting the ftp server . There's probably a "kill" option which would make it just re-read its configuration file without even restarting . |
Graham L (2) | ||
| 1 | |||||