URY Wiki - User contributions [en-gb]

Working From Home Resources/WebStudio

2023-02-07T15:41:10Z

11090: no longer two videos

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is URY's flagship Work From Home package. It's everything you ever loved about BAPS, and more, entirely online. For single-person music shows it will be all you need.

== Training Video ==

<html>
<iframe width="560" height="315" src="https://www.youtube.com/embed/Oqmq4GSE8Zo" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</html>

[[Working From Home Resources/WebStudio/Training|Transcript]]

== Getting trained ==

Once you've watched the video, please fill out [https://docs.google.com/forms/d/e/1FAIpQLSfWuE-BNA6k-TfeGgpS6lAy7UnrpcSgcK4QleHPmwK86CyaSQ/viewform?usp=sf_link this form] and we'll get you marked as trained!

Incident Report: 20230109

2023-01-11T20:05:04Z

11090:

{{Incident
|brief=ITS replaced some networking gear and broke some routes. Sad panda.
|severity=High
|impact=High (anything URY-related unavailable for around ~8 hours)
|start=2023-01-09 09:30
|end=2023-01-09 17:19
|leader=Joseph Sisson (JS)
|others=Michael Grace (MG), Marks Polakovs (MP)
}}

== Chronicle of Events ==

''(All times GMT)''

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some (ultimately futile) reboots later, we narrowed down the state of the network to:
* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.
:* With the exception of uryfw0 which has a separate IP (144.32.109.64).
:* Traceroutes showed the packets getting into a loop somewhere in Berrick Saul.
* This meant that the website and online streams were down.
* We could carry on broadcasting on AM, but FM failed
:* MP later diagnosed the FM issue to be a dependency on audio.ury.org.uk for the backup feed, and restored FM at 14:39.
::* You really don't want to know how... no, seriously, it's horrible...

An ITS ticket was filed at 12:12, and at around 17:14 service was restored.

== Lessons Learned ==

* We need to be more happy to assume, if we haven't touched the network and something's happened, it could be an ITS issue. Look at things like traceroutes earlier.
* ITS don't really know about us - like they'd have just assumed uryfw0 is just 144.32.109.64 and not a gateway for all of 144.32.64.160/27, so be happy to remind them of this.
* Phone ITS earlier if it's a big problem.
* Don't get distracted by things that are merely the result of the problem - i.e. our DNS is often external to URY (i.e. wogan or ITS nameservers), so it can't resolve DNS. But it doesn't mean the key problem is DNS - the key problem is that no traffic reached us. What didn't help was the confusion about guest PC being able to access the internet - this is because it has a web proxy (because IRN).

[[Category:Incident Reports]]

Incident Report: 20230109

2023-01-09T19:17:44Z

11090:

{{Incident
|brief=ITS replaced some networking gear and broke some routes. Sad panda.
|severity=High
|impact=Medium (anything URY-related unavailable for around ~8 hours)
|start=2023-01-09 09:30
|end=2023-01-09 17:19
|leader=Joseph Sisson (JS)
|others=Michael Grace (MG), Marks Polakovs (MP)
}}

== Chronicle of Events ==

''(All times GMT)''

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some (ultimately futile) reboots later, we narrowed down the state of the network to:
* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.
:* With the exception of uryfw0 which has a separate IP (144.32.109.64).
:* Traceroutes showed the packets getting into a loop somewhere in Berrick Saul.
* This meant that the website and online streams were down.
* We could carry on broadcasting on AM, but FM failed
:* MP later diagnosed the FM issue to be a dependency on audio.ury.org.uk for the backup feed, and restored FM at 14:39.
::* You really don't want to know how... no, seriously, it's horrible...

An ITS ticket was filed at 12:12, and at around 17:14 service was restored.

== Lessons Learned ==

TODO

[[Category:Incident Reports]]

Incident Report: 20230109

2023-01-09T17:54:45Z

11090: /* Chronicle of Events */

{{Incident
|brief=ITS replaced some networking gear and broke some routes. Sad panda.
|severity=High
|impact=Medium (anything URY-related unavailable for around ~8 hours)
|start=2023-01-09 09:30
|end=2023-01-09 17:19
|leader=Joseph Sisson (JS)
|others=Michael Grace (MG), Marks Polakovs (MP)
}}

== Chronicle of Events ==

''(All times GMT)''

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some (ultimately futile) reboots later, we narrowed down the state of the network to:
* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.
:* With the exception of uryfw0 which has a separate IP (144.32.109.64).
:* Traceroutes showed the packets getting into a loop somewhere in Berrick Saul.
* This meant that the website and online streams were down.
* We could carry on broadcasting on AM, but FM failed
:* MP later diagnosed the FM issue to be a dependency on audio.ury.org.uk for the backup feed, and restored FM at 14:39.
::* You really don't want to know how... no, seriously, it's horrible...

Cue an ITS ticket, and at around 17:14 service was restored.

== Lessons Learned ==

TODO

[[Category:Incident Reports]]

Incident Report: 20230109

2023-01-09T17:49:14Z

11090:

{{Incident
|brief=ITS replaced some networking gear and broke some routes. Sad panda.
|severity=High
|impact=Medium (anything URY-related unavailable for around ~8 hours)
|start=2023-01-09 09:30
|end=2023-01-09 17:19
|leader=Joseph Sisson (JS)
|others=Michael Grace (MG), Marks Polakovs (MP)
}}

== Chronicle of Events ==

''(All times GMT)''

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some reboots later, we narrowed down the state of the network to:
* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.
:* With the exception of uryfw0 which has a separate IP (144.32.109.64).
:* Traceroutes showed the packets getting into a loop somewhere in Berrick Saul.
* This meant that the website and online streams were down.
* We could carry on broadcasting on AM, but FM failed
:* MP later diagnosed the FM issue to be a dependency on audio.ury.org.uk for the backup feed, and restored FM at 14:39.
::* You really don't want to know how... no, seriously, it's horrible...

Cue an ITS ticket, and at around 17:14 service was restored.

== Lessons Learned ==

TODO

[[Category:Incident Reports]]

Incident Report: 20230109

2023-01-09T17:48:39Z

11090: Created page with "{{Incident |brief=ITS replaced some networking gear and broke some routes. Sad panda. |severity=High |impact=Medium (anything URY-related unavailable for around ~8 hours..."

{{Incident
|brief=ITS replaced some networking gear and broke some routes. Sad panda.
|severity=High
|impact=Medium (anything URY-related unavailable for around ~8 hours)
|start=2023-01-09 09:30
|end=2023-01-09 17:19
|leader=Joseph Sisson (JS)
|others=Michael Grace (MG), Marks Polakovs (MP)
}}

== Chronicle of Events ==

''(All times GMT)''

Early in the morning of the first day of the first week of term, IT Services (as we later found out) replaced some networking equipment in the Vanbrugh area, and may have incorrectly set some static routes. The first we found out about this is at 9:30, when all of our monitoring pinged that URY had dropped off the face of the internet.

Much scrambling and some reboots later, we narrowed down the state of the network to:
* Anything with a 144.32.64.160/27 IP (so all of URY) could send packets ''out'' of URY, but no packets would make it ''in''.
:* With the exception of uryfw0 which has a separate IP (144.32.109.64).
:* Traceroutes showed the packets getting into a loop somewhere in Berrick Saul.
* This meant that the website and online streams were down.
* We could carry on broadcasting on AM, but FM failed
:* MP later diagnosed the FM issue to be a dependency on audio.ury.org.uk for the backup feed, and restored FM at 14:39.

Cue an ITS ticket, and at around 17:14 service was restored.

== Lessons Learned ==

TODO

[[Category:Incident Reports]]

HowTo Do an OB From Your Laptop

2022-10-08T12:39:30Z

11090: VPN isn't needed anymore

Usually for an OB you'll be using the OB PC in The Rhino. Sometimes, however, The Rhino is totally overkill for your use case - sometimes a single laptop with a mini-mixer and one or two microphones is perfectly fine. This guide will tell you how to set up your laptop for it, and how to conduct the OB.

== Things You Will Need ==

