NOTE:Beginning with GroupWise Mobility Service 18.4, MCheck is expanded and enhanced to include functionality previously available only in a support tool named dsapp.
The dsapp tool lets OpenText Support personnel manage multiple users and groups, perform certificate-management tasks without requiring terminal prompt commands, and directly affect the health and content of the Mobility databases.
MCheck now makes those popular features available to GroupWise Mobility Service Administrators.
To run MCheck:
In a terminal window on the Mobility server, become root by entering su - and the root password.
Change to the following directory:
/opt/novell/datasync/tools/mcheck
Run the following command:
python3.11 mcheck.pyc
The top-level MCheck menu displays:
1 System 2 Users 3 Database 4 Checks & Queries 0 Exit Select Option:
Access the various MCheck tasks by typing numbers to navigate the menu structure shown in the left column of Table 2-1 below.
The right column outlines what MCheck does when the task number from one of the options below is entered:
Table 2-1 Navigating and Using the MCheck utility
Task Navigation Path |
Steps and/or Results - log file path is /opt/novell/datasync/tools/mcheck/logs |
||
---|---|---|---|
1. System |
Typing 1 exposes the system integrity checks and SSL/TLS certificate-related maintenance tasks explained below. |
||
|
1. Get Mobility Configuration |
This option
|
|
|
2. GroupWise System Address Book Check |
This option
|
|
|
3. SSL Check |
This option
|
|
|
3. Fix Mobility Encryption (Conditional - appears only when the host name changed and Mobility requires fixing) |
IMPORTANT:If you change the Mobility server’s host name after installing and configuring Mobility, for example as part of an upgrade process, encryption breaks and Mobility stops working. When that happens, only a restricted System is available with two options:
To repair Mobility, do the following:
Log file name: fixHostname_yyyy-mm-ddThh:mm:ss.log |
|
|
4. GroupWise Maintenance Verification |
This option
|
|
|
5. Certificates 1. Certificates (This becomes the first option if Mobility Encryption requires fixing.) |
Provides guided certificate generation and maintenance tasks as documented below. |
|
|
|
1. Generate CSR & Private Key |
Guides you through the process of generating a private key and creating a Certificate Signing Request (CSR) to submit to a trusted third-party Certificate Authority. This option
|
|
|
2. Generate self-signed certificate |
Although not recommended as a best practice, this option lets you generate a self-signed certificate from a previously created CSR. For example, the CSR that you created in 1. Generate CSR & Private Key.
|
|
|
3. Apply certificates (Generate PEM) |
After you receive the signed public certificate from a certified CA, use this option to apply the certificates by following the prompts as briefly explained below.
|
|
|
4. Verify certificate / key pair |
Use this option if you simply need to verify that a certificate and key pair match. |
|
|
5. Update GMS Services certificates |
GMS services rely on an internal certificate store named gms_server.pem. You must never manually change or modify this certificate store. On the other hand, the certificates eventually expire. When that happens, use this option to update the certificates and renew the gms_server.pem certificate store. |
|
|
0. Back to System Menu |
|
|
0. Main Menu |
|
|
|
|
|
|
2. Users |
Typing 2 in the main menu, exposes the user and group tasks explained below. |
||
|
1. Check User |
Use this option to view the GMS statistics for a given user, discover any problems with the account, and see what actions will correct the problems.
Log file name: GWuser_id_yyyy-mm-ddThh:mm:ss.log NOTE:You can also run Check User directly from the command line without accessing the menu by running the command: python3.11 mcheck.pyc --user userID A summary of results is provided for each of the GroupWise components: Email, Calendar, and Contacts. If any action is required, it will be recommended in the summary. If items are missing from these folders, MCheck will attempt to recover the missing items. More details can be found in the log file location that is displayed with the results. |
|
|
2. Remove Old Event Configurations |
Use this option to remove all event configurations that contain the MAC address that you enter.
|
|
|
3. Remove and reinitialize users options |
|
|
|
|
1. Force remove user(s)/group(s) db references |
Mobility uses databases to track which GroupWise users are registered for Mobility services and the data and messages, etc. that are associated with them. If you are unable to remove users or groups using the Web Console, you can use this option to force the removal of users and/or groups from the databases. Users, groups, and data on the GroupWise system are not affected.
|
|
|
2. Reinitialize user(s)/group(s) |
If one or more of you Mobility user accounts has problems, for example they are missing calendar or other data, MCheck can clear their data and messages and then restore everything from the backend GroupWise system.
|
|
|
3. Reinitialize all failed users |
If multiple Mobility users show a Failed state in the admin console, you can use this option to reinitialize all of them rather than using the admin console to reinitialize one of them at a time. This removes associated data from the database and synchronizes with GW again. Log file name: userActions_yyyy-mm-ddThh:mm:ss.log |
|
|
4. Reinitialize all users |
IMPORTANT:If you choose to continue after the initial prompt, this will take some time to complete. Also, a device configured with a user being reinitialized will be unable to connect to the server until that user is reinitialized.
Log file name: userActions_yyyy-mm-ddThh:mm:ss.log |
|
|
0. Back to System Menu |
|
|
0. Main Menu |
|
|
|
|
|
|
3. Database |
To enter the Database sub-menus, you must stop Mobility. MCheck prompts you as follows:
|
||
|
1. Vacuum Database |
Consider using this option when your mobility databases seem larger than expected. Vacuuming a database tightens up data records, making previously used space fragments once again available for database use. Although PostgreSQL includes a process that performs incremental vacuum operations, these are not as thorough as a full vacuum. This option performs a full vacuum of the mobility databases. You should follow this up with the next Database option to re-index the database. Log file name: dbActions_yyyy-mm-ddThh:mm:ss.log |
|
|
2. Re-index Database |
If users are experiencing performance delays, reindexing the database might help. This options rebuilds all of the indexes. Keep in mind that reindexing can take a while if the Mobility databases are large. Log file name: dbActions_yyyy-mm-ddThh:mm:ss.log |
|
|
3. CUSO (Clean-up Start Over |
|
|
|
|
1. Cleanup and Start Over (Except Users) |
This removes everything from the mobility databases except the User and Group records, which are reinitialized when the cleanup process concludes. Log file name: dbActions_yyyy-mm-ddThh:mm:ss.log |
|
|
2. Cleanup and Start Over (Everything) |
This removes everything from the mobility databases, essentially restoring the mobility server to where it was when the initial install completed. Log file name: dbActions_yyyy-mm-ddThh:mm:ss.log |
|
4. Change PostgreSQL datasync_user password |
This option enables you to change the password for the datasync_user account in the event of a lost password. The datasync_user account is used to access the PostgreSQL databases for the GroupWise Mobility Service. |
|
|
0. Back |
Because MCheck’s database operations required stopping the service, you are prompted as follows:
|
|
4. Checks & Queries |
Typing 4 in the main menu, exposes the checks and queries explained below. If you detect any unresolvable issues from running any of these checks, contact Customer Support. |
||
|
1. General Health Check |
The General Health Check runs and displays a series of tests that populate a status in the terminal. After all the checks are run, you can view more detailed information about each check in the mcheck logs at: /opt/novell/datasync/tools/mcheck/logs To find issues in an open log, search for /Failed. NOTE:You can also run the General Health Check directly from the command line without accessing the menu by running the command: python3.11 mcheck.pyc --healthCheck HINT:The first time this option is run, the gh.conf file is created in the /opt/novell/datasync/tools/mcheck/conf directory. This file is used for the NTP server time check. If you are getting an NTP failure when running the General Health Check, you can modify the file to point to a different NTP server. |
|
|
2. GW Pending Events by User (consumerevents) |
This option displays data about events that users execute on their devices that are pending processing in the Mobility Service. |
|
|
3. Mobility Pending events by User (syncevents) |
This option displays data about user events driven by the mobility service that have not yet synced with user devices. |
|
|
4. Generate csv list of inactive users |
This option enables you to generate a CSV file that lists inactive users. Output includes the last time the user accessed GroupWise or “Never”. The file is generated in the MCheck, Logs directory: /opt/novell/datasync/tools/mcheck/logs |
|
|
0. Back |
|
|
0. Exit |
Return to the terminal prompt. |