Difference between revisions of "Troubleshooting"

Revision as of 18:04, 19 February 2016

If something is wrong, run the health check under "Advanced" in the server panels.

Images removed in INDD

Check INDD server! Run top to look for percentage of CPU in use and console for InDesign server activity. If a server process appears to be stuck, use sudo kill (process number).

Solr

If items are missing from Content Station or if the Search tool has no list of facets on the left, Solr may be down.

Recovering lost work

Use either versions or Time Machine backup. Note that INDD files live in the WebEdit directory that's part of Edit.

Elvis credential error

Info on recovering from this error without losing work

See more info on InDesign recovery here.

Before rebooting

Ensure no one is in Elvis

From the desktop client: System—>Manage sessions

Ensure no one is in Enterprise

From the admin panels: Advanced—>Online users

Stop Elvis server

From the application on Prod.

InDesign server

Unmount WebEdit folder.

After a reboot

Production

• Data HD should be mounted
• Connect to edit/CCCBackup
• Elvis Server should open and start running
• Apache Solr should boot
  • If not running, check Solr for restart instructions.
• This should also start Enterprise.
• Enterprise Admin—>Health Check
  • Make fixes, re-run health check
• Elvis Admin—>Server status

INDD server

• INDD server should boot
• Connect to edit/CCCBackup
• Ensure WebEdit folder is properly mounted
• Smart Mover should boot
  • Drag Smart Mover starter to terminal and hit return to start the service.
  • Choose smart mover service from Smart Mover menu and enter “ww”.
• System prefs login items
  • Smart Mover
  • INDD server

Indesign Client

   - Aysling and Plate crashes
   - Why does INDD crash?
       - Is this an INDD problem?
       - Is this an Aysling problem?
   - Troubleshooting steps
          - Check article import
               - Did the copy come in clean from TextWrangler?
               - Is there any Word or other formatting in it?
               -Are there any smart quotes or smart apostrophes in the article? If so, change them. 
       - Check top 
           - Too many apps?
           - Not enough memory?
           - Kill some apps, free up memory?
       - Check Console
           - Any obvious errors?
       - Check Disk utility
           - Permissions
           - Disk errors?
       - Reboot INDD
           - Latest version?
           - Version same as all others?
           - Check INDD plugins/troubleshoot
           - Check INDD prefs
           - Check INDD
           - Check fonts
               - What if you replace all fonts in the doc with a standard 13 font?
               - Does the doc get better?
               - Does the font in question work on another machine?
       - Reboot Smart Connection
       - Reboot Computer
              -Does computer connect to network via Ethernet? It should.
              -Does computer connect to servers via AFP? It should NOT use SMB.
       - Open doc on another identical  machine.
           - Does it work?
           - Does it throw errors?
           - What’s the difference?
       - Connections
           - Ethernet connection but not Wifi
           - AFP connection not SMB
           - Is the computer connected to the VPN? It does not need to be. Woodwing does not require that. 

Moving license on Aysling from Prod to Dev

To migrate your data from Prod to dev you need a dump of the database and a copy of the file store. It is imperative that no one is working in the system when you create these copies because if they are out of sync you will receive errors. You will need to make sure that the name and location of the file store is exactly the same as the current one in dev. I would also recommend writing down your licenses and possibly taking a screenshot of the licenses currently activated just to make sure you put the same amount back in place. Following are the steps to take to migrate the data:

1. Remove the license from the production system from the admin licensing page. Deactivate all client licenses first and the server license last. (The server license is always the top license, called Enterprise v9).
2. Create a dump or backup of the sql database (named Enterprise) using your favorite admin tool or terminal.
3. Create a copy of your file store located at /Volumes/DataHD/FileStore.
4. Relicense your Production machine from the admin portal. At this point it will be available again for production.
5. Remove the license from the dev system from the admin licensing page.
6. Migrate the copy of your file store and database to the dev server.
7. Make sure to maintain the same file path to the file store on your dev machine. Wherever the old file store was is where you want to put your newly migrated one.
8. Import the sql database backup to the dev using your favorite admin tool or terminal.
9. Relicense the dev server from the admin portal.
10. Test to make sure everything works as expected.