‏הצגת רשומות עם תוויות error. הצג את כל הרשומות
‏הצגת רשומות עם תוויות error. הצג את כל הרשומות

יום שלישי, 19 בנובמבר 2013

You get the error "squid Unable to determine IP address from host name

Synopsis
You get the error "squid Unable to determine IP address from host name for XXXXXX" in your web browser when trying to access a site
Article
This usually occurs if you are attempting to access an internal site, such as http://intranet If fo.r any reason squid is unable to resolve "intranet" to an IP address using the name servers provided it will display this error message.
To fix this, you should add an entry to the /etc/hosts file on your CensorNet server. To do this :-
1. Log in as root
2. Type:
nano /etc/hosts
3. On a new line, add:-
10.0.0.25    intranet
(replace with the correct hostname and IP)
4. Press CTRL+X then press Y followed by enter.
5. Restart squid
/etc/init.d/squid restart
Try the web site again and the problem should be solved.

Link:

יום ראשון, 12 במאי 2013

Failure to install VMware Tools: Cannot find the answer BINDIR in the installer database (1013159)

Details

If a VMware Tools installation is stopped before it can set the BINDIR (which occurs after the first prompted question), the installer is stopped prematurely and displays the following message:

A previous installation of VMware Tools has been detected.

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
 
If you select yes, the following error message appears:

Error: Unable to find the binary installation directory (answer BINDIR)
in the installer database file "/etc/vmware-tools/locations".

Uninstall failed. Please correct the failure and re run the install.

Execution aborted.

Solution

To solve this issue, remove the /etc/vmware-tools/locations file and reinstall VMware Tools.


Link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013159

יום רביעי, 16 בינואר 2013

Creating or updating a host profile fails with the error: Socket error: [Errno 97] Address family not supported by protocol

Resolution

VMware is aware of this issue.

To workaround this issue, enable the Security Profile in the CIM server.
To enable the Security Profile in the CIM server:
  1. Log in to vCenter Server as an administrator from the vSphere Client.
  2. Click the ESX host in the inventory.
  3. Click the Configuration tab.
  4. Click the Security Profile link.
  5. Click Properties.
  6. Click CIM Server > Options.
  7. Select Start and Stop with host.
  8. Click Start > OK.

יום ראשון, 8 במאי 2011

error E00084F4 V-79-57344-34036

Backup fails with error E00084F4 (V-79-57344-34036).

Error:
A job failed with systems error e00084f4 unknown error (V-79-57344-34036)
Problem description:
There have been multiple instances in which a setting called the RetryBusyCount setting is set too low and this leads to the failure of the backup jobs.  See below for instructions in order to make the registry change on the backup server.  The original setting calls for a value set at 75 decimal,  but it is recommended to change it to 100 decimal or 64 hex,  as is needed in the registry entry.
NOTE:  Please back up the current registry before making this change to preserve the original version. Be careful when making any registry changes as this can cause serious problems.
If the backup jobs continue to fail, then it is recommended to set this value higher,   It is feasible to have this configuration setting set as high as 250, until the issue is resolved.  If issue persists at max value of 250,  then further troubleshooting steps would be in order to determine the source,  causing the failure. Your registry entry would be under the LTO-4 and not the LTO-3 as shown below.
Solution:  To resolve the media write errors, the following steps were taken to modify the registry in Windows on the media server.
1)  Launch regedit by click start, run and type regedit, click ok
2) Browse to  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\[device identifier name for the tape LTO-3 tape device]\[numeric device instance id for the LTO-3 tape device]\Device Parameters\
3) Add a key named Storport under Device Parameters (if one does not already exist).
4) Add a key name called BusyRetryCount. The key type is REG_DWORD, and the value should be set to 4b hex (75 decimal).
5) Close regedit
6) Reboot the server
Should do the trick. Worked perfectly when we experienced the issue.
Source: Symantec