Project

General

Profile

Actions

Bug #8172

closed

Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters

Added by Nicolas CHARLES about 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
1
Category:
Server components
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

On SLES11, upgrading from 2.11 to 3.1 on SLES 11 failed to preserve the configured java parameters, and restored default config file (with only 1 GB allocated to webapp)


Subtasks 1 (0 open1 closed)

Bug #8648: Previous merge broke a binary file: rsyslog-4.8.0.tar.bz2ReleasedAlexis MOUSSET2016-07-07Actions

Related issues

Related to Rudder - Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/defaultReleasedBenoît PECCATTE2015-06-19Actions
Related to Rudder - Bug #7850: Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAPRejectedActions
Related to Rudder - Bug #7166: Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systemsReleasedNicolas CHARLES2015-09-04Actions
Related to Rudder - Bug #8418: Configuration files do not get updated when user has modified the stock onesNewActions
Actions

Also available in: Atom PDF