Puppet version : 2016 / 4.8
Currently I use the puppet console to view the reports that are generated for the Node. Problem with this view is that it displays the log items one entry at a time. I can go to "Events" and filter by event status (it says Failed) but it still does not provide me the control that I need.
Is there anyway I can pull down the entire log file for one particular server for a certain time range?
I attempted "/pdb/query/v4/reports" uri but my Puppet master does not seem to support it.
Related
We are having some problems while trying to deliver some files in Clearcase .
3 out of 4 files fail with this error:
Error Messages:
An error occurred during the Deliver operation.
An error occurred while merging file elements in the target view.
Unable to perform merge.
Unable to do integration.
This happens after a windows workstation upgrade from Windows 7 to Windows 10, but we are not sure that it's related . We are using a version 8.0.1 CC client. We tried to update the view but this didn't solve the issue.
You need at least to do a cleartool status in the merge destination view, in the parent folder of those failed files.
Either the status can give you a clue, or there is another OS-related reason, like typically a Windows process keeping an handle on the file which should be modified by the merge, preventing (locking) said modification.
Also, check your environment variable, like CLEARCASE_PRIMARY_GROUP to ensure that was not lost during the workstation OS upgrade.
That would be reflected in the properties of the view:
cd /path/to/view/used/for/merge
cleartool lsview -l -full -pro -cview
We tried to update the view but this didn't solve the issue.
"update" means snapshot view.
Nothing prevent to reset/retry your merge using a brand new dynamic view: that would avoid any OS-lock issue.
I have a newly built windows 10 machine. We have a ActiveX control that hooks into Imanage and opens a requested document. On my old machine this ActiveX control worked as expected but on the new PC I am getting a Imanage error dialog.
One or more documents could not be checked out. The operation could not be performed on these document(s). The document XXX could not be checked out. The system cannot find the file specified.
I am using IE 11 with the same security settings. As I am getting an Imanage error, that implies that the ActiveX control is working thus Imanage is the issue?
I am using Filesite 9.3.1 on both machines. I am not an expert on Imanage and how it works so I could be missing something simple.
There are two reasons that this could be happening:
As already mentioned by Yevgeny, the NRT locations may be invalid, the locations are stored in the registry at:
NRTEcho:
HKEY_CURRENT_USER\Software\Interwoven\WorkSite\8.0\Common\General\Echo
NRPortbl:
HKEY_CURRENT_USER\Software\Interwoven\WorkSite\8.0\Common\General\Portable
though this may be different based on your individual iManage implementation.
If this issue is only occurring on certain documents, one's that are created via a script for example. It may be that the files are zero kilobyte. Have seen this happen before when documents are being dynamically created from sharepoint templates.
I am currently trying to automate the process of bamboo remote agent installation and uninstallation. I have run into a problem in regards to adding and removing capabilities.
What I am trying to automate:
(The following is what I do on the bamboo server via the GUI, I want to do this on the remote agent machine via bash script.)
I install the remote agent on a VM machine, then start it up. I go to the bamboo interface and click on the newly created agent's name.
I add a custom capability type, for the key I put 'buildserver' and for the value I put the name of the agent.
I add an 'Executable' capability of type 'Command' with Executable label 'cygwin' and path 'C:\cygwin64\bin\bash'
I navigate to the git executable, and remove it by clicking 'delete.' <--- (the problem step)
what I've done.
I have looked here and found a way to automate steps 1-3 using the following "bamboo-capabilities.properties" file:
buildserver="AGENTNAME"
system.builder.command.cygwin="C:\cygwin64\bin\bash"
However I am stuck on how I would remove the git capability (step 4.) I've tried something appending something like this to the file:
system.git.executable=""
but it does not seem to do anything. Does anyone know how I would do this? There seems to be very little documentation about this online.
Thanks very much.
I never found a way to get around this, but I found a workaround. I later learned the point of removing git in my situation was to allow a shared capability that was also called git to take precedence. My workaround was to set the non-shared capability to the value of the shared capability. I am not 100% sure that this does the same thing, and I am not in a position to test it yet, but as a capability seems to be only a key-value pair I don't see why it wouldn't.... will update if anything breaks.
This appears to be a common error for java. I searched for the error but could find nothing specific to domino and the ACL issue.
I have a couple of java classes in my database. One is a HttpServlet class, the other an IHttpServlet factory. I also added just a regular class to the db for testing.
Any time I make any change to the ACL, the servlet will no longer run. If any of the java source document are open, it shows Resource is out of sync with the file system: mydb.nsf Press F9 or Select File>Refresh to select the file. That test class also displays this message.
I need to refresh the document and rebuild to get the servlet to run.
I was going to submit this to tech support but thought I would ask here first. Hopefully it is an issue that can be easily resolved.
When using Jenkins, it helpfully auto-generates a colorful report filled with all of your results from testing. The issue I'm having, however, is accessing that report.
I have all of my configuration set up the same as all of my other nodes. (I'm using master-slave configuration on Jenkins, with 4 slave node VMs running Win 7 x64.) When I open up Group 5, however, and open the HTML report page, I pick up the below error.
As always, any help is appreciated.
While I apologize for not being able to share any specifics of the error (configuration, etc. I'm under an NDA for that type of thing), I was able to solve my problem.
If you have everything set up for nodes, and are copying files back and forth between the Master and Slave (there's a plugin that allows you to copy files into the workspace before building instead of using an SCM) just don't have the post-build action of "Publish HTML Reports'" option of "Keep past HTML reports" checked. Otherwise you'll end up with file conflicts and you'll have the same 404 status code that I picked up.