I followed the steps for building hono from source from this page https://www.eclipse.org/hono/docs/dev-guide/building_hono/
The build completes without errors, but when running the integration tests, I receive lots of errors related to timeouts and expired certificates. Here's an excerpt of the log:
HTTP11:59:07.040 [main] INFO o.e.h.adapter.http.impl.Application - The following profiles are active: prod
ARTEMIS2020-10-29 11:59:09,455 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking with /172.19.0.5:38356 has occurred.
QPID2020-10-29 11:59:09.827479 +0000 SERVER (info) [C4] Connection to hono-artemis.hono:5671 failed: amqp:connection:framing-error SSL Failure: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
Is it possible to update the certificates or is this not the main problem?
Here's the link to the complete log file
You are probably building sources from one of the previously released tags, i.e. not from the master branch, right?
If so, the demo certificates included in the source code may have expired in the meantime since the time of release. You can re-create the certificates by running the demo-certs/create_certs.sh script. Note that this needs to be done once only, i.e. it is not necessary to do this before each build.
Related
I am trying to submit a code review request using CodeCollaborator client v7.2.7237 (server version is same too) but fails with the following error call stack –
com.smartbear.ccollab.datamodel.DataModelException: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:355)
at com.sun.proxy.$Proxy63.loadById(Unknown Source)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation.loadById(XmlRpcClientEngineImplementation.java:441)
at com.smartbear.ccollab.datamodel.Engine$DataObjectCache.loadObjectById(Engine.java:6691)
at com.smartbear.ccollab.datamodel.Engine.loadById(Engine.java:537)
at com.smartbear.ccollab.datamodel.Engine.loadEngineObjectById(Engine.java:564)
at com.smartbear.ccollab.datamodel.Engine.versionCreate(Engine.java:5913)
at com.smartbear.ccollab.datamodel.Scm.uploadScmVersion(Scm.java:629)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:448)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:392)
at com.smartbear.ccollab.datamodel.Scm.uploadChangelist(Scm.java:291)
at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.execute(AbstractAddChangelistCommand.java:139)
at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.execute(AbstractReviewCommand.java:125)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:345)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:419)
at com.smartbear.collaborator.Collaborator.execute(Collaborator.java:160)
at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:158)
at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:103)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at org.apache.xmlrpc.client.XmlRpcCommonsTransport.writeRequest(XmlRpcCommonsTransport.java:252)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:151)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:115)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientFactory$XmlRpcCommonsTransport2.sendRequest(XmlRpcClientFactory.java:75)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:256)
... 18 more
I have no problems accessing Perforce or CodeCollaborator from the machine when I get this error. I tried to submit using CodeCollaborator plugin in P4V (P4V/NTX64/2019.1/1797168) but got the same error message. I tried JRE 1.6, 1.7 but got the same error.
When I login to my CodeCollaborator account, I see that review request is being created but it is failing to add the source files to the review. My colleagues with the same CodeCollaborator, P4 versions are successfully able to submit the review requests. Checked this thread on CodeCollaborator forum who had reported similar issue but there was no solution to try. Any suggestions on how to troubleshoot ? Thanks.
I've set up Azerothcore on a VPS following this tutorial. I've created an account but when I try to log in my client gets stuck on the authenticating phase.
I followed the tutorial completely except I had to download the data files from the recommended link in the AzerothCore Wiki, because my worldserver did not recognize the files provided in the tutorial.
I've checked the config files and database and everything seems ok. The address is what it should be (my VPS address) and ports seem to be ok, too. I've tried redownloading the client (WoWmane WotLK 3.3.5a client, with WoD models), checking my firewall (exceptions added for the WoW client) and checking the realmlist.wtf file and config file, to no avail. My folder is not read-only and I'm really lost now.
EDIT: I've now managed to get the 'Malformed package' error again. I started the auth server, then the world server, then tried to log in, then shut down both servers after the client got stuck again. I'll paste the relevant portion of the server log file:
2019-08-25 03:03:49 ERROR: WORLD: World initialized in 0 minutes 13 seconds
2019-08-25 03:03:49
2019-08-25 03:03:49 worldserver process priority class set to -15
2019-08-25 03:03:49 Max allowed socket connections 1024
2019-08-25 03:03:49 Starting up Auction House Listing thread...
2019-08-25 03:03:49 AzerothCore rev. 2f74802d03d5 2019-08-23 22:22:26 +0200 (master branch) (Unix, Release) (worldserver-daemon) ready...
2019-08-25 03:04:16 ERROR: WorldSocket::handle_input_header(): client (account: 0, char [GUID: 0, name: <none>]) sent malformed packet (size: 8, cmd: 1867972643)
2019-08-25 03:04:42 Auction House Listing thread exiting without problems.
2019-08-25 03:04:42 Halting process...
I'm trying to run example Jira add-on.
I have created credentials.json file and have run npm i and node app.js.
But I have problems with installed event. Here is nodejs log:
Watching atlassian-connect.json for changes
Add-on server running at http://MacBook-Air.local:3000
Initialized sqlite3 storage adapter
Local tunnel established at https://a277dbdf.ngrok.io/
Check http://127.0.0.1:4040 for tunnel status
Registering add-on...
GET /atlassian-connect.json 200 13.677 ms - 784
Saved tenant details for 608ff294-74b9-3edf-8124-7efae2c16397 to database
{ key: 'my-add-on',
clientKey: '608ff294-74b9-3edf-8124-7efae2c16397',
publicKey: 'MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCtKxrEBipTMXhRHlv9zcSLR2Y9h5YQgNQ5vpJ40tF9RmuIzByjkKTurCLHFwMAWU6aLQM+H+Z8wAlpL9AVlN5NKrEP8+a3mGFUOj/5nSJ7ZWHjgju0sqUruyEkKLvKuhWkKkd9NqBxogN0hxv7ue5msP5ezwei/nTJXmnmA5qOAQIDAQAB',
sharedSecret: 'LfT9elHM7iHkto5pHr+MnpH0SR1ypunIDoCyt6ugVJ1Q4hWHurG8k5DjVzLcvT2C98DDbiJiA89VNB0e3DiUvQ',
serverVersion: '100075',
pluginsVersion: '1.3.407',
baseUrl: 'https://gleb-olololololo-22.atlassian.net',
productType: 'jira',
description: 'Atlassian JIRA at https://gleb-olololololo-22.atlassian.net ',
eventType: 'installed' }
POST /installed?user_key=admin 204 51.021 ms - -
Failed to register with host https://gleb-olololololo-22%40yopmail.com:gleb-olololololo-22#gleb-olololololo-22.atlassian.net (200)
The add-on host did not respond when we tried to contact it at "https://a277dbdf.ngrok.io/installed" during installation (the attempt timed out). Please try again later or contact the add-on vendor.
{"type":"INSTALL","pingAfter":300,"status":{"done":true,"statusCode":200,"contentType":"application/vnd.atl.plugins.task.install.err+json","errorMessage":"The add-on host did not respond when we tried to contact it at \"https://a277dbdf.ngrok.io/installed\" during installation (the attempt timed out). Please try again later or contact the add-on vendor.","source":"https://a277dbdf.ngrok.io/atlassian-connect.json","name":"https://a277dbdf.ngrok.io/atlassian-connect.json"},"links":{"self":"/rest/plugins/1.0/pending/80928cb9-f64e-42d0-9a7e-a1fe8ba81055","alternate":"/rest/plugins/1.0/tasks/80928cb9-f64e-42d0-9a7e-a1fe8ba81055"},"timestamp":1513692335651,"userKey":"admin","id":"80928cb9-f64e-42d0-9a7e-a1fe8ba81055"}
Add-on not registered; no compatible hosts detected
I have reviewed tons of information in Google, but didn't found an answer.
More details, that can helps you to answer.
It happens suddenly. It worked OK, but about 1 week ago I start to get this error and cannot fix it. So I didn't change anything, just run add-on again, as I did it every day.
If I try to upload add-on manually I got error in terminal
GET / 302 17.224 ms - 0
GET /atlassian-connect.json 200 2.503 ms - 783
Found existing settings for client 608ff294-74b9-3edf-8124-7efae2c16397. Authenticating reinstall request
Authentication verification error: 401 Could not find authentication data on request
POST /installed?user_key=admin 401 22.636 ms - 45
The most possible reason (that I've found in google) is that I have wrong server time. But the time on my local machine is correct (at least for my timezone).
Anyone has any thoughts about this problem?
Thanks!
I kept randomly having this happen to me. It would be working, then run npm start and I would get the error. Since I'm not using a database right now, I simply removed all references to the juggling-sqlite database. This was in package.json, package-lock.json, config.json, and I just removed store.db. That got it working for me. Pretty frustrating that this happens, not sure a better way around it.
I am running Liferay 6.2 on WebLogic 12c server.
Out of nowhere it just stopped working.
This is the last thing I see before it throws a flurry of exceptions
<Jan 10, 2014 2:53:28 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\Oracle_2\Middleware\user_projects\domains\liferay\servers\AdminServer\logs
\AdminServer.log will be rotated. Reopen the log file if tailing has stopped. Th
is can happen on some platforms, such as Windows.>
<Jan 10, 2014 2:53:28 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\Oracle_2\Middleware\user_projects\domains\liferay\serv
ers\AdminServer\logs\AdminServer.log00369. Log messages will continue to be logg
ed in C:\Oracle_2\Middleware\user_projects\domains\liferay\servers\AdminServer\l
ogs\AdminServer.log.>
The errors are shown here http://www.pastebin.ca/2532946
Anyone have any ideas on this?
As you can see in the log files (see below excerpt of your log file), Liferay is not able to either get a handle to the HSQL database or the HSQL db might be corrupted when you updated it.
13:11:16,769 WARN [C3P0PooledConnectionPoolManager[identityToken->uArzPQ2m]-HelperThread-#4][BasicResourcePool:1851] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask#933b16 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
java.sql.SQLException: error in script file line: 15 unexpected token: AVG
So you need to answer below questions:
Did you use any Client tool to make changes to your HSQL db?
If yes, did you close the connection to HSQL database before starting Liferay?
If not, Liferay won't be able to acquire lock on your db and fail to start.
If not, did you make DB changes directly in the HSQL db file?
This is NOT Recommended. Rollback your changes and try to use HSQL client to make your db changes
HTH!
P.S. Is this issue duplicate of: https://stackoverflow.com/questions/21052236/weblogic-wont-start. If so, please delete that one.
There are alot of settings in all the versions of IE & windows, that may cause problems for users attempting to run xbap applications, particulary in fulltrust mode.
I seem to have gathered a long list of such cases during the last year.
However I'm pussled by this one exception, which occurs on a user on one of my systems, and was hoping that maybe someone here could point me in the right direction.
This application runs on all the used version of windows, and IE6 -> IE9, without problems so there is nothing wrong with the deployment/xbap it self.
The user gets the errorlog / stacktrace below. Have anyone of you encountered this vague trace, and know what the issue might be? This user is running IE8 & W7.
The user have the proper certificates installed in trusted root authorities & trusted publishers. The site in question has been added to list of trusted sites. Xbap has been enabled in IE.
URLs, publickeys, appname etc have been scrambeled.
Brgds,
Stian
PLATFORM VERSION INFO
Windows : 6.1.7600.0 (Win32NT)
Common Language Runtime : 2.0.50727.4963
System.Deployment.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)
mscorwks.dll : 2.0.50727.4963 (win7RTMGDR.050727-4900)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : http://someurl/someapplication.xbap
Application url : http://someurl/Application%20Files/someapplication_1_0_0_29/someapplication.exe.manifest
IDENTITIES
Deployment Identity : someapplication.app, Version=1.0.0.29, Culture=neutral, PublicKeyToken=sometoken, processorArchitecture=msil
Application Identity : someapplication, Version=1.0.0.29, Culture=neutral, PublicKeyToken=sometoken, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Online only application.
* Browser-hosted application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ User has refused to grant required permissions to the application.
* An exception occurred while downloading the application. Following failure messages were detected:
+ The AssertApplicationRequirements method failed. The application cannot be committed.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
No phase information is available.
ERROR DETAILS
Following errors were detected during this operation.
* [01/11/2011 09:16:02] System.Deployment.Application.TrustNotGrantedException (Unknown subtype)
- User has refused to grant required permissions to the application.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ApplicationTrust.RequestTrust(SubscriptionState subState, Boolean isShellVisible, Boolean isUpdate, ActivationContext actCtx, TrustManagerContext tmc)
at System.Deployment.Application.DeploymentManager.DetermineTrustCore(Boolean blocking, TrustParams tp)
at System.Deployment.Application.DeploymentManager.DetermineTrust(TrustParams trustParams)
at System.Deployment.Application.InPlaceHostingManager.AssertApplicationRequirements(Boolean grantApplicationTrust)
at System.Deployment.Application.InPlaceHostingManager.AssertApplicationRequirements()
at MS.Internal.AppModel.XappLauncherApp.AssertApplicationRequirementsAsync(Object unused)
* [01/11/2011 09:16:37] System.Deployment.Application.DeploymentException (Unknown subtype)
- The AssertApplicationRequirements method failed. The application cannot be committed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.DeploymentManager.WaitForAssertApplicationRequirements()
at System.Deployment.Application.DeploymentManager.SynchronizeCore(Boolean blocking)
at System.Deployment.Application.DeploymentManager.SynchronizeAsyncWorker()
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
I should have answered this one when I "solved" the issue.
In the case above there was an issue with the client computer, a change of disk, re-install of OS etc solved the trick.
What the issue was, remains a mystery ;)