while it works in command line
and apt+python is a bit too much for me
@peckpeck may know (https://issues.rudder.io/issues/17917#note-10)
bye, good night!
the < /dev/null seems to indicate that
Policy update process was stopped due to an error:
⇨ Policy update error for process '3815' at 2020-07-09 13:03:45
⇨ Cannot write nodes configuration
⇨ Accumulated: Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects. ; Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects. ; Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects.
can you share the technique (screenshot ? or export it ?) cc @VinceMacBuche ?
last week, you advised me to store the hooks and files I wanted to share from the server into :
myserver:/var/rudder/configuration-repository/shared-files/my_custom_folder
This folder is itself a git clone.
When upgrading, the upgrade script warned me about the fact that this content won't get included in the rudder's git management, that was perfectly correct to me.
About the error above : when returning into the technique editor, I got a warning about an unsaved config (though there were none) and the 'my_custom_folder' mentioned above.
I suddenly feel the urge to ask if this place really was the best choice, if it can cause troubles?
myserver:/var/rudder/configuration-repository/shared-files/my_custom_folder
This folder is itself a git clone.
When upgrading, the upgrade script warned me about the fact that this content won't get included in the rudder's git management, that was perfectly correct to me.
About the error above : when returning into the technique editor, I got a warning about an unsaved config (though there were none) and the 'my_custom_folder' mentioned above.
I suddenly feel the urge to ask if this place really was the best choice, if it can cause troubles?
I'm not sure how/why git share would impact that
cc @VinceMacBuche who would perhaps know
techniques resources are different from /var/rudder/configuration-repository/shared-files/my_custom_folder, and you cannot use a git repository as resource from a technique (but from shared files yes)
Do you have files in /var/rudder/configuration-repository/techniques/ ncf_techniques/sit___upgrade_rudder_agent__debian_like_/1.0/resources/shared-files ?
Do you have resources defined for
technique sit___upgrade_rudder_agent__debian_like_ in the web interface ?
Did you used to have some resources and moved them to the /var/rudder/configuration-repository/shared-file without deleting them ?
Ok, so I'm only using /var/rudder/configuration-repository/shared-files/sit-rudder (which was cloned from our own git repo) to share files with the "File download (Rudder server)" directive.
Following your advice, I also created a cron that regularly does a git pull, so yes, things are moving there.
In /var/rudder/configuration-repository/techniques/ncf_techniques/sit_upgrade_rudder_agentdebianlike/1.0, I only have : metadata.xml technique.cf technique.json technique.ps1
Yes, I have a Directive that is using the sit_upgrade_rudder_agentdebianlike technique (if this was your question, about ressource?)
Before knowing how to manage my own git repo, yes, I had two files directly in /var/rudder/configuration-repository/shared-file, but I have deleted them. They are now in /var/rudder/configuration-repository/shared-files/sit-rudder
Following your advice, I also created a cron that regularly does a git pull, so yes, things are moving there.
In /var/rudder/configuration-repository/techniques/ncf_techniques/sit_upgrade_rudder_agentdebianlike/1.0, I only have : metadata.xml technique.cf technique.json technique.ps1
Yes, I have a Directive that is using the sit_upgrade_rudder_agentdebianlike technique (if this was your question, about ressource?)
Before knowing how to manage my own git repo, yes, I had two files directly in /var/rudder/configuration-repository/shared-file, but I have deleted them. They are now in /var/rudder/configuration-repository/shared-files/sit-rudder
update : in /var/rudder/configuration-repository, I've had a look at 'git status', and I saw that shared-files/sit-rudder was unmanaged by git.
At first, I thought that I didn't want to disturb the inner Rudder mecanism, so I added shared-files/sit-rudder in /var/rudder/configuration-repository/.gitignore, and commited.
But when later trying to modify some custom techniques, I saw that Rudder was blocked (I think) by this .gitignore addition.
I removed it, then I tried to ADD shared-files/sit-rudder in git management. And commited.
At this point, everything began to work : I was able to regenerate the policies, I had no error in the technique editor.
At first, I thought that I didn't want to disturb the inner Rudder mecanism, so I added shared-files/sit-rudder in /var/rudder/configuration-repository/.gitignore, and commited.
But when later trying to modify some custom techniques, I saw that Rudder was blocked (I think) by this .gitignore addition.
I removed it, then I tried to ADD shared-files/sit-rudder in git management. And commited.
At this point, everything began to work : I was able to regenerate the policies, I had no error in the technique editor.
A simple workaround is to install the new dependencies (
jqfor 6.0) as part of the Rudder upgrade policy
In the technique I made to upgrade the rudder-agent package, I also added another 'Package present' method with the jq package. I see that jq has been installed, but rudder-agent has not been upgraded. This workaround is not working.
@necarnot Can you send me the metadata.xml and the technique.json file of the technique
sit___upgrade_rudder_agent__debian_like_ ? you can send them by mail vincent@rudder.io
I don't understand how comes I don't get banned out of this chat? ;)
like "testd" here
"Source path, relative to /var/rudder/configuration-repository/shared-files/ " parameter
you can type "sit-rudder" maybe in the quicksearch bar to help you find it
I have a dozen of "File download (Rudder server)" directives that are using a file from /var/rudder/configuration-repository/shared-files/sit-rudder to spread them to some nodes. In each directive, the source path is sit-rudder/my_custom_file01, 02...
Is there any problem doing so?
Is there any problem doing so?
no not at all but you have one directive/technique that looks for a template / file in
/var/rudder/configuration-repository/techniques/ ncf_techniques/sit___upgrade_rudder_agent__debian_like_/1.0/resources/shared-files but it should not and I'm looking for this technique/directive and it's not the one i asked you first
and the workaround is not working around