Skip to main content

Back on My Primary Streaming Server

Back on My Primary Streaming Server

Well I’m back on my original streaming server. Since June 29th 2013 I have been on my backup server working great to give my primary music server a break in a sense. Well with the power supply going out on my backup server I decided to bring up my primary music server after getting my backup server going again with the new power supply, then transfer the current up to date database and settings back to my primary server.

This could not be standard or simple of course. After updating my physical music tracks from the backup to the primary server I tried backing up the database and settings from SAM Broadcaster but that failed with a permissions error. I then went to MySQL Workbench to try and export the SAM database but ran into the “mysqldump.exe is version 5.5.16” will not work with version 5.6.10 of MySQL Server since the log files will be a different version of mysqldump.exe. I’m using MySQL Workbench version 5.2CE.

To correct the MySQL problem with the different mysqldump.exe versions I had to go to MySQL Workbench -> Edit -> Preferences ->Administrator -> “Path to mysqldump Tool” -> <Browse to $PATH:MySQL\ bin\mysqldump.exe”>. I then dumped that to and SQL file and copied it to my primary music server, forwarded my ports from my router back to my primary music server, started SAM broadcaster on my primary server, went to the config file on my Linux web server and pointed to my primary music server again, reinstalled RemoteWeb that syncs database tables from music server to web server as well as ftp my album files to my web server and I was done!

Phew what crazy stuff!

Some pics first of failed power supply from backup primary server, second pictures of hastily modified internals of system after replacing power supply, third picture and last back of music server showing power cable routing.

2013-07-13_22-23-07_105.jpg2013-07-13_22-22-44_708.jpg2013-07-13_22-24-04_41.jpg

Updated Main & Backup Streaming Server Database & Application

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

MicrosoftInternetExplorer4

Yeah I went for it last night and this morning, first updated my backup streaming server database and application. I had previously attempted to do this earlier in the week but had issues when my MySQL database starting eating up the CPU with the process that updates my Linux web server.

On the backup server I tried to update to the current version from MySQL 5.5 to MySQL 5.6.2 of the current database didn’t work so I removed 5.5 and reinstalled the current version database MySQL 5.6.2 fresh.

I then did a backup of my current working application and database using the SAM Broadcaster application on my primary music server and copied that backup over to the backup server. When I tried using SAM Broadcaster to import as I normally do it erred out with an error complaining about “restore failed duplicate entry for…” one of my songs. I tried backup of the main server again and a couple of restores but kept getting the same error. I figured the error was now due to the fact that the two databases were different versions with MySQL 5.1 on my primary music server and 5.6.2 now on my backup server.

So now due to the different version of MySQL on both servers I decided to bypass using the SAM application backup and restore did a MySQL dump from the primary backup server from version 5.1 copied it over to the backup streaming server imported that dump to my fresh and new MySQL 5.6.2 and it worked. I then started SAM Broadcaster to see how my streaming software liked the new database and it could not see the new database from SAM.

I now decided to update SAM broadcaster to the current version of SAM 2013.4 and restarted MySQL service and started SAM and still could not see the new database with the application. This prompted me to uninstall SAM and reinstall and setup from scratch pointing to the new settings I had created with “MySQL Workbench”. This worked fine and I could now see the new database instance!

I then configured SAM Broadcaster to talk to my ftp site on my web server to update my album artwork automatically and sync to my MySQL database on my Linux web server ( I run Windows 2003 on my Streaming servers currently). I finished updating my user and license information in SAM Broadcaster 2013.4 did another dump from MySQL on my primary music streaming server since it had been running streaming music and updating this whole time I wanted to get to the point I could cut over from my backup server to start at the next song queued on my primary server.

Once all my settings were configured on my backup I stopped my primary music streaming server, forwarded my ports in my router to my backup server, insured my Shoutcast server instance had started, was set to start automatically and now I was streaming on my backup server.

I then repeated this whole process on my primary server and that’s where I am now playing on my backup server but updating some other application packages on my primary server plus running some utilities and scans that should improve the performance plus updating supporting applications.

So kickback go up top and click on a link to listen to some crazy Internet Radio streaming music!

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,”sans-serif”;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:”Times New Roman”;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}