Back to top
Trouble-shooting Info

Can no longer do a task

  • Confirm that the exact task acutually worked at some point.
  • Address any application/log error messages starting with the ones they both have in common before the rest.
  • Check for recent changes/updates to the application/environment.
  • If you activated SELinux, look at the audit.log and address any related issues.
    • Usually just needs: restorecon -Rv affected_directory.
    • SELinux audit.log resets after module add/updates and after reboots.
    • Set SELinux to permissive mode and generate as many distinct application errors before building modules.
    • Set SELinux to enforcing mode if disabled.
  • Confirm user:group on affected files and chown as required/allowed.
  • Confirm permissions on affected files and chmod as required/allowed.

 

Adding a new task does not work

  • If it is similar to some_similar_task, then see if some_similar_task is working.
  • Address any application/log error messages starting with the ones they both have in common before the rest.
  • Confirm user:group on affected files make sense or compare to some_similar_task.
  • Confirm permissions on affected files make sense or compare to some_similar_task.
  • If you activated SELinux, look at the audit.log and address any related issues.
    • Usually just needs: restorecon -Rv affected_directory.
    • New applications will probably require building a new SELinux module.
    • SELinux audit.log resets after module add/updates and after reboots.
    • Set SELinux to permissive mode and generate as many distinct application errors before building modules.
    • Set SELinux to enforcing mode if disabled.
  • Confirm communication and configuration of network[/apache]/application layers.
  • Refer to application documentation.

 

Passwords

  • Passwords are handled by the application, by apache, or sometimes both.
  • Refer to the application documentation regarding application password assistance.
  • Refer to the local admin info.php page links for others.
  • Appliance root password:
    • Requires direct console/appliance access.
    • Appliance uses grub as a bootloader for a Debian based linux distro.
    • Refer to online info for a desired method or how to recover root password.

 

Accidentally disabled/deleted all/part of a drupal stack

  • /etc/apache2/sites-available/SITEHOSTNAME.conf does exist:
    • Confirm its contents.
    • Confirm its enabled in apache (been symlinked into sites-enabled.)
    • Compare /etc/apache2/sites-available/SITEHOSTNAME.conf to the original template /usr/share/formavid/sites-template/sitehostname.conf.
    • Modify and substitute SITEHOSTNAME accordingly.
    • Apply/restart apache.
  • /etc/apache2/sites-available/SITEHOSTNAME.conf does NOT exist:
    • Copy /usr/share/formavid/sites-template/sitehostname.conf into /etc/apache2/sites-available.
    • Substitute the desired SITEHOSTNAME for sitehostname in both the file name and the file contents.
    • Modify accordingly.
    • Add to apache via webmin or symlink into sites-enabled.
    • Apply/restart apache.