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

Processing starts, but sketches won't run when localhost is not resolvable #3123

Closed
cibomahto opened this Issue Feb 24, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@cibomahto

cibomahto commented Feb 24, 2015

System: OS X 10.9.5
Processing version: 2.2.1

The symptoms were that Processing was working fine one day, then later sketches stopped working (or sometimes would delay opening for 1-2 minutes). No errors were displayed in Processing, logged in console .err files, or reported to OS X Console. There was a repeating error in OS X Console for an unrelated service (mtmapp: MTM fs Mount server retrying...), and troubleshooting that lead to discovering that localhost wasn't resolvable. The issue was that localhost was set to "fe80::1%lo0", and IP6 routing was somehow broken. Resetting localhost to 127.0.0.1 allowed Processing sketches to work again.

@cibomahto

This comment has been minimized.

Show comment
Hide comment
@cibomahto

cibomahto Feb 24, 2015

This might be too esoteric of an issue to fix, but it would be excellent if there were some warning that this was happening, or a timeout error if Processing wasn't able to establish a connection to itself.

cibomahto commented Feb 24, 2015

This might be too esoteric of an issue to fix, but it would be excellent if there were some warning that this was happening, or a timeout error if Processing wasn't able to establish a connection to itself.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 24, 2015

Member

I'd like to fix this, but I can't imagine how we'd even detect that you've messed with your hosts file to cause resolution problems (outside of weird platform-specific hacks that don't work in all cases).

Certainly we can detect timeouts, but that's a long ways from "hey, why'd you mess with your hosts file?" or "your ipv6 routing is screwed up" in any fashion that would be suitable for our target audience.

Member

benfry commented Feb 24, 2015

I'd like to fix this, but I can't imagine how we'd even detect that you've messed with your hosts file to cause resolution problems (outside of weird platform-specific hacks that don't work in all cases).

Certainly we can detect timeouts, but that's a long ways from "hey, why'd you mess with your hosts file?" or "your ipv6 routing is screwed up" in any fashion that would be suitable for our target audience.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 9, 2016

Member

Figured out a way to at least detect that it was happening (and confirmed we don't have any control over use of the localhost name).

For the next release (3.2.4 or 3.3), this will be detected and an error shown to the user: #4738

Member

benfry commented Nov 9, 2016

Figured out a way to at least detect that it was happening (and confirmed we don't have any control over use of the localhost name).

For the next release (3.2.4 or 3.3), this will be detected and an error shown to the user: #4738

@cibomahto

This comment has been minimized.

Show comment
Hide comment
@cibomahto

cibomahto commented Nov 9, 2016

Thanks!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment