Rudder

Hi Daniel,

Sorry for this issue.
We changed a lot this page, especially on the Javascript side. Did you try to shift+f5 (or whatever solution your browser is offering as a solution to completely reload all Javascript)

If it doesn't solves your issue, could you restart the web interface with debug mode (editing the file /opt/rudder/etc/logback.xml, and replace <root level="info"> by <root level="debug">), restart the web interface, reproduce the error and send us the logs ?

Thank you !

Nicolas CHARLES wrote:

Did you have any issues during upgrade from 2.9 to 2.10 ?

The only problem i remember was that after i upgraded the packages and tried to access the interface i was still seeing the old 2.9 interface . I had a few clicks around until I realised that nothing has changed. After I restarted jetty the new interface appeared.
Checking the logs around the update time i see a few warnings and these errors:

2014-06-18 10:14:41.576:INFO::Extract jar:file:/opt/rudder/jetty7/webapps/rudder.war!/ to /tmp/jetty-127.0.0.1-8080-rudder.war-_rudder-any-/webapp
[2014-06-18 10:14:41] ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
net.liftweb.actor.PingerException: com.normation.rudder.batch.StartAutomaticReporting$@90d705a could not be scheduled on com.normation.rudder.batch.AutomaticReportLogger$LAAutomaticReportLogger@514b295a
        at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:72) ~[lift-actor_2.10-2.5.1.jar:2.5.1]
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@6d7e4794 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@7d8d7db4[Shutting down, pool size = 1, active threads = 0, queued tasks = 5, completed tasks = 20064]
        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) ~[na:1.7.0_51]
[2014-06-18 10:14:42] ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
net.liftweb.actor.PingerException: StartUpdate could not be scheduled on com.normation.rudder.batch.AbstractScheduler$StatusManager@70e4c4d2
        at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:72) ~[lift-actor_2.10-2.5.1.jar:2.5.1]
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@197b5857 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@7d8d7db4[Shutting down, pool size = 1, active threads = 0, queued tasks = 4, completed tasks = 20065]
        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) ~[na:1.7.0_51]
Use configuration file defined by JVM property -Dlogback.configurationFile : /opt/rudder/etc/logback.xml

[2014-06-18 10:14:59] ERROR com.normation.cfclerk.services.impl.GitTechniqueReader - Error when processing technique '/system/common/1.0/metadata.xml'
java.util.NoSuchElementException: key not found: MANAGED_NODES_ADMIN
        at scala.collection.MapLike$class.default(MapLike.scala:228) ~[scala-library-2.10.3.jar:na]
[2014-06-18 10:14:59] ERROR bootstrap.liftweb.checks.CheckTechniqueLibraryReload - Flag file '/opt/rudder/etc/force_technique_reload' but Techniques library reload failed, cause is: An error occured while updating <- Error when trying to read technique library
[2014-06-18 10:14:59] INFO  application - Application Rudder started
[2014-06-18 10:15:02] ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
net.liftweb.actor.PingerException: CheckLaunch could not be scheduled on LADatabaseCleaner(ArchiveAction(com.normation.rudder.services.system.DatabaseManagerImpl@6c71a096,AutomaticReportsCleaning(com.normation.rudder.services.system.DatabaseManagerImpl@6c71a096,20,10,Every day at 00:30)),10)

Could it be possible for you to send us a screen snapshot of the Rule page ?

See the attached

I have some more question for you:

• is the error message instantaneous, or is it after a while (like it timeouts)

It is after a while(2-3 seconds after click). It looks like a timeout.

• do you have the same issue on the Node/Reports screen ?

No. I saw similar issues before and they were related to firewall or postgres, but now even with firewall off I have the same problem.

• is you server loaded ?

No. The load is very light.

• do you have error messages in the postgresql log ?

No

I'm sorry for the amount of questions, but I'm trying to figure out what is going on

No problem, you can ask for any information needed.

You used ot have a strange error because of Virtuozzo/Postgrsql ( http://www.rudder-project.org/redmine/issues/4115#change-22255 )
Maybe it is related ?

That problem was solved with a VPS restart. I think postgres didn't properly detect the memory change or something went wrong when the resources were changed but the reboot fixed it .

I attached the screen shot with the errors from the console. Please let me know if you need the response headers too

Thank you for detailed bug report.
I may have found the culprit (wrong naming convention) based on the messages displayed, but I'm really surprised that it causes a problem for you, and not for anyone else, so maybe this may be unrelated.
I'm making a fix for the error "variable i redeclares argument"

ok, the issue was in 2.6, so it's very likely to be unrelated; i'm fixing it thought, in a related ticket

I will need the response from the POST to understand the issue

The issue have been nailed down.
When we have groups with single quote in them, the Rules fail to show because of improper JS escaping

https://github.com/Normation/rudder/pull/559

Applied in changeset eef395efd8c7d5e871a085ddce283a32947b351f.

This bug has been fixed in Rudder 2.10.3 (announcement , changelog) and 2.11.0~beta2 (announcement , changelog), which were released today.

• Download information: https://www.rudder-project.org/site/get-rudder/downloads/