ISPConfig 2.2.7-RC1 available for testing

Ill try it on a CentOS 4.4 this weekend !

 

I think I will wait for the 'final' version

 

Ill install it on a virtual machine, not in production, obviously.

If you didnt test it as beta you will find a lot of bugs on final versions, look .5 and .6

 

Testing ISPConfig 2.2.7 RC1

Falko & Till,

I have updated from ISPConfig 2.2.6 to 2.2.7 RC1 on a 32 bit Debian Sarge testing server.

This is my experience:

The whole ./setup procedure was perfect and without errors, so that's good.

When i visited the ISPControlpanel to login at http://192.168.0.10:81 (the address of my testingserver on my LAN) i see an error, which says:

Parse error: syntax error, unexpected ';' in /home/admispconfig/ispconfig/lib/config.inc.php on line 102

When i restart ISPConfig 2.2.7 RC1 (as root) with the command:

/etc/init.d/ispconfig_server restart

This happens:

shell-init: could not get current directory: getcwd: cannot access pa rent directories: No such file or directory
shell-init: could not get current directory: getcwd: cannot access pa rent directories: No such file or directory
Shutting down ISPConfig system...
shell-init: could not get current directory: getcwd: cannot access pa rent directories: No such file or directory
/root/ispconfig/httpd/bin/apachectl stop: httpd stopped
ISPConfig system stopped!
shell-init: could not get current directory: getcwd: cannot access pa rent directories: No such file or directory
Starting ISPConfig system...
shell-init: could not get current directory: getcwd: cannot access pa rent directories: No such file or directory
/root/ispconfig/httpd/bin/apachectl startssl: httpd started

Parse error: syntax error, unexpected ';' in /home/admispconfig/ispco nfig/lib/config.inc.php on line 102
ISPConfig system is now up and running!


----

I guess there is more work to do before releasing ISPConfig 2.2.7

 

Hallo

Update from 2.2.6 to 2.2.7-RC1 with Suse 9.3 worked fine.
I got one errormessage:
Parse error: syntax error, unexpected ';' in /home/admispconfig/ispco nfig/lib/config.inc.php on line 102
ISPConfig system is now up and running!

- Bugfix: Customers can now delete their own databases working

Version still says 2.2.6


Edi

 

I've corrected the error by changing the line 102 within file /home/admispconfig/ispconfig/lib/config.inc.php.

Change line 102 from:

$go_info["server"]["sudo_du_enabled"] = ; // enable sudo for gathering website file usage

into:

$go_info["server"]["sudo_du_enabled"] = false; // enable sudo for gathering website file usage

After that restart ISPConfig to see if there are no more errors:

/etc/init.d/ispconfig_server restart

Now, finally we can login into ISPConfig at http://www.mydomain.tld:81 to check more...

 

I upgraded Debian 3.1 V2.2.6 to the new V2.2.7 ok also however I had the same error as HANS at the end.

Made the same fix as HANS and seems ok so far... Will test it out...

 

This happens because you run the command from within the install_ispconfig directory which doesn't exist anymore after the installation. Nothing to worry about.

 

Do you know the value of that variable prior to updating? Was it set to false?

 

@ Falko,

Yes i checked line nr. 102 at one of my production servers, running 2.2.6 and indeed it was set to false

 

Thanks! I've just fixed the problem in the svn repository.

 

2.2.7 Bugs

Im testing it, ill put a list of bugs here..

1.- I guess you save the site settings even when mistakes are found.

Example: Create a reseller with 0 databases. Create a site for this reseller without databases. Modify the site to add one database (the reseller has no databases), an error message appears, but the "MySQL" and "1" are saved.

2.- Its may be related with number 1. When you create a site and there is a mistake (too many space, databases, anything) you still take the ID from the database... its not a bug, but it will be nice to check first, then save.

3.- Im installing joomla, everything seems to be right, just a little detail:

Session save path Unwriteable
/var/www/web2/phptmp/

If you can set the owner to apache it would be great !

4.- I tried to add databases to the reseller, its fine, but when i saved appears a message "The reseller already has some DNS records, the DNS manager can not be desactivated" or something similar, so, the dns manager is active now. But what if i dont want this reseller to handle the dns server?

I tried to add, delete, move sites, create users, delete, ive check how many time the recicler bin is "busy" everything seems to be ok !!! il test it a few more days to check webalizer and another cron jobs but everything seems to be great !!!

-----------------------------
EDIT: @Fabio: Moved that post here so that we have everything regarding the 2.2.7 in the rc-state in one thread...

 

Falko & Till,

Today, i had some time to test the ISPConfig 2.2.7-RC1.
I am not able to test everything, but i want you to know that i did not find any major bugs anymore!

I hope that others will have a look to this version too, and report their experiences here.

One more personal note:
I'm happy that we've the possibility to test RCs before the official version comes out!

 

MySQL isn't displayed in the web interface if the reseller is not allowed to create MySQL databases. In the field web_mysql in the isp_isp_web table you'll find a 0 which means this web site isn't allowed to create MySQL databases.

The phptmp directory has 777 permissions, so everyone can write to it.

If the reseller can create DNS records and has done so already, and now you want to take this permission from him, you'll see the error message that the reseller already has some DNS records. If you still want to take this permission from him, you first have to delete his DNS records.

 

falko,

I had the same problem, I saw before if $go_info["server"]["sudo_du_enabled"] = false; // enable sudo for gathering website file usage had false, and had. I put false after installation.

I decompress the installation file and the problem with restart was gone.

I followed your guide to Perfect Install in Ubuntu server. I don't know waht happend or what I do to do this error:

root@sol:~# /etc/init.d/bind9 restart
* Stopping domain name service...
rndc: connect failed: connection refused [ ok ]
* Starting domain name service... [ ok ]

Do you have any tip?

Thanks,

Vinicius

 

mmm yes, it was there.. that what i did, step by step. The problem is the webinterface modify the the mysql check and db accounts but didnt create them (its fine, cause the erseller has no databases), but every operation send errors, as no mysql dbs can be created..

Joomla sends errors till i set apache as owner, the same with the web folder.

No, he was not able to access the dns manager, the dns records were created adding sites. i dont want to allow my resellers to get into the dns admin.

 

SpamAssassin 3.1.6 is now available

Hi,

FYI, you might consider updating to 3.1.6 since it was just released.

Thanks!

 

I do not know if Falko/Till can release this version of Spamassassin within ISPConfig 2.2.7.

If they can, it would be nice, as the latest version of Spamassassin contain some bugfixes.