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

























  • 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


















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

























  • 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
















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
















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















share|improve this question













share|improve this question




share|improve this question








edited Jan 1 at 13:13







Harry McGovern

















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





















  • 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














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
























  • 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











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
});


}
});














draft saved

draft discarded


















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















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
























  • 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
















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
























  • 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














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













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












share|improve this answer



share|improve this answer










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



















  • 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




















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














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















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

'app-layout' is not a known element: how to share Component with different Modules

Image
0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule ...
Read more

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d ...
Read more

WPF add header to Image with URL pettitions [duplicate]

Image
up vote 0 down vote favorite This question already has an answer here: Image source URI requiring authorization 3 answers Add header to all* HTTP requests on a machine 1 answer first of all sorry for my english. Recently I added some security in the backend of my project, and now I need to send a validation code(apiKey) inside the headers to retrieve the images. I have a problem with ALL images in my project that I had attached in my UI. For example, before I had: <Image Height="90" Source="{Binding Video.Thumbnail}"/> Now I need to change my code to create a CUSTOM petition add the apiKey in the header:...
Read more