+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 (/thread-10789.html)
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - thoand - 06-04-2010 06:55 PM
Hi,
(06-04-2010 06:06 PM)mr.x Wrote: Can you please activate DEBUG mode in /etc/ispcp/ispcp.conf, create a new domain and provide us the log files,
I activated the debug output and created a domain. You can find the output of /var/log/ispcp/ispcp-dmn-mngr.stdout in the attached file. Are there other logs I should post?
/thoand
PS: I had to compress it because it was too large
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - mr.x - 06-04-2010 06:57 PM
Hi,
(06-04-2010 06:55 PM)thoand Wrote: Hi,
(06-04-2010 06:06 PM)mr.x Wrote: Can you please activate DEBUG mode in /etc/ispcp/ispcp.conf, create a new domain and provide us the log files,
I activated the debug output and created a domain. You can find the output of /var/log/ispcp/ispcp-dmn-mngr.stdout in the attached file. Are there other logs I should post?
Is there an error as well?
/Mr.X
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - thoand - 06-04-2010 07:00 PM
Sorry I had forgotten to write, that there is a /var/log/ispcp/ispcp-dmn-mngr.stderr too, but it is empty.
/thoand
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - mr.x - 06-04-2010 07:08 PM
Hi,
(06-04-2010 07:00 PM)thoand Wrote: Sorry I had forgotten to write, that there is a /var/log/ispcp/ispcp-dmn-mngr.stderr too, but it is empty.
ok, but there are a lot of error already in your provided file.
like:
Code:
msg: ERROR: '{AWSTATS_ENGINE_DIR}' eq '{AWSTATS_ENGINE_DIR}', missing '{AWSTATS_ENGINE_DIR}' in src !
msg: ERROR: '{APACHE_LOG_DIR}' eq '{APACHE_LOG_DIR}', missing '{APACHE_LOG_DIR}' in src !
msg: ERROR: '{AWSTATS_WEB_DIR}' eq '{AWSTATS_WEB_DIR}', missing '{AWSTATS_WEB_DIR}' in src !
msg: ERROR: '{CMD_CAT}' eq '{CMD_CAT}', missing '{CMD_CAT}' in src !
...Are you running your system with real customers or can we create ispcp from scratch?
If so, please follow the first steps (1-9) mentioned here:
Code:
4) Installation
53 ---------------
54 Make sure you are logged in as root and MySQL is running.
55
56 1. Untar or unzip the distribution files to a secure directory:
57 # cd /usr/local/src
58 # tar xjvf ispcp-omega-1.0.5.tar.bz2
59
60 2. Change to the newly created directory:
61 # cd ./ispcp-omega-1.0.5
62
63 3. Install the required packages
64
65 First update your system:
66 # aptitude update && aptitude safe-upgrade
67
68 Make sure you have added the non-free into your /etc/apt/sources.list:
69
70 Lenny:
71 deb http://ftp.debian.org/debian/ lenny main contrib non-free
72 deb http://security.debian.org/ lenny/updates main contrib non-free
73
74 Squeeze:
75 deb http://ftp.debian.org/debian/ squeeze main contrib non-free
76 deb http://security.debian.org/ squeeze/updates main contrib non-free
77
78 Install all required packages:
79
80 # aptitude install lsb-release
81 # aptitude install $(cat ./docs/Debian/debian-packages-`lsb_release -cs`)
82
83 (if you get to the courier screen select 'no' to web directories)
84 (if you get to the postfix screen select 'internet site'. 'mail name' should
85 be the server's domain. If you've set debian up correctly on install your
86 domain should be already shown.)
87 (if you get to the proftpd screen, select 'standalone')
88
89 4. (optional) Check the ispcp.conf and adapt it to your requirements.
90
91 5. Build the Software by using make:
92 # make install
93
94 6. Copy all the directories into your system. If you have not yet, now is a good
95 time to make backups of your server. The following steps do fundamental
96 changes to your system configuration.
97 # cp -R /tmp/ispcp/* /
98
99 7. Change or create MySQL root password, remove anonymous users, disallow root
100 login remotely, remove test database (and access to it), reload privilege tables.
101 # mysql_secure_installation
102
103 8. Now it's time to set up the frontend. Change into the engine directory and
104 start the engine setup:
105 # cd /var/www/ispcp/engine/setup
106 # perl ispcp-setup/Mr.X
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - thoand - 06-04-2010 07:28 PM
Hi,
it is a system with real customers. It was a debian etch with ispCP 1.0.0rc2 which I upgraded to lenny with ispCP 1.0.5. The problem occures directly after upgrading form 1.0.0rc2 to 1.0.5. (I upgraded to 1.0.0 final first)
If it is possible to import former customers including email accounts (they are in use and work fine) and ftp accounts. A new installation could be a way, but actually I think fixing the problem should be more "easy".
/thoand
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - gOOvER - 06-04-2010 07:40 PM
Please Note: with release of 1.0.6 Etch will not longer supported from ispCP
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - thoand - 06-04-2010 07:46 PM
therefore I upgraded to lenny...
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - thoand - 06-07-2010 08:38 PM
Hi,
we have decided to reinstall ispCP. I have tested it with just doing an perl isp-setup in /var/www/ispcp/engine/setup/, that works fine for a new domain. But an already existing domain does not work by this way. So how do I completly remove it? Does a perl ispcp-uninstall what I want?
regards, thoand
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - mr.x - 06-07-2010 09:03 PM
Hi,
(06-07-2010 08:38 PM)thoand Wrote: Hi,
we have decided to reinstall ispCP. I have tested it with just doing an perl isp-setup in /var/www/ispcp/engine/setup/, that works fine for a new domain. But an already existing domain does not work by this way. So how do I completly remove it? Does a perl ispcp-uninstall what I want?
regards, thoand
you can update the DB for the existing domains to "change" or "toadd".
/Mr.X
RE: no mySQL access via Joomla after update from 1.0.0rc2 to 1.0.0 to 1.0.5 - joximu - 06-08-2010 01:15 AM
Also:
rename or remove the php.ini for the "to-be-rnewed" domains in /var/www/fcgi/domain/*...
so theese files will be created newly!
/J