Hi all After grappling with this problem for many hours I thought I'd better ask for some help... I installed ISPConfig3 from this howto, then retraced my steps using the more popular "Perfect Server Debian Squeeze with Bind and Courier ISPConfig3" guide, updating and reinstalling packages where necessary. I removed the default FTP server (proftpd) which appeared to be installed somehow, but not running, installed pure-ftpd, and then updated ISPConfig to recognise my pure-ftpd installation, which it didn't before, but now does. At least, it shows up as a listed service under the monitor tab now, however it shows as "Offline". I watched the console during updating my ISPConfig installation and it did appear to start it with the following command: /usr/sbin/pure-ftpd-mysql-virtualchroot -l mysql:/etc/pure-ftpd/db/mysql.conf -l pam -D -b -u 1000 -Y 1 -O clf:/var/log/pure-ftpd/transfer.log -E -A -8 UTF-8 -H -B However if I run netstat, the process isn't listening on any port. (I can start it manually by running "pure-ftpd-mysql &", and it shows up in netstat. It just doesn't appear to be invoked by ISPConfig.) I've read a bunch of existing threads on the subject, but couldn't find my answer. Where do I start trying to troubleshoot this?
Perhaps edit /etc/default/saslauthd and change autostart to "yes" # Should saslauthd run automatically on startup? (default: no) START=yes Hope it works for you.
In the monitor ---> "show system log" part of the dashboard can you see pure-ftpd running every 5 minutes something like this? ....... xftp pure-ftpd: ([email protected]) [INFO] New connection from 127.0.0.1 ....... xftp pure-ftpd: ([email protected]) [INFO] Logout. ....... xftp pure-ftpd: ([email protected]) [INFO] New connection from 127.0.0.1 ....... xftp pure-ftpd: ([email protected]) [INFO] Logout. Are there any errors in the system log?
Um, I appear to have nothing in the log section, see attached image... Is there an equivalent log file I can look at not through the web interface? Untitled-1 by hazymat, on Flickr
Cool screenshot. What is happening in the "logfiles" section down the bottom there -- especially the "system log" output?
Not much appears to be happening in the log files. Last messages were from a number of hours ago since I rebooted. To be honest I don't entirely know what I'm looking at, so I'll post a bunch of lines from the messages file below, but there's nothing pertaining to FTP, or any obvious errors. Code: Aug 8 14:41:00 hogarth kernel: Detected 2261.000 MHz processor. Aug 8 14:41:00 hogarth kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4522.00 BogoMIPS (lpj=2261000) Aug 8 14:41:00 hogarth kernel: pid_max: default: 32768 minimum: 301 Aug 8 14:41:00 hogarth kernel: Security Framework initialized Aug 8 14:41:00 hogarth kernel: Mount-cache hash table entries: 512 Aug 8 14:41:00 hogarth kernel: CPU: Unsupported number of siblings 16 Aug 8 14:41:00 hogarth kernel: SMP alternatives: switching to UP code Aug 8 14:41:00 hogarth kernel: cpu 0 spinlock event irq 17 Aug 8 14:41:00 hogarth kernel: Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. Aug 8 14:41:00 hogarth kernel: installing Xen timer for CPU 1 Aug 8 14:41:00 hogarth kernel: cpu 1 spinlock event irq 23 Aug 8 14:41:00 hogarth kernel: SMP alternatives: switching to SMP code Aug 8 14:41:00 hogarth kernel: Initializing CPU#1 Aug 8 14:41:00 hogarth kernel: CPU: Unsupported number of siblings 16 Aug 8 14:41:00 hogarth kernel: installing Xen timer for CPU 2 Aug 8 14:41:00 hogarth kernel: cpu 2 spinlock event irq 29 Aug 8 14:41:00 hogarth kernel: Initializing CPU#2 Aug 8 14:41:00 hogarth kernel: CPU: Unsupported number of siblings 16 Aug 8 14:41:00 hogarth kernel: installing Xen timer for CPU 3 Aug 8 14:41:00 hogarth kernel: cpu 3 spinlock event irq 35 Aug 8 14:41:00 hogarth kernel: Initializing CPU#3 Aug 8 14:41:00 hogarth kernel: CPU: Unsupported number of siblings 16 Aug 8 14:41:00 hogarth kernel: Brought up 4 CPUs Aug 8 14:41:00 hogarth kernel: devtmpfs: initialized Aug 8 14:41:00 hogarth kernel: xor: automatically using best checksumming function: pIII_sse Aug 8 14:41:00 hogarth kernel: pIII_sse : 40416.000 MB/sec Aug 8 14:41:00 hogarth kernel: xor: using function: pIII_sse (40416.000 MB/sec) Aug 8 14:41:00 hogarth kernel: Grant table initialized Aug 8 14:41:00 hogarth kernel: NET: Registered protocol family 16 Aug 8 14:41:00 hogarth kernel: bio: create slab <bio-0> at 0 Aug 8 14:41:00 hogarth kernel: raid6: int32x1 769 MB/s Aug 8 14:41:00 hogarth kernel: raid6: int32x2 812 MB/s Aug 8 14:41:00 hogarth kernel: raid6: int32x4 507 MB/s Aug 8 14:41:00 hogarth kernel: raid6: int32x8 445 MB/s Aug 8 14:41:00 hogarth kernel: raid6: mmxx1 2515 MB/s Aug 8 14:41:00 hogarth kernel: raid6: mmxx2 6378 MB/s Aug 8 14:41:00 hogarth kernel: raid6: sse1x1 3488 MB/s Aug 8 14:41:00 hogarth kernel: raid6: sse1x2 2722 MB/s Aug 8 14:41:00 hogarth kernel: raid6: sse2x1 6511 MB/s Aug 8 14:41:00 hogarth kernel: raid6: sse2x2 5878 MB/s Aug 8 14:41:00 hogarth kernel: raid6: using algorithm sse2x1 (6511 MB/s) Aug 8 14:41:00 hogarth kernel: xen/balloon: Initialising balloon driver. Aug 8 14:41:00 hogarth kernel: last_pfn = 0x20800 max_arch_pfn = 0x1000000 Aug 8 14:41:00 hogarth kernel: Switching to clocksource xen Aug 8 14:41:00 hogarth kernel: Switched to NOHz mode on CPU #2 Aug 8 14:41:00 hogarth kernel: Switched to NOHz mode on CPU #1 Aug 8 14:41:00 hogarth kernel: Switched to NOHz mode on CPU #0 Aug 8 14:41:00 hogarth kernel: Switched to NOHz mode on CPU #3 Aug 8 14:41:00 hogarth kernel: NET: Registered protocol family 2 Aug 8 14:41:00 hogarth kernel: IP route cache hash table entries: 8192 (order: 3, 32768 bytes)
When pure-ftpd is running the logins can be seen in that log. Here is what I would do. Uninstall ISPConfig 3 To uninstall you follow the same steps as you did when you installed except you run: php -q uninstall.php (in the same directory) Remove the ispconfig user from the mysql database. (You can do this in phpmyadmin easily) Reboot your server Reinstall ISPConfig 3 If these problems persist then there is something wrong with your setup.
Tried that last night and it seemed to break even more things! Will post back once I've got it under control... right now London appears to be rioting around me...
