Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: "A duplicate file name exists, or the file cannot be found." #9

Open
autonia opened this issue Feb 24, 2022 · 12 comments
Open

Comments

@autonia
Copy link

autonia commented Feb 24, 2022

I am getting this error on all tagui modules, not sure why.

"A duplicate file name exists, or the file cannot be found."

@skadefro
Copy link
Contributor

Can you send a screenshot ?
Can you send the error message with stract trace from the console of NodeRed ?

@autonia
Copy link
Author

autonia commented Feb 24, 2022

Here you go:

24 Feb 08:47:52 - [trace] runtime event: {"id":"runtime-state","retain":true}
24 Feb 08:47:52 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"950216c6444b1c2c6b7655064492e981"},"retain":true}
24 Feb 08:47:52 - [info] Server now running at http://127.0.0.1:1880/
24 Feb 08:47:52 - [info] Starting flows
24 Feb 08:47:52 - [debug] red/nodes/flows.start : starting flow : global
24 Feb 08:47:52 - [debug] red/nodes/flows.start : starting flow : 608c7a06bc9c696a
24 Feb 08:47:52 - [debug] red/nodes/flows.start : starting flow : 91df88a7837f1d30
24 Feb 08:47:52 - [trace] [flow:global] start flow [global]
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a] start flow [608c7a06bc9c696a]
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  id               | type         | alias
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  72989475f149a1b1 | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  418f09c01764843f | tagui tagui  |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  780e7913c164d502 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  fbf4bc9877858317 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  f184a7214066ad4d | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  e8b19c9242847d90 | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  5c8813b2b21eb34b | tagui tagui  |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  f3af1605.ec32f8  | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  db71650e.26fae8  | image        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  b70aac26.17577   | file in      |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  8f0c45bc.efe9e8  | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  da8f73d9.56c67   | comment      |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  7dd22cb.07c64d4  | tagui tagui  |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  06471aaa3953cdd3 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  3519761bb38fbf79 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  c842cb8a3dc89b1a | link in      |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  fb2cd7aa40f9cf22 | function     |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  d1b730951c80e440 | link call    |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  ddd0ed22a434a764 | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  cb162b4f7f376df5 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  441c569df8ee2fb8 | link out     |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  2bf369d81c63870c | inject       |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  f55d645e635b857c | tagui tagui  |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a]  459e929c73d89058 | debug        |
24 Feb 08:47:52 - [trace] [flow:608c7a06bc9c696a] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30] start flow [91df88a7837f1d30]
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  id               | type         | alias
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  c259202afa802200 | inject       |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  1175226732afa39d | csv          |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  88a253e48133ef11 | file in      |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  e089c920752ff3b8 | function     |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  6173e93079949fe7 | join         |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  5e2681b90fe425b8 | csv          |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  0ed22016f87e717a | debug        |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30]  70c6984f8c830967 | file         |
24 Feb 08:47:52 - [trace] [flow:91df88a7837f1d30] ------------------|--------------|-----------------
24 Feb 08:47:52 - [trace] runtime event: {"id":"runtime-state","retain":true}
24 Feb 08:47:52 - [info] Started flows
24 Feb 08:47:54 - [trace] comms.open XT4LIT059vG9Br3xcc79aUxBdOsRMEIYmJlU2Dx6TXI=
24 Feb 08:48:01 - [trace] comms.close XT4LIT059vG9Br3xcc79aUxBdOsRMEIYmJlU2Dx6TXI=
24 Feb 08:48:01 - [trace] comms.open xYk8wm6Y/kEnnH3/USCHwUjMl67T7VJjjPUB8ie4YiI=
[
  'ERROR A duplicate file name exists, or the file\r\ncannot be found.'
]

sQwnrGOu35

@skadefro
Copy link
Contributor

Is this a plain nodered ( running as your user ) or running hosted in a process running as a service? Then try enabling headless
If running as your user, does chrome open?

@autonia
Copy link
Author

autonia commented Feb 24, 2022

Is this a plain nodered ( running as your user ) or running hosted in a process running as a service?

Plain I think. I am launching node-red manually through the command line.

Headless: I see the same error.

For non-headless, I see Chrome open, and the flows run correctly. It's just that they all end with that error.

@autonia
Copy link
Author

autonia commented Feb 24, 2022

Tested to make sure I wasn't seeing the same error using just TagUI in the command line. No errors there.

The larger issue here is that I don't get a success message even though the tagui module is running successfully. So it's difficult to connect the tagui nodes to my larger plan.

@autonia
Copy link
Author

autonia commented Feb 25, 2022

I was able to test this same issue on another machine and didn't receive the error. So it seems like it may be a configuration issue on my side. Do you have any advice on how to track this down? I'm not sure where to start.

@autonia
Copy link
Author

autonia commented Feb 26, 2022

I just updated NR to 2.2.2 and that appears to have solved the problem. I was on 2.1.7 before, having installed NR a few days before 2.2 was released.

Oddly, the other machine I ran the same flow with no errors is only on 2.1.4. 🤷‍♀️

@autonia autonia closed this as completed Feb 26, 2022
@autonia
Copy link
Author

autonia commented Feb 26, 2022

Sorry, I spoke too soon. The error has returned.

@autonia autonia reopened this Feb 26, 2022
@skadefro
Copy link
Contributor

So i was on v2.0.0-beta.2 ( and I'm using nodejs version 16.13.0 ) and using windows 11
I do not get an error, so tested with version 2.1.4 and 2.2.2 as well
2.1.7 seems to not exist, it fails with
image

I also tested with 2.2.1 and 2.2.2 on Debian GNU/Linux 10 (buster) with nodejs version 16.14.0

In all my tests, using my reproduction of your workflow, it runs without an error and returns an empty payload from the completed output node, as expected. (sorry for the big picture below, from my windows box )
image

I need a way to re-produce this, in order to troubleshoot. Also, if the error is from tagui I need @autonia to help out

@autonia
Copy link
Author

autonia commented Feb 28, 2022

I have node and tagui installed in my user folder. Could that be significant / possibly help reproduce the issue?

I have confirmed that running the same tag with tagui on the command line doesn't result in the same error.

2.1.7 seems to not exist

Sorry, I believe it must have been 2.1.4.

@autonia
Copy link
Author

autonia commented Feb 28, 2022

To troubleshoot, I just removed my user folder installed version of Node. I reinstalled using the 64-bit Windows Installer on the Node page to the default Program Files directory. Still returns the same error.

I also tried removing the tagui install from my user folder, and let the tagui NR module reinstall it. Same error.

Is there any kind of log file written to disk by your module at the conclusion of execution? The error results AFTER the completion of the tagui code...

sreDd7rfAf

@skadefro
Copy link
Contributor

skadefro commented Feb 28, 2022

I see that error comes from tagui, so I'm going to pass this on to @ruthtxh I have no idea how to "attack" this problem to see why it's giving this error ( personally i would properly go for processmon but i hope there is some verbose logging you can enable in tagui for this ? )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants