Activity
From 2016-04-13 to 2016-04-13
2016-04-13
- 21:02 Revision 5c4976fa (rudder): Merge branch 'branches/rudder/3.2'
- 21:02 Revision 2f7d05c5 (rudder): Merge branch 'branches/rudder/3.2'
- 19:20 Bug #7735: OOM in Rudder when there are too many repaired reports
To reproduce, go to the Rudder server, connect to Postgres ();
Then get an example of event logs: ...- 13:15 Bug #7735: OOM in Rudder when there are too many repaired reports
- By the way, we should not let Rudder in such a pity state, and simply find a solution for #5617
- 18:17 Bug #8177 (Pending release): Broken rudder-server-roles.conf prevent reporting in distributed setup
- Applied in changeset commit:rudder|b0a654219523d30be920b186879724168d0316c1.
- 18:06 Bug #8177 (Pending technical review): Broken rudder-server-roles.conf prevent reporting in distributed setup
- PR https://github.com/Normation/rudder/pull/1076
- 18:05 Bug #8177 (In progress): Broken rudder-server-roles.conf prevent reporting in distributed setup
- 18:04 Bug #8177 (Released): Broken rudder-server-roles.conf prevent reporting in distributed setup
- Since rudder 3.2 we don't produce valid rudder-server-roles.conf files
For each role, we assign their key in the c... - 18:16 Revision 0dad163a (rudder): Merge pull request #1076 from VinceMacBuche/bug_8177/broken_rudder_server_roles_conf_prevent_reporting_in_distributed_setup
- Fixes #8177: Broken rudder-server-roles.conf prevent reporting in distributed setup
- 18:16 Revision 8881c20e (rudder): Merge pull request #1076 from VinceMacBuche/bug_8177/broken_rudder_server_roles_conf_prevent_reporting_in_distributed_setup
- Fixes #8177: Broken rudder-server-roles.conf prevent reporting in distributed setup
- 18:06 Revision 8aac0b0e (rudder): Fixes #8177: Broken rudder-server-roles.conf prevent reporting in distributed setup
- 18:06 Revision b0a65421 (rudder): Fixes #8177: Broken rudder-server-roles.conf prevent reporting in distributed setup
- 17:00 User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception)
- Benoit, could you please find what it would take to have a cron script (or promise) looking in the log and checking f...
- 16:48 User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception)
- To better explain why the -XX:OnOutOfMemoryError is not a very good solution:
On a VM with 2,5G of RAM, default Ce... - 13:16 User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception)
- We could also make the OOM detection be done in a cron, looking in the last log, and restarting Rudder when Needed.
- 13:13 User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception)
- Some more info: http://stackoverflow.com/questions/12096403/java-shutting-down-on-out-of-memory-error
- 16:57 Question #8176: All nodes compliance report unexpected/missing except root server.
- Thanks for the quick reply,
What exactly do you mean with time delay? If you mean network wise, Ping times are les... - 16:30 Question #8176: All nodes compliance report unexpected/missing except root server.
- Hello Siemen, thank for reporting your issue!
Is there a time delay on the node and the root server ?
Can you ... - 15:59 Question #8176 (Resolved): All nodes compliance report unexpected/missing except root server.
- All the nodes we have connected are reporting as 50%missing/50%unexpected for all compliance reports.
Example:
Th... - 15:04 Bug #8175 (Rejected): Transitory error message when upgrading to 3.1 to 3.2 in rudder agent run
- I upgraded Rudder server from 3.1 to 3.2
right after, I ran rudder agent run, and got following error message:
<pre... - 13:25 User story #4519: Add caching information to static JS/CSS resources
- Some more information:
- if we use something maven-related, we will need to translate it for each non-maven projec... - 13:05 User story #4519: Add caching information to static JS/CSS resources
- We could add the version number in the js file, by takeing the version defined in the pom.xml
ref: http://stackover... - 13:19 User story #8173: Change paragraph order in Documentation
- That would be much appreciate. Today, "Configuration Management" at root level is very misleading. As an user, I'm su...
- 11:10 User story #8173 (Rejected): Change paragraph order in Documentation
- While doing #8169, we had the idea to change of the documentation is organized.
First in #8169, We added a section... - 12:47 Bug #8163 (Rejected): Error when clicking on Node details
- I'm rejecting it, as it occurs only once, with browser that already saw the failing page.
- 12:23 Bug #8163: Error when clicking on Node details
- i upgraded from 3.0.15 to 3.1.9, and got the same issue...
- 12:19 Bug #7800: Firefox stalls after TLS handshake on self signed certificate with a missing contact email
- removing all old certificates fixes the issue, thank you Francois
- 12:06 Bug #7800: Firefox stalls after TLS handshake on self signed certificate with a missing contact email
- Perhaps you have far too many broken certificates already present, and they have side effects.
Could you remove a... - 11:13 Bug #7800: Firefox stalls after TLS handshake on self signed certificate with a missing contact email
- After about 10 minutes, I get:
Le certificat n'est pas sûr car il est auto-signé. Le certificat n'est valide que pou... - 10:55 Bug #7800: Firefox stalls after TLS handshake on self signed certificate with a missing contact email
- Using Firefox 44.0.2, Rudder 3.0.15 and rudder-tests current master, I still have the issue
- 11:47 User story #4670: Allows inventories to be augmented by the user with custom properties
For future implementation: Fusion allows to extend what go in the report like that: http://fusioninventory.org/docu...- 09:54 Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters
- In pré-3.1, conf file for rudder-jetty was user modifiable in /opt/rudder/etc/rudder-jetty.conf; starting of 3.1 it ...
- 09:35 Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters
- Could you specify what are the files that are reverted, and that should not ?
There is a multitude of way to chan... - 06:32 Bug #8172 (Released): Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters
- On SLES11, upgrading from 2.11 to 3.1 on SLES 11 failed to preserve the configured java parameters, and restored defa...
- 06:23 Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/default
- Somehow, the migration script seems to be failing on SLES
Also available in: Atom