apt-get update not working

I'm trying to install awn and when I do the sudo apt-get update, it spits out this..

Could not get lock /var/lib/apt/lists/lock - open (11 Resource temporarily unavailable)
Unable to lock the list directory

This can happen when open synaptic. If not can try using this command.

sudo aptitude update

And if you still get the same error message, run below command.
ps -A

and then run

sudo kill -9 with apt and/or apt get ID

We can't run apt and apt-get at the same time, or at the same time as dpkg, Synaptic, Adept, or any other number of package managers. To prevent themselves from getting messed up, they each create a lock file. While the lock file for the package system (dpkg is the root) is in place, nobody can access it until the lock is released.

If you're getting the same exact error, you can always just blow away the lock file if you're REALLY sure you don't have two running.

sudo rm /var/lib/apt/lists/lock

Read More

sudo:timestamp too far in the future

make sure it's set to correct year.
If it's not working then use this command
sudo -K
and try

Read More

Troubleshooting the Microsoft Exchange Transport Service When It Fails to Start on an Exchange 2007 Hub Transport Server with Event ID 1032 or 1036

Event ID: 1032 Socket Access Denied. Binding: 0.0.0.0:25.
Event ID: 1036 Failed to open one or more bindings. The service will be stopped.

This issue occurs when the Internet Information Services (IIS) Simple Mail Transfer Protocol (SMTP) service has been installed on the server and is running.

To resolve the problem, remove the SMTP service.


On Exchange 2007 servers, the Network News Transfer Protocol (NNTP) service and the SMTP service are no longer required.

Read More

How to remove Exchange 2007 certificate

Open "Exchange Management Shell".
Write "get-ExchangeCertificate" and press on "Enter" button.
Write down the Thumbprint of the certificate that reflect.
Remove-exchangecertificate –thumbprint xxxxxxxxxx and press enter.

Its working for me.

Read More

Troubleshooting MSExchangeSA 9386 Warnings and OAB Generation and Access Issues

The warning event MSExchangeSA 9386 indicates that offline address book (OAB) versions prior to version 4 cannot be generated because a public folder server containing a replica of the offline address book system folder cannot be contacted. (Microsoft Exchange Server 2007 contains version 4 of OABs.) As a result, users of some versions of Microsoft Office Outlook clients and Office Outlook Web Access are unable to view their Address Books.

This event may occur in the following situations:

* If at least one public folder store is not in an Online state in the Exchange organization, and the Enable public folder distribution option is enabled on the properties of the default Offline Address Book.
* If the OAB folder does not correctly exist or have a valid replica. This situation may happen in cases where an Administrator creates a new OAB, designates the public folder database on server "X" as the site folder server, and the designated public folder database is subsequently deleted incorrectly. For example, ensuring that replicas are moved prior to the deletion is an incorrect method. In addition, it is also incorrect to remove the public folder database object from Active Directory directory service by using LDP.exe or AdsiEdit.msc or, if the database is on a pre-Exchange 2007 server, by uninstalling the server.
* The OAB folder was created, but hierarchy replication or maintenance didn't occur. As a result, the OAB folder was actually not created but the OAB exists in Active Directory, which lists a deleted public folder database as the designated site folder server. As a result, OAB folders do not exist anywhere in the organization.

To fix these issues, perform one of the following procedures:

* If you do not require OAB support for versions of Outlook prior to Outlook 2007, perform the procedure "To disable the "Enable public folder distribution" option."
* If you require OAB support for versions of Outlook prior to Outlook 2007 and you already have public folders deployed in your Exchange organization, perform the procedure "To enable public folder distribution for versions of Outlook prior to Outlook 2007."
* If you require OAB support for versions of Outlook prior to Outlook 2007 and you do not have public folders deployed in your Exchange organization, perform the procedure "To create a public folder database and enable public folder distribution for versions of Outlook prior to Outlook 2007."

Procedure
To disable the "Enable public folder distribution" option

1. Open the Exchange Management Console, expand the Organization Configuration container, and select the Mailbox sub-container.
2. In the center pane, select the Offline Address Book tab. This tab displays the Default Offline Address Book object.
3. Right-click Default Offline Address Book, and then select Properties.
4. Select the Distribution tab, and clear the Enable public folder distribution check box.
5. Click OK to save the changes.

To enable public folder distribution for versions of Outlook prior to Outlook 2007

