What Does This Mean I notice This Again

5:38:21 AMSammy Kershaw - National Working Womans Holiday
5:40:00 AMStarting event "bits"
5:40:00 AMSchedule: [bits] \Bits*0
10:40:12 AM*ServerTimeZone* Started (9.0.0.76)
10:40:13 AM*ServerTimeZone* Sammy Kershaw - National Working Womans Holiday
10:40:14 AM*ServerTimeZone* Relay activated
10:40:14 AM*ServerTimeZone* Connected to server! (output 1)
5:41:50 AMBrett Eldredge - Love Someone (Radio Edit)
5:45:11 AMShenandoah - Janie Baker's Love Slave
 
at 5:40:00 am is was to play the BITS

but shows 10:40:12 am
10:40:12 AM*ServerTimeZone* Started (9.0.0.76)

10:40:14 AM*ServerTimeZone* Relay activated

10:40:14 AM*ServerTimeZone* Relay activated
10:40:14 AM*ServerTimeZone* Connected to server! (output 1)

then goes back to the correct time 5:41:14 play song

this cause a disconnect in the stream
 
Those lines mean that the player was restarted for some reason. Can you please specify the account user name where this happens?
 
Account

stream7954


User Name Gary Wines

0:40:12 AM*ServerTimeZone* Started (9.0.0.76)
10:40:13 AM*ServerTimeZone* Sammy Kershaw - National Working Womans Holiday
10:40:14 AM*ServerTimeZone* Relay activated
10:40:14 AM*ServerTimeZone* Connected to server! (output 1)
@ 5:40 am on 03/25/2021
 
User
Eddie Carson

Small (stream7205)

Have the disconnect problem
 

Attachments

  • 7205stream again.txt
    1.4 KB · Views: 223
  • 7205stream.txt
    1.8 KB · Views: 224
on user Gary Wines
stream7954

again doing this


12:45:17 PMLINER1007 - DELETE
12:45:25 PMBill Medley & Jennifer Warnes - Ive Had The Time Of My Life
12:49:54 PMRelay deactivated
12:49:54 PMExit
9:49:57 AM*ServerTimeZone* Started (9.0.0.80)
9:49:58 AM*ServerTimeZone* Animotion - Obsession
9:49:59 AM*ServerTimeZone* Relay activated
9:49:59 AM*ServerTimeZone* Connected to server! (output 1)
9:50:00 AM*ServerTimeZone* Starting event "Bits"
9:50:00 AM*ServerTimeZone* Schedule: [Bits] \Bits*0
12:50:03 PMStarting event "Bits"
12:50:03 PMSchedule: [Bits] \Bits*0
12:53:45 PMMO273
12:54:08 PMMO274
 
This is because we've installed an update today to fix the non-working track repeat protection bug. Service restart was required, but as you can see from the logs, it only resulted in 4 (four) seconds downtime :)
 
Back
Top