If errors occur while starting ihttpd

This is the documentation for the deprecated product DCImanager 5. It is no longer updated and may be irrelevant. Documentation for the current version of DCImanager can be found in the DCImanager 6 section.

If "Failed to start daemon" or "Failed to become daemon" errors occur when starting ihttpd, an error in /dev/null may be the cause. To eliminate the error:

Check the format, owner, and rights of the /dev/null file:

ls -alh /dev/null && file /dev/null

An example of response

crw-rw-rw- 1 root root 1, 3 May 17 12:36 /dev/null
/dev/null: character special

If the response to the command does not match the response in the example, remove the /dev/null file and recreate it:
```
rm -f /dev/null && mknod /dev/null c 1 3 && chmod 666 /dev/null
```
Stop the running ihttpd processes:
```
killall ihttpd
```

Start ihttpd:

systemctl start ihttpd

service ihttpd start