1. Open the Exchange Management Console, expand the Organization Configuration container, and select the Mailbox sub-container.
2. In the center pane, select the Offline Address Book tab. This tab displays the Default Offline Address Book object and properties.
3. Right-click Default Offline Address Book, and then select Properties.
4. On the General tab, identify the Generation server attribute and make note of it.
5. Select the Distribution tab and confirm that the Enable public folder distribution check box has been selected. Also make sure that the appropriate check boxes in the Client Support section have been selected.
6. Click Apply, and then click OK to save the changes.
7. Next, expand the Server Configuration container, and select the Mailbox sub-container.
8. In the top center pane, select the Mailbox server that was previously identified as the OAB Generation Server.
9. In the lower center pane, identify the storage group that contains the public folder database, and click the database object.
10. Confirm that the status field shows a status of Mounted for the database. If the database is not in a Mounted state, click the Mount Database action in the right-hand action pane.
11. If the database does not mount, review any errors presented in the user interface, as well as those located in the Application event log, to identify the cause of the failure and resolve those errors. After the errors have been resolved, repeat step 10.

Read More

Event ID 12014 may appear in Exchange 2007 Application Event Log

SYMPTOMS

1. Event ID 12014 may appear in the Application event log of CAS/HUB Transport/Edge server:

"Microsoft Exchange couldn't find a certificate that contains the domain name mail.domainname.com
in the personal store on the local computer. Therefore, it is unable to offer the STARTTLS SMTP
verb for any connector with a FQDN parameter of mail.domainname.com.
Verify the connector configuration and the installed certificates to make sure that there is
a certificate with a domain name for every connector FQDN."


2. The SMTP connector may fail to support TLS connection.

CAUSE

The Exchange server, may setup to use wrong certificate or doesn't setup to use certificate.

• The certificate should reflect the external FQDN name of the server.

RESOLUTION


1. Open "Exchange Management Shell".

2. Write "get-ExchangeCertificate" and press on "Enter" button.

3. Write down the Thumbprint of the certificate that reflect the required FQDN name of the server.

4. Review the current certificate that use by the Exchange server and

each certificate function.

5. Write "Enable-ExchangeCertificate -Thumbprint 2afd26617915932ad096c48eb3b847fc7457662 -Services "SMTP"

and press on 'Enter" button.

• The value of -Thumbprint obtained in stage 3.

6. Restart the Exchange server.

Read More

USN-612-2: OpenSSH vulnerability

=========================================================== Ubuntu Security Notice USN-612-2 May 13, 2008 openssh vulnerability CVE-2008-0166, http://www.ubuntu.com/usn/usn-612-1 =========================================================== A weakness has been discovered in the random number generator used by OpenSSL on Debian and Ubuntu systems. As a result of this weakness, certain encryption keys are much more common than they should be, such that an attacker could guess the key through a brute-force attack given minimal knowledge of the system. This particularly affects the use of encryption keys in OpenSSH. This vulnerability only affects operating systems which (like Ubuntu) are based on Debian. However, other systems can be indirectly affected if weak keys are imported into them. We consider this an extremely serious vulnerability, and urge all users to act immediately to secure their systems. The following Ubuntu releases are affected: Ubuntu 7.04 Ubuntu 7.10 Ubuntu 8.04 LTS This advisory also applies to the corresponding versions of Kubuntu, Edubuntu, and Xubuntu. Updating your system: 1. Install the security updates Ubuntu 7.04: openssh-client 1:4.3p2-8ubuntu1.3 openssh-server 1:4.3p2-8ubuntu1.3 Ubuntu 7.10: openssh-client 1:4.6p1-5ubuntu0.3 openssh-server 1:4.6p1-5ubuntu0.3 Ubuntu 8.04 LTS: openssh-client 1:4.7p1-8ubuntu1.1 openssh-server 1:4.7p1-8ubuntu1.1 Once the update is applied, weak user keys will be automatically rejected where possible (though they cannot be detected in all cases). If you are using such keys for user authentication, they will immediately stop working and will need to be replaced (see step 3). OpenSSH host keys can be automatically regenerated when the OpenSSH security update is applied. The update will prompt for confirmation before taking this step. 2. Update OpenSSH known_hosts files The regeneration of host keys will cause a warning to be displayed when connecting to the system using SSH until the host key is updated in the known_hosts file. The warning will look like this: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. In this case, the host key has simply been changed, and you should update the relevant known_hosts file as indicated in the error message. 3. Check all OpenSSH user keys The safest course of action is to regenerate all OpenSSH user keys, except where it can be established to a high degree of certainty that the key was generated on an unaffected system. Check whether your key is affected by running the ssh-vulnkey tool, included in the security update. By default, ssh-vulnkey will check the standard location for user keys (~/.ssh/id_rsa, ~/.ssh/id_dsa and ~/.ssh/identity), your authorized_keys file (~/.ssh/authorized_keys and ~/.ssh/authorized_keys2), and the system's host keys (/etc/ssh/ssh_host_dsa_key and /etc/ssh/ssh_host_rsa_key). To check all your own keys, assuming they are in the standard locations (~/.ssh/id_rsa, ~/.ssh/id_dsa, or ~/.ssh/identity): $ ssh-vulnkey To check all keys on your system: $ sudo ssh-vulnkey -a To check a key in a non-standard location: $ ssh-vulnkey /path/to/key If ssh-vulnkey says "COMPROMISED", the key is vulnerable and should be replaced. If ssh-vulnkey says "Unknown (no blacklist information)", then it has no information about whether that key is affected because the key is of a type for which no blacklist is available. If in doubt, destroy the key and generate a new one. 4. Regenerate any affected user keys OpenSSH keys used for user authentication must be manually regenerated, including those which may have since been transferred to a different system after being generated. New keys can be generated using ssh-keygen, e.g.: $ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/home/user/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/user/.ssh/id_rsa. Your public key has been saved in /home/user/.ssh/id_rsa.pub. The key fingerprint is: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 user@host 5. Update authorized_keys files (if necessary) Once the user keys have been regenerated, the relevant public keys must be propagated to any authorized_keys files on remote systems. Be sure to delete the affected key.

