aboutsummaryrefslogtreecommitdiffstats
path: root/doc/Hubzilla_on_OpenShift.bb
diff options
context:
space:
mode:
authorHaakon Meland Eriksen <haakon.eriksen@far.no>2015-10-11 14:32:01 +0200
committerHaakon Meland Eriksen <haakon.eriksen@far.no>2015-10-11 14:32:01 +0200
commitdf45374041a9c955eb2ff49ba07959813360c057 (patch)
tree82d746d8608a7573a9f4d0266b968a8e4ea2166d /doc/Hubzilla_on_OpenShift.bb
parentd5788ba53a9a2d111b8502f3843b0947cf7c58d0 (diff)
downloadvolse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.tar.gz
volse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.tar.bz2
volse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.zip
Updated Hubzilla on OpenShift HOWTO with use of logging
Diffstat (limited to 'doc/Hubzilla_on_OpenShift.bb')
-rw-r--r--doc/Hubzilla_on_OpenShift.bb8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/Hubzilla_on_OpenShift.bb b/doc/Hubzilla_on_OpenShift.bb
index 0a8571908..316894564 100644
--- a/doc/Hubzilla_on_OpenShift.bb
+++ b/doc/Hubzilla_on_OpenShift.bb
@@ -24,6 +24,14 @@ Symptoms of need for MySQL database administration are:
[*] you can login and you can see your channel posts, but apparently nobody is getting your posts, comments, likes and so on. This can mean your outq table is marked as crashed.
[/list]
+You can check your OpenShift logs by doing
+
+[code]
+rhc tail -a your_app_name -n your_domain -l your@email.address -p your_account_password
+[/code]
+
+and you might be able to confirm the above suspicions about crashed tables, or other problems you need to fix.
+
[b]How to fix crashed tables in MySQL[/b]
Using MySQL and the MyISAM database engine can result in table indexes coming out of sync, and you have at least two options for fixing tables marked as crashed.
[list]