1.0.2 -> 1.0.3-1: config files don't get regenerated

[lbm]

Hi all,
I got some problems after updating ICPCP from 1.0.2 to 1.0.3 on Debian Lenny.

Firstly
/etc/apache2/sites-available/ispcp.conf
did not get updated. The newly generated file has been pretty much empty after the "# Header End" line. In consequence every customer domain has been "routed" to the control panel. Well, no worries I used the backup and the server is running.

I got the same problem with binds named.conf. This one also did not show the domains after the "//bind Data BEGIN." line.
For bind I could again used the backup to keep the system running. Anyways, now the ispCP Debugger (in the WebFrontend) keeps telling me the following for every domain and every alias:

get_tag() | ERROR: '// bind Data BEGIN. ' ne '// bind Data END. ', '// bind Data END. ' overlaps '// bind Data BEGIN. ' in src !

I've seen ticket 159 ( http://isp-control.net/ispcp/ticket/159 ) and checked /etc/bind/* with the "file" command but it did not tell me anything about "CRLF line terminators" for any file.

The structure of named.conf looks like this

Code:

// "header stuff"
// bind Data BEGIN.

// dmn [xy] cfg entry BEGIN.
zone "xy" {
        type    master;
        file    "/var/cache/bind/xy.db";
        notify  YES;
};
// dmn [xy] cfg entry END.

// ...the dmn thing (harhar) for each domain...

// dmn [{DMN_NAME}] cfg entry BEGIN.
// dmn [{DMN_NAME}] cfg entry END.

// bind Data END.

Maybe someone got a clue? I'd appreciate any help to make the debugger friendly again .

For both files (apache2/ispcp.conf & named.conf) it would be nice to find a "ispCP-template-structure-plain-unmodified-file" (errr - you know what I mean?), such that I can check the structure of my files against them manually (just to be sure for the next update). But I don't know where to look for them

Thank you very much and cheers,
Thorsten