RC6 -> RC7

[sci2tech]

(12-19-2008 05:57 PM)xister Wrote:  http://www.isp-control.net/ispcp/changeset/1444

Typo3 was a strong argument, also nuno`s project regarding multiple domains handled by same code did the trick

[nuno]

(12-20-2008 01:49 AM)sci2tech Wrote:  

(12-19-2008 05:57 PM)xister Wrote:  http://www.isp-control.net/ispcp/changeset/1444

Typo3 was a strong argument, also nuno`s project regarding multiple domains handled by same code did the trick

in my Name i want thank for that detail (Karma added)

[Claus]

(12-20-2008 04:17 AM)nuno Wrote:  

(12-20-2008 01:49 AM)sci2tech Wrote:  

(12-19-2008 05:57 PM)xister Wrote:  http://www.isp-control.net/ispcp/changeset/1444

Typo3 was a strong argument, also nuno`s project regarding multiple domains handled by same code did the trick

in my Name i want thank for that detail (Karma added)

Also many thanx for this feature and all your work !!!

[Quattro]

During the upgrade of my ispcp from rc6 to rc 7 something went wrong.
My admin panel won't show up on the domain it always appeared on.
Instead of the admin panel i get one of the subdomains of one of the customers.

my guess is that master doesn't get loaded or matched by a virtual host, but how can i check that?

<edit>
I found my problem, ip of master entry was wrong.
does the script get the ip on execution? if that's the case it detects it wrong. maybe ask the admin on execution if the ip is right.
</edit>

[Pancho]

(12-20-2008 01:49 AM)sci2tech Wrote:   Typo3 was a strong argument, also nuno`s project regarding multiple domains handled by same code did the trick

Thanks scitech for fixing this!

Note that not only Typo3 handles multi-domain installs.
Drupal supports them out of the box, as well.
And, for multi-language sites using subdomains (such as en.foo.bar, de.foo.bar, fr.foo.bar) it obviously relies on all subdomains being routed to the same Drupal install (= mountpoint).
Creating redirects for every subdomain is in these cases not more than a workaround.

From my POV, we should take the opposite direction and allow the whole Second level domain branch with arbitrary subdomains to be directed to the same mountpoint. Which means, we would add the option to delegate the whole subdomain handling to the mountpoint, which may then managed by .htaccess, Drupal or whatever.

The latter, as a feature request, probably won't get into 1.0.0...?
However, as the restriction newly imposed in RC7 breaks support for certain CMS configurations (within RC bugfix period!), to me this even warrants an RC7a or (together with some more fixes) an RC8 in a week or two.

I've not yet worked with ispCPs sources, but am experienced in PHP, so as soon as I find some time, I'm gonna trawl your code and provide a patch adding this feature.

[Pancho]

I'm having another ProFTPd issue on upgrade from RC6 to RC7 on Lenny:

Code:

Starting ftp server: proftpd - warning: the DisplayFirstChdir directive is deprecated and will be removed in a future release.  Please use the DisplayChdir directive.              
- Fatal: unknown configuration directive 'SQLAuthTypes' on line 164 of '/etc/proftpd/proftpd.conf'                                                                                
failed!

DisplayFirstChdir is easily replaced by DisplayChdir, so we get away without that warning.
Now to the fatal error: The reason is that the upgrader seems to comment out the line "SQLBackend mysql" in /etc/proftpd/proftpd.conf.
However, uncommenting this line leads to the next error:

Code:

Starting ftp server: proftpd - Fatal: unknown configuration directive 'SQLBackend' on line 163 of '/etc/proftpd/proftpd.conf'
failed!

Ticket 1528 didn't do the trick. However, it is fixed by wrapping the section of proftpd.conf in <IfModule mod_sql.c> (see http://neomars.com/spip.php?article56).

These three issues should be fixed in RC7a/8 (;-).

edit: Oh now I see that the upgrade also comments out the inclusion of modules.conf:

Code:

#Include /etc/proftpd/modules.conf

Uncommenting this line, we don't need the "<IfModule mod_sql.c>" wrapper, anyway it's better code style though, because loading the module could fail.

[r3r3]

i use roundcube as the webmail in tools/webmail
the upgrade is going to overwrite my roundcube install?

[r3r3]

