Safe to kill a process called *:etlservicemgr (LISTEN)?

Question

In my Nextjs app, I have tried storing the Stripe paymentIntent.id in the browser localStorage which is then read in the Checkout page. Since, it is stored in localStorage, the Checkout page can persistently read the stored paymentIntent.id even after page refresh. I have not stored the client_secret since the documentation advised against storing it.

There is no issue in setting and getting the paymentIntent.id to and from localStorage. But when I try to retrieve the client_secret to confirm payment using this payment id, I am getting error

const paymentIntent = await stripe.paymentIntents.retrieve(
  'pi_1DpRyD2eZvKYlo2CG4EobdYA'
);

Error: TypeError: Cannot read properties of undefined (reading 'retrieve')

Perhaps, it is not possible to retrieve paymentIntent object from client? If so, what is the best way to store or retrieve the client_secret ?

Note: I am creating the paymentIntent using a cloud function trigger when a doc is written to Firestore.

Solution

etlservicemgr is not the name of the process listening on port 9001. It's the name of the IANA-registered service for that port number.

$ grep 9001 /etc/services
etlservicemgr   9001/tcp                # ETL Service Manager
etlservicemgr   9001/udp                # ETL Service Manager

The name of the process appears in the first column, COMMAND.

We can see from your output that two processes called node are listening on this port (one on IPv4, and one on IPv6). And node is most likely a Node.js application.

Comments

[ObiwanKeTobi]

What does ps -ef | grep 3369 say? Why are you trying to use a port that is already in use? Are you the owner of the server?

[Hyppy]

Smells like TOR

[iluvatar14]

@CraigWatson ps -ef | grep 3369 leads back to my own app... whoops. Looks like it didn't exit cleanly and the process hung around. I killed it and restarted my app, which is working as expected.

[iluvatar14]

Yes, you are right. With the help of @CraigWatson and ps -ef | grep 3369, it turns out it's my own app blocking itself from restarting.