[SOLVED] Install goes fine but web gui doesn't work

[slimdanny]

here's what I get when I navigate to my web server

Code:

Notice: Undefined index: LOGIN_TEMPLATE_PATH in /var/www/ispcp/gui/include/system-message.php on line 37

Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/system-message.tpl) is not within the allowed path(s): (/var/www/ispcp/gui/:/etc/ispcp/:/var/run/ispcp.lock:/proc/:/bin/df:/bin/mount:/var/log/rkhunter.log:/var/log/chkrootkit.log:/usr/share/php/) in /var/www/ispcp/gui/include/system-message.php on line 39

Notice: Undefined index: LOGIN_TEMPLATE_PATH in /var/www/ispcp/gui/include/system-message.php on line 41
ERROR: Unable to connect to SQL server !
SQL returned: Can't create UNIX socket (12)

Any ideas?
Thanx[/code]

[slimdanny]

To clarify
It's the RC3 release from sourceforge

system debian 4.0

[gOOvER]

Did you follow the installguide?

[StevenE]

had the same problem with my first freebsd installation I'd fixed it just by change the LOGIN_TEMPLATE_PATH in the file to the path where it lays

for me it looks like this:
system-message.php:

// If we are on the login page, path will be like this
// $template = $cfg['LOGIN_TEMPLATE_PATH'].'/system-message.tpl';
$template = '../themes/omega_original/system-message.tpl';

if (!is_file($template)) {
// But if we're inside the panel it will be like this
$template = '../themes/omega_original/system-message.tpl';
}



hope it will help

[slimdanny]

gOOvER:
yes I followed the install guide for my distro.

to StevenE:
I'll try that, see if it works.
However, we shouldn't be hacking code here, maybe there's another workaround.

[slimdanny]

To: StevenE
you workaround semi works, not a good way of approaching the problem though.

I'm still getting this msg:

ERROR: Unable to connect to SQL server !
SQL returned: Can't create UNIX socket (12)

[slimdanny]

so I restarted mysql..
and it doesn't fire up. same error message: Can't create UNIX socket (12)

has anyone dealt with this?

[slimdanny]

Up and running!.

my virtual machine socket limit was set to 120 ... so the system was running out of them pretty quick.

Thank you everyone.