What is causing this IcecastV2 “Bad or missing password on admin command request” warning?

1

I'm running IcecastV2, and although everything appears to be working - the log file shows this message.

INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

I cannot find a reason that could be causing this?

Edit: Icecast V2.4.4 compiled on Mac.

EDIT:

This is from the error.log file, Followed matched by same time period from access.log

    [2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:44] INFO format-vorbis/initial_vorbis_page seen initial vorbis header

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.aac"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.aac changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.mp3"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.mp3 changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

access.log

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

icecast

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?
  
  – TBR
  Jan 1 at 12:36
  
  
  

  
  
  
  

add a comment | 

1

I'm running IcecastV2, and although everything appears to be working - the log file shows this message.

INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

I cannot find a reason that could be causing this?

Edit: Icecast V2.4.4 compiled on Mac.

EDIT:

This is from the error.log file, Followed matched by same time period from access.log

    [2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:44] INFO format-vorbis/initial_vorbis_page seen initial vorbis header

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.aac"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.aac changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.mp3"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.mp3 changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

access.log

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

icecast

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?
  
  – TBR
  Jan 1 at 12:36
  
  
  

  
  
  
  

add a comment | 

1

1

1

I'm running IcecastV2, and although everything appears to be working - the log file shows this message.

INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

I cannot find a reason that could be causing this?

Edit: Icecast V2.4.4 compiled on Mac.

EDIT:

This is from the error.log file, Followed matched by same time period from access.log

    [2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:44] INFO format-vorbis/initial_vorbis_page seen initial vorbis header

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.aac"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.aac changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.mp3"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.mp3 changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

access.log

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

icecast

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

I'm running IcecastV2, and although everything appears to be working - the log file shows this message.

INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

I cannot find a reason that could be causing this?

Edit: Icecast V2.4.4 compiled on Mac.

EDIT:

This is from the error.log file, Followed matched by same time period from access.log

    [2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:08:44] INFO format-vorbis/initial_vorbis_page seen initial vorbis header

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.aac"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.aac changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:08:44] INFO admin/admin_handle_request Received admin command metadata on mount "/live.mp3"

[2019-01-01  13:08:44] INFO admin/command_metadata Metadata on mountpoint /live.mp3 changed to "Kostas Pavlidis - Fake Life"

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:09:31] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

[2019-01-01  13:10:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: stats.xml)

access.log

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:31 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4439 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:08:44 +0000] "GET /admin/metadata HTTP/1.0" 200 396 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:31 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:09:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 1

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:10:32 +0000] "GET /admin/stats.xml HTTP/1.0" 200 4415 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

192.168.0.7 - - [01/Jan/2019:13:11:32 +0000] "GET /admin/stats.xml HTTP/1.1" 401 360 "-" "sambc/2018.10" 0

icecast

icecast

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

share|improve this question

share|improve this question

edited Jan 1 at 13:13

Harry McGovern

edited Jan 1 at 13:13

Harry McGovern

edited Jan 1 at 13:13

Harry McGovern

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

asked Jan 1 at 12:03

Harry McGovernHarry McGovern

13511

13511

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?
  
  – TBR
  Jan 1 at 12:36
  
  
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?
  
  – TBR
  Jan 1 at 12:36
  
  
  

  
  
  
  

Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?

– TBR
Jan 1 at 12:36

Please provide (edit your question) associated and unaltered lines from access.log for and around the timestamp of this message. Which version of Icecast is this?

– TBR
Jan 1 at 12:36

add a comment | 

1 Answer
1

active

oldest

votes

2

From the combined logs it's pretty obvious what's happening here:

• You are running at least 3 source clients into mountpoints


• The source client each time seems to be sambc/2018.10 (Possibly SAM Broadcaster?)


• These source clients are making stream metadata update requests via /admin/metadata
  
  
  
  
  • For Ogg that's actually a bug and likely the metadata is broken for listeners.
  
  
  • It should embed the metadata inside the stream that it sends to the server instead!
  
  
  
  


• These source clients are each polling statistics via /admin/stats.xml
  
  
  
  
  • For some reason the source client doesn't cache the fact that authentication is necessary for this URL and follows the 'from zero' HTTP request procedure every time where
    
    
    
    
    1. first it doesn't send credentials
    
    
    2. It gets refused with a HTTP 401 status
    
    
    3. It sends the same request again, but including credentials
    
    
    
    
  
  
  
  

Summarizing: The behaviour you are concerned about is perfectly within what's defined by the HTTP standards. Icecast is just a bit wordy on that particular event.

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.
  
  – Harry McGovern
  Jan 1 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.
  
  – TBR
  Jan 1 at 14:58
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995268%2fwhat-is-causing-this-icecastv2-bad-or-missing-password-on-admin-command-request%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

2

From the combined logs it's pretty obvious what's happening here:

• You are running at least 3 source clients into mountpoints


• The source client each time seems to be sambc/2018.10 (Possibly SAM Broadcaster?)


• These source clients are making stream metadata update requests via /admin/metadata
  
  
  
  
  • For Ogg that's actually a bug and likely the metadata is broken for listeners.
  
  
  • It should embed the metadata inside the stream that it sends to the server instead!
  
  
  
  


