Nextcloud 12 Internal Server after Login

When I upgraded from owncloud 9 to Nextcloud 11, my web interface was broken and I could not login to Nextcloud with the web interface. I was able to sync files to the server. I then upgraded to Nextcloud 12 through the command line interface. I still could not login to the web interface. The cause of the problem was that I moved the location of the webserver files from /var/www/owncloud to /var/www/nextcloud. I made the appropriate changes to my apache “sites-enabled” configuration file to redirect to the new location at /var/www/nextcloud. I was recieving “Internal Server” errors and the web interface was broken and unusable. I fixed the problem by following this thread on deleting the data the in the database table oc_filecache. My steps were to:

  1. stop the apache2 webserver
  2. delete everything in “oc_filecache”
  3. restart the webserver

I used phpmyadmin to remove the contents from “oc_filecache”. I think “oc_filecache” contained information pointing to the old location of my files in the owncloud directory instead of the new nextcloud directory. Below are the steps to delete the information in “oc_filecache”.

  1. Login to phpmyadmin.
  2. Select your “nextcloud” database. Your database may have a different name that “nextcloud”
  3. Select the table “oc_filecache” listed on the far left of the page
  4. Select “Operations” from the tab at the top of the page.
  5. Select “Empty the table (TRUNCATE)”
  6. Select “Ok” to confirm you will be deleting the data in “oc_filecache”.
  7. Finished.

Smoked Brisket 2015-1211

Brisket: grade choice, 14.1 lbs, cut in half to fit on Brinkman Gourmet Charcoal Grill and Smoker.
Outside Temperature 37-55 ° F, wind South 5-10 mph
0900 Brisket put on smoker. Coals used with oak wood chips for smoke. Cooking temperature ranged from 200 to 250 ° F.
0300 Meat was 155° F
14:30 Wrapped meat in two layers of foil and put in convection oven at 350° F. Meat was 153° F
1600 Meat was 165° F
1700 Meat was 180° F. Liquids leaking out of foil because foil was too small to adequately seal the meat. This caused on piece to be drier than the other.
1800 Meat was 194° F.
1900 Meat was 202° F
Brisket was very tender and not to smokey.



How to See Information about a Installed Debian Package

I needed to see what version of mythtv was installed on my Ubuntu 14.04 server and what dependencies it requires. Here is the solution.

.deb packages are stored at /var/cache/apt/archives

View mythtv package name

#ls -l /var/cache/apt/archives/mythtv*

Display Package Version

# apt-show-versions mythtv
mythtv:all/trusty 2:0.27.4+fixes.20150514.6b73976-0ubuntu0mythbuntu4 uptodate


Display Package Information

#dpkg -I mythtv_2%3a0.27.4+fixes.20150514.6b73976-0ubuntu0mythbuntu4_all.deb

new debian package, version 2.0.
size 78060 bytes: control archive=1084 bytes.
1449 bytes, 34 lines control
209 bytes, 3 lines md5sums
Package: mythtv
Version: 2:0.27.4+fixes.20150514.6b73976-0ubuntu0mythbuntu4
Architecture: all
Maintainer: MythTV Ubuntu Maintainers <>
Installed-Size: 101
Depends: mysql-server | mysql-server-5.6, mythtv-database, mythtv-frontend, mythtv-backend, ntp | time-daemon | ntp-simple
Suggests: mythtv-doc
Section: graphics
Priority: optional
Description: Personal video recorder application (client and server)
MythTV implements the following PVR features, and more, with a
unified graphical interface:
- Basic 'live-tv' functionality. Pause/Fast Forward/Rewind "live" TV.
- Video compression using RTjpeg or MPEG-4
- Program listing retrieval using XMLTV
- Themable, semi-transparent on-screen display
- Electronic program guide
- Scheduled recording of TV programs
- Resolution of conflicts between scheduled recordings
- Basic video editing
This package will install a complete MythTV client/server environment on a
single system. If you are intended on using this as your only MythTV machine,
and this machine is already configured as a desktop, this package will get you
up and running switfly.
If you are intended on installing this on a standalone/non-desktop machine,
you should look into the metapackages available:
mythtv-backend-master (backend with a local database)
mythtv-backend (backend needing a remote database)