Current time: 09-21-2024, 11:19 AM Hello There, Guest! (LoginRegister)


Thread Closed 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[ERLEDIGT]Kann keine Kunden Anlegen?!
Author Message
wejherowo112 Offline
Newbie
*

Posts: 7
Joined: Jan 2010
Reputation: 0
Post: #5
RE: Kann keine Kunden Anlegen?!
Ich Meinte ehr das! das andere Habe ich ja gefunden!

(01-21-2010 01:24 PM)ZooL Wrote:  ich würde behaupten er hat probleme mit dem lockfile,
PHP Code:
34    function check_for_lock_file() {
35    
36        $fh 
fopen(Config::get('MR_LOCK_FILE'),'r');
37        if (!$fh) {
38            return false;
39        
und mit dem eigentlich geöffneteten port.

PHP Code:
51    function read_line(&$socket) {
52        $ch '';
53        $line '';
54        do {
55            $ch socket_read($socket1);
56            $line $line $ch;
57        } while ($ch != "\r" && $ch != "\n");
58        return $line;
59    
das andere, also der Auszug der daemon.log
Quote:Jan 21 04:33:17 v220100146352439 named[2960]: starting BIND 9.4.2 -u bind
Jan 21 04:33:17 v220100146352439 named[2960]: found 16 CPUs, using 16 worker threads
Jan 21 04:33:17 v220100146352439 named[2960]: loading configuration from '/etc/bind/named.conf'
Jan 21 04:33:17 v220100146352439 named[2960]: no IPv6 interfaces found
Jan 21 04:33:17 v220100146352439 named[2960]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 21 04:33:17 v220100146352439 named[2960]: listening on IPv4 interface eth0, 78.47.79.115#53
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: D.F.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 8.E.F.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: 9.E.F.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: A.E.F.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: automatic empty zone: B.E.F.IP6.ARPA
Jan 21 04:33:17 v220100146352439 named[2960]: command channel listening on 127.0.0.1#953
Jan 21 04:33:17 v220100146352439 named[2960]: zone 0.in-addr.arpa/IN: loaded serial 1
Jan 21 04:33:17 v220100146352439 named[2960]: zone 127.in-addr.arpa/IN: loaded serial 1
Jan 21 04:33:17 v220100146352439 named[2960]: zone 255.in-addr.arpa/IN: loaded serial 1
Jan 21 04:33:17 v220100146352439 named[2960]: zone localhost/IN: loaded serial 2
Jan 21 04:33:17 v220100146352439 named[2960]: zone admin.v220100146352439.yourvserver.net/IN: loaded serial 2010012100
Jan 21 04:33:17 v220100146352439 named[2960]: running
Jan 21 04:33:17 v220100146352439 named[2960]: zone admin.v220100146352439.yourvserver.net/IN: sending notifies (serial 2010012100)
Jan 21 04:33:17 v220100146352439 mysqld_safe[3089]: started
Jan 21 04:33:17 v220100146352439 mysqld[3092]: 100121 4:33:17 InnoDB: Started; log sequence number 0 43655
Jan 21 04:33:17 v220100146352439 mysqld[3092]: 100121 4:33:17 [Note] /usr/sbin/mysqld: ready for connections.
Jan 21 04:33:17 v220100146352439 mysqld[3092]: Version: '5.0.51a-3ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3130]: Upgrading MySQL tables if necessary.
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3136]: Looking for 'mysql' in: /usr/bin/mysql
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3136]: Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3136]: This installation of MySQL is already upgraded to 5.0.51a, use --force if you still need to run mysql_upgrade
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3146]: Checking for insecure root accounts.
Jan 21 04:33:18 v220100146352439 /etc/mysql/debian-start[3150]: Checking for crashed MySQL tables.
Jan 21 04:33:18 v220100146352439 proftpd[3326]: v220100146352439.yourvserver.net - ProFTPD 1.3.1 (stable) (built Thu Feb 21 04:50:29 UTC 2008) standalone mode STARTUP
Jan 21 04:33:18 v220100146352439 ispcp_daemon[3436]: ispCP daemon v1.1 started!
Jan 21 04:41:44 v220100146352439 ispcp_daemon[31644]: child 31644 started !
Jan 21 04:41:44 v220100146352439 ispcp_daemon[3436]: EINTR was received ! continue;
Jan 21 05:00:05 v220100146352439 ispcp_daemon[1212]: child 1212 started !
Jan 21 05:00:05 v220100146352439 ispcp_daemon[3436]: EINTR was received ! continue;
(This post was last modified: 01-22-2010 12:22 AM by ZooL.)
01-21-2010 05:41 PM
Find all posts by this user
Thread Closed 


Messages In This Thread
RE: Kann keine Kunden Anlegen?! - ZooL - 01-21-2010, 01:24 PM
RE: Kann keine Kunden Anlegen?! - 4tux - 01-21-2010, 05:16 PM
RE: Kann keine Kunden Anlegen?! - wejherowo112 - 01-21-2010 05:41 PM
RE: Kann keine Kunden Anlegen?! - ZooL - 01-22-2010, 12:21 AM

Forum Jump:


User(s) browsing this thread: 3 Guest(s)