I've been using Paw flawlessly for the last two weeks, and is very happy about it.
Today, however, Paw suddenly started hanging and I can't seem to figure out why.
I checked system console and found the following:
11/03/16 13:21:49,000 kernel[0]: process Paw[80756] thread 3901396 caught burning CPU! It used more than 50% CPU (Actual recent usage: 95%) over 180 seconds. thread lifetime cpu usage 90.059289 seconds, (87.893506 user, 2.165783 system) ledger info: balance: 90009882091 credit: 90013946094 debit: 4064003 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 93974331721
11/03/16 13:21:53,382 spindump[1310]: Saved cpu_resource.diag report for Paw version 2.3.2 (2003002001) to /Library/Logs/DiagnosticReports/Paw_2016-03-11-132153_SkyAir-222.cpu_resource.diag
The cpu_resource.diag can be found here: https://gist.github.com/greew/9451a34966371035f019
I've tried force closing the app and opening again, but it hangs immediately after startup.
Does any of you have any idea about what's going on?
Best regards
/Jesper
Ok, after few tries, I found that Paw also threw this in the console:
11/03/16 13:30:42,000 kernel[0]: Sandbox: Paw(80947) deny(1) file-read-data /Users/jesper/Library/Containers/com.luckymarmot.Paw
11/03/16 13:30:42,000 kernel[0]: Sandbox: Paw(80947) deny(1) file-read-data /Users/jesper/Library/Containers
11/03/16 13:30:42,000 kernel[0]: Sandbox: Paw(80947) deny(1) file-read-data /Users/jesper/Library
11/03/16 13:30:42,000 kernel[0]: Sandbox: Paw(80947) deny(1) file-read-data /Users/jesper
11/03/16 13:30:42,000 kernel[0]: Sandbox: Paw(80947) deny(1) file-read-data /Users
I tried deleting the /Users/jesper/Library/Containers/com.luckymarmot.Paw folder and now then it worked again (I had to recreate all calls, though).
Related
I have a mobile and web app that use firebase realtime database and there are some long running tasks which are served on servers with the help of firebase-queue and firebase-admin. The long running tasks is to find out who else is using the mobile app in a person's contact book. So, if you install the app, the app will send a task to the server with your contact book data and ask it to find the people in the contact book who are also using the app. Every now and then I see two types of errors in the logs. First error is below which also cause the node process to stop.
/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:15373
return queue[i].onComplete(new Error(abortReason), false, null);
^
Error: maxretry
at /Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:15373:52
at exceptionGuard (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:4018:9)
at repoRerunTransactionQueue (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:15386:9)
at repoRerunTransactions (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:15279:5)
at /Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:15260:13
at /Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:7061:17
at PersistentConnection.onDataMessage_ (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:7088:17)
at Connection.onDataMessage_ (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:5882:14)
at Connection.onPrimaryMessageReceived_ (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:5876:18)
at WebSocketConnection.onMessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:5778:27)
at WebSocketConnection.appendFrame_ (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:4491:18)
at WebSocketConnection.handleIncomingFrame (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:4539:22)
at Client.mySock.onmessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:4438:19)
at Client.dispatchEvent (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2883:30)
at Client._receiveMessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:3042:10)
at Client$2.<anonymous> (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2924:49)
at Client$2.emit (node:events:539:35)
at Client$2.emit (node:domain:475:12)
at Client$2.<anonymous> (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2186:14)
at pipe (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:1503:40)
at Pipeline$1._loop (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:1510:3)
at Pipeline$1.processIncomingMessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:1479:8)
at Extensions$1.processIncomingMessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:1645:20)
at Client$2._emitMessage (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2177:22)
at Client$2._emitFrame (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2137:19)
at Client$2.parse (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:1863:18)
at Client$2.parse (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:2369:60)
at IO.write (/Users/varungupta/Projects/myapp-server/node_modules/#firebase/database-compat/dist/index.standalone.js:186:16)
at TLSSocket.ondata (node:internal/streams/readable:754:22)
at TLSSocket.emit (node:events:527:28)
at TLSSocket.emit (node:domain:475:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at TLSSocket.Readable.push (node:internal/streams/readable:228:10)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)
There isn't much information about what exactly caused the maxretry error. The error happens at random after a few days of running the script. It doesn't happen right away.
The second error that I see that isn't as disruptive as the one above is
[2022-06-01T10:30:49.722Z] #firebase/database: FIREBASE WARNING: transaction at /queue/tasks/-N3TDQCAdt4y-akb0_MK failed: disconnect
This doesn't stop the node process and I can see that a transaction failed but not sure why did it disconnect and how can I resolve this problem.
I am using firebase-admin 9.6.0.
Since a few days I am not able to test cloud functions locally anymore, as all write functions are not executed and nothing is returned, consequently the function hangs and eventually stops with a timeout.
Example function:
import { database as dbEvent } from "firebase-functions";
export default dbEvent.ref("/tariffs/removeHistory").onCreate((event: any) => {
console.log("START");
const bikesHistoryRef = event.data.adminRef.parent.parent.child("bikesHistory");
return bikesHistoryRef.set(null).then((res) => console.log("Delete done", res));
});
Result:
firebase > removeBikeHistory("test")
'Successfully invoked function.'
firebase > info: User function triggered, starting execution
info: START
firebase >
firebase > info: Execution took 61023 ms, finished with status: 'timeout'
info: Execution took 49694 ms, finished with status: 'crash'
Any suggestion what is wrong? This happens with all my cloud functions, and when I deploy them it works.
I have tried with:
firebase-admin#5.5.1
firebase-functions#0.7.3
firebase-tools#3.15.4 (-g)
and
firebase-admin#5.6.0
firebase-functions#0.7.5
firebase-tools#3.16.0 (-g)
EDIT:
After enabling logging I get the following errors:
info: 0: onDisconnectEvents
info: p:0: Making a connection attempt
info: p:0: Failed to get token: Error: Credential implementation provided to initializeApp() via the "credential" property failed to fetch a valid Google OAuth2 access token with the following error: "Error fetching access token: invalid_grant (Bad Request)". There are two likely causes: (1) your server time is not properly synced or (2) your certificate key file has been revoked. To solve (1), re-sync the time on your server. To solve (2), make sure the key ID for your key file is still present at https://console.firebase.google.com/iam-admin/serviceaccounts/project. If not, generate a new key file at https://console.firebase.google.com/project/_/settings/serviceaccounts/adminsdk.
p:0: data client disconnected
info: p:0: Trying to reconnect in 1283.8299240003184ms
0: onDisconnectEvents
I have actually seen this error when I installed an older firebase-function/admin version, but thought it got fixed by installing the newer version. How can I fix it?
I found the solution in this bug report:
https://github.com/firebase/firebase-functions/issues/135
I have deleted the following file, now my cloud functions work locally again:
rm ~/.config/gcloud/application_default_credentials.json
Can you help me please.
I have Eclipse Java EE IDE Kepler
M2E: version 1.4.0
eclipse.ini:
...
--launcher.XXMaxPermSize
512M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
1024m
-Xms256m
-Xmx512m
By creating a new Maven project i keep getting:
- long "Retrieving artifacts" pause
- then strange out of memory error:
An internal error occurred during: "Retrieving archetypes:".
GC overhead limit exceeded
How can it take so mutch memory?
I am using Visual Studio 2017, Xamarin 4.5.0.486, Xamarin.Android 7.3.1.2 creating a Wear 2.0 app utilizing FireBase. My code was working fine, but now I'm receiving the following during Initialization:
07-18 11:59:20.453 D/FirebaseApp( 9289): com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
07-18 11:59:20.481 D/FirebaseApp( 9289): com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
07-18 11:59:20.499 I/FA ( 9289): App measurement is starting up, version: 10298
07-18 11:59:20.499 I/FA ( 9289): To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
07-18 11:59:20.515 I/FA ( 9289): To enable faster debug mode event logging run:
07-18 11:59:20.515 I/FA ( 9289): adb shell setprop debug.firebase.analytics.app com.palarum.patient.up.wear
07-18 11:59:20.529 I/FirebaseInitProvider( 9289): FirebaseApp initialization successful
Even though it says "Successful" I am not able to get a token using var token = FirebaseInstanceId.Instance.Token. I get null where I used to get a token.
I'm also seeing FirebaseApp initialization unsuccessful every once in a while.
I'm running the debugger over WiFi to the actual device (LG W280). Google Play Services is installed and available.
I've checked my package_name, I re-downloaded my google-services.json file. All to no avail...
Anyone run into this before or have any suggestions as to what else I should check?
Thanks in advance!
When I try to run a command on a sub-process created by ProcessBuilder, i get segmentation violation.
[Symfony\Component\Process\Exception\RuntimeException]
The process has been signaled with signal "11".
But this doesn't happen upto v2.5.12 only from v2.6.0
finally the issue is found. Thanks to Rackspace support staff Cristian Banciu and Mike Bostic
Cause:
Latest newrelic php agent 4.23.1.107 causes seg fault when used with symfony 2.6.0 or above with process component.
newrelic.browser_monitoring.auto_instrument = 0 didn't help
Solution:
finally i downgraded newrelic php agent to 4.21.0.97-1 and all work fine
Anojan