Cannot Uninstall

[tgansert]

Does uninstall need to be run from /tmp?

[root@cpoc ~/ispconfig]$ ./uninstall
No results found![root@cpoc ~/ispconfig]$

This is my error when I attempt to uninstall from /root/ispconfig/uninstall

[till]

Try:

cd /root/ispconfig
./uninstall

If this wont work, you can uninstall ISPConfig by executing:

/etc/init.d/ispconfig_server stop
rm -rf /home/admispconfig
rm -rf /root/ispconfig

[tgansert]

Good times.. I am reinstalling... Something funky happened and ISPConfig was no longer able to make changes to the web root and shadow files and countless other things... Probably my fault. Tweak it 'til it breaks, that's my motto.

[tgansert]

Similar message in reinstall [No results found!]:


Connected successfully to MySQL server
Es ist schon eine Datenbank mit dem Namen db_ispconfig vorhanden!
Restarting some services...
/usr/sbin/apachectl restart: httpd restarted
Stopping mail transport agent: Postfix.
Starting mail transport agent: Postfix.
Restarting ProFTPD ftp daemon.proftpd.
.. - warning: "ProFTPD" address/port (208.44.78.14:21) already in use by "Debian"
proftpd.
done.
Starting ISPConfig system...
/root/ispconfig/httpd/bin/apachectl startssl: httpd started
No results found!FreshClam is already running!
ISPConfig system is now up and running!
Congratulations! Your ISPConfig system is now installed. If you had to install quota, please take the steps described in the installation manual. Otherwise your system is now available without reboot.

[till]

Have you created the database "db_ispconfig" manually?

[tgansert]

At that point, no. I mistakenly omitted a crucial step in the forced uninstall I had to perform: I did not drop the previous database.

After the reinstall, I saw my error and decided to go back to using a database (restore from backup) from when everything was flowers & butterflies.

The database reversion worked quite well. I am sure it is safe to ignore this error, however, I am curious as to it's origin.

[till]

The database reversion worked quite well. I am sure it is safe to ignore this error, however, I am curious as to it's origin.

If the ISPConfig installer is not run in update mode, it expects to be able to create the database itself.