link:-https://github.com/jonathanzufi/SignalR-ReactNativeClient
using this library and getting error in building connection
error: [2021-10-21T11:37:44.853Z] Debug: Starting HubConnection.
[Thu Oct 21 2021 17:07:43.711] LOG [2021-10-21T11:37:44.854Z] Debug: Starting connection with transfer format 'Text'.
[Thu Oct 21 2021 17:07:43.712] LOG [2021-10-21T11:37:44.855Z] Debug: Sending negotiation request: https://signalrdemo.com/chatHub/negotiate?negotiateVersion=1.
[Thu Oct 21 2021 17:07:43.714] LOG {"_40": 0, "_55": null, "_65": 0, "_72": null} connect
[Thu Oct 21 2021 17:07:43.721] WARN [2021-10-21T11:37:44.887Z] Warning: Error from HTTP request. 0: undefined.
[Thu Oct 21 2021 17:07:43.772] LOG Global error handler
[Thu Oct 21 2021 17:07:43.818] LOG Global error handler
[Thu Oct 21 2021 17:07:43.820] LOG [2021-10-21T11:37:44.946Z] Debug: HubConnection failed to start successfully because of error 'Error'.
[Thu Oct 21 2021 17:07:43.820] LOG [Error] err::::::::::::::
[Thu Oct 21 2021 17:07:43.821] LOG Error starting the connection: Error
technology used :-react-native
Related
On react-native application, We are trying to implement social sign-in. For IOS it's working fine, but for android after Google or Facebook sign in, I am getting below error and application is getting crashed. Please let me know what mistake I am doing.
[Tue Jun 01 2021 16:18:11.689] LOG cognito parsingCallbackUrl {"url": null}
[Tue Jun 01 2021 16:18:11.690] LOG parsingCallbackUrl {"url": null}
[Tue Jun 01 2021 16:18:13.581] LOG URLS https://myappf2077acb-f2077acb-dev.auth.ap-southeast-1.amazoncognito.com/oauth2/authorize?redirect_uri=myapp%3A%2F%2F&response_type=code&client_id=7kpeug5cf2tdb7ri3n1tceubrb&identity_provider=Google&scope=phone%20email%20openid%20profile%20aws.cognito.signin.user.admin&state=eXavpAJAD7x8RhGY5HQQGuHV1BMjOrfS&code_challenge=9jig9ys6LEqbuWlcHKbFoaGvnBISoFqYHN7VICSwwPo&code_challenge_method=S256 Redirect myapp://
[Tue Jun 01 2021 16:18:14.793] LOG cognito parsingCallbackUrl {"url": "myapp://?code=210db3a4-1e90-4a64-b16d-1bb4c45d2760&state=eXavpAJAD7x8RhGY5HQQGuHV1BMjOrfS"}
[Tue Jun 01 2021 16:18:14.794] LOG parsingCallbackUrl {"url": "myapp://?code=210db3a4-1e90-4a64-b16d-1bb4c45d2760&state=eXavpAJAD7x8RhGY5HQQGuHV1BMjOrfS"}
[Tue Jun 01 2021 16:18:14.797] LOG cognito codeFlow {}
[Tue Jun 01 2021 16:18:14.803] LOG codeFlow {}
[Tue Jun 01 2021 16:18:15.320] ERROR [ERROR] 18:14.429 OAuth - Error handling auth response. [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.407] LOG cognito signIn_failure [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.408] LOG signIn_failure [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.441] LOG cognito cognitoHostedUI_failure [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.442] LOG Sign in failed [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.443] LOG cognito customState_failure [TypeError: Network request failed]
[Tue Jun 01 2021 16:18:15.445] LOG customState_failure [TypeError: Network request failed]
PFB my config details
const awsmobile = {
aws_project_region: 'XXXXXXXX',
aws_cognito_identity_pool_id:
'XXXXXXXX',
aws_cognito_region: 'XXXXXXXX',
aws_user_pools_id: 'XXXXXXXX',
aws_user_pools_web_client_id: 'XXXXXXXX',
oauth: {
domain: 'XXXXXXXX-southeast-1.amazoncognito.com',
scope: [
'phone',
'email',
'openid',
'profile',
'aws.cognito.signin.user.admin',
],
redirectSignIn: 'myapp://',
redirectSignOut: 'myapp://',
responseType: 'code',
},
federationTarget: 'COGNITO_USER_POOLS',
};
export default awsmobile;
The issue got fixed after adding below lines to android/app/build.gradle
'''
compile "com.squareup.okhttp3:okhttp:4.2.1"
compile "com.squareup.okhttp3:logging-interceptor:4.2.1"
compile "com.squareup.okhttp3:okhttp-urlconnection:4.2.1"
'''
Have you enabled deep-linking on Android? https://reactnative.dev/docs/linking
<activity
android:name=".MainActivity"
android:launchMode="singleTask">
I'm trying to configure a logstash filter for an apache log errors filter definition. It is basically the 'combined' LogFormat with some additional field, here is the apache log format definition:
[11446] [Thu Jan 30 07:50:49 2020] [debug]: RT::Date used
Time::ParseDate to make '2020-01-31T07:20:46Z' 1580446800
(/app/rt4/sbin/../lib/RT/Date.pm:274)
or it could be of this format:
[Wed Jun 26 22:13:22 2013] [error] [client 10.10.10.100] PHP Fatal
error: Uncaught exception '\Foo\Bar'
I tried the below solution:
APACHE_ERROR_TIME %{DAY} %{MONTH} %{MONTHDAY} %{TIME} %{YEAR}
APACHE_ERROR_LOG [%{APACHE_ERROR_TIME:timestamp}]
[%{LOGLEVEL:loglevel}] (?:[client %{IPORHOST:clientip}]
){0,1}%{GREEDYDATA:errormsg}
but it gives a grok_match_failure.
Please help me with a generic working pattern for the above string (meaning it should not matter even if one of the part of string is not there)
Updated Question:
So, the above worked with https://stackoverflow.com/a/59986583/4127230 and I have again got stuck with another system log string.
Can you also suggest a generic grok pattern same for the below strings:
Feb 2 18:21:14 localhost prometheus_postgres_exporter: time=\"2020-02-02T18:21:14+04:00\" level=info msg=\"Error while closing non-pinging DB connection: \" source=\"postgres_exporter.go:1001\"
and
Feb 2 05:56:10 localhost logstash: [2020-02-02T05:56:10,934][INFO ][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>6}
Using the provided APACHE_ERROR_TIME, I got a match with this pattern:
\[%{APACHE_ERROR_TIME:timestamp}\] \[%{LOGLEVEL:loglevel}\](?: \[client %{IPORHOST:clientip}\] ){0,1}%{GREEDYDATA:errormsg}
In addition to escaping the square brackets, there was some misplaced spaces that prevented the match.
For:
[11446] [Thu Jan 30 07:50:49 2020] [debug]: RT::Date used Time::ParseDate to make '2020-01-31T07:20:46Z' 1580446800 (/app/rt4/sbin/../lib/RT/Date.pm:274)
Result:
timestamp Thu Jan 30 07:50:49 2020
loglevel debug
clientip
errormsg : RT::Date used Time::ParseDate to make '2020-01-31T07:20:46Z' 1580446800 (/app/rt4/sbin/../lib/RT/Date.pm:274)
before match: [11446]
For:
[Wed Jun 26 22:13:22 2013] [error] [client 10.10.10.100] PHP Fatal error: Uncaught exception '\Foo\Bar'
Result:
timestamp Wed Jun 26 22:13:22 2013
loglevel error
clientip 10.10.10.100
errormsg PHP Fatal error: Uncaught exception '\Foo\Bar'
Not able to start apache. Giving the below error.
Could some one please help me on this?
Error message:
ip-10-128-9-27 httpd-scl-wrapper: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf: Cannot load modules/mod_ssl.so into server: /lib64/libcrypto.so.10: version `OPENSSL_1.0.2' not found (required by /opt/rh/httpd24/root/etc/httpd/modules/mod_ssl.so)
Below is the detailed error message.
[root#ip-10-128-9-27 centos]# systemctl status httpd24-httpd.service
● httpd24-httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-12-07 12:34:05 UTC; 12s ago
Process: 29020 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
Process: 29018 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 29018 (code=exited, status=1/FAILURE)
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Starting The Apache HTTP Server...
Dec 07 12:34:05 ip-10-128-9-27 httpd-scl-wrapper[29018]: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf...
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Dec 07 12:34:05 ip-10-128-9-27 httpd-scl-wrapper[29020]: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf...
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Failed to start The Apache HTTP Server.
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Unit httpd24-httpd.service entered failed state.
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service failed.
We´re using apache (2.0, with ssl) to proxy the requests to a web service installed on weblogic. We have mod_wl.so installed, and all works fine with small requests.
However, with larger requests (say, 300 KB), the apache stalls and display this error message:
"Failure of server APACHE bridge: No Backend Sever available for connections": timed out after 20 seconds or idempotent is set to off."
We replicate the scenario in another server, and the error persists (instead of "20 seconds", it says "30 seconds" for the same request).
How can I avoid this size limitation? Is it a bug in mod_wl.so? Is it a config value that is missing? (As a side note, the web service works fine when tested directly from inside the weblogic console, no matter how big the file)
Thanks for any help!
UPDATE:
changed to mod_wl_20.so with same results, here is the chunk of the log:
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Content-Length]=[352196]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Connection]=[Keep-Alive]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-SSL]=[true]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-Client-IP]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Proxy-Client-IP]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-Forwarded-For]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[x-weblogic-cluster-hash]=[2Ik836PQKnD7XHQ2RcWGOWkcRRA]
Wed Sep 28 11:27:37 2011 <15359131722005124> operation WRITE failed on fd 23: revents=0x00000018
Wed Sep 28 11:27:37 2011 <15359131722005124> IO TImed out error
Wed Sep 28 11:27:37 2011 <15359131722005124> POST timed out to the server 10.182.5.5:7005
Wed Sep 28 11:27:37 2011 <15359131722005124> ***Exception type [WRITE_ERROR_TO_SERVER] (POST ti
med out to the server 10.182.5.5:7005
) raised at line 152 of ap_proxy.cpp
Wed Sep 28 11:27:37 2011 <15359131722005124> error sending headers or Post Data to WebLogic, sys er
r#: [0] sys errmsg [Success]
Wed Sep 28 11:27:37 2011 <15359131722005124> Marking 10.182.5.5:7005 as bad
Wed Sep 28 11:27:37 2011 <15359131722005124> got exception in sendRequest phase: WRITE_ERROR_TO_SER
VER [os error=0, line 152 of ap_proxy.cpp]: POST timed out to the server 10.182.5.5:7005
at line 2994
Wed Sep 28 11:27:37 2011 <15359131722005124> Failing over after WRITE_ERROR_TO_SERVER exception in
sendRequest()
Wed Sep 28 11:27:37 2011 <15359131722005124> attempt #1 out of a max of 10
Wed Sep 28 11:27:37 2011 <15359131722005124> No good servers left in the general list, reverting ba
ck to the static list
Wed Sep 28 11:27:37 2011 <15359131722005124> Host extracted from serverlist is [10.182.5.5]
Wed Sep 28 11:27:37 2011 <15359131722005124> Host extracted from serverlist is [10.182.5.5]
Wed Sep 28 11:27:37 2011 <15359131722005124> Initializing lastIndex=0 for a list of length=2
Post timed out to 10.182.5.5:7005
This is the WebLogic which Apache is trying to post to.
You have confirmed this works when directly posted to the same Weblogic server.
The 20 seconds mathces the default KeepAliveSecs which you can try to increase.
Have you set a value in the plugin for WLIOTimeoutSecs.
This defaults to 300. Defines the amount of time in seconds the plug-in waits for a response to a request from WebLogic Server.
But from your log it does not look like Apache is waiting for 300 seconds before failing.
Similarly MaxPostSize defaults to -1, just check that you have not set some low value for that.
Check out the other plugin parameters on this list
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143055
You might also want to tinker with the FileCaching element for POST requests
I have just looked at my error_logs for a particular site of mine which I haven't done in a while and in Apache's error_log i find hundreds of lines that have this same format:
[Mon Mar 16 19:20:03 2009] [error] [client xx.81.239.xxx] [Mon Mar 16 19:20:03 2009] [info] Executing "/home/get/public_html/fileReader.php" as UID 32596, GID 32599, referer: http://www.mysite.com/index.php
[Mon Mar 16 19:20:03 2009] [error] [client xx.3.27.xx] [Mon Mar 16 19:20:03 2009] [info] Executing "/home/get/public_html/fileReader.php" as UID 32596, GID 32599, referer: http://www.mysite.com/index.php
[Mon Mar 16 19:20:03 2009] [error] [client xx.202.191.xx] [Mon Mar 16 19:20:02 2009] [info] Executing "/home/get/public_html/fileReader.php" as UID 32596, GID 32599, referer: http://www.mysite.com/index.php
I have Googled and could not find anything on this. What does it mean? Is it even an error? If not, way record it?
Thanks all
these log entries originate from suPHP. they are info messages, not errors (the code says logger.logInfo(...), not logger.logError(...)). you can suppress them by setting suPHP's loglevel configuration option to "warn", "error", or "none".
These entries might be some custom error log format.