Tridion Publisher stopped working - tridion

I'm using Tridion 2011 SP1 HR1. Suddenly (it sounds silly, but I haven't changed any settings) my publishing stopped working. The only thing I recall doing was deleting everything from the "incoming" folder assuming that Tridion would re-create everything it needs inside.
The error that I see in the Event Viewer is:
Transport service failed to transport. <Summary state="Failed" referenceId="tcm:0-1317-66560"><Error>Transport failed for transaction: tcm:0-1317-66560. Error while generating transaction summary.null</Error><Processing><Context topic="Content Delivery"><IsRollbackOnFailure /></Context></Processing><Target /></Summary>
Component: Tridion.ContentManager.Publishing
Errorcode: 0
User: NT AUTHORITY\SYSTEM
StackTrace Information Details:
at Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.SendTransportPackage(TransportPackage package)
at Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.HandlePublishRequest(PublishTransaction publishTransaction)
at Tridion.ContentManager.Publishing.Handling.DefaultPublishTransactionHandler.ProcessPublishTransaction(PublishTransaction publishTransaction)
at Tridion.ContentManager.Publishing.Publisher.QueueMessageHandler.HandleMessage()
Then upon checking the cd_transport.log I see the following:
2013-01-04 01:13:56,359 DEBUG DestinationController - Checking destination for transport metadata
2013-01-04 01:13:56,360 DEBUG TransportPoolManager - Returning a freely available and alive TransportConnector
2013-01-04 01:13:56,360 DEBUG FileTransportConnector - Retrieving notification file if present: c:\tridion\incoming\meta.xml
2013-01-04 01:13:56,362 DEBUG TransportPoolManager - Connector is registered for reuse: Local[Location[c:\tridion\incoming]] available: 1
2013-01-04 01:13:56,362 DEBUG DestinationController - Starting polling on destination: EkJ8TTiKBx4qU16og0f3wg==
2013-01-04 01:13:56,363 DEBUG TransportPoolManager - Returning a freely available and alive TransportConnector
2013-01-04 01:13:56,363 DEBUG FileTransportConnector - Retrieving notification file if present: c:\tridion\incoming\tcm_0-1319-66560.state.xml
2013-01-04 01:13:56,363 DEBUG FileTransportConnector - Retrieving notification file if present: c:\tridion\incoming\tcm_0-1317-66560.state.xml
2013-01-04 01:13:56,363 DEBUG FileTransportConnector - Retrieving notification file if present: c:\tridion\incoming\tcm_0-1318-66560.state.xml
2013-01-04 01:13:56,363 DEBUG TransportPoolManager - Connector is registered for reuse: Local[Location[c:\tridion\incoming]] available: 1
2013-01-04 01:13:56,363 DEBUG DestinationController - Polling attempt 17 for transaction: tcm:0-1318-66560 on destination: EkJ8TTiKBx4qU16og0f3wg==
2013-01-04 01:13:56,363 DEBUG DestinationController - Polling attempt 10 for transaction: tcm:0-1319-66560 on destination: EkJ8TTiKBx4qU16og0f3wg==
2013-01-04 01:13:56,363 DEBUG DestinationController - Polling attempt 53 for transaction: tcm:0-1317-66560 on destination: EkJ8TTiKBx4qU16og0f3wg==
2013-01-04 01:13:56,532 ERROR RollingStateRetriever - Unable to deserialize transaction
2013-01-04 01:13:57,538 ERROR RollingStateRetriever - Unable to deserialize transaction
2013-01-04 01:13:58,547 ERROR RollingStateRetriever - Unable to deserialize transaction
2013-01-04 01:13:59,552 ERROR RollingStateRetriever - Unable to deserialize transaction
2013-01-04 01:14:00,558 ERROR RollingStateRetriever - Unable to deserialize transaction
The cd_core.log also shows an error:
ERROR RollingStateRetriever - Unable to deserialize transaction
The incoming folder has Transactions, Zip subfolders - both empty and a meta.xml file.
Can someone please suggest why this error is occuring?

This turns out to be a duplicate of:
Tridion 2011 SP1 - Transport service failed to transport
Since my error logs were slightly different, so I'm keeping this in for others' future reference.

Related

Appium creates driver very slowly. (Inspector loads elements tree very slowly.)

