+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: ispCP Omega 1.0.0 RC5 (/thread-3503.html)
ispCP Omega 1.0.0 RC5 - Sea - 06-12-2008 05:48 PM
Where to find file - ispcp-omega-1.0.0-rc5.tar.bz2
(http://www.isp-control.net/ispcp/browser/trunk/docs/CentOS/INSTALL)
(http://www.isp-control.net/ispcp/changeset/1095?format=diff&new=1095)
RE: ispCP Omega 1.0.0 RC5 - Zothos - 06-12-2008 07:52 PM
not released yet. Some bugs need to be closed first. But i have so less time
RE: ispCP Omega 1.0.0 RC5 - Sea - 06-12-2008 09:16 PM
When is RC5 ?
RE: ispCP Omega 1.0.0 RC5 - Zothos - 06-12-2008 10:39 PM
done when its done...
RE: ispCP Omega 1.0.0 RC5 - DaSilva - 06-16-2008 12:04 AM
I got this message at upgrade:
Quote: You can ignore this error: /bin/sed: can't read php.ini: No such file or directory
Use of uninitialized value in regexp compilation at ispcp-update line 724.
/bin/sed: kann php.ini nicht lesen: Datei oder Verzeichnis nicht gefunden
...(many many times again!)
Is this a problem?
Debian Etch 64 - Update from RC4 to RC5
RE: ispCP Omega 1.0.0 RC5 - RatS - 06-16-2008 01:19 AM
If you could read ...
RE: ispCP Omega 1.0.0 RC5 - DaSilva - 06-16-2008 01:44 AM
Now I have a really big problem:
After the update are most of the domains unreachable.
Only few are reachable.
What can I do?
RE: ispCP Omega 1.0.0 RC5 - sci2tech - 06-16-2008 01:57 AM
What is the status in table domain for the unreacheable domains?
If ok restart apache2 and bind9 solve the problem?
If both answers is no regenerating the domains file solve the problem?
If no logs say anything?
If no can you put here the settings file for one domain (bind and apache) to see what the problem is?
RE: ispCP Omega 1.0.0 RC5 - DaSilva - 06-16-2008 02:21 AM
The status for all domains are OK.
No restart helps (I have rebooted the whole server, too!)
The logs don't report errors.
The strange thing is that all domains are reachable if I put an entry of that domain in my local hosts file. So it seems that some domains cannot resolved by their IP but two domains with the same name server set have a different status. One is reachable, the other not. What could be the problem?
EDIT: It seems to be a problem with nameservers. ns1.frefel.net doesn't work, ns1.s-dns.de works. What can I do?
RE: ispCP Omega 1.0.0 RC5 - sci2tech - 06-16-2008 02:34 AM
DaSilva Wrote:The strange thing is that all domains are reachable if I put an entry of that domain in my local hosts file.Means that bind server don`t work or a wrong zone was propagated and is still cached. To check if bind is running try
Quote:ps aux | grep bindTo check how a zone is served from server use
Quote:dig @ip_of_your_domain domain_that_cant_be_reach anyand see the answer.
if the answer is ok then try
Quote:dig @your_local_dns domain_that_cant_be_reach any. Compare the result.
Logs from bind (case of debian) ar in /var/log/syslog and /var/log/daemon.log search for anything regarding bind (try a /etc/init.d/bind9 restart before checking to force logging of any errors).
at end put here zone definition for zone and .db file for one domain that don`t work. (debian case zone are defined in /etc/bind/named.conf and the /var/cache/bind/domian.db)