VMmanager Cloud Documentation
en En
es Es
Your feedback is an opportunity for improvement!
Take part in the survey and contribute to the development of the ISPsystem ecosystem.
Take the survey

If errors occur while starting ihttpd

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:

  1. 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
  2. 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
  3. Stop the running ihttpd processes:

    killall ihttpd
  4. Start ihttpd:

    systemctl start ihttpd

    or

    service ihttpd start
The article was last updated on 08.26.2020. The article was prepared by technical writers of ISPsystem.