The problem
The app can be launched quickly when I use the Appium Desktop to create a session for inspector, but it takes too long to load the elements tree for inspector. This phenomenon happens only in some apps.
Environment
Appium version (or git revision) that exhibits the issue: Appium Desktop 1.6.1 (Appium Server 1.8.0)
Last Appium version that did not exhibit the issue (if applicable):
Desktop OS/version used to run Appium:MacOS 10.13.5
Node.js version (unless using Appium.app|exe):10.1.0
Mobile platform/version under test:iOS 10.3.3
Real device or emulator/simulator:iPhone 7 real device
Appium CLI or Appium.app|exe:
Details
It's about 5 minutes to get a response loading the elements tree.
2018-06-28 09:40:05:339 - [debug] [XCUITest] Failed to create WDA session. Retrying...
2018-06-28 09:40:06:346 - [debug] [BaseDriver] Event 'wdaSessionAttempted' logged at 1530150006346 (09:40:06 GMT+0800 (CST))
2018-06-28 09:40:06:346 - [debug] [XCUITest] Sending createSession command to WDA
2018-06-28 09:40:06:347 - [debug] [JSONWP Proxy] Proxying [POST /session] to [POST http://localhost:8100/session] with body: {"desiredCapabilities":{"bundleId":"com .chinaums.ttf6","arguments":[],"environment":{},"shouldWaitForQuiescence":true,"shouldUseTestManagerForVisibilityDetection":true,"maxTypingFrequency":60,"shouldUseS ingletonTestManager":true}}
2018-06-28 09:45:28:282 - [debug] [JSONWP Proxy] Got response with status 200: {"value":{"sessionId":"9A6749D7-5A1D-431F-AA57- E1126F189E95","capabilities":{"device":"iphone","browserName":null,"sdkVersion":"10.3.3","CFBundleIdentifier":null}},"sessionId":"9A6749D7-5A1D-431F-AA57- E1126F189E95","status":0}
2018-06-28 09:45:28:282 - [debug] [BaseDriver] Event 'wdaSessionStarted' logged at 1530150328282 (09:45:28 GMT+0800 (CST))
2018-06-28 09:45:28:472 - [debug] [XCUITest] Cannot find a match for DerivedData folder path from lsof. Trying to access logs
2018-06-28 09:45:28:482 - [debug] [BaseDriver] Event 'wdaStarted' logged at 1530150328481 (09:45:28 GMT+0800 (CST))
2018-06-28 09:45:28:482 - [XCUITest] Skipping setting of the initial display orientation. Set the "orientation" capability to either "LANDSCAPE" or "PORTRAIT", if this is an undesired behavior.
Link to Appium logs
appium_server_log
I sloved it following this citation Creating session takes over 5 minutes now with Xcode 9.
Just add capability: waitForQuiescence = false

keyTemplateRetriever Failed retrieving throttling data WSO2

I was setting up prepackaged WSO2 identity server with WSO2 API Manager.Also was configuring the domain urls.
Now while starting WSO2 API Manager , below error is printed in the logs
[2017-05-12 05:37:35,237] INFO - CarbonEventManagementService Starting polling event receivers
[2017-05-12 05:37:55,848] WARN - KeyTemplateRetriever Failed retrieving throttling data from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
[2017-05-12 05:37:55,850] WARN - BlockingConditionRetriever Failed retrieving Blocking Conditions from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
[2017-05-12 05:38:01,861] WARN - FileSystemPreferences Could not lock System prefs. Unix error code 32693.
[2017-05-12 05:38:01,861] WARN - FileSystemPreferences Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
[2017-05-12 05:38:10,877] WARN - KeyTemplateRetriever Failed retrieving throttling data from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
[2017-05-12 05:38:10,878] WARN - BlockingConditionRetriever Failed retrieving Blocking Conditions from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
[2017-05-12 05:38:25,940] WARN - BlockingConditionRetriever Failed retrieving Blocking Conditions from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
[2017-05-12 05:38:25,940] WARN - KeyTemplateRetriever Failed retrieving throttling data from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
Can anyone tell me what could have i done wrong..May be i did some configuration wrong.Where should i check to find the problem?
Can it be because of SSL issues? I have not yet set up SSL.
Yes, this seems to be from SSL handshake failure specially since you have used hostnames. The default certificates that come with WSO2 Servers are created for localhost.
You can try creating self-signed certificates for APIM and IS hostnames. Then export the public certs of APIM to trust-store.jks of IS and vice versa. This should resolve the SSL handshake failure.
So what happens is when APIM boots up it makes an HTTP call to a web app in Key Manager (throttle data at KM_URL/throttle/data/v1/keyTemplates). APIM decides the URL of the KM from the URL configured in the api-manager.xml
You are seeing the error,
WARN - KeyTemplateRetriever Failed retrieving throttling data from remote endpoint: Received fatal alert: handshake_failure. Retrying after 15 seconds...
because the APIM cannot make this HTTP call retrieve throttle data from KM.

ERROR when sending data to my KAA server

When using first kaa server application and sending data to my Kaa server from outside I get this error: CONNACK message + KAASYNC message.
My configuration for kaa server is:
transport host...=localhost=My PUBLIC ip
My config mongo on kaa server is:
host: MY PUBLIC IP port: 27017
THIS IS WHAT I GET WHEN I COMPILE MY SDK
[pool-2-thread-1] INFO org.kaaproject.kaa.client.channel.failover.DefaultFailoverManager - Server [BOOTSTRAP, -1835393002] failed
[pool-2-thread-1] WARN org.kaaproject.kaa.client.channel.impl.DefaultChannelManager - Attempt to connect to the next bootstrap service will be made in 2000 ms, according to failover strategy decision
[pool-1-thread-1] INFO FirstKaaDemo - Sampled Temperature: 34
[pool-4-thread-14] INFO org.kaaproject.kaa.client.logging.strategies.RecordCountLogUploadStrategy - Need to upload logs - current count: 14, threshold: 1
[Thread-2] INFO org.kaaproject.kaa.client.channel.impl.channels.DefaultOperationTcpChannel - Can't sync. Channel [default_operation_tcp_channel] is waiting for CONNACK message + KAASYNC message
[pool-6-thread-1] INFO org.kaaproject.kaa.client.channel.impl.channels.AbstractHttpChannel - Processing sync all for channel default_bootstrap_channel
[pool-1-thread-1] INFO FirstKaaDemo - Sampled Temperature: 25
[pool-4-thread-15] INFO org.kaaproject.kaa.client.logging.strategies.RecordCountLogUploadStrategy - Need to upload logs - current count: 15, threshold: 1
[Thread-2] INFO org.kaaproject.kaa.client.channel.impl.channels.DefaultOperationTcpChannel - Can't sync. Channel [default_operation_tcp_channel] is waiting for CONNACK message + KAASYNC message
Step 1: Change Kaa Host/IP
To VM ip address. My case is 192.168.1.142
Step 2: Regenerate SDK and recompide and run. Done

What does "Could not process download request: Failed to load properties for" in Artifactory logs mean?

We see a lot of these errors in our Artifactory logs:
20161228 121638 [http-nio-8081-exec-22933] [WARN ]
(o.a.r.ArtifactoryResponseBase:107) - Sending HTTP error code 500: Could not
process download request: Failed to load properties for 314050135
what does it mean?
Looking closer at the warnings we see that in most cases the warning comes after trying to read a metadata-xml of some sort.
cat artifactory.log | grep http-nio-8081-exec-2441 | grep -A 2 -B 5 "Sending HTTP error code 500"
Similar to the below:
2017-01-04 09:02:48,788 [http-nio-8081-exec-2419] [DEBUG] (o.a.w.s.RepoFilter :98) - Entering request GET (10.67.6.51) /internal-release-rhel6/repodata/repomd.xml.
2017-01-04 09:03:48,791 [http-nio-8081-exec-2419] [WARN ] (o.a.r.ArtifactoryResponseBase:107) - Sending HTTP error code 500: Could not process download request: Failed to load properties for 335095695
Update
We have increased the log level to get some context:
2017-01-04 09:01:05,955 [http-nio-8081-exec-2445] [DEBUG] (o.a.w.s.RepoFilter :98) - Entering request GET (10.67.7.101) /core-release/com/jeppesen/jcms/airport/maven-metadata.
xml.
2017-01-04 09:01:06,187 [http-nio-8081-exec-2443] [DEBUG] (o.a.w.s.RepoFilter :98) - Entering request HEAD (10.67.7.101) /ots-release/com/jeppesen/jcms/atriumorc/maven-metadat
a.xml.
2017-01-04 09:01:12,143 [http-nio-8081-exec-2373] [ERROR] (o.a.r.c.e.GlobalExceptionMapper:48) - Failed to load properties for 165931919
org.artifactory.storage.StorageException: Failed to load properties for 165931919
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.loadProperties(DbPropertiesServiceImpl.java:113) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.getProperties(DbPropertiesServiceImpl.java:84) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.repo.service.RepositoryServiceImpl.getProperties(RepositoryServiceImpl.java:1046) ~[artifactory-core-4.15.0.jar:na]
.....
2017-01-04 09:01:12,143 [http-nio-8081-exec-2359] [ERROR] (o.a.r.c.e.GlobalExceptionMapper:48) - Failed to load properties for 59628724
org.artifactory.storage.StorageException: Failed to load properties for 59628724
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.loadProperties(DbPropertiesServiceImpl.java:113) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.getProperties(DbPropertiesServiceImpl.java:84) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.repo.service.RepositoryServiceImpl.getProperties(RepositoryServiceImpl.java:1046) ~[artifactory-core-4.15.0.jar:
......
2017-01-04 09:01:12,143 [http-nio-8081-exec-2422] [ERROR] (o.a.r.c.e.GlobalExceptionMapper:48) - Failed to load properties for 26449553
org.artifactory.storage.StorageException: Failed to load properties for 26449553
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.loadProperties(DbPropertiesServiceImpl.java:113) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.getProperties(DbPropertiesServiceImpl.java:84) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.repo.service.RepositoryServiceImpl.getProperties(RepositoryServiceImpl.java:104
.....
.....
.....
2017-01-04 09:01:12,180 [http-nio-8081-exec-2428] [DEBUG] (o.a.w.s.RepoFilter :204) - Exiting request GET (10.67.20.240) /api/npm/npm-all/grunt-contrib-copy/-/grunt-contrib-copy-1.0.0.tgz
2017-01-04 09:01:12,943 [http-nio-8081-exec-2416] [WARN ] (o.a.r.ArtifactoryResponseBase:107) - Sending HTTP error code 500: Could not process download request: Failed to load properties for 59815778
2017-01-04 09:01:12,948 [http-nio-8081-exec-2416] [DEBUG] (o.a.w.s.RepoFilter :283) - Could not process download request: Failed to load properties for 59815778
org.artifactory.storage.StorageException: Failed to load properties for 59815778
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.loadProperties(DbPropertiesServiceImpl.java:113) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.storage.db.fs.service.DbPropertiesServiceImpl.getProperties(DbPropertiesServiceImpl.java:84) ~[artifactory-storage-db-4.15.0.jar:na]
at org.artifactory.repo.service.RepositoryServiceImpl.getProperties(RepositoryServiceImpl.java:1046) ~[artifactory-core-4.15.0.jar:na]
at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source) ~[na:na]
The root cause is an SQL error when trying to load an artifact properties while trying to download the artifact. It can indicate some kind of a corruption in the database.
For more concrete details about the error set the log level of org.artifactory.webapp.servlet.RepoFilter to debug. This should provide a full stack trace in the log.

Tridion 2011 SP1 - Transport service failed to transport

When I publish I get the following error:
Transport service failed to transport. <Summary state="Failed" referenceId="tcm:0-122-66560"><Error>Transport failed for transaction: tcm:0-122-66560. Error while generating transaction summary.null</Error><Processing><Context topic="Content Delivery"><IsRollbackOnFailure /></Context></Processing><Target /></Summary>
The cd_core.log contains the following:
2012-07-09 13:41:07,497 DEBUG TransportService - Starting handing of a transaction
2012-07-09 13:41:07,513 INFO TransactionProcessor - No existing transport transaction information for: tcm:0-121-66560 creating new transaction state
2012-07-09 13:41:07,513 DEBUG TransactionHeader - Writing[TransactionHeader transactionId=tcm:0-121-66560 control=COMMIT] to C:\Temp\tcm_0-121-66560.Content\t
ransaction.xml
2012-07-09 13:41:07,513 DEBUG DestinationControllerFactory - Returning existing destination controller.
2012-07-09 13:41:07,513 DEBUG InstructionEncoder - Transaction state could not be serialized to file. Serialization error.
2012-07-09 13:41:07,513 DEBUG InstructionEncoder - Transaction state could not be serialized to file. Serialization error.
2012-07-09 13:41:07,513 INFO TransportService - Starting transport handling of transaction: tcm:0-121-66560
2012-07-09 13:41:07,513 DEBUG DestinationControllerFactory - Returning existing destination controller.
2012-07-09 13:41:07,513 INFO TransportPoolManager - Creating a new TransportPoolConnector, because no available connectors in connection pool
2012-07-09 13:41:07,513 DEBUG TransportPoolConnector - Configuring TransportPoolConnector.
2012-07-09 13:41:07,513 DEBUG DestinationProgressWorker - Starting retrieving active transactions at destination: EkJ8TTiKBx4qU16og0f3wg==
2012-07-09 13:41:07,513 DEBUG DestinationProgressWorker - Found 0 transactions in progress and 0 waiting transactions.
2012-07-09 13:41:07,513 DEBUG TransportPoolManager - Connector is registered for reuse: Local[Location[c:\tridion\incoming]] available: 1
2012-07-09 13:41:07,513 INFO DestinationController - Transaction fits inside current window, proceeding transaction: tcm:0-121-66560
2012-07-09 13:41:07,513 DEBUG TransactionManager - Destination is available for transport: EkJ8TTiKBx4qU16og0f3wg==
2012-07-09 13:41:07,513 DEBUG TransactionManager - All destinations are available for transport of transaction: tcm:0-121-66560
2012-07-09 13:41:07,513 DEBUG InstructionEncoder - Transaction state could not be serialized to file. Serialization error.
2012-07-09 13:41:07,513 INFO ZipWorker - Preparing TransportPackage for id: tcm:0-121-66560
2012-07-09 13:41:07,513 DEBUG ZipWorker - Zipping Transportpackage: c:\Temp\tcm_0-121-66560.Content
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/components.xml
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/instructions.xml
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/Pages/Test Website/_XSL/Nav.xsl
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/pages.xml
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/Schemas/tcm_10-25-8
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/schemas.xml
2012-07-09 13:41:07,513 DEBUG ZipUtils - Adding tcm_0-121-66560.Content/transaction.xml
2012-07-09 13:41:07,529 DEBUG InstructionEncoder - Transaction state could not be serialized to file. Serialization error.
2012-07-09 13:41:07,529 DEBUG ZipWorker - Zipping has been completed for transaction: tcm:0-121-66560
2012-07-09 13:41:07,529 DEBUG StepPrepare - Zipping has been completed successfully for transaction: tcm:0-121-66560
2012-07-09 13:41:07,529 DEBUG DestinationControllerFactory - Returning existing destination controller.
2012-07-09 13:41:07,529 DEBUG InstructionEncoder - Transaction state could not be serialized to file. Serialization error.
2012-07-09 13:41:07,529 ERROR TransactionManager - Error while generating transaction summary.
javax.xml.bind.JAXBException: null
at javax.xml.bind.ContextFinder.newInstance(Unknown Source) ~[na:1.6.0_26]
at javax.xml.bind.ContextFinder.find(Unknown Source) ~[na:1.6.0_26]
at javax.xml.bind.JAXBContext.newInstance(Unknown Source) ~[na:1.6.0_26]
at javax.xml.bind.JAXBContext.newInstance(Unknown Source) ~[na:1.6.0_26]
at com.tridion.util.JAXBUtil.registerContext(JAXBUtil.java:93) ~[cd_core.jar:na]
at com.tridion.util.JAXBUtil.getContext(JAXBUtil.java:68) ~[cd_core.jar:na]
at com.tridion.util.JAXBUtil.marshalToString(JAXBUtil.java:107) ~[cd_core.jar:na]
at com.tridion.transport.model.transaction.context.StepPrepare.execute(StepPrepare.java:49) ~[cd_transport.jar:na]
at com.tridion.transport.model.transaction.context.TransactionProcessor.transport(TransactionProcessor.java:63) ~[cd_transport.jar:na]
at com.tridion.transport.TransactionManager.transport(TransactionManager.java:38) ~[cd_transport.jar:na]
at com.tridion.transport.TransportService.handleTransaction(TransportService.java:228) [cd_transport.jar:na]
Caused by: java.lang.ClassNotFoundException: com/sun/xml/bind/v2/ContextFactory
at java.lang.Class.forName0(Native Method) ~[na:1.6.0_26]
at java.lang.Class.forName(Unknown Source) ~[na:1.6.0_26]
at javax.xml.bind.ContextFinder.safeLoadClass(Unknown Source) ~[na:1.6.0_26]
... 11 common frames omitted
Any help would be greatly appreciated.
Thanks
Check your ..\Tridion\lib\ folder - if the files:
jaxb-api.jar
jaxb-impl.jar
are there, remove them, restart the Publisher & Transport services, and re-test.

Resources