E
Emanuele
Guest
Hi,
While updating base PSA package on a 7.5.3 installation, local EDP people thought the server was hanging (during the loooong quotacheck), and powered it off.
Now update script are messed up (both 7.5.3 and 7.5.4 are stated 'updating', some packages are dated to "January 2039"!) and, worse, horde is not showing up in webmail but the Apache misconfiguration screen...
Now: in order to fix in absence of a full system backup (just psa data dumps), is it suitable to force the installation of all the rpms (/root/psa/7.5.4/...) with a
rpm -Uvh *.rpm
or I risk to compromise some config files or the db structure?
Thank you
While updating base PSA package on a 7.5.3 installation, local EDP people thought the server was hanging (during the loooong quotacheck), and powered it off.
Now update script are messed up (both 7.5.3 and 7.5.4 are stated 'updating', some packages are dated to "January 2039"!) and, worse, horde is not showing up in webmail but the Apache misconfiguration screen...
Now: in order to fix in absence of a full system backup (just psa data dumps), is it suitable to force the installation of all the rpms (/root/psa/7.5.4/...) with a
rpm -Uvh *.rpm
or I risk to compromise some config files or the db structure?
Thank you