Having the the CMS and Transmitter on the same tuner is not recommended in production; Lab environment should be ok unless you are going to try do stress testing.

Before upgrading any channels you will first you will need to upgrade the tuner. If there is no Infra Service you will need to subscribe to one. Once the Infra Service is subscribed and finishes upgrading the tuner it will restart the tuner. I can see from the logs that the tuner was restarted:

[27/Jan/2015:11:25:42 +0530] - info Administrator 1007 Kernel exited: 2

[27/Jan/2015:11:25:45 +0530] - info Administrator 1000 Kernel started: -service

[27/Jan/2015:11:25:45 +0530] - info Administrator 1850 Token provider: Marimba

Please elaborate on what you mean by the tuner is not working after subscribing the Infra Service? Is the CMS not starting up? seems like a compatibility issue. Try using the Channel Manager channel and subscribing the Infra Service, you can then see what channels are failing to start

Ok first subscribe to the Channel Manager channel. it will give you an interface to work with. something like the attached..

You have to use this as you have CMS and the Tx on the same tuner.

Before you do that please send me the CMS channels history logs under ch.xx/data/logs, the Infra Service channel history logs and the tuner history logs

From the 8.3 Release:

To upgrade to version 8.3.00, you can upgrade from the following tuner versions:

  8.1.01.009

Note:

  Schema upgrade is not directly supported from 8.1.01.009 to 8.3.00. You must

first upgrade to 8200007, 8201003, or 8202002 and then upgrade to 8.3.00

schema.

  If you are using a version older than 8.1.01.009f, and if you want to upgrade to a

64-bit server profile, ensure to first upgrade Infrastucture Service to the latest

GA Hotfix for Infrastructure Service 8101009, and then upgrade to 8.3.00.

  8.2.00.007

  8.2.01.003

  8.2.02.002 or later