diff options
| author | Haakon Meland Eriksen <haakon.eriksen@far.no> | 2015-10-11 14:32:01 +0200 |
|---|---|---|
| committer | Haakon Meland Eriksen <haakon.eriksen@far.no> | 2015-10-11 14:32:01 +0200 |
| commit | df45374041a9c955eb2ff49ba07959813360c057 (patch) | |
| tree | 82d746d8608a7573a9f4d0266b968a8e4ea2166d | |
| parent | d5788ba53a9a2d111b8502f3843b0947cf7c58d0 (diff) | |
| download | volse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.tar.gz volse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.tar.bz2 volse-hubzilla-df45374041a9c955eb2ff49ba07959813360c057.zip | |
Updated Hubzilla on OpenShift HOWTO with use of logging
| -rw-r--r-- | .openshift/README.md | 8 | ||||
| -rw-r--r-- | doc/Hubzilla_on_OpenShift.bb | 8 |
2 files changed, 16 insertions, 0 deletions
diff --git a/.openshift/README.md b/.openshift/README.md index 3ed5fd595..535b9bdd1 100644 --- a/.openshift/README.md +++ b/.openshift/README.md @@ -24,6 +24,14 @@ Symptoms of need for MySQL database administration are: - you can login, but your channel posts are not visible. This can mean your item table is marked as crashed. - 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. +You can check your OpenShift logs by doing + +``` +rhc tail -a your_app_name -n your_domain -l your@email.address -p your_account_password +``` + +and you might be able to confirm the above suspicions about crashed tables, or other problems you need to fix. + ###How to fix crashed tables in MySQL 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. - Use the database username and password OpenShift creates for your instance at https://your_app_name-your_domain.rhcloud.com/phpmyadmin/ to login via the web into your phpMyAdmin web interface, click your database in the left column, in the right column scroll down to the bottom of the list of tables and click the checkbox for marking all tables, then select Check tables from the drop down menu. This will check the tables for problems, and you can then checkmark only those tables with problems, and select Repair table from the same drop down menu at the bottom. 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] |