error 1.0.0 -> 1.0.3

[Zeitkind]

Hi,
missing the other updates, I today tried to update to 1.0.3.1
Debian 4, was running RC's and 1.0.0 for months without problems.
Did apt-get install & update & upgrade, all went fine till perl scipt:

Rebuilding all customer configuration files
Please wait, this may take some time:DEBUG: push_el() sub_name: rebuild_customers_cfg(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: sys_command_rs(), msg: Starting...
DEBUG: push_el() sub_name: sys_command_rs(), msg: Ending...
DEBUG: push_el() sub_name: exit_msg(), msg: Starting...
[failed]


FATAL: An error was occured during update process!

Any ideas? I don't find any more info, a tail -f /tmp/ispcp-update-customers.log is empty.

[Zeitkind]

The last entry in mysql.log is:

212 Query update domain_aliasses set alias_status='ok' where alias_id = 21
100101 22:55:59 212 Quit
9 Query select subdomain_alias_id, subdomain_alias_name, subdomain_alias_status from subdomain_alias where subdomain_alias_status != 'ok' order by subdomain_alias_id
9 Query select alias_id, alias_name, alias_status from domain_aliasses where alias_status = 'delete' order by alias_id
100101 22:56:04 9 Quit

Then the error in the update-script comes up.

[Zeitkind]

_Fixed_

Solution:
apt-get -t etch-backports install libapache2-mod-fcgid

[bulkmania]

(01-02-2010 09:53 AM)Zeitkind Wrote:  _Fixed_

Solution:
apt-get -t etch-backports install libapache2-mod-fcgid

any other ideas ? cause i have the same problem and your solution is not working for me cause mine is already libapache2-mod-fcgid is already the newest version.

[tomdooley]

(01-02-2010 06:48 PM)bulkmania Wrote:  

(01-02-2010 09:53 AM)Zeitkind Wrote:  _Fixed_

Solution:
apt-get -t etch-backports install libapache2-mod-fcgid

any other ideas ? cause i have the same problem and your solution is not working for me cause mine is already libapache2-mod-fcgid is already the newest version.

Yes there is. I had the same issues described here. Following steps helped me to get the update to success:

1. Check if you have a valid value for DEFAULT_ADMIN_ADDRESS in ispcp.conf and ispcp.old.conf.
2. Edit /etc/ispcp/apache/fcgid_ispcp.conf and comment out the last configuration option (MaxRequestsPerProcess).
3. Repeat the last step for /etc/ispcp/apache/working/fcgid_ispcp.conf if this option is also in this file.

This should solve the problem. To validate if there is not another Apache configuration error for Etch, you have to edit also the fcgid_ispcp.conf in /etc/apache2/mods-available and validate your changes by /etc/init.d/apache2 restart.

[kilburn]

Keep in mind that you fist have to add an etch-backports source to your /etc/apt/sources.list and execute "apt-get update" before running the "apt-get -t etch-backports install libapache2-mod-fcgid".

Upgrading to this version is highly recommended because the older, etch (non-backport) one is known to have some memory issues, random failures, etc..

[tomdooley]

(01-02-2010 08:22 PM)kilburn Wrote:  Keep in mind that you fist have to add an etch-backports source to your /etc/apt/sources.list and execute "apt-get update" before running the "apt-get -t etch-backports install libapache2-mod-fcgid".

Upgrading to this version is highly recommended because the older, etch (non-backport) one is known to have some memory issues, random failures, etc..

OK, you are right. I did not know this way. Installed the package -> running with default configuration. :-)

[Nuxwin]

(01-02-2010 08:22 PM)kilburn Wrote:  Keep in mind that you fist have to add an etch-backports source to your /etc/apt/sources.list and execute "apt-get update" before running the "apt-get -t etch-backports install libapache2-mod-fcgid".

Upgrading to this version is highly recommended because the older, etch (non-backport) one is known to have some memory issues, random failures, etc..

@Kilburn ;

Can you adds the fcgid backports issue int the INSTALL file (only for etch) ?

Thanks in advance

[Zeitkind]

If you're (like me..) still running Etch for some reasons, it's a good idea to add some repositories:

#volatile
deb http://volatile.debian.org/debian-volatile etch/volatile main contrib non-free
deb http://volatile.debian.org/debian-volatile etch/volatile-sloppy main contrib non-free

#Backports
deb http://www.backports.org/debian etch-backports main contrib non-free

Volatile is for newer versions of eg. clamav and backports adds some newer stuff - like the one missing for the 1.0.3.1 update.
Backports are not installed automatically, you have to force install by giving the source:

apt-get -t etch-backports install libapache2-mod-fcgid

And before, you should also install the keyring:

apt-get install debian-backports-keyring

I had some other minor issues (like a double entry in named.conf), but that might be because of the failed updates. Another thing that was not so good: the update overwrote my main.cf from postfix without making a backup before (but I did...). I had enabled TLS and had added a bunch strict rules (like smtpd_junk_command_limit = 10) and some whitelist stuff (like check_client_access cidr:/etc/postfix/postfix-dnswl-permit) and enabled amavis. So check your postfix after the update (postconf -n).

[tomdooley]

I'm using backports since maia integration (clamav/spamassassin).

You're right, the postfix configuration has been overwritten... Had to reenable amavis... Thanks for your reply!