Read More

How to Install Exchange 2007 in an Existing Exchange Server 2003 Organization

How to Install Exchange 2007 in an Existing Exchange Server 2003 Organization

Applies to: Exchange Server 2007, Exchange Server 2007 SP1 Topic Last Modified: 2007-03-14

This topic explains how to use Exchange Server 2007 Setup or unattended installation to install the first Microsoft Exchange Server 2007 server in an existing Exchange organization.

You can't perform an in-place upgrade from Exchange Server 2003 or Exchange 2000 Server to Exchange 2007. However, you can install an Exchange 2007 server into the existing Exchange organization and then move the Exchange resources, such as mailboxes, public folders, and connectors to Exchange 2007. After you perform this procedure, you will be running in a coexistence mode. You can maintain this mode for an indefinite period of time, or you can immediately complete the transition to Exchange 2007 by moving all resources from Exchange 2003 to Exchange 2007 and then decommissioning the Exchange 2003 servers.
Note:
There are no procedural differences between Exchange 2007 coexistence with Exchange 2003 and Exchange 2007 coexistence with Exchange 2000. Any procedures or documentation that refer to Exchange 2003 only also apply to Exchange 2000.

When you install Exchange 2007 in an existing Exchange 2003 organization, Setup performs the following coexistence-specific tasks:

* It creates the Active Directory universal security group ExchangeLegacyInterop. This group is granted the permissions that allow the Exchange 2003 and Exchange 2000 servers to send e-mail to the Exchange 2007 servers.
* It creates the Exchange 2007 Administrative Group. This administrative group is called Exchange Administrative Group (FYDIBOHF23SPDLT).
Caution:
Do not move Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) and do not rename Exchange Administrative Group (FYDIBOHF23SPDLT) by using a low-level directory editor. Exchange 2007 must use this administrative group for configuration data storage. We do not support moving Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) or renaming of Exchange Administrative Group (FYDIBOHF23SPDLT).
* It creates the Exchange 2007 Routing Group. This routing group is called Exchange Routing Group (DWBGZMFD01QNBJR).
Caution:
Do not move Exchange 2007 servers out of Exchange Routing Group (DWBGZMFD01QNBJR) and do not rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Exchange 2007 must use this routing group for communication with earlier versions of Exchange. We do not support moving Exchange 2007 servers out of Exchange Routing Group (DWBGZMFD01QNBJR) or renaming of Exchange Routing Group (DWBGZMFD01QNBJR)
* It creates a two-way routing group connector between Exchange 2007 and a selected Exchange 2003 bridgehead server. Exchange 2007 and Exchange 2003 use different routing topologies. You must configure a routing group connector to enable mail flow between the Exchange versions.

Note:
You can install Exchange 2007 in a native mode Exchange organization. However, if you create a new forest in which to install Exchange 2007, you cannot later add earlier versions of Exchange. This scenario is not supported.

You complete Exchange 2007 installation by performing several tasks. You can complete all these tasks at the same time, or you can perform some of the tasks before you start Exchange 2007 server role installation. To complete installation, follow these steps:

