We just purchased a performance license, when adding it to the config section, and running /resizer.debug we get the following error:
resizer configuration(Warning): License key was issued in the future; check system clock: ourdomain
License keys
You do not have any license keys installed.
System time is fine. Perhaps the generation of license key is in US timezone? We just have to wait?
Waiting a few hours rectified the issue.
Related
I'm starting to build a dapp on Aptos and I notice that there are two development networks, devnet and testnet. What are the differences between these two?
Update - 2022-01-26: Previously the testnet faucet required the user to complete a captcha. This is no longer true, the faucets of both networks work similarly, so that section has been removed from the answer.
Release cadence
Devnet is generally released every week. Testnet is generally released every two weeks, after devnet.
This means devnet gets new features sooner and more frequently.
Persistence
With devnet, the chain is reset every release. All data is wiped, including any deployed modules, accounts, etc. and the chain restarts from genesis with a new chain ID. If you're building on devnet this means you must redeploy your Move modules and accounts every week.
Testnet is never wiped, similar to mainnet.
Faucet access
On both devnet and testnet you can create new accounts and get new APT easily by either:
Using the "Faucet" button in your wallet (e.g. in Petra).
Using the FaucetClient in the SDK.
Using the aptos CLI:
aptos account fund-with-faucet --account 0xd0f523c9e73e6f3d68c16ae883a9febc616e484c4998a72d8899a1009e5a89d6
Hitting the faucet directly:
curl -X POST 'https://faucet.devnet.aptoslabs.com/mint?amount=100&address=0xd0f523c9e73e6f3d68c16ae883a9febc616e484c4998a72d8899a1009e5a89d6'
Which should you use?
Generally speaking testnet is a friendlier developer experience because you don't need to keep redeploying your code / recreating accounts. For standard development the amount of APT the testnet faucets give you should be more than sufficient.
Devnet is good for rapid experimentation where you don't care about data persistence or if you're running tests that require programmatic access to APT.
Mule has recommended a security update on 19th March which was supposed to be for all supported version of Mule. The below URL is dead:
https://help.mulesoft.com/s/article/High-security-issue-affecting-Mule-runtimes-of-all-supported-versions-March-19th-2020
Could someone help what this vulnerability or security patch was about?
I am using Mule runtime v3.9.0
As per the latest article, I could only find out that the security patch on 19th March has some issues and was fixed by mule through https://help.mulesoft.com/s/article/Error-Provided-value-xx-is-not-compliant-with-the-format-datetime-provided-in-rfc3339
The URL is valid but it requires to be logged in from a customer account to access it. If you are a customer you have to be logged in Help Center before accessing the URL.
If you are not a customer I would assume that you are using Mule Community Edition 3.9.0. I'm not sure if the community edition is affected by the issue or not. You should download the latest hotfix release, 3.9.0-hf2, just in case.
The security patch introduced more strict date time validation, which could cause issues for applications that previously accepted invalid date time values, as explained in the second KB article you shared.
I'm having a problem with a Solaris server I inherited that has been happening for years. (The release is Solaris 10 5/09 s10x_u7wos_08 X86)
Every few seconds in my /var/adm/messages file I get the following line:
httpd[2910]: [ID 218067 user.debug] pkcs11_softtoken: Keystore access failed
I'm pretty sure this is what is causing my core dumps that are filling up my hard drive causing my database to stop functioning, so I'd love to figure this out.
My apologies if I did not provide enough information, I really have no clue what the error means so I don't know what would be relevant to post. Thanks!
Disclaimer: I am a programmer by profession, not a server administrator... so please be gentle.
If you do not store certificates in Solaris PKCS11 token, then simply disable/comment SSLCryptoDevice pkcs11 in Apache config. Note that Solaris PKCS11 token do correctly work just with Solaris bundled OpenSSL. On X86 it doesn't bring much performance improvement too, to use this token. On SPARC since T1 it has its meaning, cause there are hardware accelerators on CPU. Refer to man cryptoadm for Solaris token details.
I've been using NServiceBus successfully for I don't know how long. The license claimed to expire and informed me that I needed a new license file. So I went to the website and generated a new one (For a dev machine). Everytime I debug I get the same message and it requests the license file. Is there any way to prevent this message from showing up EVERY time I try to debug? (Like set a path programmatically possibly?)
<
Andreas : The ONLY mention of the license in the log file is as follows :
2013-03-05 14:24:23,983 [1] [INFO ] [NServiceBus.Licensing.LicenseManager] - No valid license found.
2013-03-05 14:24:23,986 [1] [DEBUG] [NServiceBus.Licensing.LicenseManager] - Trial for NServiceBus v3.3 has expired.
2013-03-05 14:24:23,988 [1] [WARN ] [NServiceBus.Licensing.LicenseManager] - Falling back to run in Basic1 license mode.
Here's a quick screen capture of the prompt after I select the new file. Just so you know it's SAYING it's a valid file.
I believe this can also happen if your license is for a different version of the software than you are running. You may need to request a license that aligns with your NSB version.
Once you received your free license, did you import it?
You need to click the "Browse..." button and select the license to import it!
Our code-signing certificate recently expired. It's been renewed, but now whenever I try to package the app with the renewed cert (whether I attempt a migration of the expired cert or not), after installation, I get the following message any time I try to run the app:
"This installation of this application is damaged. Try re-installing or contacting the publisher for assistance."
Opening up the package contents, the publisherid file inside Resources/META-INF/AIR is blank. This is apparently the problem, because if I manually edit it to contain our previous publisherID, the app will run.
But of course, it's not like we can tell all our users "oh install it then manually edit this file inside the package."
Has anyone encountered this or know how to fix it?
Ah, after a bit more banging my head against my desk I got it.
For anyone who comes after me:
I had to change a couple things in my app descriptor file.
First I had to change the namespace to point at AIR 1.5.3 instead of 1.5
<application xmlns="http://ns.adobe.com/air/application/1.5.3">
And then I had to manually specify our old publisherID in the descriptor as well
<id>OurAppID</id>
<publisherID>OurOldPublisherID</publisherID>
Now it works just as it's supposed to, installs as an update to our old version instead of a new app, and actually runs instead of just throwing that error.