• These source clients are each polling statistics via /admin/stats.xml
  
  
  
  
  • For some reason the source client doesn't cache the fact that authentication is necessary for this URL and follows the 'from zero' HTTP request procedure every time where
    
    
    
    
    1. first it doesn't send credentials
    
    
    2. It gets refused with a HTTP 401 status
    
    
    3. It sends the same request again, but including credentials
    
    
    
    
  
  
  
  

Summarizing: The behaviour you are concerned about is perfectly within what's defined by the HTTP standards. Icecast is just a bit wordy on that particular event.

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.
  
  – Harry McGovern
  Jan 1 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.
  
  – TBR
  Jan 1 at 14:58
  

  
  
  
  

add a comment | 

2

From the combined logs it's pretty obvious what's happening here:

• You are running at least 3 source clients into mountpoints


• The source client each time seems to be sambc/2018.10 (Possibly SAM Broadcaster?)


• These source clients are making stream metadata update requests via /admin/metadata
  
  
  
  
  • For Ogg that's actually a bug and likely the metadata is broken for listeners.
  
  
  • It should embed the metadata inside the stream that it sends to the server instead!
  
  
  
  


• These source clients are each polling statistics via /admin/stats.xml
  
  
  
  
  • For some reason the source client doesn't cache the fact that authentication is necessary for this URL and follows the 'from zero' HTTP request procedure every time where
    
    
    
    
    1. first it doesn't send credentials
    
    
    2. It gets refused with a HTTP 401 status
    
    
    3. It sends the same request again, but including credentials
    
    
    
    
  
  
  
  

Summarizing: The behaviour you are concerned about is perfectly within what's defined by the HTTP standards. Icecast is just a bit wordy on that particular event.

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.
  
  – Harry McGovern
  Jan 1 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.
  
  – TBR
  Jan 1 at 14:58
  

  
  
  
  

add a comment | 

2

2

2

From the combined logs it's pretty obvious what's happening here:

• You are running at least 3 source clients into mountpoints


• The source client each time seems to be sambc/2018.10 (Possibly SAM Broadcaster?)


• These source clients are making stream metadata update requests via /admin/metadata
  
  
  
  
  • For Ogg that's actually a bug and likely the metadata is broken for listeners.
  
  
  • It should embed the metadata inside the stream that it sends to the server instead!
  
  
  
  


• These source clients are each polling statistics via /admin/stats.xml
  
  
  
  
  • For some reason the source client doesn't cache the fact that authentication is necessary for this URL and follows the 'from zero' HTTP request procedure every time where
    
    
    
    
    1. first it doesn't send credentials
    
    
    2. It gets refused with a HTTP 401 status
    
    
    3. It sends the same request again, but including credentials
    
    
    
    
  
  
  
  

Summarizing: The behaviour you are concerned about is perfectly within what's defined by the HTTP standards. Icecast is just a bit wordy on that particular event.

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

From the combined logs it's pretty obvious what's happening here:

• You are running at least 3 source clients into mountpoints


• The source client each time seems to be sambc/2018.10 (Possibly SAM Broadcaster?)


• These source clients are making stream metadata update requests via /admin/metadata
  
  
  
  
  • For Ogg that's actually a bug and likely the metadata is broken for listeners.
  
  
  • It should embed the metadata inside the stream that it sends to the server instead!
  
  
  
  


• These source clients are each polling statistics via /admin/stats.xml
  
  
  
  
  • For some reason the source client doesn't cache the fact that authentication is necessary for this URL and follows the 'from zero' HTTP request procedure every time where
    
    
    
    
    1. first it doesn't send credentials
    
    
    2. It gets refused with a HTTP 401 status
    
    
    3. It sends the same request again, but including credentials
    
    
    
    
  
  
  
  

Summarizing: The behaviour you are concerned about is perfectly within what's defined by the HTTP standards. Icecast is just a bit wordy on that particular event.

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

share|improve this answer

share|improve this answer

answered Jan 1 at 13:21

TBRTBR

1,8241716

answered Jan 1 at 13:21

TBRTBR

1,8241716

answered Jan 1 at 13:21

TBRTBR

1,8241716

1,8241716

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.
  
  – Harry McGovern
  Jan 1 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.
  
  – TBR
  Jan 1 at 14:58
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.
  
  – Harry McGovern
  Jan 1 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.
  
  – TBR
  Jan 1 at 14:58
  

  
  
  
  

I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.

– Harry McGovern
Jan 1 at 14:02

I'm kind of following what you say. So basically I can ignore these messages as just excessive talk from Icecast. I should change the log level I guess.

– Harry McGovern
Jan 1 at 14:02

Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.

– TBR
Jan 1 at 14:58

Correct, it's safe to ignore as it just says in this case "I served a 401", which is part of the full authentication process.

– TBR
Jan 1 at 14:58

add a comment | 

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53995268%2fwhat-is-causing-this-icecastv2-bad-or-missing-password-on-admin-command-request%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

This page is only for reference, If you need detailed information, please check here