* Install prerequisite tools You can install the prerequisite tools on the computer where you will install Exchange 2007 before you install the server roles. The prerequisite tools are Microsoft .NET Framework 2.0, Microsoft Management Console 3.0, and Microsoft Windows PowerShell. Links to these tools are provided in Exchange Server 2007 Setup.
* Prepare the Active Directory directory service You can extend the Active Directory schema and create the Active Directory objects and universal security groups to support Exchange 2007 before you install the server roles. Run setup.com /PrepareAD from the command line on the domain controller that is the schema master at the forest root. When you run setup.com /PrepareAD, the task setup.com /PrepareLegacyExchangePermissions also runs to create the universal security group that is granted permissions to send e-mail to Exchange 2007 Hub Transport servers. If you do not perform this task before you start installation, it will run during installation. For more information, see How to Prepare Active Directory and Domains.
* Install server roles You can install Exchange 2007 by using Exchange Server 2007 Setup, or perform an unattended installation by running setup.com from the command line. You can select to perform a typical installation to install the Mailbox, Hub Transport, and Client Access server roles, or you can select to perform a custom installation to install one or more server roles. If the Exchange 2003 organization has front end servers, the Client Access server role is typically the first role deployed. You must install the Hub Transport server role and the Mailbox server role to have a fully functional Exchange 2007 organization.

Before You Begin

Before you begin, follow these steps:

* Create a transition plan. If you plan to maintain a coexistence environment for any period of time, see Planning for Coexistence.
To complete your transition plan, see the following topics:
o Upgrading to Exchange 2007
o Best Practices for Transitioning an Exchange Organization
* Verify that the server on which you will install Exchange 2007 meets the system requirements for the server roles that you are installing. For more information, see Exchange 2007 System Requirements.
* Verify that your existing Exchange organization is running in native mode. An Exchange organization is running in native mode should not contain any servers that are running a version of Exchange previous to Exchange 2000 Server. For more information, see Coexisting with Exchange Server 2003 and Exchange 2000 Server.

To perform the following procedure, the account you use must be delegated membership in the Schema Administrators group if you have not previously prepared the Active Directory schema.

If you are installing the first Exchange 2007 server in the organization, the account you use must have membership in the Enterprise Administrators group.

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.
Procedure
To use Exchange Server 2007 Setup to install Exchange 2007 in an existing Exchange organization

1.

Log on to the server on which you want to install Exchange 2007.
2.

Insert the Exchange Server 2007 DVD into the DVD drive. If Setup.exe does not start automatically, open the DVD directory, and then double-click Setup.exe.
3.

On the Start page, complete Steps 1 through 3 to install the prerequisite tools.
Note:
If you already have Microsoft .NET Framework 2.0, Microsoft Management Console (MMC) 3.0, and Windows PowerShell installed, these steps will be unavailable. If you have not installed Microsoft .NET Framework 2.0, Setup will link to .NET Framework Developer Center. If you have not installed Microsoft Management Console (MMC) 3.0, Setup will link to MMC 3.0 update is available for Windows Server 2003 and for Windows XP. If you have not installed Microsoft Windows PowerShell, Setup will link to Windows PowerShell 1.0 English Language Installation Packages for Windows Server 2003 Service Pack 1 and for Windows XP Service Pack 2.
4.

On the Start page, click Step 4: Install Microsoft Exchange. Setup copies the setup files to the computer on which you are installing Exchange 2007.
5.

In Exchange Server 2007 Setup, on the Introduction page, click Next.
6.

On the License Agreement page, select I Accept the terms in the license agreement, and then click Next.
7.

On the Error Reporting page, select the appropriate selection and then click Next.
8.

On the Installation Type page, click Typical Exchange Server Installation or Custom Exchange Server Installation. If you want to change the path for the Exchange Server 2007 installation, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next.
Note:
If you select the Typical Exchange Server Installation option, you will be unable to install the Unified Messaging server role, Edge Transport server role, or clustered mailbox servers during this installation. You can install additional server roles later by using Setup.com or Add or Remove Programs from Control Panel.
9.

On the Mail Flow Settings page, click Browse to select an Exchange 2003 bridgehead server that is located in the routing group to which you will create the initial routing group connector.

Figure 1 Mail Flow Settings page

Read More

Ubuntu 7.10 evolution send/received button doest not active

If its in offine mode send/receive option will be grayed out... (It will not be active)

if so,

Select File -> work online allows you to use the send/receive button.

Read More

Nambara Sanda Wage

Read More

NEW TRAFFIC PLAN -Colombo

Read More

An Exchange 2007 server on which an address list service is active cannot be found.

Problem
0 succeeded, 1 failed.
Elapsed time: 00:03:49

testuser
Failed

