First was my emails stopped working. The biggest thing that keeps happening is that I can not log into ispconfig and I have to reinstall everything all over again. when this happens the web site still works but it runs real low, My question is can this be fixed without a reinstall of everything. You can check out what I mean at http://letsebid.com:8080/ and if you go to the web site you will see it works fine just real slow. This has happened three time now. I even updated my Debian the last time I had to reinstall everything.
There are no known issues with ispconfig updates. Which of the perfect server tutorials did you use to install the server for ispconfig, there must be something really wrong in the base setup when a update of ispconfig breaks your server.
I originally installed it a few years ago using the Debian install. The system has worked great for a few years. About a month or two or three ago I updated to the newest version. Just doing the update. a few days or maybe weeks later I one day could not log on anymore. So at that time I did the new install with the updated debian. Complete fresh install even formatted the HDD. I got all done and the email would not work. I have when I got time been looking at settings but changing any. I went to logon today and it was back to the point where I could not log on again. So I was just wondering if anyone had seen this and is there a way to fix it without a full install. I do not think it is Ispconfig I thing something )static maybe ) else is causing the problem. It would just be nice if I could fix it without a full reinstall.
Which tutorial did you use, we have several debian guides? And which errors did you get in the apache error.log?
think this is the one I used http://www.howtoforge.com/perfect-server-debian-wheezy-apache2-bind-dovecot-ispconfig-3 It looks like just cron errors but I have not been able to get my crons to work. The last cron error does not look like anything I did so maybe someone is hacking into my system. This is the last cron errors I have in the log file. [Sun Feb 09 06:35:41 2014] [notice] Digest: generating secret for digest authentication ... [Sun Feb 09 06:35:41 2014] [notice] Digest: done [Sun Feb 09 06:35:41 2014] [notice] Apache/2.2.9 (Debian) DAV/2 PHP/5.2.6-1+lenny16 with Suhosin-Patch mod_ruby/1.2.6 Ruby/1.8.7(2008-08-11) mod_ssl/2.2.9 OpenSSL/0.9.8g configured -- resuming normal operations [Sun Feb 09 06:35:41 2014] [warn] long lost child came home! (pid 15838) [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] --2014-02-09 06:35:57-- http://bestpc.nazwa.pl/fotosen/cron [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] Resolving bestpc.nazwa.pl... [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] 85.128.152.133 [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] Connecting to bestpc.nazwa.pl|85.128.152.133|:80... [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] connected. [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] HTTP request sent, awaiting response... [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] 200 OK [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] Length: 2324 (2.3K) [text/plain] [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] Saving to: `/var/tmp/cron' [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] 0K .. 100% 19.2M=0s [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] [Sun Feb 09 06:35:57 2014] [error] [client 37.187.99.73] 2014-02-09 06:35:57 (19.2 MB/s) - `/var/tmp/cron' saved [2324/2324]
yes, thats looks like a hack attempt. Check which user owns the file /var/tmp/cron to see which website was hacked. and scan your server with rkhunter.
Thanks I will check that. The only website on that server is letsebid,com and I am the only one that should be setting up crons even though I have not been able to get any to work. I have been doing them manualy. So is there a way to restore my ispconfig login without doing a full restore. Thanks you have been a big help.