* A laptop (duh)
''Note that this guide is written for Windows PCs - it can probably be adapted to work on macOS or Linux but you're on your own there.''
* An audio interface (unless you're using a mixer with a built-in one)
* A mixer (not always necessary)

== Setting Up The Laptop ==

This is a bit of a long section, but you only need to do it once.

To do an OB from your laptop, you'll need a piece of software, butt - it stands for "Broadcast Using This Tool" and its acronym makes it hilariously un-Google-able. Track it down and install it.

Once you've got it, crack it open (ha!) and set up the profile. Click the settings button, and under "Servers" click "New". Fill it in with the following details:

Name: ''whatever''
Type: IceCast
Address: <code>dolby.ury.york.ac.uk</code>
Port: 7070
Password: ''ask your friendly neighbourhood compuneer''
IceCast mountpoint: <code>OB-Line</code> '''(caps matter!)'''
IceCast user: <code>source</code>

Save it all. While you're at it, head over to the Audio tab and set streaming bitrate to at least 192K. Also, check it's using the right audio input - it should be your mixer or audio interface.

== Streaming ==

Now you're ready to start the stream, whether just to test it all works, or to actually go live! To fire it up, click the play icon in butt (not the record icon - common mistake). After a few seconds the "Stream Time" should start ticking up. To check that everything has gone to plan, go to [https://ury.org.uk/timelord] and check that the OB box at the bottom has lit up. If it has, you're good to go! When the time comes for your OB, just switch the studio (or, more likely, ask Computing to do it) and you're live!

Constitution

2022-09-18T21:18:31Z

11090: update it...

This is the '''constitution''' of the University Radio York society. Any errors in the transcription should be reported to the last editor.

The current (2022) constitution can be viewed [https://drive.google.com/file/d/1ELKnd1XT07CUriM9Gb2jPlCblW7LB0Ns/view here].

URY Memes

2021-08-14T17:09:21Z

11090: colin got a job

An in-definitive list of all URY Memes and in jokes.

{| class="wikitable"
|+[[URY Memes|Memes]]
|-
! Meme
! Explanation
|-
| Christmas on my Face (A terrible case of Xmas)
| A smash hit URY christmas single from 2008 written by Rob Watts and Steve Gardner [https://www.youtube.com/watch?v=OVICvXorh-s]
|-
| [[Christmas Endeavours]] in general
| They are so numerous there's a whole page about them. Basically we embarrass ourselves every year in the name of Xmas
|-
| 'There's no News'
| [quoting Anthony Williams] 'Came from a Roses where the news fader had been re-purposed for something. Helen M came in to do handover to the OB (this is when you had to read out the news intro text yourself), and it went something like this... "*this* is URY News.... there's no news!"
|-
| Wives
| The name given for our roll up banners. Originally known as 'Station Manager's Wife' as it is the only thing an SM can be trusted with at an OB
|-
| DO YOU LIKE VANBRUGH JAZZ?
| From a failed OB of Vanbrugh Jazz in 2014 where Alex Light accosted innocent people
|-
| 'Black Christmas'
| At the same Vanbrugh Jazz OB as 'DO YOU LIKE VANBRUGH JAZZ' the jazz band decided to do a rendition of 'White Christmas' but reworked as 'Black Christmas'. It was a bit racist. We had to fade down the feed.
|-
| 'News is Happening'
| How every News and Sport update must begin at Station Meetings, started by George Lane.
|-
| Superb Owl
| Live coverage of Super Bowls, by people who do not know anything about American Football. Usually involves way too much nudity that is generally acceptable for radio.
|-
| Alex Light
| The biggest meme of all
|-
| Talkback
| Someone will finish this eight year old engineering project so we can talk to the office and studio 2 from studio 1 soon, I promise. In the meantime, mad, occasionally violent gesturing through the window will have to suffice.
|-
| Anthony William's Flute
| From an infamous Alex Light house party where Anthony consumed way too much alcohol through a flute.
|-
| Ainsley Harriot
| A station wide obsession instigated by Qumarth Jash. Ainsley's face would frequently appear as the background to guest pc and an emoji was even made for him when we made a ury slack.
|-
| Biscuit News
| How did this win an award?
|-
| Unbelievable Scenes
| A phrase constantly said by Joshua Kerr to describe sport, antics and anything happening at all, ever
|-
| Other [insert branded item here] are available
| We take impartiality very seriously here at URY
|-
| EWA (Engineers Without Attitude)
| When a band bailed on URY Sessions, Jed Fulwell, Marco Bolt, Peter Rogers and Sam Merryweather stepped up to the plate and performed arguably the worst/best session in URY history. They also returned for a surprisingly excellent come-back at the Cover Your Ears event.
|-
| Michael Eats Kids
| We really don't know where this started. Someone just said it and it stuck.
|-
| Alex plugs stuff
| If he's on air, he's plugging his shows (he does so many), and if we're off air, plugging production meeting.
|-
| Kermit the Frog
| Station manager Ben Allen could do a really good Kermit impression, including singing live on air on multiple occasions.
|-
| In Other Gravy News
| On a Newshour episode, there was a story of a woman storing loads of money in gravy tins, which was found by the recycling people. Beth then went on to continue the show by saying "In Other Gravy News". Admittedly, the next clip was about chips cheese and gravy.
|-
| Hppenong
| An end of term special 12 hour show of just absolute chaos. Moving through the night there is often pizza, a need for air-fresheners and an hour of just playing songs called Go.
|-
| Rob 's House
| This is a joke that was filled in on a fill-in-the-blanks. It wasn't that funny, but we couldn't stop laughing for 15 minutes.
|-
| Let's Buy Chairs
| The chairs in the studio are '''awful'''. You sit on them, and they just sink and get lower. Despite discussing it for a year, Engineering team still haven't bought any.
|-
| Yeah No
| Station manager Ben Allen can never make up his mind, and always says Yeah-No. We made https://yeahno.xyz
|-
| broken - WAT!
| Don't say broken. People will be angry, and shout WAT!, because we're too lazy to add the h to "what".
|-
| Colin's Unemployed
| Literally everybody else got a job after graduating during the pandemic. The BBC still haven't replied about the One Show job. (Update: they got a job. Not at the One Show.)
|-
|}

Constitution

2021-03-15T19:56:24Z

11090:

This is the '''constitution''' of the University Radio York society. Any errors in the transcription should be reported to the last editor.

The current (2021) constitution can be viewed [https://drive.google.com/file/d/1fNkLEag6aKlcDjI2P6xfhI2q5lA-X0yi/view here].

Computing

2021-03-14T22:46:03Z

11090: /* Members (past and present) */

{{Team
|tstyle={{Teamstyle Computing}}
|name=Computing Team
|logo=[[File:Ctlogo.png]]
|brief=Maintains URY's computer systems, both hardware and software. Keeps the URY streams and website running.
|csec=[[Constitution#Computing_Team|Here]]
|roles=[[Head of Computing]]<br />[[Assistant Head of Computing]]<br />[[Webmaster]]<br />[[Computing Officer]] (multiple)
|teammail=computing@ury.org.uk
|freshermail=computing@ury.org.uk
|hotmail=head.of.computing@ury.org.uk
}}
'''Computing Team''' is the URY [[team]] responsible for maintaining URY's computer ordinance, both hardware and software.

== What do we do? ==

We like to think of ourselves as the ''everything'' team, because while we're limited to poking anything that involves computers, we actually do an incredible amount of stuff:

=== Website ===

We look after the URY website and make sure that other teams are able to keep it full of content.

The main public website is written in Go, and our website runs on the '''Nginx''' web server.

=== Servers ===

We run our own physical servers, which involves a lot of nipping into our server shed to turn things off and on, swap cables around and shout at power supplies. If you like pulling things out of racks, staring at them, sticking RAM in them and putting them back in racks, then we offer one of the finest physical server admin experiences available to York students.

Of course, it isn't all about the hardware. We also do a lot of system administration on the software side, making sure that all the processes that keep URY running stay up and don't tie themselves in knots. We run '''FreeBSD''' and '''Debian GNU/Linux''', with a '''Windows Server''' domain controller for the desktop systems.

=== Desktops ===

Each studio has a few computers, typically running '''Windows''', that are used by presenters for playing out sound, connecting to the Internet, and using our Studio Information Service. These have to be maintained, of course, and it's us that rise to the challenge.

=== Software ===

Compteam develop and maintain most of our software in-house, a fact that we are very proud of - know of any other society at the university that can say that? Know of any other student radio station that can say that? We don't. We've listed some of our things below, and linked to our ''Ceedox'' wiki which keeps all our technical documentation and secrets. You have to have a URY account to see those pages, I'm afraid, but York students can get one instantly by going to [https://ury.org.uk/getinvolved].

==== LoggerNG ====
[https://ury.org.uk/ceedox/computing:software:in-house:loggerng Ceedox Documentation]

LoggerNG is our output logging system. Our Ofcom licence means we have to have a log of 42 days of output at all times - if we aren't recording, we aren't broadcasting. The old logger system runned on some vintage desktop hardware from around 2001, so we needed something new.

LoggerNG includes two dedicated servers, a ''sox''-based recording program, 65 days of FLAC files and a HTML5 download interface on a third server. It's a big thing, and needs to work 100% of the time, all the time (well, term time).

==== Broadcasting and Presenting Suite (BAPS) ====
This is another one of our older systems. Written around 2003 in Managed C++, at the time it was seen as everything a presenter would need to do a show - on a computer. Of course, the original designers did not plan for a decade in the future, where social media, HTML5 and APIs are the way of the future, so it is now starting to seem somewhat dated.

The server side of the system manages the ability to play out different audio to different sound cards. It lacks lots of functionality, but is in fact very very good at what it does.

It is a computing team joke about people starting BAPS3. Various people have tried this, and the current try is a server called BAPSicle using the WebStudio interface. Let's see if it works.

==== If No Show, I Do an Instantly Organised, Unending Show - Totally Outrageous Non-stop Entertainment System (insidious Tones (iTones)) ====
[https://ury.org.uk/ceedox/computing:software:in-house:insidioustones Ceedox Documentation]

Publically known as URY's Campus Jukebox, this is the system that plays songs when there's not a presenter on air. It's another of our mission critical things as we can't broadcast silence, but it also has lots of neat tricks in the form of a web interface to define a range of pre-defined playlist schedules and some automated playlist generation. Its scheduler is part of the MyRadio framework and integrates with the telnet interface of a little-known thing called Liquidsoap (a Savonet project). Trust us when we say it is very powerful and a lot of fun to play with. There's also a lot of shouting and arguing with it too. Its a range of emotions.

==== MyRadio ====
This magical little thing is designed to be the glue for URY's services. Written in PHP, Twig and HTML5, this is essentially our intranet. Here's some of the things it pulls together:

* Presenter Training
* Show Scheduling
* URYPlayer Podcasts
* Show Resources (beds, jingles etc.)
* Show Planning
* In-Studio Information (live messages, news & stats)
* Chart & Playlists
* Central Music Library
* iTones
* Mailing Lists
* Webcams (and archives)
* Show Monitoring
* Statistics

All of this is also exposed using an API [https://ury.org.uk/api/] which provides us with easy control and remote access to all of the above as well as Users, Committees, Images, Tracklists and our Studio Selector.

This API is then in turn used by a range of our resources, including our RadioPlayer page, E-mail service, MixCloud uploader, Presenter website pages, IRC bot and more. Put simply, this bundle of PHP holds our station together.

Oh, did I mention we're trying to generalise it so other stations can learn what we do under the hood? It's open sourced at [https://github.com/UniversityRadioYork/MyRadio]!

==== WebStudio ====

2020 happened. Pandemic happened. WebStudio got made, to allow people to present from home. Written in TypeScript, React and Redux, with the server side in Python.

==== Show Planner (this is pretty much dead now, this is here for the history) ====
[https://ury.org.uk/ceedox/computing:software:in-house:myury:nipsweb Ceedox Documentation]

Built upon the MyRadio framework, Show Planner is a HTML5 version of the in-studio BAPS client, but in a web browser. It allows anyone to plan shows, upload files and do lots of other neat stuff. If you like lots of pretty client side stuff, with a multi-user editable backend, then you'll love this.

During initial development, it went through several names - BAPSWeb 2, BAPS Planner and NIPSWeb, before eventually being named the more simple Show Planner. It replaced BAPSWeb, a single several-thousand line PHP file and a Comic-Sans interface which were developed around the same time as BAPS itself.

Version 1 was featured as part of our Less Black and More Graphics entry in the Student Radio Awards 2012, but was replaced by the MyRadio integrated version over the next year.

Version 2 of this little gizmo won us a Silver Best Technical Achievement at the Student Radio Awards 2013.

Version 3 is current near-completion, the client-side complete rewritten as part of MyRadio's move to Bootstrap.

=== Fun ===

Though Compteam have the burden of a lot of responsibility for critical systems most of the time, really most of us are here to '''have fun'''.

Being in and around a student radio station gives people who want to play around with new ideas in an existing context a real jumpstart, and as a consequence whenever we're not fixing stuff we're often in URY working on making new things. Here are a few examples:

* BAPS, URY's very own custom playout system (Matt Fortune, 20??/??)
* The studio clock system (Lloyd Wallis, 2011/12)

We also spend a lot of time in the studios just tinkering around, and helping engineering team with Outside Broadcasts.

== Prospective members ==

Computing Team is always looking for new members, so if you're interested by what we do, send us an email (see the infobox on the right hand side)!

URY membership is £7 if you make a regular habit of poking our systems, but anyone is free to come and have a go. The team often has meetings at on Wednesdays in VBar around 7pm.

=== What we use ===

As Computing Team's goals involve education and development just as much as professionalism and dependability, there is no requirement for prior knowledge. We use all of these things, and you'll learn so much more too!

* Administration of Unix-style systems, especially Debian GNU/Linux and FreeBSD
* Administration of Windows client systems, Active Directory and Windows Server
* Python
* PHP
* Go
* SQL, especially PostgreSQL
* Network administration (hardware and software)
* Continuous integration - Jenkins/Hudson, Travis
* Shell scripting
* Systems programming - C, Go, etc.

== History ==

* Computing Team was formed by separation from the [[Technical]] Team as URY's dependency on computer systems increased during the late 90s and early 2000s.
* URY's longest ever serving servers (heh) were the [[First Generation Computing Loggers]], in production for 14 years and with 10 years of HDD runtime hours each.

== Members (past and present) ==

=== Heads of Teams ===
* ''2021-Present'': [[Isaac Lowe]]
* ''2020-2021'': [[Marks Polakovs]]
* ''2019-2020'': [[Laura Silaja]]
* ''2018-2019'': [[Jordan Cameron]]
* ''2017-2018'': [[Matthew Stratford]]
* ''2017-2017'': [[Charles Pigott]]
* ''2016-2017'': [[Chris Taylor]]
* ''2014-2016'': [[Anthony Williams]]
* ''2011-2014'': [[Matt Windsor]]
* ''2010-2011'': [[Gareth Andrew Lloyd]]
* ''2009-2010'': [[Alex Williams]]
* ''2008-2009'': [[Gareth Andrew Lloyd]]
* (More to be inserted here)

=== Other Members ===

In a rough reverse chronological order.
* [[Joseph Sisson]]
* [[Connor Sanders]]
* [[Ben Allen]]
* [[Michael Grace]]
* [[Brooke Hatton]]
* [[Sophie Kinley]]
* [[Qumarth Jash]]
* [[Charles Pigott]]
* [[Sam Willcocks]]
* [[Adam Taylor]]
* [[Andrei-Costin Zisu]]
* [[Vivan Jayant]] (Webmaster, 2012)
* [[Sam Gamble]] (2011-12)
* [[Anthony Williams]]
* [[Danny Bell]]
* [[Donal Cahill]]
* [[Lloyd Wallis]] (2011-2014, still an active alumnus)
* [[Andy Durant]] (as a "computerneer")
* (Expand this list!)

== Big Updates ==
During breaks between terms, CompTeam will often update or upgrade a large number of services. We like to post a list of changes toward the end of the break.

* [[Computing Updates: Christmas 2013]]
* [[Computing Updates: Summer 2013]]
* [[Computing Updates: Easter 2013]]
* Spring 2021: We're still here, and realising the wiki is very out of date.

Working From Home Resources/Advanced

2021-01-05T21:31:07Z

11090: /* Have Someone Else Mix It */

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company on your show, someone to share the airwaves with.

Sadly, at the time of writing there's no great solution for this. This page will attempt to summarise the current best practice for getting other people on your show.

== Pre-Record Links ==

If you can't get your co-hosts' voices into WebStudio live, a good option is to pre-record your links. This involves you recording your chatting in advance, then uploading it into Show Planner, and then playing it out live in between songs in WebStudio.

The advantage of this is that it requires no special fiddling on the day of the show. It's just like any other WebStudio show, except that you play your link recordings instead of doing them live. This is certainly the lowest-tech approach.

A related advantage is that you can try your links over and over again until they sound good, which may make your show sound slicker. (Though it must be noted that the perfect is the enemy of the good, and to not stress about it too much.)

The obvious problem with this approach is that you lose the immediacy of live radio, which is certainly undesirable. Also, sitting there pressing the "play" button over and over again can get a little boring.

To use this approach, [https://docs.google.com/document/d/1PwHvL9HU8eY5GqAvQgJGOEyZnmdGoc18CzFvP3alcWo/edit follow this guide]. (If you can't access the document, contact someone on the [https://ury.org.uk/teams/management/ Management Team] on Slack.)

== Pre-Record Entire Show ==

You may be thinking, "if I'm pre-recording bits of my show, why not edit it all together in one go?" And indeed, this is possible. There are quite a few caveats though:

* This is very time-consuming. You will need to record all the links, and then edit them together with the music, in advance.
* You will need legal copies of all the music you want to play - you '''cannot''' download songs from Show Planner.
* You will need to tracklist each song as it is played (otherwise you are in breach of the [[Presenters' Contract]]).
* Currently there is no way to play it automatically, so you will need to play the show out via WebStudio at the scheduled time. (The Computing Team are working on this though.)

Given the above, if you wish to use this approach, please speak to the Programme Controller ([mailto:pc@ury.org.uk pc@ury.org.uk] or ''@Michael'' on Slack) and he will point you in the right direction.

== Have Someone Else Mix It ==

If you don't have the technical skills to mix a multi-person show yourself, you could ask someone else to do it. A number of our presenters and technicians have the skills and equipment to do it - so for you it'd be as simple as joining a Zoom call.

One massive caveat though: many (if not all) of those people are '''extremely busy''' at the present time, with uni work, URY admin, and personal commitments. Don't count on someone being available at the time you need.

If you want to do this, ask around in #remote-broadcasting in Slack. '''Make sure you have this sorted at least a week before your show.''' Remember that ultimately your show is your responsibility, and we will not be held responsible if you can't find someone to mix it for you. For this reason, you should always have a back-up plan.

== Mix It Yourself ==

If you're adept with audio routing (either physical or virtual), there's no reason why you couldn't mix in your guests yourself - essentially, mix them on top of your microphone feed into WebStudio.

There are many different ways of doing this. We have [https://ury.org.uk/ceedox/engineering:documentation:voicemeeter_guide a guide] to one way, using Voicemeeter on Windows. If you're using macOS or Linux, there are certainly tools for that. If you prefer to do it in hardware, there are ways to do that too.

Remember, however, '''you do this at your own risk'''. While members of the Engineering and Computing teams may make an effort to support you, there are no guarantees, and responsibility remains with you if your show goes wrong. For this reason, this should only be attempted if you know what you're doing and how to fix it without anyone from URY helping you.

== Bribe The Computing Team To Implement Native Multi-Person Shows In WebStudio ==

I'm told they accept payment in alcoholic and/or caffeinated beverages.

Working From Home Resources/Requirements

2021-01-05T19:42:03Z

11090: /* Microphone */

<small>[[Working From Home Resources|back to hub]]</small>

On this page, we'll summarise everything you need to start making radio from home.

== Computer ==

You'll want a fairly fast one, just to make sure there are no issues, but anything bought in the last 5 years (and even a lot of older ones) will do just fine. Any MacBook that still works will probably do, as should most Windows laptops made after 2013. Chromebooks may work, but you might start having issues with external microphones and such, so we wouldn't recommend them unless you have no other option.

You'll need [https://www.google.com/chrome/ Google Chrome] installed. WebStudio MAY work in other browsers, but Computing won't support it - if you ask us for help using anything except Chrome our response might just be "try again in Chrome". (We're using a lot of bleeding-edge technology, and don't always have the time to test it in all browsers. Support for other browsers is planned, but for now, Chrome is the only one we will support.) While you're at it, make sure it's got the latest updates installed (usually it'll do this automatically).

Try to avoid any unnecessary programs running in the background, even programs like Spotify and Microsoft Office can negatively impact the performance of the computer, and interfere with the stability of your connection to URY's servers.
If possible you should also disable your VPN while connecting to webstudio in order to improve connection latency and stability. You do '''not''' need the university VPN running in order to access webstudio.

Try to have all your equipment set up and tested before you do your show, and not disturbed from a working configuration until needed. Even doing something as innocent as plugging a new set of headphones in can break everything (speaking from experience here...), which you may not have time to fix before you need to begin.

=== Using a phone ===

If you are not the presenter on a show and do not need access to webstudio and other virtual studio features, consider using your phone with a set of headphones, most modern phones have respectable microphones built in, and are easily capable of accessing URY's recommended remote high quality audio line for studio guests [https://cleanfeed.net/ Cleanfeed.net], be sure to follow best practices on microphone usage and keep your battery well charged when doing this though!

== Internet connection ==

You'll want a fairly fast connection. If you're on campus, the network is more than sufficient (although we still recommend connecting to Ethernet if possible instead of using eduroam). If you're at home, most home broadband should do, but go to [https://speedtest.net Speedtest.net] to check your speed - you'll want at least 10mbps down and 3mbps up (slower download will slow downloading of songs but still be fine, slower upload may cause connection issues). If you're having issues, 4G may work better than home broadband, but that causes reliability issues, so broadband is preferable unless yours is hopelessly slow.

Hard-wire Ethernet is always preferable over WiFi, not for speed but for stability. The line is only as good as its stability - WiFi may be fine when you first test it, but can you guarantee that will be the case when you are doing your show? Sharing a WiFi connection between multiple people will perform much worse than you might expect, so if possible get a wired connection. If that's not an option, consider timing your show when as few people as possible will be using WiFi, or ask the people you share the internet with if they could curtail their usage for the period of your show.

== Headphones ==

Please, please, PLEASE do not try to do a radio show using laptop speakers. It will sound God-awful whenever you turn on your mic. You don't need high quality studio headphones like we have at York, even a pair of EarPods will do you just fine, but make sure you have some. Be aware that if you are using an external USB microphone, the direct monitoring port on the microphone may not also pass you audio from webstudio.

Also, do not use Bluetooth headphones, unless you have no other option. Not only does Bluetooth introduce a delay which can throw all your timings off (fun fact: it takes longer for sound to go from your laptop to your AirPods than for data to go from London to York - no, really!), the quality of Bluetooth microphones on computers is, for lack of a better word, total crap. A pair of Bluetooths is better than nothing at all, but anything hard-wired will almost always be better.

== Microphone ==

The tricky one. Take a look at our [[Working From Home Resources/Microphone Recommendations|microphone recommendations]] page and choose one that fits your budget. You don't need to splash out on a mic if you're only doing one show a week, as even an EarPod mic will sound ''okay'', but do think about it if you want to get more serious about making radio from home.

Working From Home Resources/Requirements

2021-01-05T19:41:03Z

11090: /* Internet connection */

<small>[[Working From Home Resources|back to hub]]</small>

On this page, we'll summarise everything you need to start making radio from home.

== Computer ==

You'll want a fairly fast one, just to make sure there are no issues, but anything bought in the last 5 years (and even a lot of older ones) will do just fine. Any MacBook that still works will probably do, as should most Windows laptops made after 2013. Chromebooks may work, but you might start having issues with external microphones and such, so we wouldn't recommend them unless you have no other option.

You'll need [https://www.google.com/chrome/ Google Chrome] installed. WebStudio MAY work in other browsers, but Computing won't support it - if you ask us for help using anything except Chrome our response might just be "try again in Chrome". (We're using a lot of bleeding-edge technology, and don't always have the time to test it in all browsers. Support for other browsers is planned, but for now, Chrome is the only one we will support.) While you're at it, make sure it's got the latest updates installed (usually it'll do this automatically).

Try to avoid any unnecessary programs running in the background, even programs like Spotify and Microsoft Office can negatively impact the performance of the computer, and interfere with the stability of your connection to URY's servers.
If possible you should also disable your VPN while connecting to webstudio in order to improve connection latency and stability. You do '''not''' need the university VPN running in order to access webstudio.

Try to have all your equipment set up and tested before you do your show, and not disturbed from a working configuration until needed. Even doing something as innocent as plugging a new set of headphones in can break everything (speaking from experience here...), which you may not have time to fix before you need to begin.

=== Using a phone ===

If you are not the presenter on a show and do not need access to webstudio and other virtual studio features, consider using your phone with a set of headphones, most modern phones have respectable microphones built in, and are easily capable of accessing URY's recommended remote high quality audio line for studio guests [https://cleanfeed.net/ Cleanfeed.net], be sure to follow best practices on microphone usage and keep your battery well charged when doing this though!

== Internet connection ==

You'll want a fairly fast connection. If you're on campus, the network is more than sufficient (although we still recommend connecting to Ethernet if possible instead of using eduroam). If you're at home, most home broadband should do, but go to [https://speedtest.net Speedtest.net] to check your speed - you'll want at least 10mbps down and 3mbps up (slower download will slow downloading of songs but still be fine, slower upload may cause connection issues). If you're having issues, 4G may work better than home broadband, but that causes reliability issues, so broadband is preferable unless yours is hopelessly slow.

Hard-wire Ethernet is always preferable over WiFi, not for speed but for stability. The line is only as good as its stability - WiFi may be fine when you first test it, but can you guarantee that will be the case when you are doing your show? Sharing a WiFi connection between multiple people will perform much worse than you might expect, so if possible get a wired connection. If that's not an option, consider timing your show when as few people as possible will be using WiFi, or ask the people you share the internet with if they could curtail their usage for the period of your show.

== Headphones ==

Please, please, PLEASE do not try to do a radio show using laptop speakers. It will sound God-awful whenever you turn on your mic. You don't need high quality studio headphones like we have at York, even a pair of EarPods will do you just fine, but make sure you have some. Be aware that if you are using an external USB microphone, the direct monitoring port on the microphone may not also pass you audio from webstudio.

Also, do not use Bluetooth headphones, unless you have no other option. Not only does Bluetooth introduce a delay which can throw all your timings off (fun fact: it takes longer for sound to go from your laptop to your AirPods than for data to go from London to York - no, really!), the quality of Bluetooth microphones on computers is, for lack of a better word, total crap. A pair of Bluetooths is better than nothing at all, but anything hard-wired will almost always be better.

== Microphone ==

The tricky one. Take a look at our [[Working From Home Resources/Microphone Recommendations|microphone recommendations]] page and choose one that fits your budget. You don't need to splash out on a mic if you're only doing one show a week, as even an EarPod mic will sound ''okay'', but do think about it if you want to get more serious about making radio from home. There are best practices about how to setup your microphone and get the most out of equipment available to you on our [[Working From Home Resources/Microphone Technique|Microphone Technique]] page, this may also help you decide on what type of microphone may be best for you should you wish to purchase one.

Working From Home Resources

2021-01-05T19:40:19Z

11090:

URY is in a strange place. With the country on lockdown and the (almost) closure of campus, our normal method of making radio (going into the studio and talking into a microphone) simply won't do. We're students, though, and if there's one thing we are it's resourceful!

On these pages you'll find some guidance on how to continue making radio from the comfort and safety of your self-isolation bedroom.

* [[Working From Home Resources/Requirements|Requirements for Working from Home]]
* [[Working From Home Resources/Microphone Recommendations|Microphone Recommendations]]

* [[Working From Home Resources/WebStudio|Simple shows: How To Use WebStudio]]
* [[Working From Home Resources/Advanced|Advanced: Shows With Guests]]

Working From Home Resources/Advanced

2021-01-05T19:33:56Z

11090: /* Pre-Record Entire Show */

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company on your show, someone to share the airwaves with.

Sadly, at the time of writing there's no great solution for this. This page will attempt to summarise the current best practice for getting other people on your show.

== Pre-Record Links ==

If you can't get your co-hosts' voices into WebStudio live, a good option is to pre-record your links. This involves you recording your chatting in advance, then uploading it into Show Planner, and then playing it out live in between songs in WebStudio.

The advantage of this is that it requires no special fiddling on the day of the show. It's just like any other WebStudio show, except that you play your link recordings instead of doing them live. This is certainly the lowest-tech approach.

A related advantage is that you can try your links over and over again until they sound good, which may make your show sound slicker. (Though it must be noted that the perfect is the enemy of the good, and to not stress about it too much.)

The obvious problem with this approach is that you lose the immediacy of live radio, which is certainly undesirable. Also, sitting there pressing the "play" button over and over again can get a little boring.

To use this approach, [https://docs.google.com/document/d/1PwHvL9HU8eY5GqAvQgJGOEyZnmdGoc18CzFvP3alcWo/edit follow this guide]. (If you can't access the document, contact someone on the [https://ury.org.uk/teams/management/ Management Team] on Slack.)

== Pre-Record Entire Show ==

You may be thinking, "if I'm pre-recording bits of my show, why not edit it all together in one go?" And indeed, this is possible. There are quite a few caveats though:

* This is very time-consuming. You will need to record all the links, and then edit them together with the music, in advance.
* You will need legal copies of all the music you want to play - you '''cannot''' download songs from Show Planner.
* You will need to tracklist each song as it is played (otherwise you are in breach of the [[Presenters' Contract]]).
* Currently there is no way to play it automatically, so you will need to play the show out via WebStudio at the scheduled time. (The Computing Team are working on this though.)

Given the above, if you wish to use this approach, please speak to the Programme Controller ([mailto:pc@ury.org.uk pc@ury.org.uk] or ''@Michael'' on Slack) and he will point you in the right direction.

== Have Someone Else Mix It ==

If you don't have the technical skills to mix a multi-person show yourself, you could ask someone else to do it. A number of our presenters and technicians have the skills and equipment to do it - so for you it'd be as simple as joining a Zoom call.

One massive caveat though: many (if not all) of those people are '''extremely busy''' at the present time, with uni work, URY admin, and personal commitments. Don't count on this.

If you want to do this, ask around in #remote-broadcasting in Slack. '''Make sure you have this sorted at least a week before your show.''' Remember that ultimately your show is your responsibility, and we will not be held responsible if you can't find someone to mix it for you. For this reason, you should always have a back-up plan.

== Mix It Yourself ==

If you're adept with audio routing (either physical or virtual), there's no reason why you couldn't mix in your guests yourself - essentially, mix them on top of your microphone feed into WebStudio.

There are many different ways of doing this. We have [https://ury.org.uk/ceedox/engineering:documentation:voicemeeter_guide a guide] to one way, using Voicemeeter on Windows. If you're using macOS or Linux, there are certainly tools for that. If you prefer to do it in hardware, there are ways to do that too.

Remember, however, '''you do this at your own risk'''. While members of the Engineering and Computing teams may make an effort to support you, there are no guarantees, and responsibility remains with you if your show goes wrong. For this reason, this should only be attempted if you know what you're doing and how to fix it without anyone from URY helping you.

== Bribe The Computing Team To Implement Native Multi-Person Shows In WebStudio ==

I'm told they accept payment in alcoholic and/or caffeinated beverages.

Working From Home Resources/Advanced

2021-01-05T19:27:59Z

11090: /* Mix It Yourself */

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company on your show, someone to share the airwaves with.

Sadly, at the time of writing there's no great solution for this. This page will attempt to summarise the current best practice for getting other people on your show.

== Pre-Record Links ==

If you can't get your co-hosts' voices into WebStudio live, a good option is to pre-record your links. This involves you recording your chatting in advance, then uploading it into Show Planner, and then playing it out live in between songs in WebStudio.

The advantage of this is that it requires no special fiddling on the day of the show. It's just like any other WebStudio show, except that you play your link recordings instead of doing them live. This is certainly the lowest-tech approach.

A related advantage is that you can try your links over and over again until they sound good, which may make your show sound slicker. (Though it must be noted that the perfect is the enemy of the good, and to not stress about it too much.)

The obvious problem with this approach is that you lose the immediacy of live radio, which is certainly undesirable. Also, sitting there pressing the "play" button over and over again can get a little boring.

To use this approach, [https://docs.google.com/document/d/1PwHvL9HU8eY5GqAvQgJGOEyZnmdGoc18CzFvP3alcWo/edit follow this guide]. (If you can't access the document, contact someone on the [https://ury.org.uk/teams/management/ Management Team] on Slack.)

== Pre-Record Entire Show ==

You may be thinking, "if I'm pre-recording bits of my show, why not edit it all together in one go?" And indeed, this is possible. There are quite a few caveats though:

* This is very time-consuming.
* You will need legal copies of all the music you want to play - you '''cannot''' download songs from Show Planner.
* You will need to tracklist each song as it is played (otherwise you are in breach of the [[Presenters' Contract]]).
* Currently there is no way to play it automatically, so you will need to play the show out via WebStudio at the scheduled time. (The Computing Team are working on this though.)

Given the above, if you wish to use this approach, please speak to the Programme Controller ([mailto:pc@ury.org.uk pc@ury.org.uk] or ''@Michael'' on Slack) and he will point you in the right direction.

== Have Someone Else Mix It ==

If you don't have the technical skills to mix a multi-person show yourself, you could ask someone else to do it. A number of our presenters and technicians have the skills and equipment to do it - so for you it'd be as simple as joining a Zoom call.

One massive caveat though: many (if not all) of those people are '''extremely busy''' at the present time, with uni work, URY admin, and personal commitments. Don't count on this.

If you want to do this, ask around in #remote-broadcasting in Slack. '''Make sure you have this sorted at least a week before your show.''' Remember that ultimately your show is your responsibility, and we will not be held responsible if you can't find someone to mix it for you. For this reason, you should always have a back-up plan.

== Mix It Yourself ==

If you're adept with audio routing (either physical or virtual), there's no reason why you couldn't mix in your guests yourself - essentially, mix them on top of your microphone feed into WebStudio.

There are many different ways of doing this. We have [https://ury.org.uk/ceedox/engineering:documentation:voicemeeter_guide a guide] to one way, using Voicemeeter on Windows. If you're using macOS or Linux, there are certainly tools for that. If you prefer to do it in hardware, there are ways to do that too.

Remember, however, '''you do this at your own risk'''. While members of the Engineering and Computing teams may make an effort to support you, there are no guarantees, and responsibility remains with you if your show goes wrong. For this reason, this should only be attempted if you know what you're doing and how to fix it without anyone from URY helping you.

== Bribe The Computing Team To Implement Native Multi-Person Shows In WebStudio ==

I'm told they accept payment in alcoholic and/or caffeinated beverages.

Working From Home Resources/Advanced

2021-01-05T19:26:13Z

11090: /* Pre-Record Links */

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company on your show, someone to share the airwaves with.

Sadly, at the time of writing there's no great solution for this. This page will attempt to summarise the current best practice for getting other people on your show.

== Pre-Record Links ==

If you can't get your co-hosts' voices into WebStudio live, a good option is to pre-record your links. This involves you recording your chatting in advance, then uploading it into Show Planner, and then playing it out live in between songs in WebStudio.

The advantage of this is that it requires no special fiddling on the day of the show. It's just like any other WebStudio show, except that you play your link recordings instead of doing them live. This is certainly the lowest-tech approach.

A related advantage is that you can try your links over and over again until they sound good, which may make your show sound slicker. (Though it must be noted that the perfect is the enemy of the good, and to not stress about it too much.)

The obvious problem with this approach is that you lose the immediacy of live radio, which is certainly undesirable. Also, sitting there pressing the "play" button over and over again can get a little boring.

To use this approach, [https://docs.google.com/document/d/1PwHvL9HU8eY5GqAvQgJGOEyZnmdGoc18CzFvP3alcWo/edit follow this guide]. (If you can't access the document, contact someone on the [https://ury.org.uk/teams/management/ Management Team] on Slack.)

== Pre-Record Entire Show ==

You may be thinking, "if I'm pre-recording bits of my show, why not edit it all together in one go?" And indeed, this is possible. There are quite a few caveats though:

* This is very time-consuming.
* You will need legal copies of all the music you want to play - you '''cannot''' download songs from Show Planner.
* You will need to tracklist each song as it is played (otherwise you are in breach of the [[Presenters' Contract]]).
* Currently there is no way to play it automatically, so you will need to play the show out via WebStudio at the scheduled time. (The Computing Team are working on this though.)

Given the above, if you wish to use this approach, please speak to the Programme Controller ([mailto:pc@ury.org.uk pc@ury.org.uk] or ''@Michael'' on Slack) and he will point you in the right direction.

== Have Someone Else Mix It ==

If you don't have the technical skills to mix a multi-person show yourself, you could ask someone else to do it. A number of our presenters and technicians have the skills and equipment to do it - so for you it'd be as simple as joining a Zoom call.

One massive caveat though: many (if not all) of those people are '''extremely busy''' at the present time, with uni work, URY admin, and personal commitments. Don't count on this.

If you want to do this, ask around in #remote-broadcasting in Slack. '''Make sure you have this sorted at least a week before your show.''' Remember that ultimately your show is your responsibility, and we will not be held responsible if you can't find someone to mix it for you. For this reason, you should always have a back-up plan.

== Mix It Yourself ==

If you're adept with audio routing (either physical or virtual), there's no reason why you couldn't mix in your guests yourself - essentially, mix them on top of your microphone feed into WebStudio.

There are many different ways of doing this. We have [https://ury.org.uk/ceedox/engineering:documentation:voicemeeter_guide a guide] to one way, using Voicemeeter on Windows. If you're using macOS or Linux, there are certainly tools for that. If you prefer to do it in hardware, there are ways to do that too.

Remember, however, '''you do this at your own risk'''. While the Engineering and Computing teams will make an effort to support you, there are no guarantees and responsibility remains with you if your show goes wrong. For this reason, this should only be attempted if you know what you're doing and how to fix it without anyone from URY helping you.

== Bribe The Computing Team To Implement Native Multi-Person Shows In WebStudio ==

I'm told they accept payment in alcoholic and/or caffeinated beverages.

Working From Home Resources/Advanced

2021-01-05T19:25:22Z

11090: Created page with "<small>back to hub</small> WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company o..."

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is great and all, but doing a show all by your lonesome gets a bit samey. Perhaps you want some company on your show, someone to share the airwaves with.

Sadly, at the time of writing there's no great solution for this. This page will attempt to summarise the current best practice for getting other people on your show.

== Pre-Record Links ==

If you can't get your co-hosts' voices into WebStudio live, a good option is to pre-record your links. This involves you recording your chatting in advance, then uploading it into Show Planner, and then playing it out live in between songs in WebStudio.

The advantage of this is that it requires no special fiddling on the day of the show. It's just like any other WebStudio show, except that you play your link recordings instead of doing them live. This is certainly the lowest-tech approach.

A related advantage is that you can try your links over and over again until they sound good, which may make your show sound slicker. (Though it must be noted that the perfect is the enemy of the good, and to not stress about it too much.)

The obvious problem with this approach is that you lose the immediacy of live radio, which is certainly undesirable. Also, sitting there pressing the "play" button over and over again can get a little boring.

To use this approach, [https://docs.google.com/document/d/1PwHvL9HU8eY5GqAvQgJGOEyZnmdGoc18CzFvP3alcWo/edit follow this guide]. (If you can't access the document, contact someone on the [https://ury.org.uk/teams/management/ Management Team] on Slack.

== Pre-Record Entire Show ==

You may be thinking, "if I'm pre-recording bits of my show, why not edit it all together in one go?" And indeed, this is possible. There are quite a few caveats though:

* This is very time-consuming.
* You will need legal copies of all the music you want to play - you '''cannot''' download songs from Show Planner.
* You will need to tracklist each song as it is played (otherwise you are in breach of the [[Presenters' Contract]]).
* Currently there is no way to play it automatically, so you will need to play the show out via WebStudio at the scheduled time. (The Computing Team are working on this though.)

Given the above, if you wish to use this approach, please speak to the Programme Controller ([mailto:pc@ury.org.uk pc@ury.org.uk] or ''@Michael'' on Slack) and he will point you in the right direction.

== Have Someone Else Mix It ==

If you don't have the technical skills to mix a multi-person show yourself, you could ask someone else to do it. A number of our presenters and technicians have the skills and equipment to do it - so for you it'd be as simple as joining a Zoom call.

One massive caveat though: many (if not all) of those people are '''extremely busy''' at the present time, with uni work, URY admin, and personal commitments. Don't count on this.

If you want to do this, ask around in #remote-broadcasting in Slack. '''Make sure you have this sorted at least a week before your show.''' Remember that ultimately your show is your responsibility, and we will not be held responsible if you can't find someone to mix it for you. For this reason, you should always have a back-up plan.

== Mix It Yourself ==

If you're adept with audio routing (either physical or virtual), there's no reason why you couldn't mix in your guests yourself - essentially, mix them on top of your microphone feed into WebStudio.

There are many different ways of doing this. We have [https://ury.org.uk/ceedox/engineering:documentation:voicemeeter_guide a guide] to one way, using Voicemeeter on Windows. If you're using macOS or Linux, there are certainly tools for that. If you prefer to do it in hardware, there are ways to do that too.

Remember, however, '''you do this at your own risk'''. While the Engineering and Computing teams will make an effort to support you, there are no guarantees and responsibility remains with you if your show goes wrong. For this reason, this should only be attempted if you know what you're doing and how to fix it without anyone from URY helping you.

== Bribe The Computing Team To Implement Native Multi-Person Shows In WebStudio ==

I'm told they accept payment in alcoholic and/or caffeinated beverages.

Working From Home Resources/WebStudio

2020-10-19T18:43:00Z

11090:

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is URY's flagship Work From Home package. It's everything you ever loved about BAPS, and more, entirely online. For single-person music shows it will be all you need.

== Training Video ==

<html>
<iframe width="560" height="315" src="https://www.youtube.com/embed/Oqmq4GSE8Zo" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</html>

[[Working From Home Resources/WebStudio/Training|Transcript]]

== Getting trained ==

Once you've watched the videos, please fill out [https://docs.google.com/forms/d/e/1FAIpQLSfWuE-BNA6k-TfeGgpS6lAy7UnrpcSgcK4QleHPmwK86CyaSQ/viewform?usp=sf_link this form] and we'll get you marked as trained!

Working From Home Resources/WebStudio/Training

2020-10-19T18:42:45Z

11090:

1.
Hi! I’m Alex Towells, University Radio York’s Production Manager. If you’re here, that means you want to know how to use our remote broadcasting tool, Webstudio! I’m here to take you through preparing and presenting a show using Webstudio, as well as showing you all the little features our computing team has added to make your life easier.

2.
First things first, there’s a specific web browser we need you to use when you use Webstudio, and that browser is Google Chrome. The reason being it had all the right bells and whistles to make our Computing Team’s lives easier when they were setting it up.

3.
After you’ve got that, you can find Webstudio on our existing backpages, MyRadio. If you’ve forgotten where that is, you can find it on our website here. Once you’ve logged in, Webstudio can be found under My Services, at the bottom of the list of Show Tools. Pick the show you want to work with, and you’re in!

4.
If you aren’t already WebStudio trained, you’ll be able to access all WebStudio features, but you won’t be able to put yourself on air, so feel free to play around as much as you like.

5.
If you’re familiar with BAPS, our Broadcast Audio Playout System, WebStudio is very similar - you have three columns, representing three players, which can all play any music, jingles, beds and so on. If you’ve already prepared your show in Show Planner, the plan you’ve made will open up when you open that show in Webstudio. You can move things around within a column, and between columns, and you can use the sidebar to search up any songs, jingles, or beds you want to add to your show on the fly. Keep in mind, though, that changes you make in WebStudio won’t be saved - if you reload the tab for any reason, they’ll disappear.

6.
If you make changes in Show Planner while Webstudio is open, and want them to move over to Webstudio, you can find a “Reload Show Plan” button by clicking on the drop-down up here on the show’s time, though that will erase any changes you made in Webstudio. You can also change which show you’re working with by clicking the “switch timeslot” button from the same drop-down, though be aware this will completely reload webstudio. On smaller screens, this top bar will be hidden to save space - to access it, hold your mouse over the bar labelled “hover for MyRadio Menu”.

7.
If you want to use music, beds, jingles or entire plans from other show plans, you can do so using the import function. Just select “import”, choose the show, season and episode you want to import from, then you can choose which channel on the original show plan you want to import from. You can select specific items you want to move over, or click “select all” up here. If you want to clear your selections while staying on the import screen, click “select none”. Once you’ve chosen what you want to import, select which channel on your show plan you want to import to. The final step is to reload your show plan to bring up your imports, then you’re done! However, reloading your show plan will discard any changes made, so make sure importing is the first thing you do if you plan on making lots of changes in Webstudio in a session.

8.
To cue something up for playback, just click on it. The grey bar at the bottom will start to fill up, representing loading progress. Depending on the speed of your internet connection it may take a couple of seconds for a song to load, so make sure you’ve got it loaded up before you need it.

9.
To play an item, press the play button, to pause or unpause it click pause, and to stop it completely press the stop button. We also have some keyboard shortcuts set up for you - Q, W, and E to play, pause, and stop the left channel, R, T, and Y for the middle channel, and U, I, and O for the right channel.

10.
Below the playback controls and the waveform you’ll find the fader. This has three levels - fully off, bed level, which is a suitable level for talking over, and fully on. To fade things in and out, click the relevant buttons, or use the keyboard shortcuts - A, S, and D for off, bed level, and fully on for the left channel, F, G, and H for the middle channel, and J, K, and L for the right.

11.
There are a few buttons above the item name on each channel. If the Auto Advance button is on, after an item finishes the next thing in its channel will be loaded in automatically. If Play on Load is on, an item will start to play immediately after being loaded in, instead of you having to click play. Using the repeat button you can set either one item to repeat over and over again, or the whole channel to repeat, running on top to bottom forever like a little music-y dog chasing its own tail. On smaller screens, these may be hidden to save space. To see them, hover over the bar labelled “channel controls” and they’ll appear.

12.
You can mark intro, cue and outro points on songs by using the buttons between the waveform and the play/pause buttons on each channel. To set an intro, play the song until the end of the intro, then hit pause and hit the intro button. This will shade the section of the song up to your cursor light blue. Setting cue and outro points works the same way. A Cue point will add a green marker at the new start point, and an outro point will shade the section of the song from the marked point to the end red. Cue points allow you to start the song partway through; to toggle between the cue point and the actual start of the song, press “stop” while the song is loaded, but not playing. These markers can also be deleted - click the delete button to the right of the marker buttons, then click the button labelled for whichever marker you want to delete - for example, to delete an intro, click the delete button then click the intro button again. At the moment, cues work for every item you can load in Webstudio, but intro and outro markers only work for songs, not jingles or beds - keep an eye out though, our computing team is working on getting them to work with everything, so that’ll be coming soon.

13.
To enable your microphone, click “Options” in the sidebar, and go to the Microphone tab. Click “Find Microphones”, grant permission if Chrome asks for it, and then choose a microphone to work with. To ensure that the levels are set right, speak into the microphone at a normal volume and adjust the blue gain slider until the volume bar is green while you’re speaking and yellow while you’re not - make sure it doesn’t hit the red.

14.
If you need to push the gain very high or very low, double-check the volume settings on your computer, as you may have accidentally turned your microphone’s volume too low or too high on your computer.

15.
To control the volume of your microphone, use the buttons in the sidebar. They work just like the channel faders, except the mic only has two levels - fully on and fully off. The keyboard shortcut to turn it on or off is X.

16.
After all that, you’re about ready to go live! But before you do, please close all programmes on your computer that aren’t Chrome. If you have programmes running in the background, they could overload your system, leading to sound dropouts during your show.

17.
When you’re ready to go live, just click the “Register for Show” button in the top bar of WebStudio. You must register for your show at least a minute before the news is due to start. If you do not register in time, the system will not know you’re there and will not switch to you - you’ll then have to register after the news, as the system is too busy blaring the news to hear you asking to join in. So make sure you do it a couple minutes before you’re due to go on air, to avoid running into issues right at the start.

18.
You should see the text next to it change from “Not Connected” to “Connecting”, and then to “Connected”. Once it says “Connected”, you’re good to go! You aren’t on the air yet though, that’ll happen after the news.

19.
Speaking of the news, you don’t have to worry about doing the news! It’s all handled by our servers. To cue you into your show, you’ll hear a jingle in your headphones at the appropriate time, but you don’t need to fade anything up or down during the news. When the news comes to an end, two minutes past the hour, you’ll hear a countdown and the News Out jingle - once it finishes, you’re good to start your show.

20.
To keep an eye on messages from your listeners, open the Studio Information Service (SIS) in another tab - go to MyRadio and click Studio Information Service.

21.
At the end of your show, you’ll hear the News In jingle at 15 seconds to the hour. Make sure you’ve finished your show by then, else it’ll cut you off, which makes for a weird listening experience. Once the news jingle has started to play, you’re safe to close WebStudio. The system will automatically do the news and then switch to either the next show or Jukebox. Congratulations on a (hopefully) successful show!

22.
So remember: your show starts two minutes past the hour, and ends 15 seconds to the hour; for example, if you have a 3pm slot, it’ll start at 15:02 and end at 15:59:45.

23.
If your show is longer than an hour, the news will also automatically happen in the middle of your show, on every hour gap, so make sure you’re aware of that as well. Again, starting at 15 seconds to the hour, and ending at two minutes past the hour.

24.
In a perfect world, this would be all there is to it. But sometimes, things don’t go to plan, and it’s possible that your connection to our servers fails for some reason. You’ll see the text next to the register button on the top change to “Connection lost, reconnecting”. If you see this, WebStudio will try to automatically reconnect and you don’t need to do anything. If it changes to just “Connection lost!”, click the “register for show” button again to reconnect, and go on with your show. If it still doesn’t work, reload the page and double-check your internet connection. If it *still* doesn’t work, it’s time to hit up the Remote Broadcasting channel in Slack and ask for help - hopefully someone will be able to get you up and running. After 30 seconds of silence, the station output will be switched to Jukebox - but if this happens, don’t worry, as soon as you can reconnect you’ll be put right back on air.

25.
That’s just about all you need to know about WebStudio to do your first show. Before you run off and blast the airwaves with your tunes of choice, we recommend you check out the Working From Home Resource Hub on our wiki, ury.org.uk/wiki. It has lots of useful information about how to optimise your setup for going live. Again, if you encounter any issues or need any support in your WebStudio adventures, message #remote-broadcasting in Slack and someone will (hopefully) get you back on track. Keep in touch, and happy broadcasting!

Working From Home Resources/WebStudio/Training

2020-10-19T18:42:33Z

11090: Created page with "1. Hi! I’m Alex Towells, University Radio York’s Production Manager. If you’re here, that means you want to know how to use our remote broadcasting tool, Webstudio! I’..."

Working From Home Resources/WebStudio

2020-10-19T18:42:06Z

11090:

<small>[[Working From Home Resources|back to hub]]</small>

WebStudio is URY's flagship Work From Home package. It's everything you ever loved about BAPS, and more, entirely online. For single-person music shows it will be all you need.

'''Note: these videos were recorded using a slightly older version of WebStudio which looks a bit different - all the key features are still in the same place.'''

== Training Video ==

<html>
<iframe width="560" height="315" src="https://www.youtube.com/embed/Oqmq4GSE8Zo" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</html>

[[Working From Home Resources/WebStudio/Training|Transcript]]

== Getting trained ==

Once you've watched the videos, please fill out [https://docs.google.com/forms/d/e/1FAIpQLSfWuE-BNA6k-TfeGgpS6lAy7UnrpcSgcK4QleHPmwK86CyaSQ/viewform?usp=sf_link this form] and we'll get you marked as trained!

Website History

2020-08-26T11:56:29Z

11090: /* 2018-Present */

Here's a potted '''history''' of the URY '''website''', courtesy of the Wayback Machine.

== c.1999-Oct 2003 ==

[[File:ws1.png]]

The earliest version of the website available on the Web Archive was definitely a product of its time, with the bright orange branding of that era prominent throughout and a very 90s GIF-based sidebar on the left.

It even had a guestbook, with some rather ''interesting'' contents.

At one point in 2000, [[Gavin Atkinson]] updated the site.

This design was created by [[Leo Warner]], and doesn't really work too well in 1080p.

=== Webcasting ===

At the start of Web Archive captures of the URY website, URY were still broadcasting only on 999kHz and did not yet simulcast on the Internet; however, by 2003, URY had leapt forward into the Internet Age by hosting a worldwide live stream... using ''RealPlayer''. Oh well...

== Oct 2003-Summer? 2006 ==

[[File:ws2.png]]

A radically new website design was launched in time for Autumn term 2003, featuring for the first time what seemed to be sensible web design (for it was a new millennium and the days of gaudy sidebars and orange on grey were far behind the URY computing team, in all their wisdom).

The guestbook and RealPlayer streams were still there, though.

This website ''does'' work quite well in 1080p, considering.

The then Head of Production, Simon Taghioff, was instrumental in this overhaul.

== 2006-2010 ==

[[File:ws3.png]]

A minor update of the previous website, with even more orange... and no guestbook in sight! RealPlayer by now had been joined by MP3 and Ogg Vorbis streams as URY's streaming technology marched on.

What the ''hell'' is that font on the advertising banner?

This design was jiggled around a bit over its four years of service, but remained mostly the same.

== 2010-2011 ==

[[File:URYsite09.png]]

In what was probably the most short-lived (and expensive!) of website designs, URY got [http://www.freelancegraphicdesigner.co.uk/ury-web-design.html a professional graphics designer] in to completely redesign the website in conjunction with URY's comprehensive rebranding.

The result was a lovely set of graphics (lovely being subjective on whether or not you like Impact as a font), but the code for the website wasn't as lovely. According to legend, the site was programmed in under a week to meet harsh deadlines and was therefore effectively hacked together. Despite all this, it worked for a year and as of writing the code is still there in heavily modified form.

Sources indicate that a DaveX was responsible for the coding.

== 2011-2012 ==

[[File:ws2011.png]]

The current website was largely the result of a rehashing of the design from last year by the combined efforts of [[Darren Webb]] and [[Rob Stonehouse]] on design and [[Matt Windsor]] on programming (which mainly involved tidying up the previous round of code and implementing the design changes in HTML5 and CSS).

This website won a YUM award in 2011.

There's still no guestbook.

== 2012-2013 ==
[[File:ws2012.png]]

In October 2012, the website was completely replaced with a shinier, newer, completely re-written site based on Django (a Python web framework). Despite the shiny new design, we immediately regretted this decision. The site was put live before it was ready - features were missing and never were fully implemented on this generation, and large amounts of it relied on a completely new database schema, so all of the Members' Internal website tools broke with the replacement. It suffered in service for less than a year before it was retired on August 2013.

== 2013-2018 ==

Sticking with the Python, Matt Windsor again went on an endeavour for a better website. With an entirely new codebase in Pyramid (another Python web framework) and SQLAlchemy, and a few shinifications to the actual design itself, this site went into production in August 2013, at the same time as our upgrade to Apache 2.4 and the replacement of Members' Internal with MyURY. Over the remainder of the Summer Holidays, MyURY was expanded to ensure it had capabilities to actually maintain this website, and so shiny Banner and Podcast systems were available and the site once again looked pretty.

There's still no guest book, but there is a sign up form on the Get Involved page.

== 2018-Present ==

''For a picture, load up [http://ury.org.uk ury.org.uk]!''

[[File:2016-site.png|1280px]]

The current version of the site, amusingly enough codenamed 2016-site, for it was started in 2016 but only released in 2018 (arguably still not finished...), was designed by Brooke Hatton and coded up by himself alongside (at various times) Matthew Stratford, Chris Taylor, Matt Windsor, Natalie Harris, Danny Roberts, and many others. Out went Python, and in came the modern programming language ''du jour'', Go. In between, MyURY was replaced by (read: renamed to) MyRadio, which feeds it everything - scheduling, podcasts, team info, you name it.

There's still no guest book.

Website History

2020-08-26T11:56:17Z

11090: /* 2018-Present */

Here's a potted '''history''' of the URY '''website''', courtesy of the Wayback Machine.

== c.1999-Oct 2003 ==

[[File:ws1.png]]

The earliest version of the website available on the Web Archive was definitely a product of its time, with the bright orange branding of that era prominent throughout and a very 90s GIF-based sidebar on the left.

It even had a guestbook, with some rather ''interesting'' contents.

At one point in 2000, [[Gavin Atkinson]] updated the site.

This design was created by [[Leo Warner]], and doesn't really work too well in 1080p.

=== Webcasting ===

At the start of Web Archive captures of the URY website, URY were still broadcasting only on 999kHz and did not yet simulcast on the Internet; however, by 2003, URY had leapt forward into the Internet Age by hosting a worldwide live stream... using ''RealPlayer''. Oh well...

== Oct 2003-Summer? 2006 ==

[[File:ws2.png]]

A radically new website design was launched in time for Autumn term 2003, featuring for the first time what seemed to be sensible web design (for it was a new millennium and the days of gaudy sidebars and orange on grey were far behind the URY computing team, in all their wisdom).

The guestbook and RealPlayer streams were still there, though.

This website ''does'' work quite well in 1080p, considering.

The then Head of Production, Simon Taghioff, was instrumental in this overhaul.

== 2006-2010 ==

[[File:ws3.png]]

A minor update of the previous website, with even more orange... and no guestbook in sight! RealPlayer by now had been joined by MP3 and Ogg Vorbis streams as URY's streaming technology marched on.

What the ''hell'' is that font on the advertising banner?

This design was jiggled around a bit over its four years of service, but remained mostly the same.

== 2010-2011 ==

[[File:URYsite09.png]]

In what was probably the most short-lived (and expensive!) of website designs, URY got [http://www.freelancegraphicdesigner.co.uk/ury-web-design.html a professional graphics designer] in to completely redesign the website in conjunction with URY's comprehensive rebranding.

The result was a lovely set of graphics (lovely being subjective on whether or not you like Impact as a font), but the code for the website wasn't as lovely. According to legend, the site was programmed in under a week to meet harsh deadlines and was therefore effectively hacked together. Despite all this, it worked for a year and as of writing the code is still there in heavily modified form.

Sources indicate that a DaveX was responsible for the coding.

== 2011-2012 ==

[[File:ws2011.png]]

The current website was largely the result of a rehashing of the design from last year by the combined efforts of [[Darren Webb]] and [[Rob Stonehouse]] on design and [[Matt Windsor]] on programming (which mainly involved tidying up the previous round of code and implementing the design changes in HTML5 and CSS).

This website won a YUM award in 2011.

There's still no guestbook.

== 2012-2013 ==
[[File:ws2012.png]]

In October 2012, the website was completely replaced with a shinier, newer, completely re-written site based on Django (a Python web framework). Despite the shiny new design, we immediately regretted this decision. The site was put live before it was ready - features were missing and never were fully implemented on this generation, and large amounts of it relied on a completely new database schema, so all of the Members' Internal website tools broke with the replacement. It suffered in service for less than a year before it was retired on August 2013.

== 2013-2018 ==

Sticking with the Python, Matt Windsor again went on an endeavour for a better website. With an entirely new codebase in Pyramid (another Python web framework) and SQLAlchemy, and a few shinifications to the actual design itself, this site went into production in August 2013, at the same time as our upgrade to Apache 2.4 and the replacement of Members' Internal with MyURY. Over the remainder of the Summer Holidays, MyURY was expanded to ensure it had capabilities to actually maintain this website, and so shiny Banner and Podcast systems were available and the site once again looked pretty.

There's still no guest book, but there is a sign up form on the Get Involved page.

== 2018-Present ==

''For a picture, load up [http://ury.org.uk ury.org.uk]!''

[[File:2016-site.png]]

The current version of the site, amusingly enough codenamed 2016-site, for it was started in 2016 but only released in 2018 (arguably still not finished...), was designed by Brooke Hatton and coded up by himself alongside (at various times) Matthew Stratford, Chris Taylor, Matt Windsor, Natalie Harris, Danny Roberts, and many others. Out went Python, and in came the modern programming language ''du jour'', Go. In between, MyURY was replaced by (read: renamed to) MyRadio, which feeds it everything - scheduling, podcasts, team info, you name it.

There's still no guest book.

Website History

2020-08-26T11:56:12Z

11090: /* 2018-Present */

Here's a potted '''history''' of the URY '''website''', courtesy of the Wayback Machine.

== c.1999-Oct 2003 ==

[[File:ws1.png]]

The earliest version of the website available on the Web Archive was definitely a product of its time, with the bright orange branding of that era prominent throughout and a very 90s GIF-based sidebar on the left.

It even had a guestbook, with some rather ''interesting'' contents.

At one point in 2000, [[Gavin Atkinson]] updated the site.

This design was created by [[Leo Warner]], and doesn't really work too well in 1080p.

=== Webcasting ===

At the start of Web Archive captures of the URY website, URY were still broadcasting only on 999kHz and did not yet simulcast on the Internet; however, by 2003, URY had leapt forward into the Internet Age by hosting a worldwide live stream... using ''RealPlayer''. Oh well...

== Oct 2003-Summer? 2006 ==

[[File:ws2.png]]

A radically new website design was launched in time for Autumn term 2003, featuring for the first time what seemed to be sensible web design (for it was a new millennium and the days of gaudy sidebars and orange on grey were far behind the URY computing team, in all their wisdom).

The guestbook and RealPlayer streams were still there, though.

This website ''does'' work quite well in 1080p, considering.

The then Head of Production, Simon Taghioff, was instrumental in this overhaul.

== 2006-2010 ==

[[File:ws3.png]]

A minor update of the previous website, with even more orange... and no guestbook in sight! RealPlayer by now had been joined by MP3 and Ogg Vorbis streams as URY's streaming technology marched on.

What the ''hell'' is that font on the advertising banner?

This design was jiggled around a bit over its four years of service, but remained mostly the same.

== 2010-2011 ==

[[File:URYsite09.png]]

In what was probably the most short-lived (and expensive!) of website designs, URY got [http://www.freelancegraphicdesigner.co.uk/ury-web-design.html a professional graphics designer] in to completely redesign the website in conjunction with URY's comprehensive rebranding.

The result was a lovely set of graphics (lovely being subjective on whether or not you like Impact as a font), but the code for the website wasn't as lovely. According to legend, the site was programmed in under a week to meet harsh deadlines and was therefore effectively hacked together. Despite all this, it worked for a year and as of writing the code is still there in heavily modified form.

Sources indicate that a DaveX was responsible for the coding.

== 2011-2012 ==

[[File:ws2011.png]]

The current website was largely the result of a rehashing of the design from last year by the combined efforts of [[Darren Webb]] and [[Rob Stonehouse]] on design and [[Matt Windsor]] on programming (which mainly involved tidying up the previous round of code and implementing the design changes in HTML5 and CSS).

This website won a YUM award in 2011.

There's still no guestbook.

== 2012-2013 ==
[[File:ws2012.png]]

In October 2012, the website was completely replaced with a shinier, newer, completely re-written site based on Django (a Python web framework). Despite the shiny new design, we immediately regretted this decision. The site was put live before it was ready - features were missing and never were fully implemented on this generation, and large amounts of it relied on a completely new database schema, so all of the Members' Internal website tools broke with the replacement. It suffered in service for less than a year before it was retired on August 2013.

== 2013-2018 ==

Sticking with the Python, Matt Windsor again went on an endeavour for a better website. With an entirely new codebase in Pyramid (another Python web framework) and SQLAlchemy, and a few shinifications to the actual design itself, this site went into production in August 2013, at the same time as our upgrade to Apache 2.4 and the replacement of Members' Internal with MyURY. Over the remainder of the Summer Holidays, MyURY was expanded to ensure it had capabilities to actually maintain this website, and so shiny Banner and Podcast systems were available and the site once again looked pretty.

There's still no guest book, but there is a sign up form on the Get Involved page.

== 2018-Present ==

''For a picture, load up [http://ury.org.uk ury.org.uk]!''

[[File:2016-site.png|9]]

The current version of the site, amusingly enough codenamed 2016-site, for it was started in 2016 but only released in 2018 (arguably still not finished...), was designed by Brooke Hatton and coded up by himself alongside (at various times) Matthew Stratford, Chris Taylor, Matt Windsor, Natalie Harris, Danny Roberts, and many others. Out went Python, and in came the modern programming language ''du jour'', Go. In between, MyURY was replaced by (read: renamed to) MyRadio, which feeds it everything - scheduling, podcasts, team info, you name it.

There's still no guest book.

Website History

2020-08-26T11:52:23Z

11090: /* 2018-Present */

Here's a potted '''history''' of the URY '''website''', courtesy of the Wayback Machine.

== c.1999-Oct 2003 ==

[[File:ws1.png]]

The earliest version of the website available on the Web Archive was definitely a product of its time, with the bright orange branding of that era prominent throughout and a very 90s GIF-based sidebar on the left.

It even had a guestbook, with some rather ''interesting'' contents.

At one point in 2000, [[Gavin Atkinson]] updated the site.

This design was created by [[Leo Warner]], and doesn't really work too well in 1080p.

=== Webcasting ===

At the start of Web Archive captures of the URY website, URY were still broadcasting only on 999kHz and did not yet simulcast on the Internet; however, by 2003, URY had leapt forward into the Internet Age by hosting a worldwide live stream... using ''RealPlayer''. Oh well...

== Oct 2003-Summer? 2006 ==

[[File:ws2.png]]

A radically new website design was launched in time for Autumn term 2003, featuring for the first time what seemed to be sensible web design (for it was a new millennium and the days of gaudy sidebars and orange on grey were far behind the URY computing team, in all their wisdom).

The guestbook and RealPlayer streams were still there, though.

This website ''does'' work quite well in 1080p, considering.

The then Head of Production, Simon Taghioff, was instrumental in this overhaul.

== 2006-2010 ==

[[File:ws3.png]]

A minor update of the previous website, with even more orange... and no guestbook in sight! RealPlayer by now had been joined by MP3 and Ogg Vorbis streams as URY's streaming technology marched on.

What the ''hell'' is that font on the advertising banner?

This design was jiggled around a bit over its four years of service, but remained mostly the same.

== 2010-2011 ==

[[File:URYsite09.png]]

In what was probably the most short-lived (and expensive!) of website designs, URY got [http://www.freelancegraphicdesigner.co.uk/ury-web-design.html a professional graphics designer] in to completely redesign the website in conjunction with URY's comprehensive rebranding.

The result was a lovely set of graphics (lovely being subjective on whether or not you like Impact as a font), but the code for the website wasn't as lovely. According to legend, the site was programmed in under a week to meet harsh deadlines and was therefore effectively hacked together. Despite all this, it worked for a year and as of writing the code is still there in heavily modified form.

Sources indicate that a DaveX was responsible for the coding.

== 2011-2012 ==

[[File:ws2011.png]]

The current website was largely the result of a rehashing of the design from last year by the combined efforts of [[Darren Webb]] and [[Rob Stonehouse]] on design and [[Matt Windsor]] on programming (which mainly involved tidying up the previous round of code and implementing the design changes in HTML5 and CSS).

This website won a YUM award in 2011.

There's still no guestbook.

== 2012-2013 ==
[[File:ws2012.png]]

In October 2012, the website was completely replaced with a shinier, newer, completely re-written site based on Django (a Python web framework). Despite the shiny new design, we immediately regretted this decision. The site was put live before it was ready - features were missing and never were fully implemented on this generation, and large amounts of it relied on a completely new database schema, so all of the Members' Internal website tools broke with the replacement. It suffered in service for less than a year before it was retired on August 2013.

== 2013-2018 ==

Sticking with the Python, Matt Windsor again went on an endeavour for a better website. With an entirely new codebase in Pyramid (another Python web framework) and SQLAlchemy, and a few shinifications to the actual design itself, this site went into production in August 2013, at the same time as our upgrade to Apache 2.4 and the replacement of Members' Internal with MyURY. Over the remainder of the Summer Holidays, MyURY was expanded to ensure it had capabilities to actually maintain this website, and so shiny Banner and Podcast systems were available and the site once again looked pretty.

There's still no guest book, but there is a sign up form on the Get Involved page.

== 2018-Present ==

''For a picture, load up [http://ury.org.uk ury.org.uk]!''

[[File:2016-site.png|960px]]

The current version of the site, amusingly enough codenamed 2016-site, for it was started in 2016 but only released in 2018 (arguably still not finished...), was designed by Brooke Hatton and coded up by himself alongside (at various times) Matthew Stratford, Chris Taylor, Matt Windsor, Natalie Harris, Danny Roberts, and many others. Out went Python, and in came the modern programming language ''du jour'', Go. In between, MyURY was replaced by (read: renamed to) MyRadio, which feeds it everything - scheduling, podcasts, team info, you name it.

There's still no guest book.

File:2016-site.png

2020-08-26T11:52:02Z

11090:

Incident Report: 20200627

2020-07-31T14:40:22Z

11090:

{{Incident
|brief=uryups0 forgot what "uninterruptible power" means
|severity=High
|impact=Medium (Total loss of computing services for 2 hours - but we were off air)
|start=2020-06-27 13:59
|end=2020-06-27
|mitigation=Improve monitoring
|leader=Marks Polakovs (MP)
|others=Michael Grace (MG), Matthew Stratford (MS), Isaac Lowe (IL), Harry Smith (HS), Alice Milburn (AVM), Jacob Dicker (JD)
}}

== Chronicle of Events ==

''(All times BST)''

At 13:58:29 the Stores UPS logged “UPS: The output power is turned off.” For, seemingly, no apparent reason. It tried to send us emails to warn us, but, considering it had just turned off power to the email server, that didn’t go well. At this point all of URY was down. '''OUTAGE BEGINS.'''

: Note: IL asked Danny to check his email (he uses a non-URY email for computing emails) for UPS alerts. None. Although that makes sense, as it had just killed the gateway it tried sending us the emails through.

At 14:01 HS asked in Slack “Is it just me or is the website down?”, and at 14:03 MG confirmed with an @channel that we had dropped off completely. '''INCIDENT BEGINS.'''

14:03:30 the UPS logged “UPS: The output power is turned on.” Great, except that all (read: most) servers were powered off, and weren’t set to power on boot (rightly so). Note that at this point we weren’t aware of a power problem, we presumed it was a janky uryfw0 ethernet cable again. AVM was closest to URY at the time, so she was sent in to investigate.

She arrived at around 14:30, checked the physical links in The Hub, all looked normal. She tried reseating fw0’s ethernet cables (unaware that it was completely off). At 14:42 she tried power-cycling fw0, and at 14:45 she reported that it was displaying the fateful error message: “RAID Adapter Memory Error!!!” (the exclamation marks are really part of the error). Sadly, she had to leave now to do Boring Things in The Real World. HS was next closest, so he was dispatched.

While the motley crew on the Zoom call (read: MP, MG, and MS) waited for HTS to arrive, they started discussing plans. They realise that urystv has near-identical hardware, so the plan becomes to swap uryfw0 and urystv’s hard disks - in effect making urystv the primary router.

HS arrives at 15:05. He reports that roughly half the servers were powered off (namely: uryfw0 (before AVM turned it on), urystv, urybackup0, ?). He gets to work on swapping the drives. This is finished at around 15:40 - HS tries importing the RAID array on urystv’s onboard adapter and booting it up. Has some issues, some related to the boot order, but gets it booted up at around 16:10ish. At this point we now have network access, and the gang get to work powering the other servers back up. '''OUTAGE ENDS-ish.'''

At 16:25 MP checks the UPS logs, and spots the errors from earlier. He is very confused. So is JD. The job of a UPS is normally to provide uninterruptible power, and today it did exactly the opposite of that, for essentially no reason. At JD’s suggestion MP runs a self-test and it passes.

At 16:54 at MS’ suggestion MP ran a full runtime calibration on the UPS - this also passed fine, although it still stubbornly reports a runtime of five minutes.

Server recovery:
* ury - the website came back at 16:38. Somewhat hilariously, Freshping reported that the website is down at 16:39, having somehow missed the previous three hours of downtime and deciding that up is down and down is up. This made MP very angry and he killed freshping.
* urybsod - unsurprisingly it reported pending sectors and went into single-user mode. HS ran a fsck and it booted fine… or did it? More on that later.
* urybackup0 - it had tres fun. As MS put it, “backup0 more like hiccup0.” I don’t actually remember much of this. Someone remind me to rewatch the Zoom recording.
* One of the loggers’ loggerng service didn’t start up properly for some reason. MP started it manually.

Aftermath:
* pool0/backup needed to be manually mounted on bsod - intuitively enough, at /mnt/pool0, not /mnt/pool0/backup.
* IL gave uryfw0's raid SDRAM a good kick, and it seems to work fine-ish. We still need to procure a spare, and it's not reliable enough to be our router so urystv is still doing that.

== Root Cause Analysis ==

Why did we drop off the internet? Because uryfw0 lost power.

Why did uryfw0 lose power? Because uryups0 turned it off.

Why did uryups0 turn off power? Nobody knows.

Why did nobody notice? Well, they did - and also, Freshping is awful.

Why did it take us so long to come back? Because nobody was on-site at the time, and because the servers didn’t boot back up immediately.

Why was nobody onsite? Because rona.

Why did the servers not boot back up? Because they weren’t set to boot on power.

Why weren’t they set to boot on power? Because the rush of power may trip the breaker. Sensible.

== Post-Recovery Actions ==

* Replace freshping with something better - MP done with uptimerobot
* Get a spare stick of raid RAM
* Figure out what the hell went wrong with the UPS - it shouldn't really be in the business of killing power willy-nilly

[[Category:Incident Reports]]

Cold-Starting URY Systems

2020-07-23T11:25:03Z

11090:

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY In A Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks. If you see any angry red X-es, mouse over them to check which box they're complaining about, and ensure it's powered on
* Check that you can hear
** Studio Red in Blue, and vice versa
** Jukebox and News (beeeeeeeep) in both studios
** AM on Phil in the office

== Additional Servers ==
Power on other systems:
* urybsod
** Don't forget to remount <code>urybackup0:/pool0/backup</code> to <code>/mnt/pool0</code>
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-23T11:24:39Z

11090:

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in A Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks. If you see any angry red X-es, mouse over them to check which box they're complaining about, and ensure it's powered on
* Check that you can hear
** Studio Red in Blue, and vice versa
** Jukebox and News (beeeeeeeep) in both studios
** AM on Phil in the office

== Additional Servers ==
Power on other systems:
* urybsod
** Don't forget to remount <code>urybackup0:/pool0/backup</code> to <code>/mnt/pool0</code>
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

User:11090/Shutting Down URY In A Hurry 2020

2020-07-23T11:23:41Z

11090: 11090 moved page User:11090/Shutting Down URY In A Hurry 2020 to Shutting Down URY In A Hurry

#REDIRECT [[Shutting Down URY In A Hurry]]

Shutting Down URY In A Hurry

2020-07-23T11:23:41Z

11090: 11090 moved page User:11090/Shutting Down URY In A Hurry 2020 to Shutting Down URY In A Hurry

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

Turn servers off in this order, waiting a few seconds between each button:

* urystv [no need to wait]
* ury (thunderhorn)
* dolby
* urybsod
* urysteve
* urybackup0
* uryfw0
* transmitter, uryblue, uryred [call engineering now]
* uryrrod [VMWare]

''Note: The KVM is powered by a 12V brick, so can’t go on UPS power. So you need to move the monitor cable between each server if one seems to be having trouble going down. The keyboard should still pass through using power gleaned from the PS/2 ports, if you want to risk that.'' [not sure if this is still a thing?]

A big factor in delays on powering down is hanging waiting on NFS/SMB - problematic if you’ve shut down whatever was providing the mount, so stick to this order.

As early as possible during this process, try to reach one of: Station Manager; Assistant Station Manager; Programme Controller to inform them of the service outage so they can invoke necessary social media routes.

Remember: Once these servers are off, sending emails to @ury.org.uk email accounts doesn't work! Use Slack, @york.ac.uk addresses, Facebook or phone numbers.

You now won't have much to do until the power's back on, most likely. Using a manual writing implement, make note of how the procedure went in preparation for [[Cold-Starting URY Systems]] later on.

== Rationale ==
* urystv has no critical mounts, so it can be a quick way to shed some load
* ury goes after that since it doesn’t have any mounts elsewhere
* dolby after that, because of postgres
* urybsod has some exports pertaining to log generation, namely to uryrrod and ury
* urysteve now, because of /music
* urybackup0 now because urysteve backs up to it. [If the UPS is absolutely screaming about low battery, you can risk taking this down first as it does draw the most power - still accurate?]
* uryfw0 after all that -- would be handy to still have comms if servers need to cross networks (unmounting loggers)
* The loggers, in no particular order.
* The transmitter must be turned off if the loggers are powered down, and especially if the UPS power fails altogether, due to lack of logging capability, a legal requirement. Call engineering to let them know this has happened.
* uryrrod mounts urybsod for mixclouder and urybackup0 for webcams, so it may be unhappy if it's unmounted - this is not critical though

[[Category:Technical How-Tos]]

User:11090/Cold-Starting URY Systems 2020

2020-07-23T11:23:27Z

11090: 11090 moved page User:11090/Cold-Starting URY Systems 2020 to Cold-Starting URY Systems

#REDIRECT [[Cold-Starting URY Systems]]

Cold-Starting URY Systems

2020-07-23T11:23:27Z

11090: 11090 moved page User:11090/Cold-Starting URY Systems 2020 to Cold-Starting URY Systems

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks. If you see any angry red X-es, mouse over them to check which box they're complaining about, and ensure it's powered on
* Check that you can hear
** Studio Red in Blue, and vice versa
** Jukebox and News (beeeeeeeep) in both studios
** AM on Phil in the office

== Additional Servers ==
Power on other systems:
* urybsod
** Don't forget to remount <code>urybackup0:/pool0/backup</code> to <code>/mnt/pool0</code>
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Incident Report: 20200627

2020-07-22T09:56:52Z

11090: /* Post-Recovery Actions */

Incident Report: 20200627

2020-07-22T09:53:20Z

11090: /* Chronicle of Events */

Incident Report: 20200627

2020-07-22T09:50:29Z

11090:

{{Incident
|brief=uryups0 forgot what "uninterruptible power" means
|severity=High
|impact=Medium (Total loss of computing services for 2 hours - but we were off air)
|start=2020-06-27 13:59
|end=2020-06-27
|mitigation=Improve monitoring
|leader=Marks Polakovs (MP)
|others=Michael Grace (MG), Matthew Stratford (MS), Isaac Lowe (IL), Harry Smith (HS), Alice Milburn (AVM), Jacob Dicker (JD)
}}

== Chronicle of Events ==

''(All times BST)''

At 13:58:29 the Stores UPS logged “UPS: The output power is turned off.” For, seemingly, no apparent reason. It tried to send us emails to warn us, but, considering it had just turned off power to the email server, that didn’t go well. At this point all of URY was down. '''OUTAGE BEGINS.'''

At 14:01 HS asked in Slack “Is it just me or is the website down?”, and at 14:03 MG confirmed with an @channel that we had dropped off completely. '''INCIDENT BEGINS.'''

14:03:30 the UPS logged “UPS: The output power is turned on.” Great, except that all (read: most) servers were powered off, and weren’t set to power on boot (rightly so). Note that at this point we weren’t aware of a power problem, we presumed it was a janky uryfw0 ethernet cable again. AVM was closest to URY at the time, so she was sent in to investigate.

She arrived at around 14:30, checked the physical links in The Hub, all looked normal. She tried reseating fw0’s ethernet cables (unaware that it was completely off). At 14:42 she tried power-cycling fw0, and at 14:45 she reported that it was displaying the fateful error message: “RAID Adapter Memory Error!!!” (the exclamation marks are really part of the error). Sadly, she had to leave now to do Boring Things in The Real World. HS was next closest, so he was dispatched.

While the motley crew on the Zoom call (read: MP, MG, and MS) waited for HTS to arrive, they started discussing plans. They realise that urystv has near-identical hardware, so the plan becomes to swap uryfw0 and urystv’s hard disks - in effect making urystv the primary router.

HS arrives at 15:05. He reports that roughly half the servers were powered off (namely: uryfw0 (before AVM turned it on), urystv, urybackup0, ?). He gets to work on swapping the drives. This is finished at around 15:40 - HS tries importing the RAID array on urystv’s onboard adapter and booting it up. Has some issues, some related to the boot order, but gets it booted up at around 16:10ish. At this point we now have network access, and the gang get to work powering the other servers back up. '''OUTAGE ENDS-ish.'''

At 16:25 MP checks the UPS logs, and spots the errors from earlier. He is very confused. So is JD. The job of a UPS is normally to provide uninterruptible power, and today it did exactly the opposite of that, for essentially no reason. At JD’s suggestion MP runs a self-test and it passes.

At 16:54 at MS’ suggestion MP ran a full runtime calibration on the UPS - this also passed fine, although it still stubbornly reports a runtime of five minutes.

Server recovery:
* ury - the website came back at 16:38. Somewhat hilariously, Freshping reported that the website is down at 16:39, having somehow missed the previous three hours of downtime and deciding that up is down and down is up. This made MP very angry and he killed freshping.
* urybsod - unsurprisingly it reported pending sectors and went into single-user mode. HS ran a fsck and it booted fine… or did it? More on that later.
* urybackup0 - it had tres fun. As MS put it, “backup0 more like hiccup0.” I don’t actually remember much of this. Someone remind me to rewatch the Zoom recording.
* One of the loggers’ loggerng service didn’t start up properly for some reason. MP started it manually.

Aftermath:
* pool0/backup needed to be manually mounted on bsod - intuitively enough, at /mnt/pool0, not /mnt/pool0/backup.
* IL gave uryfw0's raid SDRAM a good kick, and it seems to work fine-ish. We still need to procure a spare, and it's not reliable enough to be our router so urystv is still doing that.

== Root Cause Analysis ==

Why did we drop off the internet? Because uryfw0 lost power.

Why did uryfw0 lose power? Because uryups0 turned it off.

Why did uryups0 turn off power? Nobody knows.

Why did nobody notice? Well, they did - and also, Freshping is awful.

Why did it take us so long to come back? Because nobody was on-site at the time, and because the servers didn’t boot back up immediately.

Why was nobody onsite? Because rona.

Why did the servers not boot back up? Because they weren’t set to boot on power.

Why weren’t they set to boot on power? Because the rush of power may trip the breaker. Sensible.

== Post-Recovery Actions ==

* Replace freshping with something better - MP done with uptimerobot
* Get a spare stick of raid RAM

Incident Report: 20200627

2020-07-22T09:48:00Z

11090: Created page with "{{Incident |brief=uryups0 forgot what "uninterruptible power" means |severity=High |impact=Medium (Total loss of computing services for 2 hours - but we were off air)..."

{{Incident
|brief=uryups0 forgot what "uninterruptible power" means
|severity=High
|impact=Medium (Total loss of computing services for 2 hours - but we were off air)
|start=2020-06-27 13:59
|end=2020-06-27
|mitigation=Improve monitoring
|leader=Marks Polakovs (MP)
|others=Michael Grace (MG), Matthew Stratford (MS), Isaac Lowe (IL), Harry Smith (HS), Alice Milburn (AVM), Jacob Dicker (JD)
}}

== Chronicle of Events ==

''(All times BST)''

At 13:58:29 the Stores UPS logged “UPS: The output power is turned off.” For, seemingly, no apparent reason. It tried to send us emails to warn us, but, considering it had just turned off power to the email server, that didn’t go well. At this point all of URY was down. '''OUTAGE BEGINS.'''

At 14:01 HS asked in Slack “Is it just me or is the website down?”, and at 14:03 MG confirmed with an @channel that we had dropped off completely. '''INCIDENT BEGINS.'''

14:03:30 the UPS logged “UPS: The output power is turned on.” Great, except that all (read: most) servers were powered off, and weren’t set to power on boot (rightly so). Note that at this point we weren’t aware of a power problem, we presumed it was a janky uryfw0 ethernet cable again. AVM was closest to URY at the time, so she was sent in to investigate.

She arrived at around 14:30, checked the physical links in The Hub, all looked normal. She tried reseating fw0’s ethernet cables (unaware that it was completely off). At 14:42 she tried power-cycling fw0, and at 14:45 she reported that it was displaying the fateful error message: “RAID Adapter Memory Error!!!” (the exclamation marks are really part of the error). Sadly, she had to leave now to do Boring Things in The Real World. HS was next closest, so he was dispatched.

While the motley crew on the Zoom call (read: MP, MG, and MS) waited for HTS to arrive, they started discussing plans. They realise that urystv has near-identical hardware, so the plan becomes to swap uryfw0 and urystv’s hard disks - in effect making urystv the primary router.

HS arrives at 15:05. He reports that roughly half the servers were powered off (namely: uryfw0 (before AVM turned it on), urystv, urybackup0, ?). He gets to work on swapping the drives. This is finished at around 15:40 - HS tries importing the RAID array on urystv’s onboard adapter and booting it up. Has some issues, some related to the boot order, but gets it booted up at around 16:10ish. At this point we now have network access, and the gang get to work powering the other servers back up. '''OUTAGE ENDS-ish.'''

At 16:25 MP checks the UPS logs, and spots the errors from earlier. He is very confused. So is JD. The job of a UPS is normally to provide uninterruptible power, and today it did exactly the opposite of that, for essentially no reason. At JD’s suggestion MP runs a self-test and it passes.

At 16:54 at MS’ suggestion MP ran a full runtime calibration on the UPS - this also passed fine, although it still stubbornly reports a runtime of five minutes.

Server recovery:
* ury - the website came back at 16:38. Somewhat hilariously, Freshping reported that the website is down at 16:39, having somehow missed the previous three hours of downtime and deciding that up is down and down is up. This made MP very angry and he killed freshping.
* urybsod - unsurprisingly it reported pending sectors and went into single-user mode. HS ran a fsck and it booted fine… or did it? More on that later.
* urybackup0 - it had tres fun. As MS put it, “backup0 more like hiccup0.” I don’t actually remember much of this. Someone remind me to rewatch the Zoom recording.
* One of the loggers’ loggerng service didn’t start up properly for some reason. MP started it manually.

Aftermath:
* pool0/backup needed to be manually mounted on bsod - intuitively enough, at /mnt/pool0, not /mnt/pool0/backup.

== Root Cause Analysis ==

Why did we drop off the internet? Because uryfw0 lost power.

Why did uryfw0 lose power? Because uryups0 turned it off.

Why did uryups0 turn off power? Nobody knows.

Why did nobody notice? Well, they did - and also, Freshping is awful.

Why did it take us so long to come back? Because nobody was on-site at the time, and because the servers didn’t boot back up immediately.

Why was nobody onsite? Because rona.

Why did the servers not boot back up? Because they weren’t set to boot on power.

Why weren’t they set to boot on power? Because the rush of power may trip the breaker. Sensible.

== Post-Recovery Actions ==

* Replace freshping with something better - MP done with uptimerobot

Website History

2020-07-19T10:18:32Z

11090:

Here's a potted '''history''' of the URY '''website''', courtesy of the Wayback Machine.

== c.1999-Oct 2003 ==

[[File:ws1.png]]

The earliest version of the website available on the Web Archive was definitely a product of its time, with the bright orange branding of that era prominent throughout and a very 90s GIF-based sidebar on the left.

It even had a guestbook, with some rather ''interesting'' contents.

At one point in 2000, [[Gavin Atkinson]] updated the site.

This design was created by [[Leo Warner]], and doesn't really work too well in 1080p.

=== Webcasting ===

At the start of Web Archive captures of the URY website, URY were still broadcasting only on 999kHz and did not yet simulcast on the Internet; however, by 2003, URY had leapt forward into the Internet Age by hosting a worldwide live stream... using ''RealPlayer''. Oh well...

== Oct 2003-Summer? 2006 ==

[[File:ws2.png]]

A radically new website design was launched in time for Autumn term 2003, featuring for the first time what seemed to be sensible web design (for it was a new millennium and the days of gaudy sidebars and orange on grey were far behind the URY computing team, in all their wisdom).

The guestbook and RealPlayer streams were still there, though.

This website ''does'' work quite well in 1080p, considering.

The then Head of Production, Simon Taghioff, was instrumental in this overhaul.

== 2006-2010 ==

[[File:ws3.png]]

A minor update of the previous website, with even more orange... and no guestbook in sight! RealPlayer by now had been joined by MP3 and Ogg Vorbis streams as URY's streaming technology marched on.

What the ''hell'' is that font on the advertising banner?

This design was jiggled around a bit over its four years of service, but remained mostly the same.

== 2010-2011 ==

[[File:URYsite09.png]]

In what was probably the most short-lived (and expensive!) of website designs, URY got [http://www.freelancegraphicdesigner.co.uk/ury-web-design.html a professional graphics designer] in to completely redesign the website in conjunction with URY's comprehensive rebranding.

The result was a lovely set of graphics (lovely being subjective on whether or not you like Impact as a font), but the code for the website wasn't as lovely. According to legend, the site was programmed in under a week to meet harsh deadlines and was therefore effectively hacked together. Despite all this, it worked for a year and as of writing the code is still there in heavily modified form.

Sources indicate that a DaveX was responsible for the coding.

== 2011-2012 ==

[[File:ws2011.png]]

The current website was largely the result of a rehashing of the design from last year by the combined efforts of [[Darren Webb]] and [[Rob Stonehouse]] on design and [[Matt Windsor]] on programming (which mainly involved tidying up the previous round of code and implementing the design changes in HTML5 and CSS).

This website won a YUM award in 2011.

There's still no guestbook.

== 2012-2013 ==
[[File:ws2012.png]]

In October 2012, the website was completely replaced with a shinier, newer, completely re-written site based on Django (a Python web framework). Despite the shiny new design, we immediately regretted this decision. The site was put live before it was ready - features were missing and never were fully implemented on this generation, and large amounts of it relied on a completely new database schema, so all of the Members' Internal website tools broke with the replacement. It suffered in service for less than a year before it was retired on August 2013.

== 2013-2018 ==

Sticking with the Python, Matt Windsor again went on an endeavour for a better website. With an entirely new codebase in Pyramid (another Python web framework) and SQLAlchemy, and a few shinifications to the actual design itself, this site went into production in August 2013, at the same time as our upgrade to Apache 2.4 and the replacement of Members' Internal with MyURY. Over the remainder of the Summer Holidays, MyURY was expanded to ensure it had capabilities to actually maintain this website, and so shiny Banner and Podcast systems were available and the site once again looked pretty.

There's still no guest book, but there is a sign up form on the Get Involved page.

== 2018-Present ==

''For a picture, load up [http://ury.org.uk ury.org.uk]!''

The current version of the site, amusingly enough codenamed 2016-site, for it was started in 2016 but only released in 2018 (arguably still not finished...), was designed by Brooke Hatton and coded up by himself alongside (at various times) Matthew Stratford, Chris Taylor, Matt Windsor, Natalie Harris, Danny Roberts, and many others. Out went Python, and in came the modern programming language ''du jour'', Go. In between, MyURY was replaced by (read: renamed to) MyRadio, which feeds it everything - scheduling, podcasts, team info, you name it.

There's still no guest book.

Cold-Starting URY Systems

2020-07-19T09:50:09Z

11090: /* Dante */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks. If you see any angry red X-es, mouse over them to check which box they're complaining about, and ensure it's powered on
* Check that you can hear
** Studio Red in Blue, and vice versa
** Jukebox and News (beeeeeeeep) in both studios
** AM on Phil in the office

== Additional Servers ==
Power on other systems:
* urybsod
** Don't forget to remount <code>urybackup0:/pool0/backup</code> to <code>/mnt/pool0</code>
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-19T09:44:43Z

11090: /* Additional Servers */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks.

== Additional Servers ==
Power on other systems:
* urybsod
** Don't forget to remount <code>urybackup0:/pool0/backup</code> to <code>/mnt/pool0</code>
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-07T12:20:54Z

11090: /* Additional Servers */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
** Note that in the event of a full power outage, the ITS Cloud may not be immediately available. Patience.
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
** See above about the ITS Cloud.
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-07T10:49:26Z

11090:

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

==Dante==

* Open Dante Controller on one of the studio or production PCs (you might need Wogan up for this), and ensure that everything is happy and you see lots of green check marks.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Shutting Down URY In A Hurry

2020-07-07T10:44:42Z

11090:

Cold-Starting URY Systems

2020-07-07T10:41:04Z

11090:

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-07T10:40:24Z

11090: /* Core Computing Services */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' <code>telnet mta.york.ac.uk 25`</code>
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-07T10:38:55Z

11090: /* Critical Servers */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* No really, turn on uryfw0. Are you sure it’s on yet? Since this is the gateway for all URY systems, other servers may have trouble bringing up interfaces if it is not up.
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' `telnet mta.york.ac.uk 25`
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Cold-Starting URY Systems

2020-07-07T10:37:44Z

11090: /* Additional Servers */

'''PLEASE EVACUATE THE BUILDING SAFELY AND UPDATE SOCIAL MEDIA BEFORE ATTEMPTING TO RESTORE SERVICE'''

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

So, you've done a full shutdown. Or, there was a power cut or zombie apocalypse that interrupted the ability of our physical servers to operate. The good news is that you now thing you're ready to turn things back on.

''Remember - during any power failure it is advised to immediately switch off the transmitter. See [[Shutting Down URY in a Hurry]].''

== Before You Start - Is It Safe Checklist ==
* Is power back on yet? Has it been stable for a few minutes?
* Has the Head of Computing or Station Manager given consent to restoring service?
* Does information from Estates, YUSU or other relevant sources suggest all is okay?
* If you are going to re-start AM Transmission, have you got consent from the Chief Engineer to power on the transmitter audio path?
* Do you have at least two technical team members on site (ideally one engineer)?

Great - lets give this a go.

== Network Infrastructure ==
We got all these servers right? Well they ain't no good until there's a network. You do this stage in [[The Hub]].

* urysw4 should come up on its own, as it has PoE [???] - check the injector is on
* Power on urysw3 (The HP ProCurve 2626 [The top one])
* Power on urysw1 (The Netgear GS748T [The bottom one])

Have both of these switched on? Is urysw3 blinking happily? Is urysw1 looking like nothing much is happening? Perfect.

== Stores Power ==
Our power supply gets a little upset very easily. If this outage was caused by a power cut, chances are you'll want to use this section to restore power to the [[Server Cupboard]] circuit.

* Ensure the Transmitter is switched OFF (if it wasn't already, you aren't very good at reading this guide)
* Ensure the AM compressor is switched OFF
* Ensure the output compressor is switched OFF
* Ensure the AM Receiver is switched OFF

If you don't do this, then the initial inrush of power from turning on a rack full of equipment will overload the B16 breaker. It will make a noise as things try to turn on, give you a little fright, then promptly trip again. Possibly with a bright flash of light for dramatic effect.

* [Two People Required] Turn on the breaker labelled "metal clad sockets"
* If it did not do so automatically, switch on the UPS
* Turn the AM '''Receiver''' back on and ensure it is still tuned to 1350AM
* Turn the lower output compressor back ON (third box from the top)

The UPS will now begin charging. If it is fully depleted, it will be around 5 minutes before it will enable output power to the servers. Depending on the BIOS configuration, some may then start to automatically boot. Avoid this, if at all possible.

== Critical Servers ==
We identify critical servers as those that enable us to broadcast on AM. URY Policy states that we must have '''two''' operating loggers before restoration of AM service. You'll also want the jukebox to play some noise.

* Power on [[uryfw0]]
* Power on [[uryred]]
* Power on [[uryblue]]
* On both the loggers, run <code>sudo service loggerng status</code> and start it if it fails to auto-start
* Power on [[dolby]]
* If you don't get audio, run <code>cd /usr/local/etc/liquidsoap/scripts && sudo ./startAudio.sh</code>

The station should start outputting the world's most annoying loop, featuring a happy instrumental tune and someone telling you that we're off air right now. We're most definitely not.
:* If it tries to play a jingle, this might fail spectacularly and go to a loop of Monty Python's Intermission, featuring Alex Boyall giving a grammatically incorrect technical difficulties message.

== AM Broadcast ==
You can't start this section until at least 5-10 minutes after following ''Critical Servers''. It might be worth skipping to ''Core Computing Services'' and coming back in a bit. It also requires permission from the Chief Engineer.

* '''Two persons''' must '''separately check and verify''' that '''at least two''' logger services are operating correctly and have recorded the last 5 minutes of station output (or in the case of an AM logger, several minutes of static).
* Switch on the AM compressor (second box from the top)
* Switch on the AM Transmitter

If any of the following tests fail, '''switch off the transmitter immediately''' and follow [[Transmitter Troubleshooting]]
* Are all four power indicators on the left lit?
* Is the fan on the rear of the unit spinning?
* Is the forward power meter registering approximately 20W?
* Is the reflected power meter registering a negligible level (2-3W is okay, slightly more if it's damp outside)?
* Is the AM receiver showing 3 signal bars on its display?

* After 5 minutes, two people should then check the AM loggers.

== Core Computing Services ==
Core Computing Services are defined as those which must be operational for URY to broadcast anything other than [[iTones]] (or, at this point, Intermission).

* Power on [[urybackup0]] and [[urysteve]]
* ''Wait'' for urysteve to finish booting
* Power on [[ury]]
* Ensure selector is powered in The Hub
* Fade up jukebox in [[Studio Red]], then switch to S1 then back to S3
** This ensures selector state is up to date
** Jukebox should now be playing actual music. You might need to restart it if it's stuck on techlude - on Dolby, <code>cd /usr/local/etc/liquidsoap/scripts && sudo systemctl stop ury-jack && sudo ./startAudio.sh && sel 8 && sel 3</code>

That's the absolute basics. Now verify the following are accessible and functioning:

* http://ury.org.uk/
* https://ury.org.uk/myradio/
* https://ury.org.uk/roundcube/ (including sending test emails both internally and externally)
** It is possible that mta.york.ac.uk is not yet back online, or that it is but refuses to route mail. You can test this with good ol' `telnet mta.york.ac.uk 25`
* http://ury.org.uk/live/
* live-high, live-mobile, live-high-ogg, jukebox streams are visible at https://audio.ury.org.uk/status
* BAPS (all the presenter and guest PCs)
* Timelord (might need a reboot on eccleston/tennant/smith)
* myradio_daemon

We're now at a point where shows can go on and things will mostly be okay.

== Additional Servers ==
Power on other systems:
* urybsod
** Use https://urybsod.york.ac.uk/xymon/ to monitor other services
** https://ury.org.uk/loggerng/ should now be available
* uryrrod
** Only provides mixclouder service and webcams, will have no immediate noticable impact
* wogan
** The Windows PCs may be a bit unhappy if it isn't around
* urystv
* moyles - you'll need ITS to do this

== Nearly Done ==
Everything should be bright and cheery again now. You should now complete a full incident report and make it available online in [[:Category:Incident Reports]].

Ideally, you'd also act on any recommendations this review brings up to make things run better in future.

[[Category:Technical How-Tos]]

Shutting Down URY In A Hurry

2020-07-07T10:32:47Z

11090:

''This is a ops-critical document. A printed copy is available in the Server Cupboard and should be updated whenever this online version is.''

Turn servers off in this order, waiting a few seconds between each button:

* urystv [no need to wait]
* ury (thunderhorn)
* dolby
* urybsod
* urysteve
* urybackup0
* uryfw0
* transmitter, uryblue, uryred [call engineering now]
* uryrrod [VMWare]

''Note: The KVM is powered by a 12V brick, so can’t go on UPS power. So you need to move the monitor cable between each server if one seems to be having trouble going down. The keyboard should still pass through using power gleaned from the PS/2 ports, if you want to risk that.'' [not sure if this is still a thing?]

A big factor in delays on powering down is hanging waiting on NFS/SMB - problematic if you’ve shut down whatever was providing the mount, so stick to this order.

As early as possible during this process, try to reach one of: Station Manager; Assistant Station Manager; Programme Controller to inform them of the service outage so they can invoke necessary social media routes.

Remember: Once these servers are off, sending emails to @ury.org.uk email accounts doesn't work! Use @york.ac.uk addresses, Facebook or phone numbers.

You now won't have much to do until the power's back on, most likely. Using a manual writing implement, make note of how the procedure went in preparation for [[Cold-Starting URY Systems]] later on.

== Rationale ==
* urystv has no critical mounts, so it can be a quick way to shed some load
* ury goes after that since it doesn’t have any mounts elsewhere
* dolby after that, because of postgres
* urybsod has some exports pertaining to log generation, namely to uryrrod and ury
* urysteve now, because of /music
* urybackup0 now because urysteve backs up to it. [If the UPS is absolutely screaming about low battery, you can risk taking this down first as it does draw the most power - still accurate?]
* uryfw0 after all that -- would be handy to still have comms if servers need to cross networks (unmounting loggers)
* The loggers, in no particular order.
* The transmitter must be turned off if the loggers are powered down, and especially if the UPS power fails altogether, due to lack of logging capability, a legal requirement. Call engineering to let them know this has happened.
* uryrrod mounts urybsod for mixclouder and urybackup0 for webcams, so it may be unhappy if it's unmounted - this is not critical though

[[Category:Technical How-Tos]]