I added a few new features which fixed the album art issue on the requests page long with moving the entire site to a new system as mention on my personal blog on this site (http://dhoytt.com/mainblog/)
I also updated the OS of the system the music stream plays from which caused the stream to be down for a brief time.
Well I built up the new server moved over the database and pointed the configuration files and ports to the new server off of the evaluation server and the migration from old server is complete. I actually went from older server, then to evaluation server and now permanent server as of now. This is something I normally do every 2 or 3 years dependant on technology changes. I went a bit longer than normal this time so was really due for an update!
Basically I moved my SAM Broadcaster software off of an old ancient system running Xeon multi-core (not dual core) with W2003 to evaluation copy of W2012 R2 with dual Quad core Xeon CPUs server for testing then to w2012 R2 Essentials for my permanent solution also running dual Quad core Xeon CPUs with more memory on the music streaming side of the house. I continue to run my web servers with Fedora & Centos Linux flavors mostly in the virtual environment of XenServer with FreeNAS providing the storage. Now the evaluation music server which is identical will switch to music server backup.
What the new server provides is the ability to scale the way I want with double the encoders without impacting CPU or memory as on my older system. You will hear a much cleaner sound with less buffering. I also went back to using internal soundcards since the USB with 2012 r2 seemed a bit flaky but the side on this is it will also provide much better sound with the way I use SAM and better interface if I want to use items such as mikes or other inputs.
More updates coming soon on the web side of the house since the backend is stronger so stay tuned but in the mean time enjoy the updated sounds provided from my update of the music server!
Tonight I am evaluating a new music server I built. I have a new OS and new hardware with updated streaming application. There has been a little up and down with the music stream as I get everything configured but it’s looking very good!
I will end up having the equal amount of streams on Icecast as I have had for years on Shoutcast with identical bit rates.
This new setup will allow me to also use my NAS setup to manage my music better. There will be less buffering for listeners even with the amount of encoders I have running more than doubling the system is handling this increase with very little memory or CPU impact.
Stay tuned the backend is changing dramatically and I like to have that solid before making the website changes that will better reveal my backend updates for you to use.
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;}