Latest interface: 0.3.1
Latest system: 010

6 posts

Posted on 20 April 2016 @ 08:42
To protect against the Badlock exploit, I unwisely did
pkg update and pkg upgrade

ZFSguru seemed to work, but the web interface didn't work. lighttpd seemed to be running. From this page I found where lighttpd.conf lives:
ERROR: PHP script is not running as the "zfsguru-web" user; aborting
CIPHER's post gave info about the zfsguru-web user.

I found that lighttpd.conf didn't have a reference to zfsguru-web. So theses lines were entered:
Steps 1 and 2 were skipped.
Step 3. Now, let the webserver Lighttpd run with the new user by modifying /usr/local/www/lighttpd/lighttpd.conf, and replace the current 'www' user configuration with 'zfsguru-web' like this:
server.username = "zfsguru-web"
server.groupname = "zfsguru-web"

Step 4. Then you might need to change permissions to zfsguru-web for some directories:
chown -R 888:888 /var/spool/lighttpd
chown -R 888:888 /var/log/lighttpd

Then I updated lighttpd with the new lighttpd.conf:
service lighttpd -f /usr/local/etc/lighttpd/lighttpd.conf restart

lighttpd will remember the location of lighttpd.conf.
If the ZFSguru web interface doesn't work, reboot the computer.

Is it practicable to add a lighttpd config check in ZFSguru's startup scripts? The commands in CIPHER's post could update /usr/local/etc/lighttpd/lighttpd.conf
so that the ZFSguru web interface would always work if a pkg upgrade is done.

Last Page

Valid XHTML 1.1