gentoo: Warnung bei Installation und kein Zugriff aufs Panel

[GhostTyper]

Hallo,

 

ich habe gerade auf ein frisch aufgesetztes gentoo froxlor ?ber das layman overlay installiert (http://redmine.froxlor.org/projects/froxlor/wiki/Installing_Froxlor-09_on_Gentoo_Linux). Nach dem Beantworten der Fragen von: emerge --config www-apps/froxlor beim einf?gen der IP-Adresse in die mysql-Datenbank ist das Query fehlgeschlagen. Alle anderen Querys liefen durch (=die datenbank wurde erstellt, etc.).

 

Als ich dann versucht habe auf die Seite von Froxlor zuzugreifen bekam ich HTTP/403. Im apache-log f?r den froxlor vhost sehe ich:

 

 

[sun Mar 18 13:05:23 2012] [error] [client <meineip>] client denied by server configuration: /var/www/froxlor/index.php

[sun Mar 18 13:05:23 2012] [error] [client <meineip>] client denied by server configuration: /var/www/froxlor/favicon.ico

 

kann ich den fehlenden eintrag manuell nachtragen oder k?nnte der fehler insgesamt an meiner systemkonfiguration liegen?

 

das system wurde zuvor frisch mit folgenden globalen use-flags aufgesetzt:

 

mmx perl python sse sse2 utf8 nls unicode -gtk -gnome -qt -X -cups -kde -dvd -alsa -cdr -dvdr -opengl -ipv6 -java

 

und folgenden paketspezifischen use-flags:

 

 

www-apps/froxlor fcgid

net-libs/courier-authlib mysql

net-ftp/proftpd mysql

dev-libs/cyrus-sasl mysql

www-servers/apache suexec

dev-lang/php cgi ftp gd mysql pcntl bcmath xsl apache2

mail-mta/postfix sasl mysql

media-libs/gd png jpeg

 

mg

[GhostTyper]

Ich habe jetzt nochmals versucht zu installieren und zuvor sicher gestellt, dass auch wirklich alle domain-namen auf die korrekte ip zeigen. dabei sind mir beim setup noch zwei weitere fehler aufgefallen:

 

 

/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2504: vhostcontainer: Kommando nicht gefunden.

/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2504: vhostcontainer_servername_statement: Kommando nicht gefunden.

ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' ) VALUES ('80.255.8.104', '80', '1', '1', '1')' at line 1

[GhostTyper]

Es sieht so aus, wie wenn die Zeile:

 

 

INSERT INTO \`panel_ipsandports\` (\`ip\`, \`port\`, \`namevirtualhost_statement\`, `vhostcontainer`, `vhostcontainer_servername_statement`) VALUES ('${serverip}', '80', '1', '1', '1');

 

so aussehen sollte:

 

 

INSERT INTO \`panel_ipsandports\` (\`ip\`, \`port\`, \`namevirtualhost_statement\`, \`vhostcontainer\`, \`vhostcontainer_servername_statement\`) VALUES ('${serverip}', '80', '1', '1', '1');

 

ich guck' mal, ob ich das irgendwie ab?ndern kann, bzw. ob es ausreicht die jetzt fehlende zeile manuell einzutragen.

[GhostTyper]

Nein, das f?hrt leider auch nicht zur L?sung. Es folgt sp?ter noch ein weiterer Fehler:

 

chattr: Unpassender IOCTL (I/O-Control) f?r das Ger?t beim Lesens der Flags in //var/www/php-fcgi-scripts/froxlor.panel/froxlor.example.net/php-fcgi-starter

 

Ich habe beim durchbl?ttern aber gelesen, dass das an reiserfs liegen k?nnte. Das k?nnte also daf?r sorgen, dass index.php nicht anstartet, nicht aber, dass favicon.ico nicht erlaubt ist.

 

Hat jemand eine Idee, woher diese Fehler kommen k?nnten?

[mark.doe]

Same here!

 

Ich kann einfach froloxor nicht ans laufen kriegen!

 

here der Log:

 

froxlor # emerge --config froxlor


Configuring pkg...

* Gentoo-Froxlor Basic Configuration

* This will setup Gentoo-Froxlor on your system, it will create and
* populate the MySQL database, create and chmod the needed files
* correctly and configure all services to work out-of-the-box
* with Gentoo-Froxlor, using a sane default configuration, and
* start them, along with creating the correct Gentoo-Froxlor Apache
* VirtualHost for you.
* CAUTION: this will backup and then replace your services
* configuration and restart them!

* Do you want to proceed? [Y/N]

> y


* Enter the domain under wich Froxlor shall be reached, this normally
* is the FQDN (Fully Qualified Domain Name) of your system.
* If you don't know the FQDN of your system, execute 'hostname -f'.
* This installscript will try to guess your FQDN automatically if
* you leave this field blank, setting it to the output of 'hostname -f'.

> xxx.xxxxxx.xxx


* Enter the IP address of your system, under wich all
* websites shall then be reached. This must be the same
* IP address the domain you inserted above points to.
* You *must* set this to your correct IP address.

x.x.x.x


* Enter the IP address of the MySQL server, if the MySQL
* server is on the same machine, enter 'localhost' or
* simply leave the field blank.

>


* Enter the username of the MySQL root user.
* The default is 'root'.

>


* Enter the password of the MySQL root user.

>

* Confirm the password of the MySQL root user.

>

* Enter the name of the database you want to
* use for Froxlor. The default is 'froxlor'.
* CAUTION: any database with that name will
* be dropped!

>


* Enter the username of the unprivileged
* MySQL user you want Froxlor to use.
* The default is 'froxlor'.
* CAUTION: any user with that name will
* be deleted!

>


* Enter the password of the unprivileged
* MySQL user.

>

* Confirm the password of the unprivileged
* MySQL user.

>

* Enter the username of the admin user you
* want in your Froxlor panel.
* Default is 'admin'.

>


* Enter the password of the Froxlor admin user.

>

* Confirm the password of the Froxlor admin user.

>

* Adding MySQL server to 'default' runlevel ...
* rc-update: mysql already installed in runlevel `default'; skipping
* (Re)Starting MySQL server ...
* WARNING: you are stopping a sysinit service
* Stopping mysql ...
[ ok ]
* Starting mysql ...
[ ok ]
* Creating temporary work directory ...
* Preparing SQL database files ...
* Creating Froxlor database ...
* Installing SQL database files ...
* Adding system ip/port to database
/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2566: vhostcontainer: Kommando nicht gefunden.
/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2566: vhostcontainer_servername_statement: Kommando nicht gefunden.
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' ) VALUES ('x.x.x.x', '80', '1', '1', '1')' at line 1
* Adding Froxlor admin-user
* Deleting SQL database files ...
* Installing Froxlor data file ...
* Creating needed SSL certificates ...
* Please enter the correct input when it's requested.
*
* ATTENTION: when you're requested to enter a
* 'Common Name' enter xxx.xxxxxxx.xxxx.
*
Generating RSA private key, 2048 bit long modulus
.................+++
...............+++
e is 65537 (0x10001)
Enter pass phrase for //etc/ssl/server/xxx.xxxxxxx.xxxx.key:
Verifying - Enter pass phrase for //etc/ssl/server/xxx.xxxxxxx.xxxx.key:
Enter pass phrase for //etc/ssl/server/xxx.xxxxxxx.xxxx.key:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:NL
State or Province Name (full name) [some-State]:Limburg
Locality Name (eg, city) []:
Organization Name (eg, company) [internet Widgits Pty Ltd]:solandor.tk
Organizational Unit Name (eg, section) []:
Common Name (e.g. server FQDN or YOUR name) []:
Email Address []:

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Enter pass phrase for //etc/ssl/server/xxx.xxxxxxx.xxxx.orig:
writing RSA key
* You can now submit //etc/ssl/server/xxx.xxxxxxx.xxxx.csr
* to an official CA (Certification Authority) to be
* signed (with costs) or you can sign it yourself (free).
* For more informations regarding SSL please visit:
* http://httpd.apache.org/docs/2.0/ssl/ssl_intro.html

* Do you want to self-sign your certificate? [Y/N]

> y


Signature ok
subject=/C=NL/ST=Limburg/O=solandor.tk
Getting Private key
* Writing Gentoo-Froxlor vhost configuration ...
* Configuring nginx

ssl on;
ssl_certificate /etc/ssl/server/xxx.xxxxxxx.xxxx.pem
/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2779:
ssl_certificate_key /etc/ssl/server/xxx.xxxxxxx.xxxx.pem: Datei oder Verzeichnis nicht gefunden
/var/tmp/portage/www-apps/froxlor-0.9.26/temp/environment: Zeile 2780: : Kommando nicht gefunden.
* Modifying nsswitch.conf to use MySQL ...
* Configuring ProFTPd ...
* Configuring Gentoo-Froxlor cronjob ...
* Configuring Dovecot-IMAP ...
* Configuring Postfix ...
* Creating aliases.db for postfix ...
* Configuring Bind ..
* Add Gentoo-Froxlor include to Bind configuration ...
* Adding apache2 to 'default' runlevel ...
* rc-update: apache2 already installed in runlevel `default'; skipping
* (Re)Starting apache2 ...
* Caching service dependencies ...
[ ok ]
* Starting apache2 ...
[ ok ]
* Adding vixie-cron to 'default' runlevel ...
* rc-update: vixie-cron already installed in runlevel `default'; skipping
* (Re)Starting vixie-cron ...
* Stopping vixie-cron ...
[ ok ]
* Starting vixie-cron ...
[ ok ]
* Adding named to 'default' runlevel ...
* rc-update: named already installed in runlevel `default'; skipping
* (Re)Starting named ...
* Starting named ...
* Checking named configuration ...
[ ok ]
* start-stop-daemon: failed to start `/usr/sbin/named'
[ !! ]
* ERROR: named failed to start
* Adding proftpd to 'default' runlevel ...
* rc-update: proftpd already installed in runlevel `default'; skipping
* (Re)Starting proftpd ...
* Starting ProFTPD ...
[ !! ]
* ERROR: proftpd failed to start
* Adding dovecot to 'default' runlevel ...
* rc-update: dovecot already installed in runlevel `default'; skipping
* (Re)Starting dovecot ...
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'imaps' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'pop3s' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:13: ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:36: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:38: passdb sql {} has been replaced by passdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:42: userdb prefetch {} has been replaced by userdb { driver=prefetch }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:45: userdb sql {} has been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:49: auth_user has been replaced by service auth { user }
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'imaps' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'pop3s' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:13: ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:36: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:38: passdb sql {} has been replaced by passdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:42: userdb prefetch {} has been replaced by userdb { driver=prefetch }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:45: userdb sql {} has been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:49: auth_user has been replaced by service auth { user }
* Starting dovecot ...
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'imaps' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'pop3s' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:13: ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:36: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:38: passdb sql {} has been replaced by passdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:42: userdb prefetch {} has been replaced by userdb { driver=prefetch }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:45: userdb sql {} has been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:49: auth_user has been replaced by service auth { user }
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'imaps' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:2: 'pop3s' protocol is no longer necessary, remove it
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:13: ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:36: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:38: passdb sql {} has been replaced by passdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:42: userdb prefetch {} has been replaced by userdb { driver=prefetch }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:45: userdb sql {} has been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:49: auth_user has been replaced by service auth { user }
[ ok ]
* Adding dkim-filter to 'default' runlevel ...
* service dkim-filter added to runlevel default
* (Re)Starting dkim-filter ...
* Starting DKIM filter ...
dkim-filter: /etc/mail/dkim-filter/dkim-filter.conf: /etc/mail/dkim-filter/my-selector-name.private: stat(): No such file or directory
* start-stop-daemon: failed to start `/usr/sbin/dkim-filter'
[ !! ]
* ERROR: dkim-filter failed to start
* Adding nscd to 'default' runlevel ...
* rc-update: nscd already installed in runlevel `default'; skipping
* (Re)Starting nscd ...
* Shutting down Name Service Cache Daemon ...
[ ok ]
* Starting Name Service Cache Daemon ...
[ ok ]
* Adding postfix to 'default' runlevel ...
* rc-update: postfix already installed in runlevel `default'; skipping
* (Re)Starting postfix ...
* Stopping postfix (/etc/postfix) ...
[ ok ]
* Starting postfix (/etc/postfix) ...
[ ok ]
* Configuration completed successfully!
*
* You can now open your Froxlor under https://www.xxxxxxxxx.xxx/index.php

 

von hier an geht nichts.

 

 

Zudem muss ich anmerken:

#required by www-apps/froxlor-0.9.26[domainkey,bind], required by froxlor (argument)

# /usr/portage/profiles/package.mask:

# Eray Aslan <eras@gentoo.org> (10 Apr 2012)

# Dead upstream. Use mail-filter/opendkim instead.

# Removal in 30 days - bug 411429

=mail-filter/dkim-milter-2.8.3-r1

 

--> opendkim ist eh besser.

 

 

Basis: gentoo/funtoo stable

[mark.doe]

ich kann leider bei Bugs nichts Posten.

Das ist schade!

[d00p]

Das ebuild ist uralt und wird anscheinend nicht mehr gepflegt, konfigurier Froxlor lieber manuell. Das emerge'n sollte noch korrekt funktionieren, allerdings ist die config-routine nicht mehr aktuell. Statt diese aufzurufen, schau, dass du via http://[ip]/froxlor auf das panel kommst (apache sollte im normalfall daf?r ausreichend konfiguriert sein, von haus aus) und folge da den Installationsanweisungen

[mark.doe]

Alles klar, danke dir, ich teste das mal aus.

[mark.doe]

ich kann best?tigen das der h?ndische Install funktioniert !

[d00p]

Klar tut er das W?r auch bitter wenn nicht oder?