ISPconfig installation broke

Hello again,
I have a serious problem with my installation.
ISPconfig seems to not respond any more. Let me explain. It was working fine. I had it up to date and centos is up to date with yum update. At 23:26 i tried to disable a disable a dns zone, so i went to the ispconfig control panel, at the dns and made a zone inactive but had the feeling that the zone didn't deactivated because i was doing "dig example.com" and return my ip address. I checked /etc/named.conf.local and the zone was there, waited some minutes and desided to restart named. The zone was still there. Deleted the zone and restarted the server but the zone still there. Then i tried adding a new zone but the zone wasn't added. At the ISPConfig it looks like it is added and the one i tried to delete isn't there but it's still in the /etc/named.conf.local file.
Then i checked the monitor of the server and everything looks like to have stopped at 23:25. No logs are read from the monitor after that.
I checked the syslog and the log is working.
At the time of the issue the syslog says:

Code:

Mar  4 23:24:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Mar  4 23:25:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] New connection from 127.0.0.1
Mar  4 23:25:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Mar  4 23:25:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] New connection from 127.0.0.1
Mar  4 23:25:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Mar  4 23:26:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] New connection from 127.0.0.1
Mar  4 23:26:01 s1 pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Mar  4 23:29:24 s1 named[31585]: received control channel command 'stop'
Mar  4 23:29:24 s1 named[31585]: shutting down: flushing changes
Mar  4 23:29:24 s1 named[31585]: stopping command channel on 127.0.0.1#953
Mar  4 23:29:24 s1 named[31585]: no longer listening on 127.0.0.1#53
Mar  4 23:29:24 s1 named[31585]: no longer listening on 79.143.178.166#53
Mar  4 23:29:24 s1 named[31585]: no longer listening on ::1#53
Mar  4 23:29:24 s1 named[31585]: no longer listening on fe80::250:56ff:fe3c:1318%2#53
Mar  4 23:29:24 s1 named[31585]: exiting
Mar  4 23:29:26 s1 named[21033]: starting BIND 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 -u named
Mar  4 23:29:26 s1 named[21033]: built with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--target=x86_64-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-libtool' '--localstatedir=/var' '--enable-threads' '--enable-ipv6' '--with-pic' '--disable-static' '--disable-openssl-version-check' '--with-dlz-ldap=yes' '--with-dlz-postgres=yes' '--with-dlz-mysql=yes' '--with-dlz-filesystem=yes' '--with-gssapi=yes' '--disable-isc-spnego' '--with-docbook-xsl=/usr/share/sgml/docbook/xsl-stylesheets' '--enable-fixed-rrset' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'target_alias=x86_64-redhat-linux-gnu' 'CFLAGS= -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' 'CPPFLAGS= -DDIG_SIGCHASE'
Mar  4 23:29:26 s1 named[21033]: ----------------------------------------------------
Mar  4 23:29:26 s1 named[21033]: BIND 9 is maintained by Internet Systems Consortium,
Mar  4 23:29:26 s1 named[21033]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Mar  4 23:29:26 s1 named[21033]: corporation.  Support and training for BIND 9 are
Mar  4 23:29:26 s1 named[21033]: available at [url]https://www.isc.org/support[/url]
Mar  4 23:29:26 s1 named[21033]: ----------------------------------------------------
Mar  4 23:29:26 s1 named[21033]: adjusted limit on open files from 4096 to 1048576
Mar  4 23:29:26 s1 named[21033]: found 1 CPU, using 1 worker thread
Mar  4 23:29:26 s1 named[21033]: using up to 4096 sockets
Mar  4 23:29:26 s1 named[21033]: loading configuration from '/etc/named.conf'
Mar  4 23:29:26 s1 named[21033]: using default UDP/IPv4 port range: [1024, 65535]
Mar  4 23:29:26 s1 named[21033]: using default UDP/IPv6 port range: [1024, 65535]
Mar  4 23:29:26 s1 named[21033]: listening on IPv4 interface lo, 127.0.0.1#53
Mar  4 23:29:26 s1 named[21033]: listening on IPv4 interface eth0, 79.143.178.166#53
Mar  4 23:29:26 s1 named[21033]: listening on IPv6 interface lo, ::1#53
Mar  4 23:29:26 s1 named[21033]: listening on IPv6 interface eth0, fe80::250:56ff:fe3c:1318%2#53
Mar  4 23:29:26 s1 named[21033]: generating session key for dynamic DNS
Mar  4 23:29:26 s1 named[21033]: sizing zone task pool based on 10 zones
Mar  4 23:29:26 s1 named[21033]: set up managed keys zone for view _default, file 'dynamic/managed-keys.bind'
Mar  4 23:29:26 s1 named[21033]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 0.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 127.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 254.169.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Mar  4 23:29:26 s1 named[21033]: 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
Mar  4 23:29:26 s1 named[21033]: 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
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: D.F.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 8.E.F.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 9.E.F.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: A.E.F.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: B.E.F.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Mar  4 23:29:26 s1 named[21033]: command channel listening on 127.0.0.1#953
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.mpineliki.gr:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone mpineliki.gr/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.riosif.gr:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone riosif.gr/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.k00.me:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone k00.me/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.yh5.org:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone yh5.org/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.containersband.tk:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone containersband.tk/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.riosif.tk:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone riosif.tk/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.sirosnews.tk:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone sirosnews.tk/IN: loaded serial 2013021210
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.syrosnews.tk:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone syrosnews.tk/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: /var/named/pri.yourhost5.tk:11: ignoring out-of-zone data (166.178.143.79.in-addr.arpa)
Mar  4 23:29:26 s1 named[21033]: zone yourhost5.tk/IN: loaded serial 2013021101
Mar  4 23:29:26 s1 named[21033]: managed-keys-zone ./IN: loaded serial 0
Mar  4 23:29:26 s1 named[21033]: running
Mar  4 23:29:26 s1 named[21033]: zone yh5.org/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone containersband.tk/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone sirosnews.tk/IN: sending notifies (serial 2013021210)
Mar  4 23:29:26 s1 named[21033]: zone mpineliki.gr/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone k00.me/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone riosif.tk/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone syrosnews.tk/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone yourhost5.tk/IN: sending notifies (serial 2013021101)
Mar  4 23:29:26 s1 named[21033]: zone riosif.gr/IN: sending notifies (serial 2013021101)
Mar  4 23:30:57 s1 named[21033]: received control channel command 'stop'
Mar  4 23:30:57 s1 named[21033]: shutting down: flushing changes
Mar  4 23:30:57 s1 named[21033]: stopping command channel on 127.0.0.1#953
Mar  4 23:30:57 s1 named[21033]: no longer listening on 127.0.0.1#53
Mar  4 23:30:57 s1 named[21033]: no longer listening on 79.143.178.166#53
Mar  4 23:30:57 s1 named[21033]: no longer listening on ::1#53
Mar  4 23:30:57 s1 named[21033]: no longer listening on fe80::250:56ff:fe3c:1318%2#53
Mar  4 23:30:57 s1 named[21033]: exiting
Mar  4 23:30:57 s1 named[21136]: starting BIND 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 -u named

