I am using mod_Push module to send push notification.
After starting this module, my messaging service has stopped and as I stop this module, it starts working again. I customized the mod_push module and used user_send_packet hook so that I can send push notification for each and every message received at server.
Log is as follows giving crash in mod_mam
[error] <0.16149.0>#ejabberd_hooks:run_fold1:371 {function_clause,[{mod_mam,should_archive,[ok],[{file,"src/mod_mam.erl"},{line,308}]},{mod_mam,user_send_packet,4,[{file,"src/mod_mam.erl"},{}
Your mod_push will need to be updated to support the latest version of ejabberd API. The log you provided shows that messages are lost because mod_push is crashing archiving module, probably by passing an incorrect return from an ejabberd API hook.
Related
I'm attempting to send notifications to my via via Back4App.com which is a parse backend server, but nothing is being sent and I'm not sure why.
Everything was working fine, when I first implemented it - but now that I have rolled out the current app version to TestFlight I am no longer able to send notifications from the dashboard - getting the following error: stream ended unexpectedly.
I have tried recreating and re-uploading both the development and production push certificates but still having the same issue. I've also tested on a APNs service which is sending notifications as expected.
Any ideas what I could have missed here?
I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!
We have implemented contract testing using message pact and directly accessing Kafka Topics for retrieving the messages from queues. Kafka topics can be accessed using authentication PLAINTEXT. So we have a separate LoginModule defined in a config file with username and password. When I do the test from consumer end it is picking up the correct config file and the scripts are running. But when I run pact:verify using the same setting in the script, LoginModule is not getting recognized and I get an error "unable to find LoginModule class". From pact side I am getting an error "Failed to invoke provider method". Have anyone faced such issues with using pact with kafka before please ?
Are you talking about this one? github.com/reevoo/pact-messages If so, we are not currently supporting pact-messages as we have yet to finalize the base level tech with http/json.
This has been brought up in the past and is known within the Foundation, but we'd rather lock down the core technology before trying to tackle other message protocols/formats.
I'm trying to run the CRM Plugin Registration Tool for the first time and I'm getting the following error: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
I'm using the following for the Discovery URL as it's web based CRM: https://dev.crm.dynamics.com.
User name and label are correct.
Thanks in advance.
I had same issue in registering new assembly.
My problem solved in this way:
1- Close current connection in Plugin Registration Tool.
2- Create new connection to server (login again). If you couldn't login, you should reset IIS or Recycle Application Pool or (at least) Restart Server.
Best Regards.
Does anyone know of a decent way of diagnosing MSMQ access errors. I'm using NServiceBus in a web application. There is a service running that actually creates the private queues, and the web application sends messages to that queue.
The web site uses anonymous access, and the application pool runs using the Network Service account. When my application tries to send a message to the queue (using NServiceBus), I get MSMQ access denied errors. I have tried all combinations of full control with ANONYMOUS LOGON, Everyone, etc, and still no luck. I have tried deleting the queues and letting NServiceBus recreate them, and still no luck.
When I set the IIS App Pool to run using a local administrator account, then it all works fine. How can I work out exactly what permissions I need to apply? Using the accounts/permissions that are added by default clearly isn't working.
You need to set up the queue permissions so that "everyone" can send to any queue.