Multicast ASR Error

I'm testing multicast ASR for imaging the Macs in a lab. The clients are on the same subnet as the server. The clients definitely see the server and the source image. However, the imaging fails almost immediately (right after the 'Restoring" notice) with this error message:
"asr: failed to read the stream: can't assign requested address."
I created the image with Bombich's NetRestore Helper. Any ideas to solve this would be much appreciated.

Additional clues: I know this isn't a firewall issue, at least on the server side. I stopped the service and tried again, but got the same error message. I've also rebuilt the asrconfig.plist file, in case that was corrupted.

Similar Messages

  • Network install through multicast ASR

    *Environment*
    Server: Mac OS X server tiger 10.4.11 serving DHCP
    Clients: Over 50 MacBooks
    **What I want to complete**
    Client MacBooks will boot from the server and retrieve the image loaded on the server through multicast asr so that I can install 50 laptops at one time from single image
    **What I have done**
    Run the "asr -source /Images/client.dmg -server /Users/administrator/Desktop/asr.plist" and got "Ready to start accepting clients". (client.dmg was built by using Bombich's NetRestore Helper)
    **Problem I got**
    When booting up the Macbook clients by holding down the "N" key, the clients could not boot from network to retrieve the image successfully
    **Questions I have**
    1. On the server, what services do I need to run other than the DHCP service?
    2. What else did I miss?
    Thanks much!
    Message was edited by: RabbitSF

    Thanks very much for the quick response, foilpan.
    I now start the Netboot and NFS services. On the NetBoot Settings, I have the Ethernet Port enabled and the Client.dmg image enabled and set as Default, Protocol is NFS. The Architecture is PowerPC, I want to change it to Intel but it grayed out and I can't change it. (The Client.dmg is built from a Snow Leopard machine.)
    But it is still not working when tried to boot the client. The client got no problem getting an IP from the server. I can see that from the DHCP service.
    Anything I did wrong? Does the Architecture matter?
    Thanks much again!

  • LV2011 udp multicast open error 54

    Hi guys,
    I'm working on conversion from LV8.6 to 2011 for one of my projects. One thing I found was that the UDP broadcast module no longer worked. After digging into the vi i found that the "UDP Multicast Read-Write Open.vi" did not work the way as in 8.6.
    I used a net address string input of "172.16.1.234" (my secondary network card), after string-to-ip conversion it gave 2886730218. then the UDP vi gave an error 54 in LV2011. (in 8.6 this does not happen)
    I even tried using 127.0.0.1 or with ONLY my primary network card enabled (172.22.1.100), it always gives error 54.
    The only input to make it pass i found was 0.
    I have attached a ss of my test vi. Thanks for your inputs.
    LabVIEW 2011 newbie >.<
    Certified LabVIEW Developer
    Solved!
    Go to Solution.

    Thanks for the reply. I have also checked that example. Please note that in the example it doesn't have an input for the net address, which i assume labview 2011 will use 0.
    I have also just received a reply from NI and confirmed it's a known bug in 2011. i will post it below.
    I hope this finds you doing well. I am glad to hear that you are starting to upgrade to 2011 and I apologize for the issues you are seeing. I suspect you are using this on one of our Real-Time targets if so the good news is that this behavior has been documented in the form of a CAR (actually a
    few): Broadcasts and the UDP Open VI have an INCONSISTANT behavior depending on the OS. Pharlap/Windows receive broadcasts when the "net address" terminal is wired while vxWorks/Linux don't. These CARs are scheduled as major incoviencience and will be fixed in a future version of LabVIEW as of now the work around is to simple not wire the net address field.
    The CAR numbers incase you would like to see when they are fixed are:
    257627, 233344,235444, 283205
    LabVIEW 2011 newbie >.<
    Certified LabVIEW Developer

  • Error creating a netboot image with System Image Utility

    Hi all !
    I am trying to create a NetBoot image from my Panther CD, to boot an old iBook.
    I am using System Image Utility version 10.4.11.
    I can create a NetInstall image, but when I create a NetBoot image SIU give me an error.
    I looked in the logs and I can see the error is generated by the script Applications/Server/System Image Utility.app/Contents/Resources/.preinstall
    This command is the culprit:
    /usr/sbin/installer -verbose -lang 'eng' -pkg '/Volumes/Mac OS X Install Disc 1/System/Installation/Packages/OSInstall.mpkg' -target /Library/NetBoot/NetBootSP0/PantBoot3.nbi/mnt -_multiDiscPath /tmp/siuInstallExtras
    The error is (as seen in the logs):
    This package requires authentication to install.
    If I take the command and run it in the terminal using sudo it goes thru, but gives another error:
    installer: Cannot install on volume /Library/NetBoot/NetBootSP0/PantBoot3.nbi/mnt because it is disabled.
    installer: Mac OS X cannot start up from this volume.
    Is this thing supposed to work ?? It seems to me SIU is buggy.
    Any help would be much appreciated.
    Regards
    Mike

    I'm not digging the new SIU at all yet. Maybe I'll get used to it in time. I couldn't get it to accept a Tiger 10.4.6 Install disc the other day to build a NetInstall. Don't know if I was doing something wrong or if it was instinctively rejecting it because I was doing something unsupported.
    I miss NetRestore. I think Mike wants use to use Automator... but I want NetRestore's automated Multicast ASR and Windows image restore. It would take a lot of work to match Mike's shrink-wrapped solution.
    Speaking of NetRestore, its creator Mike Bombich advises against use CCC for mass deployment. This may include what you're doing. It's really a backup tool, but unfortunately a lot of people got into the habit of using it for creating deployment images and these often have problems. It's the best tool for create images that you will deploy onto multiple Macs.

  • System Image Utility Workflow

    Hello,
    I'm brand new to System Image Utility and NetInstall. Up until recently I had been using MultiCast ASR. Does anyone know of any good tutorials, or how tos on setting up work flows. I have not been able to NetInstall a cloned image yet, and I have yet to automate an install based off a NetInstall Image of the Snow Leopard DVD. I have however been able to boot using NetInstall and do a manual installation as if I put the cd in the machine itself.
    Thank You in Advance,
    John

    Don't have any assistance with the tutorials, but you might want to check out my thread here:
    http://discussions.apple.com/thread.jspa?messageID=10592492#10592492
    Seems as though automated installs are broken in 10.6, and the 10.6.2 update that was supposed to fix it, didn't.
    Automated installs of 10.5 images work great on 10.5 server.

  • When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?

    When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
    edit  "applications/multicast/main.asc" ?
    HELP ME !!! THANKS!!!
    * File: main.asc
    * The server-side portion of the multicast sample application.
    * This app accepts publish and unpublish requests from FMLE, and republishes
    * the live stream from FMLE into a target Flash Group.
    // General Constants
    // "Constants" representing multicast event types.
    var TYPE_FUSION = 1;
    var TYPE_IP = 2;
    var TYPE_P2P = 3;
    // StreamContext Description, Constants and Functions
    * Type: StreamContext
    * This application tracks the context for live streams published to the server
    * that are being republished into a Flash Group. The StreamContext "type" used
    * for this is just an Object containing the following members:
    *   client         - The encoding/publishing client.
    *   streamName     - The source Stream name as published by the client.
    *   type           - The multicast event type.
    *   groupspec      - The groupspec identifying the Flash Group and capabilities.
    *   address        - IP multicast address (optional for pure P2P events).
    *   netConnection  - A loopback NetConnection used for the mcastNetStream.
    *   mcastNetStream - The NetStream used to republish the source Stream into
    *                    the Flash Group.
    *   netGroup       - An (optional) NetGroup handle for the target Group.
    *                    Only present for Fusion or P2P events.
    *   state          - One of the state constants defined immediately below
    *                    this comment.
    var STATE_INIT            = 0; // Starting state for a StreamContext.
    var STATE_CONNECTING      = 1; // Establishing loop-back connection.
    var STATE_CONNECTED       = 2; // Connection established.
    var STATE_PUBLISH_PENDING = 3; // Attempting to publish.
    var STATE_REPUBLISHING    = 4; // Actively republishing to multicast.
    var STATE_UNPUBLISHING    = 5; // Shutting down multicast republish.
    var STATE_UNPUBLISHED     = 6; // Unpublished successfully.
    var STATE_DISCONNECTING   = 7; // Shutting down loopback connection.
    var STATE_DISCONNECTED    = 8; // Connection shut down. Done.
    * Registers a source Stream published by the specified client, along with the
    * context for the multicast event, as a StreamContext Object.
    * @param client - The Client publishing the stream.
    * @param streamName - The source Stream name.
    * @param params - The parameters resulting from parsing the source Stream's
    *                 query string.
    * @return The new StreamContext Object for the registered Stream.
    function registerStream(client, streamName, params)
        var streamContext = { "client": client,
                              "streamName": streamName,
                              "type": params["fms.multicast.type"],
                              "groupspec": params["fms.multicast.groupspec"] };
    if (params["fms.multicast.interface"])
      streamContext["interfaceAddress"] = params["fms.multicast.interface"];
        if (params["fms.multicast.address"])
            streamContext["address"] = params["fms.multicast.address"],
        streamContext.state = STATE_INIT;
        updateStreamContextLookups(streamContext);
        trace("Registered multicast context for source stream: " + streamName);
        return streamContext;
    * Updates the indexed lookups installed for the passed StreamContext Object
    * with the application.
    * @param streamContext - The StreamContext Object to (re)index.
    function updateStreamContextLookups(streamContext)
        application.streamTable[streamContext.streamName] = streamContext;
        if (streamContext.netConnection)
            application.netConnTable[streamContext.netConnection] = streamContext;
        if (streamContext.mcastNetStream)
            application.mcastNetStreamTable[streamContext.mcastNetStream] = streamContext;
        if (streamContext.netGroup)
            application.netGroupTable[streamContext.netGroup] = streamContext;
    * Provides access to the StreamContext Object for a registered source Stream
    * by name.
    * @param streamName - A registered source Stream name.
    * @return The associated StreamContext Object; undefined if the source Stream
    *         name is not registered.
    function getStreamContextForSourceStream(streamName)
        return application.streamTable[streamName];
    * Provides access to the StreamContext Object for a given server-side
    * NetConnection hosting a multicast NetStream.
    * @param netConnection - A server-side NetConnection.
    * @return The associated StreamContext Object; undefined if the passed
    *         NetConnection is not indexed to a StreamContext.
    function getStreamContextForNetConnection(netConnection)
        return application.netConnTable[netConnection];
    * Provides access to the StreamContext Object for a given multicast NetStream.
    * @param netStream - A multicast NetStream.
    * @return The associated StreamContext Object; undefined if the passed
    *         NetStream is not indexed to a StreamContext.
    function getStreamContextForMulticastNetStream(netStream)
        return application.mcastNetStreamTable[netStream];
    * Provides access to the StreamContext Object for a given NetGroup associated
    * with a multicast NetStream.
    * @param netGroup - A NetGroup.
    * @return The associated StreamContext Object; undefined if the passed
    *         NetGroup is not indexed to a StreamContext.
    function getStreamContextForNetGroup(netGroup)
        return application.netGroupTable[netGroup];
    * Unregisters the StreamContext from the application.
    * @param streamContext - The StreamContext Object to unregister.
    function unregisterStreamContext(streamContext)
        if (streamContext.netConnection)
            delete application.netConnTable[streamContext.netConnection];
        if (streamContext.mcastNetStream)
            delete application.mcastNetStreamTable[streamContext.mcastNetStream];
        if (streamContext.netGroup)
            delete application.netGroupTable[streamContext.netGroup];
        trace("Unregistered multicast context for source stream: " +
              streamContext.streamName);
    // Application callback functions
    * Initializes global StreamContext lookup tables.
    application.onAppStart = function()
        application.streamTable = {};
        application.netConnTable = {};
        application.mcastNetStreamTable = {};
        application.netGroupTable = {};
    * Handles a publish event for the application by validating the request
    * and bridging the published stream into a target Flash Group. Invalid
    * publish requests are ignored and the publishing client's connection
    * is closed.
    * @param client - The publishing client.
    * @param stream - The published stream.
    application.onPublish = function(client, stream)
        //trace("Handling publish request for source stream: " + stream.name);
        var params = parseQueryString(stream.publishQueryString);
        if (!validateStreamParams(params))
            application.disconnect(client);
            return;
        var prevContext = getStreamContextForSourceStream(stream.name);
        if (prevContext)
            forceCloseStreamContext(prevContext);
        // Register source Stream, and kick off the async process that will
        // eventually wire-up the associated multicast NetStream.
        var streamContext = registerStream(client, stream.name, params);
        openMulticastConnection(streamContext);
    * Handles an unpublish event for the application by shutting down
    * any associated multicast NetStream.
    * @param client - The unpublishing client.
    * @param stream - The source stream being unpublished.
    application.onUnpublish = function(client, stream)
        trace("Handling unpublish request for source stream: " + stream.name);
        var streamContext = getStreamContextForSourceStream(stream.name);
        if (streamContext && (streamContext.state <= STATE_REPUBLISHING))
            destroyStreamContext(streamContext);
    // Callback functions for NetConnection and multicast NetStream/NetGroup wiring.
    * First step in setting up a republished multicast NetStream; open the loopback
    * connection it requires.
    * @param streamContext - The StreamContext Object for the publish event.
    function openMulticastConnection(streamContext)
        var nc = new NetConnection();
        nc.onStatus = netConnectionStatusHandler;
        streamContext.netConnection = nc;
        updateStreamContextLookups(streamContext);
        streamContext.state = STATE_CONNECTING;
        nc.connect(resetUriProtocol(streamContext.client.uri, "rtmfp"));
    * Status event handler for the loopback NetConnection used by the multicast
    * NetStream. Advances setup upon successful connection, or triggers or advances
    * tear-down as a result of connection loss or an unpublish and clean shutdown.
    * @param info - The status info Object.
    function netConnectionStatusHandler(info)
        var streamContext = getStreamContextForNetConnection(this);
        trace("Multicast NetConnection Status: " + info.code +
              (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."));
        if (streamContext)
            switch (info.code)
            case "NetConnection.Connect.Success":
                streamContext.state = STATE_CONNECTED;
                // If event type is Fusion or P2p, wire up a NetGroup for neighbor
                // bootstrapping and maintenance ahead of (re)publishing the stream.
                var type = streamContext.type;
                if (type == TYPE_FUSION || type == TYPE_P2P)
                    initNetGroup(streamContext);
                else
                    initMulticastNetStream(streamContext);
                break;
            case "NetConnection.Connect.Failed":
            case "NetConnection.Connect.Rejected":
            case "NetConnection.Connect.AppShutdown":
                trace("MULTICAST PUBLISH ERROR: Failed to establish server-side NetConnection for use by multicast NetStream. " +
                      "Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
                      streamContext.streamName);
                streamContext.state = STATE_DISCONNECTED;
                destroyStreamContext(streamContext);
                break;
            case "NetConnection.Connect.Closed":
                if (streamContext.state < STATE_DISCONNECTING)
                    trace("MULTICAST PUBLISH ERROR: Unexpected server-side NetConnection close. " +
                         "Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
                         streamContext.streamName);
                streamContext.state = STATE_DISCONNECTED;
                destroyStreamContext(streamContext);
                break;
            default:
                // Ignore.
    * Initializes the multicast NetGroup following a successful connection of its
    * underlying loopback NetConnection. This hook is optional and only runs for
    * event types of Fusion and pure P2P.
    * @param streamContext - The StreamContext Object for the multicast publish.
    function initNetGroup(streamContext)
        var ng = null;
        try
            ng = new NetGroup(streamContext.netConnection, streamContext.groupspec);
        catch (e)
            trace("MULTICAST PUBLISH ERROR: Failed to construct NetGroup. Error: "
                  + e.name + (e.message ? " " + e.message : "") +
                  ", Source stream: " + streamContext.streamName);
            destroyStreamContext(streamContext);
            return;
        ng.onStatus = netGroupStatusHandler;
        streamContext.netGroup = ng;
        updateStreamContextLookups(streamContext);
    * Status event handler for the multicast NetGroup. Advances to initializing the
    * multicast NetStream upon successful NetGroup connect. Otherwise, triggers
    * shut down.
    * @param info - The status info Object.
    function netGroupStatusHandler(info)
        var streamContext = getStreamContextForNetGroup(this);
        trace("Multicast NetGroup Status: " + info.code +
              (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
        if (streamContext)
            switch (info.code)
            case "NetGroup.Connect.Success":
                initMulticastNetStream(streamContext);
                break;
            case "NetGroup.Connect.Failed":
            case "NetGroup.Connect.Rejected":
                trace("MULTICAST PUBLISH ERROR: Failed to connect multicast NetGroup. " +
                      "Status code: " + info.code + ", description: " + info.description +
                      ", Source stream: " + streamContext.streamName);
                destroyStreamContext(streamContext);
                break;
            case "NetGroup.MulticastStream.UnpublishNotify":
                // At this point, multicast publishers will be notified;
                // continue shut down.
                destroyStreamContext(streamContext);
                break;
            default:
                // Ignore.
    * Initializes the multicast NetStream following a successful connection of its
    * underlying loopback NetConnection.
    * @param streamContext - The StreamContext Object for the multicast publish.
    function initMulticastNetStream(streamContext)
        var ns = null;
        try
            ns = new NetStream(streamContext.netConnection, streamContext.groupspec);
        catch (e)
            trace("MULTICAST PUBLISH ERROR: Failed to construct multicast NetStream. Error: " +
                  e.name + (e.message ? " " + e.message : "") +
                  ", Source stream: " + streamContext.streamName);
            destroyStreamContext(streamContext);
            return;
        var type = streamContext.type;
        if (type == TYPE_FUSION || type == TYPE_IP)
      var iAddr = (streamContext.interfaceAddress) ? streamContext.interfaceAddress : null;
            try
                trace("Multicast NetStream will publish to IP address: " + streamContext.address +
          " on interface address: " + ((iAddr) ? iAddr : "default") +
                      ", Source stream: " + streamContext.streamName);
                ns.setIPMulticastPublishAddress(streamContext.address, iAddr);
            catch (e2)
                trace("MULTICAST PUBLISH ERROR: Failed to assign IP multicast address and port for publishing. Address: "
                      + streamContext.address + " on interface address: " + ((iAddr) ? iAddr : "default") +
          ", Source stream: " + streamContext.streamName);
                destroyStreamContext(streamContext);
                return;
        ns.onStatus = netStreamStatusHandler;
        streamContext.mcastNetStream = ns;
        updateStreamContextLookups(streamContext);
        streamContext.state = STATE_PUBLISH_PENDING;
    * Status event handler for the multicast NetStream. Advances state upon successful
    * connect and publish, or upon successful unpublish. Triggers tear-down if we fail
    * to attach to a source Stream to republish.
    * @param info - The status info Object.
    function netStreamStatusHandler(info)
        var streamContext = getStreamContextForMulticastNetStream(this);
        trace("Multicast NetStream Status: " + info.code +
              (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
        if (streamContext)
            switch (info.code)
            case "NetStream.Connect.Success":
                if (!this.attach(Stream.get(streamContext.streamName)))
                    trace("MULTICAST PUBLISH ERROR: Failed to attach multicast NetStream to source. Source stream: " +
                          streamContext.streamName);
                    destroyStreamContext(streamContext);
        //var stream;
                //stream = Stream.get("liveStream");
                    //return;
                }else{
                this.publish(streamContext.streamName, "live");
                break;
            case "NetStream.Publish.Start":
                streamContext.state = STATE_REPUBLISHING;
                break;
            case "NetStream.Unpublish.Success":
                streamContext.state = STATE_UNPUBLISHED;
                // Wait for unpublish notify event if the context has a NetGroup;
                // otherwise continue shut down now.
                if (!streamContext.netGroup)
                    destroyStreamContext(streamContext);
                    break;
            default:
                // Ignore.
    * The common tear-down hook. Other functions that manage or shut down
    * the StreamContext Object delegate to this function upon detecting a fatal
    * error or during shut down.
    * @param streamContext - The StreamContext Object for the source Stream and
    *                        (potentially wired-up) multicast NetStream.
    function destroyStreamContext(streamContext)
        // Unregister by Stream name immediately; lookups by NetConnection, NetGroup
        // and multicast NetStream remain in place until tear-down is complete.
        delete application.streamTable[streamContext.streamName];
        switch (streamContext.state)
        case STATE_REPUBLISHING:
            streamContext.mcastNetStream.attach(false);
            streamContext.mcastNetStream.publish(false);
            streamContext.state = STATE_UNPUBLISHING;
            return;
        case STATE_CONNECTING:
        case STATE_CONNECTED:
        case STATE_PUBLISH_PENDING:
        case STATE_UNPUBLISHED:
            // Delete status handler callbacks and cleanup in case we arrived here
            // as a result of a force close.
            if (streamContext.netGroup)
                delete streamContext.netGroup.onStatus;
            if (streamContext.mcastNetStream)
                streamContext.mcastNetStream.attach(false);
                delete streamContext.mcastNetStream.onStatus;
            streamContext.netConnection.close();
            streamContext.state = STATE_DISCONNECTING;
            return;
        default:
            // Fall-through.
        // At this point, we either never got to the republishing state or we've
        // proceeded through the clean shut down steps above. Everything for this
        // StreamContext can go away.
        unregisterStreamContext(streamContext);
    * Utility function used to force close a StreamContext in the event that we
    * start handling a republish of a Source stream before the context for its
    * prior incarnation has been torn down.
    * @param streamContext - The StreamContext Object for the source Stream.
    function forceCloseStreamContext(streamContext)
        trace("Force closing previous multicast context for source stream: " + stream.name);
        prevContext.state = STATE_UNPUBLISHED;
        destroyStreamContext(prevContext);
    // Client callback functions
    * A no-op. Answers the RPC in the fashion expected by encoders, but the real
    * work happens in application.onPublish.
    * @param streamName - The name of the stream being published.
    Client.prototype.FCPublish = function(streamName)
        this.call("onFCPublish",
                  null,
                  {code:"NetStream.Publish.Start", description:streamName});
    * A no-op. Answers the RPC in the fashion expected by encoders, but the real
    * work happens in application.onUnpublish.
    * @param streamName - The name of the stream being unpublished.
    Client.prototype.FCUnpublish = function(streamName)
        this.call("onFCUnpublish",
                  null,
                  {code:"NetStream.Unpublish.Success", description:streamName});
    * If the client invoker's ip matches what was captured for a currently publishing
    * stream, assume it's the same client and reset the stream. Otherwise, ignore.
    * @param streamName - The name of the stream being released.
    Client.prototype.releaseStream = function(streamName)
        var streamContext = getStreamContextForSourceStream(streamName);
        if (streamContext &&
            (streamContext.client.ip == this.ip) &&
            (streamContext.state <= STATE_REPUBLISHING))
            // Only tear-down an orphaned stream if it's not
            // already shutting down (see state check above).
            destroyStreamContext(streamContext);
    // Helper functions
    * Validates that a newly published stream has correct metadata (e.g. query
    * string parameters) to republish into a Flash Group. This function also
    * writes a message to the application log for any validation failures.
    * @param params - The quiery string parameters for the source Stream.
    * @return true if valid; otherwise false.
    function validateStreamParams(params)
        var empty = true;
        for (var param in params)
           empty = false;
           break;
        if (empty)
            trace("MULTICAST PUBLISH ERROR: Stream query string is empty.");
            return false;
        if (!params["fms.multicast.type"])
    trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.type'.");
            return false;
        var type = params["fms.multicast.type"];
        if (type != 1 && type != 2 && type != 3)
            trace("MULTICAST PUBLISH ERROR: 'fms.multicast.type' has invalid value: " + type);
            return false;
        if (!params["fms.multicast.groupspec"])
            trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.groupspec'.");
            return false;
        // Fusion and IP require an address:port.
        if ((type == 1 || type == 2) &&
            !params["fms.multicast.address"])
            trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.address'.");
            return false;
        // No obvious validation issues.
        return true;
    * Parses the supplied query string, and if valid, returns an Object populated
    * with the name-value pairs contained in the query string. The simple processing
    * here does not preserve multiple name-value pairings having the same name; the
    * last value seen wins. Parameters with no value are mapped to "" (empty String)
    * in the returned Object.
    * @param queryString - A query string portion of a URI, not including the leading
    *                     '?' character.
    * @return An Object containing a key-value mapping for each name-value parameter
    *         defined in the query string; Object is empty if the query string is
    *         invalid.
    function parseQueryString(queryString)
        var result = {};
        var decoded = "";
        try
            decoded = decodeURIComponent(queryString);
        catch (e) // Invalid URI component; return empty result.
            return result;
        if (decoded.length)
            var params = decoded.split('&');
            for (var i in params)
                var pair = params[i];
         var sepIndex = pair.indexOf('=');
                if (sepIndex != -1)
                    var name = pair.substr(0, sepIndex);
                    result[name] = pair.substr(sepIndex + 1);
                else
                    result[pair] = "";
        return result;
    * Utility function used to swap out the protocol (scheme) portion
    * of a given URI with an alternate.
    * @param uri - The full URI.
    * @param desiredProtocol - The replacement protocol.
    * @return The URI with its protocol replaced.
    function resetUriProtocol(uri, desiredProtocol)
        var sepIndex = uri.indexOf("://");
        return desiredProtocol + uri.substr(sepIndex);

    HELP ME !!! THANKS!!!

  • Need Guidance in Building an app With Sh Script Commands

    Let me start off by saying this will be long:
    I've been tasked with creating an application at work that provides a GUI interface to the user while it runs a shell script in the background. I have very limited experience with Xcode and the developer tools so please explain in simplest terms possible
    On to the application. It will be broken down into five different GUI windows. I know I need to use IB, but thats about as far as I know how to pull this off.
    1. Intro screen that gives a description of the program and a start button.
    2. Asks the user to specify the location where they want to save their image and provide a name for it,then a next button. (I would like to do a drag and drop field if that is possible where they could drag the folder and the path would be read and have whatever name they type automatically append .dmg onto the end)
    3. This window asks them to drag and drop (if possible) the windows partition into the window, and then click next.
    4. A progress bar
    5. Successfully finished.
    There is an additional unix file that script calls as well
    The script which needs to be modified to work for this program is:
    #!/bin/sh
    echo ""
    echo ""
    echo ""
    echo "This script will create a sparsebundle for Windows imaging."
    echo ""
    echo "Please make sure to have an external Firewire drive to where your image will be saved connected to your machine"
    echo ""
    #echo "Type in how large you want your sparsebundle to be (ie 50g for 50 Gigabytes):"
    #read "hd_size"
    echo "MAKE SURE TO PRESS ENTER AFTER EACH STEP!!!"
    echo "MAKE SURE TO RUN AS ROOT!!!"
    echo ""
    echo "Drag the icon of the folder or device you want to save your Windows image INTO this window (Because of the large size of the file that will be created, it is recommended to use a firewire device and/or folder.):"
    read "target_disk"
    echo "Type in the name you want your final image to be called (include .dmg to the end of the name. i.e. LIBRN310_SPR09.dmg)"
    read "Image_Name"
    echo "Step 1: sparsebundle creation"
    echo "Please wait while your sparsebundle is created"
    target_folder="$target_disk/Windows_ntfsclone_image"
    if [ -e $target_folder ]; then
    echo "A folder with the name 'Windows_ntfsclone_image' already exists. Please delete or rename this folder and launch this script again."
    exit 0;
    fi
    /bin/mkdir $target_disk/Windows_ntfsclone_image
    hd_size="`diskutil list | grep Vista | awk '{print int(1+ $4)}'`g"
    /usr/bin/hdiutil create -type SPARSEBUNDLE -layout NONE -size $hd_size $target_folder/windows
    echo "Your sparsebundle has been created here: $target_folder/windows.sparsebundle"
    echo ""
    echo "Your sparsebundle is being attached to the system as a device..."
    sparsebundle_Device="`/usr/bin/hdiutil attach -nomount $target_folder/windows.sparsebundle`"
    echo ""
    echo "Your sparsebundle has been attached."
    echo ""
    echo "Step 2: Cloning your Windows NTFS volume to the sparsebundle."
    echo "Cloning your Windows volume to the sparsebundle..."
    Vista_Volume="/Volumes/Vista"
    Vista_Device="/dev/`/usr/sbin/diskutil list | grep Vista | awk '{print $6}'`"
    /usr/sbin/diskutil unmount $Vista_Device
    $HOME/Desktop/Windows_Imaging_Tools/ntfsclone -f -f -O $sparsebundle_Device $Vista_Device
    echo ""
    echo "Windows has cloned to your sparsebundle."
    echo ""
    echo "Detaching sparsebundle..."
    /usr/sbin/diskutil eject $sparsebundle_Device
    echo "sparsebundle detatched"
    echo ""
    echo "Step 3: Converting the sparsebundle to scannable UDIF image for Multicast or Unicast ASR."
    echo "Converting Windows sparsebundle to compressed Apple UDIF image."
    sparsebundle_File="$target_folder/windows.sparsebundle"
    /bin/mkdir $target_folder/Windows_Final_Image
    Windows_Image_Folder="$target_folder/Windows_Final_Image"
    /usr/bin/hdiutil convert $sparsebundle_File -format UDCO -o $Windows_Image_Folder/$Image_Name
    echo ""
    echo "Your sparsebundle has been sucessfully converted."
    echo "It is located at $Windows_Image_Folder/$Image_Name"
    echo ""
    echo "Step 4: Scanning your $Image_Name image for restore..."
    /usr/sbin/asr imagescan -source $Windows_Image_Folder/$Image_Name
    echo ""
    echo "Your $Image_Name has finished scanning. You can now use the image located at $Windows_Image_Folder/$Image_Name for Multicast ASR or Unicast ASR."
    exit 0;

    Couple of options:
    - Pashua: http://www.bluem.net/en/mac/pashua
    - Platypus: http://www.sveinbjorn.org/platypus

  • How to confirm the Network latency in welclogic server

    Hi,
    Please help me on below query.
    If a production server is having a network bottle neck or network throttling. How can i confirm? and What would you do?
    Request you to guide me on this.
    Thanks,
    Raj

    Hi,
    N/W Issues
    If your WebLogic Servers are part of Cluster and if you see any Multicast related errors or warnings like ... ManagedServer is getting Kicked of of Cluster and then again Joining after some time...or if you see any Multicast Lost Messages more than 2-3 times...it means there may be some N/W Issues ...to test this you can use MulticastTest ot MulticastMonitor Utilities.... Like this u will get some idea abt n/w issues.
    N/W latency
    WebLogic Servers logs/Access Logs ... will never be useful to identify the N/W Latency.
    Thanks
    Jay SenSharma

  • Clustering problems and load balancing question

              I am using Weblogic 6.1. My Windows NT environment consists of 10 web client-simulator
              machines, 2 App. Server machines and one database server machine. I have defined
              one cluster on each app. server. Each cluster is running 3 Weblogic instances, or
              so it should be when I fix my problems!
              My questions/problems are the following:
              1. Can I use a software dispatcher to perform workload balancing between the 2 weblogic
              clusters? That is, the client-simulator machines send the requests to the software
              dispatcher which performs workload balancing between the 2 Weblogic clusters. The
              clusters perform round-robin amongst all instances. Note that the documentation only
              talks about Hardware Balancing.
              2. I am having problems with my multicast IP addresses. For instance, on one App.
              Server machine, I am using the multicast IP address: 239.0.0.1 for MyCluster. When
              I start the Admin Server, I get a JDBC error: "... multicast socket error: Request
              Time Out". I have used the utils.MulticastTest utility which shows the packets not
              being received:
              I (S1) sent message num 1
              I (S1) sent message num 2
              I (S1) sent message num 3
              I (S1) sent message num 4
              What am I doing wrong?
              3. Re. the cluster configuration:
              NOTE: I have executed my workload using 2 independent App. Server machines with a
              software dispatcher - no clustering. Each App. Server used a jdbc connection pool
              of 84 database connections. The db connections happened to become my bottleneck.
              When I tried to increase the number of connections in the jdbc pool, throughput decreased
              dramatically. Thus, I decided to add a cluster of Weblogic instances to each one
              of my 8 x 900Mhz machines in order to scale up. Unfortunatly, adding clusters have
              not been that simple a task - probably because I am totally new to the Web Application
              Server world!
              Here is what I've got so far:
              I have obtained 3 static IP addresses for the 3 instances of Weblogic instances that
              I wish to run within the cluster. All servers in the cluster use port number 80.
              There is a corresponding DNS entry for each IP address. My base assumption is that
              one of these instances will double up as the Administration Server... Is it true,
              or do I need to define a separate Admin server if I wish to run 3 Weblogic instances
              (each with a connection pool of 84 database connections for a total of 252 database
              connections)?
              Do I need to re-deploy my applications for the cluster? And if so, would this explain
              why I am having problem starting my Admin Server?
              I think this is it for now. Any help will be greatly appreciated!
              Thanks in advance,
              Guylaine.
              

              Guylaine Cantin wrote:
              > I am using Weblogic 6.1. My Windows NT environment consists of 10 web client-simulator
              > machines, 2 App. Server machines and one database server machine. I have defined
              > one cluster on each app. server. Each cluster is running 3 Weblogic instances, or
              > so it should be when I fix my problems!
              >
              > My questions/problems are the following:
              >
              > 1. Can I use a software dispatcher to perform workload balancing between the 2 weblogic
              > clusters? That is, the client-simulator machines send the requests to the software
              > dispatcher which performs workload balancing between the 2 Weblogic clusters. The
              > clusters perform round-robin amongst all instances. Note that the documentation only
              > talks about Hardware Balancing.
              >
              We also support software load balancers (for e.g. resonate)
              The software dispatcher should be intelligent enough to decode the
              cookie and route the request to the appropriate servers. This is
              necessary to maintain sticky load balancing.
              > 2. I am having problems with my multicast IP addresses. For instance, on one App.
              > Server machine, I am using the multicast IP address: 239.0.0.1 for MyCluster. When
              > I start the Admin Server, I get a JDBC error: "... multicast socket error: Request
              > Time Out". I have used the utils.MulticastTest utility which shows the packets not
              > being received:
              >
              > I (S1) sent message num 1
              > I (S1) sent message num 2
              > I (S1) sent message num 3
              > I (S1) sent message num 4
              > ...
              >
              > What am I doing wrong?
              >
              You should run the above utility from multiple windows and see if each
              of them being recognized or not.
              i.e. java utils.MulticastTest -N S1 -A 239.0.0.1
              java utils.MulticastTest -N S1 -A 239.0.0.1
              > 3. Re. the cluster configuration:
              >
              > NOTE: I have executed my workload using 2 independent App. Server machines with a
              > software dispatcher - no clustering. Each App. Server used a jdbc connection pool
              > of 84 database connections. The db connections happened to become my bottleneck.
              > When I tried to increase the number of connections in the jdbc pool, throughput decreased
              > dramatically. Thus, I decided to add a cluster of Weblogic instances to each one
              > of my 8 x 900Mhz machines in order to scale up. Unfortunatly, adding clusters have
              > not been that simple a task - probably because I am totally new to the Web Application
              > Server world!
              >
              You have to stress test your application several times and set
              maxCapacity of the conn pool accordingly.
              > Here is what I've got so far:
              >
              > I have obtained 3 static IP addresses for the 3 instances of Weblogic instances that
              > I wish to run within the cluster. All servers in the cluster use port number 80.
              > There is a corresponding DNS entry for each IP address. My base assumption is that
              > one of these instances will double up as the Administration Server... Is it true,
              > or do I need to define a separate Admin server if I wish to run 3 Weblogic instances
              > (each with a connection pool of 84 database connections for a total of 252 database
              > connections)?
              BEA recommends to use Admin server for administrative tasks only
              like configuring new deployments, jdbc conn pools, adding users etc..
              It's not a good idea to have admin server part of cluster.
              >
              > Do I need to re-deploy my applications for the cluster? And if so, would this explain
              > why I am having problem starting my Admin Server?
              >
              You have to target all your apps to the Cluster.
              > I think this is it for now. Any help will be greatly appreciated!
              >
              > Thanks in advance,
              >
              > Guylaine.
              >
              

  • Has anyone ever deployed EJBs in a 4.5.1 cluster on AIX?

    Interesting conundrum.
              We've done our development on NT w/JDK 1.2.2 and Weblogic 4.5.1, but are
              looking to deploy on AIX 4.3.3. Weblogic 4.5.1 is only supported on 1.1.6,
              though. Attempting to deploy in the unsupported AIX 4.3.3/Weblogic
              4.5.1/JDK 1.2.2 configuration met with multicast IO errors (message size too
              large). Unless this issue can be resolved, it looks like our 2 solutions
              are:
              1.) build under JDK 1.1.6 and deploy on AIX under same
              2.) move to the supported Weblogic 5.1/JDK 1.2.2 configuration
              Has anyone actually followed either of these paths to success? Or is there
              a different configuration that might yield positive results? Thanks in
              advance.
              Brian Dainton
              Pervado Systems, Inc.
              www.pervado.com
              

    I have done this without any problems using:
              AIX 4.3.3
              JDK 1.1.8
              WLS 4.5.1 SP7
              Robert
              Brian Dainton wrote:
              > Interesting conundrum.
              >
              > We've done our development on NT w/JDK 1.2.2 and Weblogic 4.5.1, but are
              > looking to deploy on AIX 4.3.3. Weblogic 4.5.1 is only supported on 1.1.6,
              > though. Attempting to deploy in the unsupported AIX 4.3.3/Weblogic
              > 4.5.1/JDK 1.2.2 configuration met with multicast IO errors (message size too
              > large). Unless this issue can be resolved, it looks like our 2 solutions
              > are:
              > 1.) build under JDK 1.1.6 and deploy on AIX under same
              > 2.) move to the supported Weblogic 5.1/JDK 1.2.2 configuration
              > Has anyone actually followed either of these paths to success? Or is there
              > a different configuration that might yield positive results? Thanks in
              > advance.
              >
              > Brian Dainton
              > Pervado Systems, Inc.
              > www.pervado.com
              

  • Modifying default boot image

    I need to edit default x86 boot image and add one address to host file. 
    In default directory: \Program Files\Microsoft Configuration Manager\OSD\boot\i386 I see two wim files. Boot.PS100002.wim and boot.wim. What is the one that is used with PXE?

    This was a test. I had a problem with multicast (giving error 0x80091007 = hash error) when trying multicast in different vlan than
    where configmgr server resides. Multicast was working fine in same vlan as confimgr server.
    In problematic vlan only fqdn resolves to configmgr server, not short name. When I add ConfigMgr server  to WinPE host file, then multicast
    starts to work.

  • Cross Subnet Netboot Issues

    Hello,
    I've been working to set up a netboot and Open Directory server in school district. We have the network segmented into VLANs by campus with different subnets for each. The changes have been made to the router to allow bootp/bsdp (IPHelper address set and relay agent on) to communicate across subnets, but I am still unable to netboot/netinstall across subnets.
    Watching the logs on the server when I attempt to, it seems to be communicating partially as seen here:
    Jul 19 12:48:37 axposeidon bootpd[1822]: BSDP DISCOVER [en1] 1,0:16:cb:8e:50:a6 NetBoot035 arch=i386 sysid=MacBookPro1,1
    Jul 19 12:48:37 axposeidon bootpd[1822]: BSDP OFFER sent [1,0:16:cb:8e:50:a6] pktsize 369
    Jul 19 12:48:37 axposeidon bootpd[1822]: BSDP DISCOVER [en1] 1,0:16:cb:8e:50:a6 NetBoot035 arch=i386 sysid=MacBookPro1,1
    Jul 19 12:48:37 axposeidon bootpd[1822]: BSDP OFFER sent [1,0:16:cb:8e:50:a6] pktsize 369
    Unfortunately it fails to actually boot the machine. Im not positive what's going on but it seems like its sending a response back to the netbooting machine but the machine is not getting it and its resending?
    The OS X Server is an Intel Xserve running 10.4.10 (though we've been experiencing this issue since as far back as I've been trying with 10.4.8), the image was created in 10.4.8, and works on the local subnet (including multicast ASR). The booting machine is, as noted above, a Macbook Pro.
    As a side note, when booted into the OS, the machines can see the server in the Startup Disk preference pane.
    Any suggestions or ideas? Let me know if there's more information I can give that will help.

    In our district there are multiple public and private subnets. The public and private combination I have the server on currently just happen to be on this physical network, so they are sharing the same router.
    I think Im getting a little lost on what you're asking so I'll explain our network structure a little further. The district runs a VLANed network with a different public and private subnet for each campus (the private subnets function mostly as IP address overflow when the public subnet IP limit is exceeded). The network is predominantly PC based and implements active directory servers. The Xserve simply operates as a standalone server currently just handling some web serving tasks and a netboot server.
    The issue, regardless of the public and private subnet interfaces on the server, is that I am unable to get anything to boot from another subnet than the one the xserve is running on. If I run it on the public interface, local machines boot perfectly, but I a log like the one above if I try and boot from another campus (ie another VLAN or subnet). To test it locally I've been running it on the private subnet interface (on the same physical network segment) to boot machines on the local public subnet (which fails with the above log).
    According to Apple and other sources, all that should need to be configured is our CISCO routers need to be set to pass BOOTP information across VLANs/Subnets, which we have configured (using the IP helper-address and DHCP relay agent), but as stated, the connection is still not succeeding.
    I'm checking with our network engineer on a few specifics on how the routers are configured to make sure they are set properly for the forwarding, but he's not available at the moment.
    I applogize if this doesnt address the information you're needing, but please let me know if it does not, and I will try my best to get you the needed information.

  • System Deployment with 10.5 Server System Image Utility

    I am trying to image a classroom lab of iMacs and I'm getting nowhere mighty fast.
    I have created the 10.5 client image on a test machine and had it placed on test for students and faculty. After the image was tested for stability I was ready to create the image for deployment. In the past I had used Bombich's NetRestore to deploy images but have found it to be incompatible with 10.5, as it will not resolve the Leopard ByHost file problem correctly. While I can create a Net Install image using the 10.5 System Image Utility I can't determine how to deploy it with multicast ASR. As least from what things appear, the Net Install will run as a unicast and if I try to run it on a number of machines it will bog down the network so severely that it will be impossible to deploy the image - at least this is my understanding.
    The last time I had assistance from our regional Apple System Engineer he informed me of an application call Proton Pack, but I can neither get the application to recognize the image nor do I understand how the main issue, the ByHost file, will be corrected without any sort of post-install action taking place since as far as I know mASR on the client only "grabs" the image and doesn't to anything more. I had emailed our System Engineer twice and have yet to hear from him. I can't let this go much longer.
    The frustration is mounting as those above me want these machines deployed and there always seems to be problems with this. There are great and robust solutions in the Windows world, how come there isn't anything as simple and elegant as the likes of Ghost? At this point I'm about at my wit's end and find myself cursing the very platform that I had been championing for more than 24 years.

    Jeff Kelleher wrote:
    Believe me, I share some of your frustrations. But ranting here after folks, meaning to be helpful by offering suggestions, maybe isn;t what this forum is best suited for.
    I'm not ranting after the folks here, I am attempting to make a point and my point is that the tools available are inadequate for the purpose. Do you really think a company should hinge a deployment strategy on tools either developed as "shareware/freeware" or a feature set that claims it works but doesn't?
    Jeff Kelleher wrote:
    Again, let me state that I've been frustrated by OS X Server. I applaud you for speaking directly to Apple for solutions. Ranting to people who try to offer solutions won't help.
    Sorry to vent, but I have just grown tired of the excuses. Even my sales rep is quick to try to point the finger elsewhere. I have been exposed to for the shortcoming of a consumer platform that is suppose to be targeted toward K-12 and businesses. If Apple is serious in being in the enterprise markets they need to have a decent, reliable tool, be it something from them or another vendor. Ghost for the Mac is a no-brainer, as I'm sure I'm not the only one who has wasted time with the pitfalls of Mac deployment. I know I can't be the only one who is frustrated by the less than optimal methodology to rolling out Macs in this manner.
    Jeff Kelleher wrote:
    Believe me, I share some of your frustrations. But ranting here after folks, meaning to be helpful by offering suggestions, maybe isn;t what this forum is best suited for.
    I'm not ranting after the folks here, I am attempting to make a point. My point is that the tools given aren't worth beans. I had been a champion of Apple since 1980 and a certified tech since 1981 (starting with the Apple II platform) and while many things have improved dramatically through the years this is one area that has lagged behind for some time.
    Jeff Kelleher wrote:
    Finally, deploying 30 Macs is, like it or not, a small venture. 100's or 1000's is a lot.
    Sure, 30 may be small, but how likely am I to deploy a district's worth of these machines if the tools available make deploying Wondows machines such a breeze by comparison? I think somebody's cutting their own throat and it's not Mr. Gates.
    foilpan wrote:
    it's possible that your energy could be better spent solving the issue and moving on rather than blaming apple for not doing what you want out of the box. if your job is to deploy 30 macs, just do it however possible and spend time later to refine the process. you can easily finish that job in a day (or way less) with proper prep.
    This is a reoccurring scenario with Mac deployments which is getting old and tired. I'm up to the point to let these machines sit in the boxes since my time could be better used to support PCs.
    Sadly it seems most people are missing the point that the tools that are suppose to make this work, don't. If you have the patience to work around these shortcoming, that's good. If you have the knowledge of being able to script your way around the areas where the tools promise something but don't carry through, you score more points. I, for one, don't have the luxury of time on my side, being dealt a multitude of district responsibilities that include areas besides PC and Mac support.
    foilpan wrote:
    another option is to hire apple or an outside consultant who may be able to help if you don't have the scripting experience in house to do what you need.
    That's a great idea. Unfortunately with the state of school budgets it's quite unlikely this will happen in the near future.

  • Apple Training for Image Deployment

    Has anyone here attended one of the Apple Training seminars on Mac OS X Deployment v10.4 (listed as MacOS 310 on the training units site)? I'm trying to find out if the training covers multicast ASR.

    Thanks. You were right, and it was a great class.

  • Sp5 Cluster issues

    Has anyone had problems with Clustered managed servers in Weblogic Sp5.
    Reason I ask is that we have been having problems like Multicast outOfmemory errors & Cluster members failing one after other for no reason.
    If aware of any such issues, please let me know.
    Thx
    Anil

    If you have memory issues starting up managed servers it might be that you have not allocated enough memory to the servers. You can increase the memory setting on you admin console or alternatively it might be that you need to remove old log files.

Maybe you are looking for

  • I Mac 10.6.8 Start updating and update wont quit. Runs all night.

    I am using an iMac, version 10.6.8. I currently have Mozilla Firefox version 5. I have tried, per your notice, to update several times. Each time, the updating begins and doesn't stop. The last time, I started the process and let it run over night. T

  • A simple way to password protect my personal website?

    I have an online photo album, and I don't necessarily want everyone to have access to my baby pics and me running around in my underwear when I was seven years old, so I want to password-protect the site. I have a good basic knowledge of building a s

  • Product Import Never Notifies When Finished and Successful

    For over a year now it seems BC never notifies when a product import has successfully completed, if you are importing more than a couple hundred records. This happens whether you use IE, Firefox, or Chrome in Windows, and it happens in the many diffe

  • HP assist won't install updates

    Hi My HP assist is showing that I need to update a few things. I click updates and it goes through all the processes, and then downloads the update. It then moves onto the installing, but after  a few minutes finishes, but there is a cross by the box

  • Regarding Tcode VA01

    Hi,      I have a requirement in VA01 Tcode. I enter a sold-to-party value if it is blocked means knkk-crblb value is X it is giving message" Order receipt/delivery not possible, credit customer blocked" , instead of this message i have to display a