Skip to main content
K
Komal_Mehta
Participating Frequently
July 12, 2012
Question

Admin logs not appearing

  • July 12, 2012
  • 1 reply
  • 1753 views

Hi,

I am using FMS 4.5.1 and Windows 2008 (64 bits) OS. I am loading the media files from a different machine.  Thus I started running the FMSMaster as Network service on the console.  Ever since this is running on a console, the error logs have stopped appearing on the Admin panel.  I am getting following error on the console while FMS is running:

Failed to open log file C:\Program Files\Adobe\Flash Media Server 4.5\logs\master.00.log errno=13

Machine configuration:

Windows 2008 R2 Enterprise,
SP1, 64-bit Operating System

RAM 16GB

Process Intel(R) Xeon (R) CPU E5607 @ 2.27GHz


Please suggest.

thanks,

Komal

This topic has been closed for replies.

1 reply

K
Komal_MehtaAuthor
Participating Frequently
July 13, 2012

Hi,

I installed the FMS on a different machine today. This is a Windows 7 machine. I installed it on D:/Program Files location. I am getting the same problem.

Till the time, videos were placed in FMS vod folder, logs were appearing in the Admin panel. But as I reconfigured the fms.ini and Applicaton.xml to load videos from a remote machine, logs do not appear. Here is the detailed error output on the FMS cmd prompt:

--------------------------

D:\Program Files\Adobe\Flash Media Server 4.5>FMSMaster.exe -console

TimeResolutionImpl::set(00.001000000)

  returning 00.000976500

Adobe Flash Media Server (Master) [4.5.0.r297.x86]

Copyright(c) 1993-2011 Adobe Systems Incorporated. All Rights Reserved.

Console mode.

FMS detected IPv6 protocol stack!

FMS config <NetworkingIPv6 enable=false>

FMS running in IPv4 protocol stack mode!

Host: HDCHNVETA22759 IPv4: 10.105.195.19

Server starting...

D:\Program Files\Adobe\Flash Media Server 4.5\Apache2.2\bin\httpd -f ./conf/httpd.conf -d "D:\Program Files\Adobe\Flash Media Server 4.5\Apache2.2" -n FMSHttpd -k start returned 1: [Fri Jul 13 10:54:56 2012] [info] mod_jithttp - FMS installation path: "D:\\Program Files\\Adobe\\Flash Media Server 4.

5\\"

(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:8134

no listening sockets available, shutting down

Unable to open logs

Server started (D:\Program Files\Adobe\Flash Media Server 4.5\conf\server.xml).

Core (4168) is no longer active.

Core (6376) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -console  -conf "D:\Program Files\Adobe\Flash Media Server 4.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1".

------------------------

I think there is some catch in these lines, which I am not able to identify.

(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : make_sock: could not bind to address 0.0.0.0:8134

no listening sockets available, shutting down

Unable to open logs

Please help me.

Thanks,

Komal

K
Komal_MehtaAuthor
Participating Frequently
July 17, 2012

Adobe folks - Please help me. This is a show stopper for my project. I need to showcase the logs to my customer.

N
Adobe Employee
NpComplete
Adobe Employee
July 17, 2012

It seems there are some either permission issues with FMS to write in the log directory or there is some conflict with some other already running FMS service

There are few things that I can suggest you:

1. Make sure, when you start FMS from console, there is no instance of FMS or FMSAdmin already started on that machine. You may check the service.. look out for Flash Media Server / Flash Media Admin Server services. If they are running stop them, before starting FMSMaster or Admin from console.

2. Make sure you start the cmd prompt with the right privileges. FMSMaster take the console privileges in case you start with console. Right click on console icon, it will prompt you option to start as Adminstrator.

You may try to create a file in the log directory from the console to find whether it has rights to write in the log directory.

3. Or set up the log directory to a location where the console has right to write.

Hope it helps

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices