Yaws Embedded on R13B04 failing for me with ** exception exit: {noproc,{gen_server,call, [yaws_server,check_certs,infinity]}} about yaws HOT 2 CLOSED

My hunch here is that there is something wrong with your OTP installation.
The error

 Reason:     {'EXIT',{error,could_not_load_driver}}

Seems to indicate that there is something wrong with your OTP installation.
You fail to load the linked in driver for sendfile().
Next step to debug this - at your end - is to try to start yaws outside your application
as

% yaws -i

And see if the driver still cannot be loaded.

I've tried on R13B04 and see no problems.

/klacke

from yaws.

I figured it out. I had naively 'vendored' a copy of yaws under my deps dir in my OTP app, assuming I could push that around to any env without having to do a local install of Yaws (thinking it was only beam files). Obviously this is incorrect since at least the following native libs where included in that dir (compiled for OS X) which were failing to load on the linux server.

deps/yaws/priv/lib/setuid_drv.so
deps/yaws/priv/lib/yaws_sendfile_drv.so

Once I changed my erl -pa to include /usr/local/lib/yaws/ebin on both systems (which now have native installs of Yaws compiled from source) all was good under R13B04 on both systems.

yaws -i works fine.

Thanks. My error.

from yaws.