Error:
The mailbox has been moved, but an unexpected error occurred while trying to apply policies or clean source mailbox: An Exchange 2007 server on which an address list service is active cannot be found.

An Exchange 2007 server on which an address list service is active cannot be found.

Error:
A dump is being generated.

An Exchange 2007 server on which an address list service is active cannot be found.

Exchange Management Shell command attempted:
'89088210-9ccd-4714-abd9-5f7b88bb44c3' | move-mailbox -TargetDatabase 'CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=test,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=test,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=test,DC=com'

Elapsed Time: 00:03:50

Solution
START the Microsoft Exchange System Attendant service from Services.msc

Read More

June 07

Read More

Microsoft Outlook 2003: Manually updating the Exchange Server Global Address List (GAL)

The following guide demonstrates how to refresh the Global Address List with current information from the Exchange Server.

What is the Global Address List (GAL)?

The Global Address List (GAL) serves as a directory for the Microsoft Exchange Server e-mail system. Set as the default Address Book for Exchange Server e-mail accounts, the GAL provides Exchange with a database of all distribution lists and e-mail users on the LSU system.

If you are using Outlook 2003 with an Exchange Server e-mail account, you may have to periodically update your Global Address List.
This guide demonstrates how to manually download the current GAL from the Exchange Server.

To manually update your Global Address List (GAL):

1. In the Outlook menu bar, go to Tools and select Send and Receive.
2. Click Download Address Book.
3. The default selections should be set to Download changes since last Send/Receive and Full Details. Click OK to download the current Global Address List.

Read More

Randenigala Sanctuary

Great value for the money and time you spent at Randenigala T.R.E.E. Center. The calm and quiet environment absolute comfort will help to relax your mind and body.

The sound of birds and fascinating scenery is pleasing to the eye and soothing to the heart.

You are assured of an extremely happy and unforgettable experience at the Victoria, Randenigala, Rantambe ( VRR ) Sanctuary.

Climatic Conditions
The month of May, June & July are extremely dry and windy.

Rainy Season
September up to February

VRR Sanctuary extended 104,000 Ackers

Nearest Town – Mahiyangana
Services and facilities @ Mahiyangana-
02 Fuel Stations
Hospital
Police Station
Garage
Banks – BOC, Peoples Bank, Sampath Bank

Access to TREE Centre
From Colombo via Kandy. The shortest route being via Rajamawatha - Tennekumbura, Mailapitiya, Adikarigama, Keerthibandarapura, Randenigala.
200 km

Via Digana, Teldeniya, Hunnasgiriya, eighteen world famous hairpin bends to Hasalaka, Weheragantota, Mahiyangana, via Minipe - Randenigala. 217 km

Other Attractive Locations for Visit-
Bambiya Peak Hiking, Bio-diversity, Ecology, Study of Mahaveli projects (walking distance )

Rantambe Nature Trail- Bird watching, Scenic beauty.
(walking distance )

Mahiyangana Temple- Historical & educational value.

Sorabora Wewa- Ancient anicut, Historical, educational value.

Ratna Ella water Fall-
Dambana Veddhas Village-
Wasgamuwa National Park-
Maduru Oya National Park-
Loggal Oya Camping Site- one night with meals

Randenigal, Rantambe Dam, Minipe Anicut,
Loggal Oya,Uma Oya-

Ginipetti palama- educational value for students about reservoirs, dams and anicuts

Fauna-
Elephants- 40 nos recorded among the 02 Tuskers

Leopards, Spotted Deer, Sambhur, Mouse Deer,
Barking Deer, Wild Boar, Large grey Langer monkey,
Torque monkey, Porcupine, mongoose, Otters.

Birds- 137 species recorded
Butterflies- 71 species recorded

Vegetation
Most of secondary forest

Primary forest
Represent – burutha, kaluwara,kalumediriya, lunuwarana, visnukanthi, penela, dadiya,

TREE Centre Facilities-

Accommodation- 100 visitors at a time, A/C and non A/C separate bungalows

Restaurant- providing variety cooked foods, snacks and drinks.

Charges affordable and very reasonable low prices

TREE Centre Activities-

Training out bound adventures programs
Workshops for group to build Team work
Conference facilities + multimedia
Wildlife expeditions including boat rides

Reservations-

Wildlife Trust – Sri Lanka
342, Pitakotte, Kotte, Sri Lanka.
0094 011 2809891 Colombo office
0094 055 22 45 777 TREE Centre, Randenigala

E-mail – wildlifetrustsl@gmail.com

Wildlife Trust Sri Lanka
(Affiliated to the Ministry of Environment & Natural Resources)

Read More