i upgraded to ispCP RC7 from RC6
fucked up all my config and stuff now half the shit stoped working
yay!
i followed the upgrade routine step by step the perl script said all was fine
main domain = fucked up : error 503
serval of my subdomains : fucked up
custom roundcube mail messed up
none of the email account are actually working
can t even login into ispCP anymore
phpmyadmin : can't login
proftpd : Fail
and probably many other FAIL

lovely

gotta restore a backup now

Code:

Please select from which version you want to update:
        (1) VHCS 2.4.7 or VHCS 2.4.7.1
        (2) VHCS 2.4.8 RC1
        (3) ispCP OMEGA 1.0.0 RC2 (incl. b and c)
        (4) ispCP OMEGA 1.0.0 RC3
        (5) ispCP OMEGA 1.0.0 RC4
        (6) ispCP OMEGA 1.0.0 RC5
        (7) ispCP OMEGA 1.0.0 RC6
        (0) abort
        Your selection: 7
        Stopping ispCP GUI-Backend communication Daemon: ispcp_daemon.
        Stopping ispCP Network Traffic Logger: ispcp_network.
        Upgrading system values...done
        Upgrading database structure...done
        Rebuilding system configurations...
        Please enter ispCP ftp SQL user. [vftp]:

        Please enter ispCP ftp SQL user password. [auto generate]:
        ispCP ftp SQL user password set to: XXXXXXXXXXXXXXXXXXX
done


        Setting GUI Permissions:
        Setting Engine Permissions: .............done
        Rebuilding customers...done
Starting ispCP GUI-Backend communication Daemon: ispcp_daemon.
Starting ispCP Network Traffic Logger: ispcp_network.
Syntax error on line 26 of /etc/apache2/sites-enabled/00_master.conf:
ServerAdmin takes one argument, The email address of the server administrator
httpd not running, trying to start
Stopping Postfix Mail Transport Agent: postfix.
Starting Postfix Mail Transport Agent: postfix.
Stopping domain name service...: bind.
Starting domain name service...: bind.
Stopping Courier POP3 server: pop3d.
Starting Courier POP3 server: pop3d.
Stopping Courier IMAP server: imapd.
Starting Courier IMAP server: imapd.
Stopping ftp server: proftpd.
Starting ftp server: proftpd - processing configuration directory '/etc/proftpd/ispcp'
.
Stopping Courier authentication services: authdaemond.
Starting Courier authentication services: authdaemond.

        Congratulations!

        ispCP '1.0.0 RC7 OMEGA' Update completed successfully!

        Please type XXXXXXXXXXXXXXXXXXX in your browser,
        log in with your Administrator Account and perform
        Database Updates if exists.

XXXXXXXXXXXXXXXXXXX /var/www/ispcp/engine/setup: rm -fR /tmp/ispcp/

[pgentoo]

(12-20-2008 01:49 AM)sci2tech Wrote:  

(12-19-2008 05:57 PM)xister Wrote:  http://www.isp-control.net/ispcp/changeset/1444

Typo3 was a strong argument, also nuno`s project regarding multiple domains handled by same code did the trick

I see that this limitation was removed for alias domains, but it still seems to be enforced for subdomains. The problem is very similar for me as the Typo3 problem. I develop several sites that allow multiple domains to be run off the same DocumentRoot/Database/etc... When I do development for these, i like to just setup a few different subdomains to the site to test the system is working as expected. I suppose I could do just use alias domains instead, but then i have to have multiple free domains to work with.

I could also see myself doing a simliar thing to the language specific sites that another poster mentioned. en.domain.com, es.domain.com, etc...

Would it be possible to remove the limitation for subdomains as well, so two different subdomains can share the same mount point?

Thanks,
pGentoo

[Shayne]

(12-14-2008 06:39 AM)lschafroth Wrote:  My upgrade from RC6 to RC7 went flawlessly.

One questions and maybe I overlooked it. What is the username and password assigned to the awstats folders?

I tried the control panel login for each domain which did not work. I tried the email address and password which did not work.

Lannie

---

(12-14-2008 06:39 AM)lschafroth Wrote:  One questions and maybe I overlooked it. What is the username and password assigned to the awstats folders?

I tried the control panel login for each domain which did not work. I tried the email address and password which did not work.

Nevermind! I found it. Had to login as the domain user, add a user then assign him to the awstats group.

Lannie

Hey Guys I addes the use and assigned him to the group but before I read this I was messing in the config.inc file. Could you tell me what Authentication to use there as I am still trying to loggin. Thanks!