Crash Yaws after running

Crash Yaws after running

[vinoski]

In Erlang, a crash doesn't necessarily indicate a bug, but rather it can mean that an important expectation failed, and the system should not proceed until the problem is corrected. The issue in this case is that Yaws is configured for logging but due to permissions issues, it can't write its logs.

The key element of everything you posted is this:

{{badmatch,
{error,
{handler_not_added,
{open_failed,"/usr/local/var/log/yaws/report.log",eacces}}}}

Getting an EACCES error for a file means "permission denied", so maybe one or more of its parent directories are not accessible to your application, or maybe report.log is not writable by your application.

• Check permissions on the /usr/local/var/log directories to make sure all have at least 555 (r-xr-xr-x) permissions
• Check that the /usr/local/var/log/yaws directory is also writable, something like 755 (rwxr-xr-x, for user write) or 775 (rwxrwxr-x, for user and group write) permissions
• Verify that your application is running as a user or group that has write permissions for /usr/local/var/log/yaws
• Similarly, verify that the file /usr/local/var/log/yaws/report.log is writable by the user or group your application runs as

If you're using log rotation, also make sure any existing rotated log files have suitable write permissions.

Steve, Thank you very much!
My trouble was that I didn't have enough rights to write to the report.log
When I set 775 for report.log Yaws started successfully!
Now I suddenly realized that I want to learn more about Erlang.