I just started a 30 day trial of Artifactory Pro and Xray on prem, stood up using docker-compose.
Most functionality is working fine, however when I try to sync the Xray vulnerability DB through the UI, it fails. Looking at the xray server service log I see:
2021-08-03T08:54:44.091Z [33m[jfxr ][0m [1m[31m[ERROR][0m [f1000c9d14bbcc48] [updates_job:389 ] [main ] Updates worker id 0 failed to download updates from https://jxray.jfrog.io/api/v1/updates/onboarding?version=3.25.1: failed to get online updates
--- at /go/src/jfrog.com/xray/internal/jobs/scanner/scanner_job.go:793 (DownloadOnlineUpdates) ---
Caused by: Failed to access :https://jxray.jfrog.io/api/v1/updates/onboarding?version=3.25.1 return status code : 401
2021-08-03T08:54:44.091Z [33m[jfxr ][0m [1m[31m[ERROR][0m [f1000c9d14bbcc48] [updates_job:341 ] [main ] failed to Download online updates
--- at /go/src/jfrog.com/xray/internal/jobs/updates_job.go:397 (UpdatesJob.downloadUpdateUrlsAndLastUpdateTime) ---
Caused by: failed to get online updates
--- at /go/src/jfrog.com/xray/internal/jobs/scanner/scanner_job.go:793 (DownloadOnlineUpdates) ---
Caused by: Failed to access :https://jxray.jfrog.io/api/v1/updates/onboarding?version=3.25.1 return status code : 401
2021-08-03T08:55:01.076Z [33m[jfxr ][0m [34m[INFO ][0m [ ] [samplers:327 ] [main ]
I get a similar response if I switch to offline sync and run the offline update:
~/src/artifactory ❯ jfrog xr offline-update --license-id=[redacted for posting] --version=3.25.1
[Info] Getting updates...
[Error] Response: Server response: 401 Unauthorized
I'm assuming this is a licensing problem? Any suggestions please? - I'm assuming the xray trial includes access to the vulnerability DB?
The issue seems to be related to the Xray trial license not being added correctly as 401 means license validation is failing at the JFrog end. Kindly confirm if the Xray trial license is added correctly under the UI --> Administration --> License | Xray trial license. Also, refer to this KB article for more insights.
Seems to be an issue with the license. I signed up for another trial, and used the xray license on my existing cluster. It initially failed in the same way, but shortly afterwards I was able to do an offline download (and when that worked, I tried an online sync which did work).
Related
I am not able to set up SCM import or export to my repo on Bitbucket. I did not have such an issue before, in other words, I configure my project SCM exactly the same as on my current instance, but for a new RD instance that runs on RHEL 8.6 I get an error.
Please help.
My repo is setup with ssh access key
Failed cloning the repository from ssh://git#stash.ilabs.io:7999/qaiac/rd-draftpaper.git: ssh://git#stash.ilabs.io:7999/qaiac/rd-draftpaper.git: remote hung up unexpectedly
apiversion : 41
base : /var/lib/rundeck
build : 4.6.1-20220914
buildGit : v4.6.1-0-gc78ff2c
Log file
[2022-10-03T21:15:17,193] ERROR transport.TransportImpl [sshj-Reader-stash.ilabs.io/199.119.122.142:7999] - Dying because - Session has timed out waiting for authentication after 120000 ms.
net.schmizz.sshj.transport.TransportException: Session has timed out waiting for authentication after 120000 ms.
at net.schmizz.sshj.transport.TransportImpl.gotDisconnect(TransportImpl.java:533) ~[sshj-0.33.0.jar:?]
at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:489) [sshj-0.33.0.jar:?]
at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:113) ~[sshj-0.33.0.jar:?]
at net.schmizz.sshj.transport.Decoder.received(Decoder.java:200) ~[sshj-0.33.0.jar:?]
at net.schmizz.sshj.transport.Reader.run(Reader.java:60) [sshj-0.33.0.jar:?]
That is a known issue, the solution is to regenerate the keys in this (ed25519 format) way.
This error is popping-up intermittently while trying to deploy my github webpages. I have no clue what to do, I already deleted and recreated the repository but the error persists. I have the same problem for all my github pages repositories.
Here is one repository example: https://github.com/cnftstats/borgs
Run actions/deploy-pages#v1
Actor: github-pages[bot]
Action ID: 1998855719
Artifact URL: https://pipelines.actions.githubusercontent.com/odmqpuZ7yGar25NNWIM53v9pBjO9vEwDjecGIYtf9ECZfcxi8V/_apis/pipelines/workflows/1998855719/artifacts?api-version=6.0-preview
{"count":1,"value":[{"containerId":359584,"size":14684160,"signedContent":null,"fileContainerResourceUrl":"https://pipelines.actions.githubusercontent.com/odmqpuZ7yGar25NNWIM53v9pBjO9vEwDjecGIYtf9ECZfcxi8V/_apis/resources/Containers/359584","type":"actions_storage","name":"github-pages","url":"https://pipelines.actions.githubusercontent.com/odmqpuZ7yGar25NNWIM53v9pBjO9vEwDjecGIYtf9ECZfcxi8V/_apis/pipelines/1/runs/21/artifacts?artifactName=github-pages","expiresOn":"2022-06-15T13:26:01.9505756Z","items":null}]}
Creating deployment with payload:
{
"artifact_url": "https://pipelines.actions.githubusercontent.com/odmqpuZ7yGar25NNWIM53v9pBjO9vEwDjecGIYtf9ECZfcxi8V/_apis/pipelines/1/runs/21/artifacts?artifactName=github-pages&%24expand=SignedContent",
"pages_build_version": "bf8f96d22c5dd116a5d94ee24cd398bdda60035f",
"oidc_token": "***"
}
Failed to create deployment for bf8f96d22c5dd116a5d94ee24cd398bdda60035f.
{"message":"Deployment request failed for bf8f96d22c5dd116a5d94ee24cd398bdda60035f due to in progress deployment. Please cancel e92de3f483b775a12d4f784d7cc661ff2847fa62 first or wait for it to complete.","documentation_url":"https://docs.github.com/rest/reference/repos#create-a-github-pages-deployment"}
Error: Error: Request failed with status code 400
Error: Error: Request failed with status code 400
Sending telemetry for run id 1998855719
GitHub Actions is currently experiencing degraded performance and published this on their status page. Therefore, you are most likely experiencing a side effect of the current problems. Other users are reporting the same issue as well. Try again later when the issue has been resolved by GitHub.
Update: More products are now affected and experience degraded performance. Check their status page for more details: https://www.githubstatus.com
[It was a bug of GitHub, happens to all its users---date: 18/03/2022]
It happens to me today too.. :(
Maybe is a bug of GitHub pages: https://github.com/actions/deploy-pages/issues/22
https://github.community/t/pages-deploy-wedged-incorrect-request-failed-due-to-in-progress-deployment/234793/4
I tried to update an existing jenkins stack from https://github.com/widdix/aws-cf-templates and just modified the jenkins rpm and the AWS AMI Versions.
But on updating the stack I get this error message:
2019-12-17 19:14:16 UTC+0100 vpc-ci-jenkins UPDATE_ROLLBACK_IN_PROGRESS The following resource(s) failed to update: [MasterASG].
2019-12-17 19:14:15 UTC+0100 MasterASG UPDATE_FAILED Received 1 FAILURE signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
Anyone an idea what might gone wrong with the update?
There were no changes in the MasterASG section of the template.
I am following Diem (libra) documentation on My First Transaction, everything worked fine until Submit a Transaction. As mentioned in the following document, I tried to submit a transaction. https://developers.libra.org/docs/my-first-transaction#submit-a-transaction
But it fails with below error, tried going thru troubleshooting articles, but not much helpful.
libra% transfer 0 1 10
>> Transferring
[ERROR] Failed to perform transaction: Transaction failed with vm status: Validation(UnknownScript)
libra%
Wondering if anyone able to successfully submit the transaction.
OS: macos
Seems you are building the client cli off master branch, you may need to build using testnet instead. I faced the same issue, it worked after switching to testnet branch.
$ git checkout testnet
$./scripts/cli/start_cli_testnet.sh
.
.
.
libra% transfer 0 1 10
>> Transferring
Transaction submitted to validator
To query for transaction status, run: query txn_acc_seq 0 0 <fetch_events=true|false
I'd like to have sonar comments on github pull requests. For that I set up a jenkins job which runs ./gradlew clean sonarRunner [properties].
I read through this:
jenkins + sonar + github integration
My setup is similar, I don't start sonar with maven but with gradle.
I use the following properties:
-Dsonar.github.login=
-Dsonar.github.repository=company/repo
-Dsonar.analysis.mode=preview
-Dsonar.issuesReport.console.enable=true
-Dsonar.github.login=gitusername
-Dsonar.github.oauth=token
As described here:
http://docs.sonarqube.org/display/PLUG/GitHub+Plugin
The end of the log on jenkins is:
11:06:02.167 INFO - Sensor GitHub Plugin InputFile Cache
11:06:02.167 INFO - Sensor GitHub Plugin InputFile Cache (done) | time=0ms
11:06:02.168 INFO - Load server issues
11:06:02.532 INFO -
------------- Issues Report -------------
+620 issues
+2 blocking
+43 critical
+402 major
+169 minor
+4 info
11:06:02.532 INFO - Export issues to
/jenkins/workspace/scheduling-sonar-pull-request/jdk/JDK8/label/Linux/build/sonar/sonar-report.json
11:06:02.611 INFO - ANALYSIS SUCCESSFUL
INFO: EXECUTION SUCCESS INFO:
Total time: 20.198s Final Memory: 26M/742M INFO:
BUILD SUCCESSFUL
But there are no comments appearing on github.
In order to debug changed the oauth token, which gave:
ERROR: Caused by: Unable to perform GitHub WS operation
ERROR: Caused by: Server returned HTTP response code: 401 for URL:
Why are no comments appearing on github? The github plugin is installed on sonarqube, jenkins triggers the sonarRunner, the PR id is correct (tried it hard-coded), the PR has a lot of files, a wrong oauth token gives an error.