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

Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

Image
28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
Read more

Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

Image
up vote 13 down vote favorite 1 After the 2018 errata, the disintegrate spell description now reads: A creature targeted by this spell must make a Dexterity saving throw. On a failed save, the target takes 10d6 + 40 force damage. The target is disintegrated if this damage leaves it with 0 hit points. If you were to polymorph an enemy into a rat and then disintegrate it, would the enemy be disintegrated or would it just return to its original form? I know that for Druids, it’s not an instant kill anymore, but is this the case for polymorph as well? dnd-5e spells polymorph errata share | improve this question edited 18 hours ago
Read more

A Topological Invariant for $pi_3(U(n))$

Image
3 3 $begingroup$ Recently, I saw a construction of topological invariant for $pi_3(U(n))$ with $ngeq 2$ : $$ N=frac{1}{24pi^2}int_{S^3} d^3x epsilon^{ijk} Tr[(U^{-1}partial_{x_i}U)(U^{-1}partial_{x_j}U)(U^{-1}partial_{x_k}U)] , $$ where $Uin U(n)$ depends on $boldsymbol{x}=(x_1,x_2,x_3)in S^3$ , $epsilon^{ijk}$ is the Levi-Civita symbol, $i,j,k=1,2,3$ , and the duplicated indexes are summed over. It is claimed that $N$ is an integer, but why? Update 02/02/2019 I think I got an argument for $n=2$ . In this case, $U=e^{i varphi} q$ with $qin SU(2)$ . Due to the trace and the Levi-Civita symbol in $N$ , $varphi$ does not contribute to $N$ . As $Tr[q^{dagger}partial_i q]=0$ and $(q^{dagger}partial_i q)^{dagger}=-q^{dagger}partial_i q$ , $q^{dagger}partial_i q$ in geneeral has the form $q^{dagger}partia
Read more