Please help me. I had the same issue before and reinstalled... i don't want to reinstall again... maybe it's a permissions problem. Is there any way to fix permissions? Or what to try?

Thanks

PS: I'm sorry, i'm in a panic and forgot to tell that i have a centos 6.3 server with latest ispconfig installed.

 

See debug instructions in irst post of this orum.

 

Thanks,
i did as it says for debug my installation and get this error:

Code:

05.03.2013-23:56 - DEBUG - There is already an instance of server.php running. Exiting.

How can i fix that?(i'll google it and try to find a solution but reply here too in case i find nothing)

Update:

Code:

[root@s1 www]# rm -f /usr/local/ispconfig/server/temp/.ispconfig_lock
[root@s1 www]# /usr/bin/php -q /usr/local/ispconfig/server/server.php
06.03.2013-00:03 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
06.03.2013-00:03 - DEBUG - Found 368 changes, starting update process.
06.03.2013-00:03 - DEBUG - Calling function 'update' from plugin 'shelluser_base_plugin' raised by event 'shell_user_update'.
PHP Fatal error:  Call to undefined function posix_getgrnam() in /usr/local/ispconfig/server/plugins-available/shelluser_base_plugin.inc.php on line 165

What should i do to work that out?

Thanks!

 

Cent OS / RHEL comes with Posix functions disabled by default. Try:

Code:

$ [sudo] yum install php-process

followed by restarting Apache (and PHP-FPM, if you are using it).

EDIT: It also looks like you have a large number of pending updates (368). Be careful.

 

The php posix functions seem to be missing in your php binary or you disabled it in php.ini. Please install the php posix functions package from centos if it is not installed and check your php.ini if you disabled it otherwise.

 

Thank you both very much! It worked and fixed the problem! You saved me from hours of work!
For future reference the problem was that ISPConfig was not writing at the hard disk.
I commented out the server.sh cron job:

Code:

#* * * * * /usr/local/ispconfig/server/server.sh > /dev/null >> /var/log/ispconfig/cron.log

then i run

Code:

rm -f /usr/local/ispconfig/server/temp/.ispconfig_lock
/usr/bin/php -q /usr/local/ispconfig/server/server.php

I had to install posix with:

Code:

yum install php-process

Rerun previous 2 commands. The missing updates updated and problem solved!!

Thanks!!

Do you have any clue what could cause the problem? What is causing ISPconfig to stop writing?

 

The missing posix functions stopped the ispconfig process. It might be that the posix function wer not required in 3.0.4.6.

 

Thanks again very much!
Should i keep posix enabled or disable it?