These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Error report ProFTPD FTP Server on the new forum.
Web Hosting and Cloud Computing Control Panels
Howdy,
What error do you see in the error logs when that occurs?
You may want to take a peek in /var/log/messages, that should have some info about the issue.
-Eric
Hi,
Thank you.
Here is my log /var/log/messages
Jan 17 15:39:51 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="560" x-info="http://www.rsyslog.com"] start
Jan 17 15:39:36 localhost journal: Runtime journal is using 8.0M (max 189.4M, leaving 284.2M of free 1.8G, current limit 189.4M).
Jan 17 15:39:36 localhost journal: Runtime journal is using 8.0M (max 189.4M, leaving 284.2M of free 1.8G, current limit 189.4M).
Jan 17 15:39:36 localhost kernel: CPU0 microcode updated early to revision 0x60f, date = 2010-09-29
Jan 17 15:39:36 localhost kernel: Initializing cgroup subsys cpuset
Jan 17 15:39:36 localhost kernel: Initializing cgroup subsys cpu
Jan 17 15:39:36 localhost kernel: Initializing cgroup subsys cpuacct
Jan 17 15:39:36 localhost kernel: Linux version 3.10.0-229.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #1 SMP Fri Mar 6 11:36:42 UTC 2015
Jan 17 15:39:36 localhost kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-229.el7.x86_64 root=UUID=be25c354-166b-489a-b51c-4e2121f6015c ro crashkernel=auto rhgb quiet LANG=ko_KR.UTF-8
Jan 17 15:39:36 localhost kernel: e820: BIOS-provided physical RAM map:
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfd9ffff] usable
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000cfda0000-0x00000000cfdadfff] ACPI data
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000cfdae000-0x00000000cfdeffff] ACPI NVS
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000cfdf0000-0x00000000cfdfdfff] reserved
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x00000000ffb80000-0x00000000ffffffff] reserved
Jan 17 15:39:36 localhost kernel: BIOS-e820: [mem 0x0000000100000000-0x000000012fffffff] usable
Jan 17 15:39:36 localhost kernel: NX (Execute Disable) protection: active
Jan 17 15:39:36 localhost kernel: SMBIOS 2.5 present.
Jan 17 15:39:36 localhost kernel: No AGP bridge found
Jan 17 15:39:36 localhost kernel: e820: last_pfn = 0x130000 max_arch_pfn = 0x400000000
Jan 17 15:39:36 localhost kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jan 17 15:39:36 localhost kernel: total RAM covered: 4094M
Jan 17 15:39:36 localhost kernel: Found optimal setting for mtrr clean up
Jan 17 15:39:36 localhost kernel: gran_size: 64K chunk_size: 4M num_reg: 6 lose cover RAM: 0G
Jan 17 15:39:36 localhost kernel: e820: last_pfn = 0xcfda0 max_arch_pfn = 0x400000000
Jan 17 15:39:36 localhost kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780]
Jan 17 15:39:36 localhost kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Jan 17 15:39:36 localhost kernel: init_memory_mapping: [mem 0x12fe00000-0x12fffffff]
Jan 17 15:39:36 localhost kernel: init_memory_mapping: [mem 0x12c000000-0x12fdfffff]
Jan 17 15:39:36 localhost kernel: init_memory_mapping: [mem 0x100000000-0x12bffffff]
Jan 17 15:39:36 localhost kernel: init_memory_mapping: [mem 0x00100000-0xcfd9ffff]
Jan 17 15:39:36 localhost kernel: RAMDISK: [mem 0x3601c000-0x37005fff]
Jan 17 15:39:36 localhost kernel: ACPI: RSDP 00000000000f9b80 00014 (v00 ACPIAM)
Jan 17 15:39:36 localhost kernel: ACPI: RSDT 00000000cfda0000 00040 (v01 073108 RSDT1329 20080731 MSFT 00000097)
Jan 17 15:39:36 localhost kernel: ACPI: FACP 00000000cfda0200 00084 (v01 073108 FACP1329 20080731 MSFT 00000097)
Jan 17 15:39:36 localhost kernel: ACPI: DSDT 00000000cfda0440 05AF2 (v01 1AAAA 1AAAA000 00000000 INTL 20051117)
Jan 17 15:39:36 localhost kernel: ACPI: FACS 00000000cfdae000 00040
- Old man novice
I've been running into the same problem the past three days while trying to install VirtualMin on CentOS 6.7 and CentOS7. I ran a test that worked a few minutes ago. The problem is in the GPL VirtualMin proFTP install file; it's corrupt or misconfigured. The FTP not starting errors that Virtualmin outputs when proFTP faisl to start are different between CentOS 6.7 and 7. 6.7 simply said proFTP failed to start. 7 gave the message: “Failed to start service : Job for proftpd.service failed because the control process exited with error code. See "systemctl status proftpd.service" and "journalctl -xe" for details.”
I de-installed ProFTP via the install modules function in WebMin. You'll have to hit yes on the two radial buttons, dependencies, you'll see during de-install. Once ProFTP is de-installed click on the VirtualMin tab up top. Go down to the status area that shows ProFTP not running. Clikc on the name Pro FTP, it's hotlink. Once the system sees that ProFTP isn't there it will ask you to re-install ProFT from WebMin. Click on the link and it will re-install ProFTP. Once that's done successfully start her up. It worked fine and I was able to login via ftp right afterwards.
Hope this helps bro.
Wasss UPPPPPPPPP!
Oh, thank you for the kind comments.
I pay tribute to your troubleshooting efforts.
I'll try again.
I look forward to the success of my attempt.
Thank you.
- Old man novice
It works, and I've been able to do it numerous times. Just delete the proftp package installed on the server now. Once ProFTP is de-installed click on the VirtualMin tab up top. Go down to the status area that shows ProFTP not running. Clikc on the name Pro FTP, it's hotlink. Once the system sees that ProFTP isn't there it will ask you to re-install ProFT from WebMin. Click on the link and it will re-install ProFTP. Once that's done successfully start her up.
I wish you luck my brother, I was pretty frustrated trying to figure out a fix for the problem. I'm having a beer and relaxing now and my server is rocking.
---SuperSpook
Wasss UPPPPPPPPP!
I tried but was unsuccessful.
I can see that being a running proftpd service.
I stopped iptables and fail2ban service.
And I edited my hosts.deny and hosts.allow file.
However, I can not be an ftp connection.
"connection refused"
I need a more detailed guide more.
Thank you.
- Old man novice
Hi superspook I tried your solution, but when i Go down to the status area that shows ProFTPD not running. Click on the name Pro FTP (hotlink). The system sees that ProFTP isn't there it says as: "Error - File not found". So this solution did not work. Any one else with solution please