> OK, getting a bit further with this :-) > > So after rebuilding uwsgi (updated to 1aac5be), rebuilding the handler > code, the rebuild was triggered by a change to the underling file, but it > ended with a bad address error: > > Tue May 7 14:56:01 2013 - [uwsgi-touch-exec] running go build main3.go > Tue May 7 14:56:02 2013 - *** /Users/0x6e6562/Workspace/src/main3 has > been > touched... grace them all !!! *** > gateway "uWSGI http 1" has been buried (pid: 92886) > ...gracefully killing workers... > subprocess 92891 exited with code 0 > Gracefully killing worker 1 (pid: 92885)... > worker 1 buried after 1 seconds > binary reloading uWSGI... > chdir() to /Users/0x6e6562/Workspace/src > closing all non-uwsgi socket fds > 2 (max_fd = 2560)... > found fd 3 mapped to socket 0 (127.0.0.1:56274) > running /Users/0x6e6562/Workspace/src/main3 > execvp(): Bad address [core/master_utils.c line 443] > > I'll have a look into the master_utils module. > >
I have managed to fix it. Unfortunately i fear go support in uWSGI could be dropped after go 1.1: https://groups.google.com/forum/?fromgroups=#!topic/golang-nuts/KAR8r6fZaVA i will try to do my best to avoid it... -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
