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.

Sign up for GitHub

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

Jump to bottom

UDP:out error requires node-red restart after deployment #1470

Closed
gusev-genotek opened this issue Oct 30, 2017 · 2 comments · Fixed by #1508 · May be fixed by ajesse11x/node-red#6 or ajesse11x/node-red#8
Closed

UDP:out error requires node-red restart after deployment #1470

gusev-genotek opened this issue Oct 30, 2017 · 2 comments · Fixed by #1508 · May be fixed by ajesse11x/node-red#6 or ajesse11x/node-red#8
Labels
bug

Comments

@gusev-genotek
Copy link

With a UDP sender node, I have to restart node-red after each redeployment, because of the error thrown when I hit Deploy button (after that UDP sender does not work). I am using it with a preceding OSC node (node-red-contrib-osc), but the error is thrown regardless of OSC. I have confirmed it both on ubuntu and OSX. The flow is attached.

The error:

30 Oct 10:54:49 - [info] Node-RED version: v0.17.5
30 Oct 10:54:49 - [info] Node.js  version: v7.10.1
30 Oct 10:54:49 - [info] Linux 4.4.0-72-generic x64 LE
30 Oct 10:54:50 - [info] Loading palette nodes
30 Oct 10:54:50 - [warn] ------------------------------------------------------
30 Oct 10:54:50 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
30 Oct 10:54:50 - [warn] ------------------------------------------------------
30 Oct 10:54:50 - [info] Settings file  : /home/vgusev/.node-red/settings.js
30 Oct 10:54:50 - [info] User directory : /home/vgusev/.node-red
30 Oct 10:54:50 - [info] Flows file     : /home/vgusev/.node-red/flows_dellgv.json
30 Oct 10:54:50 - [info] Server now running at http://127.0.0.1:1880/
30 Oct 10:54:50 - [info] Starting flows
30 Oct 10:54:50 - [info] Started flows
30 Oct 10:54:50 - [info] [udp out:65bd6199.7fee1] udp broadcast ready: 3000 -> 255.255.255.255:3000
30 Oct 10:54:50 - [info] [udp in:e00d1277.83cb9] udp listener at 0.0.0.0:3001
30 Oct 10:55:29 - [info] Stopping flows
30 Oct 10:55:29 - [info] [udp out:65bd6199.7fee1] udp output stopped
30 Oct 10:55:29 - [info] [udp in:e00d1277.83cb9] udp listener stopped
30 Oct 10:55:29 - [info] Stopped flows
30 Oct 10:55:29 - [info] Starting flows
**30 Oct 10:55:29 - [error] [udp out:65bd6199.7fee1] Error: Not running**
30 Oct 10:55:29 - [info] Started flows
30 Oct 10:55:29 - [info] [udp in:e00d1277.83cb9] udp listener at 0.0.0.0:3001

flows_dellgv.json.zip
@echtelerp
Copy link

I have some similar issue:
When I change the Port inside a UPD node send or recieve, I also have to reboot my pi. After the reboot the UDP receiver node can receive again.

@dceejay dceejay added the bug label Dec 5, 2017
@dceejay
Copy link
Member

dceejay commented Dec 5, 2017

Should only need to stop / restart Node-RED rather than reboot... but yeah tis a bug.

dceejay pushed a commit that referenced this issue Dec 5, 2017
tag ports in use properly so they get closed correctly
00b6f6a 
to close #1470
@dceejay dceejay mentioned this issue Dec 5, 2017
Merged
knolleary pushed a commit that referenced this issue Jan 11, 2018
@dceejay @knolleary
tag UDP ports in use properly so they get closed correctly (#1508)
a3640bd 
* tag ports in use properly so they get closed correctly

to close #1470

* redo test for udp port in use

* check port in use correctly on close
@snyk-bot snyk-bot mentioned this issue Jul 10, 2020
Open
@snyk-bot snyk-bot mentioned this issue Jul 20, 2020
Open
@rvalle rvalle mentioned this issue Mar 16, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
3 participants
@dceejay @echtelerp @gusev-genotek