https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# report-bugs
s
This message was deleted.
b
(I’m online)
Then it gets stuck:
Copy code
ERROR: Cannot run more than one Graphite process at once.
no other graphite process is running
j
what does the output look like with 
—-debug
b
Copy code
2023-07-24T14:18:23.595Z: Forking: background upgrade-prompt...
2023-07-24T14:18:23.603Z: Forked and unrefed: background upgrade-prompt
2023-07-24T14:18:23.678Z: Reading cache seed data...
2023-07-24T14:18:23.720Z: Loading cache...
2023-07-24T14:18:23.731Z: Acquiring cache lock...
ERROR: Cannot run more than one Graphite process at once.
2023-07-24T14:18:23.784Z: ConcurrentExecutionError: Cannot run more than one Graphite process at once.
    at Object.lock (/snapshot/monologue/apps/public/cli/dist/graphite.js)
    at /snapshot/monologue/apps/public/cli/dist/graphite.js
    at Generator.next (<anonymous>)
    at /snapshot/monologue/apps/public/cli/dist/graphite.js
    at new Promise (<anonymous>)
    at An (/snapshot/monologue/apps/public/cli/dist/graphite.js)
    at /snapshot/monologue/apps/public/cli/dist/graphite.js
    at /snapshot/monologue/apps/public/cli/dist/graphite.js
    at Generator.next (<anonymous>)
    at /snapshot/monologue/apps/public/cli/dist/graphite.js
2023-07-24T14:18:23.785Z: Forking: background post-traces...
2023-07-24T14:18:23.793Z: Forked: background post-traces
2023-07-24T14:18:23.793Z: Flushing trace...
2023-07-24T14:18:23.795Z: Sent trace to child...
2023-07-24T14:18:23.795Z: Done
2023-07-24T14:18:24.001Z: Child disconnected
j
Try 
rm .git/.graphite_cache_lock
and then run the command with 
--debug
again
b
That fixed the graphite process issue, and submitting a stack works this time around
I think it was just a temporary network issue or something, which happens — real issue is that caused the lock, and it’s not clear how to clear the lock (I looked in the docs)
maybe not so temporary
UNCAUGHT EXCEPTION: request to https://api.graphite.dev/v1/graphite/pull-requests failed, reason: getaddrinfo ENOTFOUND api.graphite.dev UNCAUGHT EXCEPTION: FetchError: request to https://api.graphite.dev/v1/graphite/pull-requests failed, reason: getaddrinfo ENOTFOUND api.graphite.dev
j
Yeah, as you caught, the key issue is that we only unlock when we catch the exception (the "uncaught exception" should never be hit) — which 
gt
command is causing the uncaught exceptions?
b
gt ss
also I’m getting that network error very often
no network issues otherwise
Copy code
ping api.graphite.dev
PING api.graphite.dev (34.223.167.44): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
Copy code
% ping <http://google.com|google.com>
PING <http://google.com|google.com> (142.251.143.78): 56 data bytes
64 bytes from 142.251.143.78: icmp_seq=0 ttl=116 time=25.209 ms
64 bytes from 142.251.143.78: icmp_seq=1 ttl=116 time=26.664 ms
64 bytes from 142.251.143.78: icmp_seq=2 ttl=116 time=25.851 ms
I can’t access app.graphite.dev either
d
what do you get for
Copy code
dig api.graphite.dev
actually one sec let me check something
if i do this, i get a 404 page (which is correct i believe)
Copy code
╰ curl -is <https://api.graphite.dev/>
HTTP/2 404
date: Mon, 24 Jul 2023 18:26:28 GMT
content-type: text/html; charset=utf-8
content-length: 139
x-powered-by: Express
x-graphite-request-id: a573b7bf-4781-4b35-9d2e-ee9034d87ddb
vary: Origin
access-control-allow-credentials: true
content-security-policy: default-src 'none'
x-content-type-options: nosniff

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /</pre>
</body>
</html>
our Express server is responding at least. what do you get for that? i also see that 
ping <http://api.graphite.dev|api.graphite.dev>
doesn't work, but we might just drop ping packets on the floor
b
I’d dropped off yesterday. I’ll report back if I encounter these issues again today and see if I can get the details you’re asking for at that time
First command I ran today…
Copy code
% gt rs
🌲 Pulling master from remote...
From <http://github.com|github.com>:....
 * branch              master     -> FETCH_HEAD
master fast-forwarded to b2567d7fadda2396bcbb907bb60129f5f8a3534f.

tip: You can skip pulling trunk with the `--no-pull` flag.
Feeling expert? `gt user tips --disable`

ERROR: request to <https://api.graphite.dev/v1/graphite/pull-requests> failed, reason: getaddrinfo ENOTFOUND api.graphite.dev
Copy code
; <<>> DiG 9.10.6 <<>> api.graphite.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9601
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.graphite.dev.		IN	A

;; ANSWER SECTION:
api.graphite.dev.	60	IN	A	34.223.167.44
api.graphite.dev.	60	IN	A	52.36.59.207
api.graphite.dev.	60	IN	A	34.216.49.219

;; Query time: 61 msec
;; SERVER: 10.128.128.128#53(10.128.128.128)
;; WHEN: Tue Jul 25 13:17:56 CEST 2023
;; MSG SIZE  rcvd: 93
Worked a second time. When I repro next I’ll try the curl
d
if you do this
Copy code
╰ whois graphite.dev | rg "Name Server"
Name Server: <http://ns-1506.awsdns-60.org|ns-1506.awsdns-60.org>
Name Server: <http://ns-1950.awsdns-51.co.uk|ns-1950.awsdns-51.co.uk>
Name Server: <http://ns-419.awsdns-52.com|ns-419.awsdns-52.com>
Name Server: <http://ns-578.awsdns-08.net|ns-578.awsdns-08.net>
Name Server: <http://ns-1506.awsdns-60.org|ns-1506.awsdns-60.org>
Name Server: <http://ns-1950.awsdns-51.co.uk|ns-1950.awsdns-51.co.uk>
Name Server: <http://ns-419.awsdns-52.com|ns-419.awsdns-52.com>
Name Server: <http://ns-578.awsdns-08.net|ns-578.awsdns-08.net>
i get this
Copy code
╰ dig api.graphite.dev @ns-1506.awsdns-60.org

; <<>> DiG 9.10.6 <<>> api.graphite.dev @ns-1506.awsdns-60.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23878
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;api.graphite.dev.              IN      A

;; ANSWER SECTION:
api.graphite.dev.       60      IN      A       52.36.59.207
api.graphite.dev.       60      IN      A       34.223.167.44
api.graphite.dev.       60      IN      A       34.216.49.219

;; AUTHORITY SECTION:
graphite.dev.           180     IN      NS      <http://ns-1506.awsdns-60.org|ns-1506.awsdns-60.org>.
graphite.dev.           180     IN      NS      <http://ns-1950.awsdns-51.co.uk|ns-1950.awsdns-51.co.uk>.
graphite.dev.           180     IN      NS      <http://ns-419.awsdns-52.com|ns-419.awsdns-52.com>.
graphite.dev.           180     IN      NS      ns-578.awsdns-08.net.
which more or less matches your DNS results
do you have a funny DNS setup where you're at? a pihole perhaps?
b
I don’t think there’s a funny DNS setup. I haven’t run into this since, will check the above if/when I do
f
also running into 
cannot run more than one graphite process at once
, seems like it occurs when graphite is unable to commit to github due to bad wifi signal
b
Yeah, error recovery from network issues needs to be better. And it would be helpful if there was more public information on how to fix an invalid “more than one graphite process”
j
more than one graphite process
this bug is fixed in the most recent version
🙌 1
Sorry about that!
❤️ 1
Open in Slack
PreviousNext
Powered by