Directory Server 6.2 upgrade to 6.3: import LDIF problem

Hi all,
I have tried upgrading my Directory Server 6.2 to version 6.3 because of the database integrity issues as stated in:
http://blogs.sun.com/dsee/entry/directory_server_6_2_database
I have followed the steps defined in this article:
1. Shut down each directory server instance, as described in Starting, Stopping, and Restarting a Directory Server Instance.
2. Perform an LDIF export of the database, as described in Backing Up to LDIF.
3. Install the hotfix for bug 6642430 on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to see this bug description.
But when importing the LDIF export, I got the following error:
[17/Dec/2008:14:44:08 +0100] - import ec: WARNING: Skipping entry "sunPortalAdminPortalDomainPortalServerInstanceMonitoringID=Monitoring,sunPortalAdminPortalDomainPortalServerInstanceID=sol10portal-80,sunPortalAdminPortalDomainPortalID=portal1,sunPortalAdminPortalDomainID=defaultDomain,o=example" whichIt's the only information I get about why the entry was skipped (I did not forget to copy the part after 'which', there was no information there :-))
This resulted in a missing Portal instance configuration and thus I got a 'configuration error' when surfing through the gateway to the portal.
I have also tried: manually importing that entry, which resulted in a 'Object does not exist' error. I have tried copying the whole tree from another backup with identical setup, which wasn't working either.
Did anyone experience the same problems before? Did I do something wrong or is there a workaround for this?
Second question: What is the exact reason why a export and import is necessary? Or is it only necessary if the database is already corrupt? Is there a way to check that?
Thanks alot!
Sten

The entry was not imported most likely because it's parent isn't in the database yet. Are entries above this in another backend ? If so try importing that backend first. Also, that dn is so long, that it exhausted the buffer which is used to write messages in the access log. This is why, there's nothing after "which".
What is the exact reason why a export and import is necessary? Or is it only necessary if
the database is already corrupt? Is there a way to check that?The database corruption could be silent. So a binary backup/restore when going from 6.2 to 6.3 is not recommended and the LDIF route must be used.

Similar Messages

Error in Directory Server 5.0 SP1

I have encoutered with following error message on Directory Server 5.0 SP1. Any resolution for this problem?
[07/May/2007:18:41:32 +0100] - libdb: Lock table is out of available locks
[07/May/2007:18:41:32 +0100] - idl_store(=uid=siegertszs,ou=members,ou=lai003,ou=tradingpartners,o=asite,o=asite.com) returns 12 Not enough space
[07/May/2007:18:41:32 +0100] - idl_delete_key(=uid=siegertszs,ou=members,ou=lai003,ou=tradingpartners,o=asite,o=asite.com) 1 BAD 12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1130, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1140, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1230, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - libdb: Lock table is out of available locks
[07/May/2007:18:41:32 +0100] - idl_fetch_one error 12 Not enough space
[07/May/2007:18:41:32 +0100] - idl_insert_key 0 BAD 12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1100, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1110, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1170, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - database index operation failed BAD 1040, err=12 Not enough space
[07/May/2007:18:41:32 +0100] - index_add_mods failed, err=12 Not enough space

Were you trying to create a new index and then reintdex the Database....if so Did you check the free space of your database filesystem??because it mentions about space problem for the database..after reindexin

Replication problem with iPlanet directory server 5.1 SP2 HF1

If I make a apply a change to either of consumer servers for an entry that belongs to the large database, that change does get applied to the consumer targated but it can not refer the change to teh master. Neither the master, nor the other consumers get updated consequently. I did not have this problem with directory server 5.1 SP1. I only see this problem after I apply directory server 5.1 SP2 HF1.
From the error log file, I see the following message:
NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica

I have a suggestion - try another means for administering your directory - use the console only for maintenance and tuning purposes. There are several products out there that are much better for day to day operations ...
Otherwise - I think with 5.1 the view is based on the rdn of the entries - and I am not sure it is customizable. Additionally I know 5.2 solved your second issue - maybe the latest SP of 5.1 has solved it as well - though I don't really know ...
-Chris Larivee

Changing IP Address and ports in Directory Server 5.1 SP 4 and 5.2 SP4

I have installed multiple instance of Sun Directory Server 5.1 and 5.2 on ports 389 and 390,now I want to change the IP Address and ports, I am able to change the directory server port from 389 by editing the dse.ldif file, now I want to change the port 390 and the IP address same as directory server, can someone expert from the forum guide me.
Thanks in Advance.
Mukesh Kumar

1) I don't know what you've typed in when installing... but I've never seen that message. Are you using any language specific characters ?
Do you get the error after this screen ?
<b>
The suffix is the root of your directory tree. You may have more than
one suffix.
Suffix [dc=sun,dc=com]:
</b>
If yes, then this means that the value you typed in is not a valid DN... and you must enter a valid one.
2)The Directory Server is installed under /usr/iplanet but the database is under /var/iplanet/ds5 and configuration is under /etc/iplanet/ds5 ...
You can use symbolic links if you want to move things around.
3) You mean you downloaded the tar.gx file of iDS 5.1 and install it on Solaris 9... No problem, I do this every day. As long as you have right to create directories and files, you should be able to install as anyone. If not, you should install as root and then let the server run as a special user.
4) Solaris 9 comes with iDS5.1 packages already installed. But the server is not configured at all.
Running directoryserver setup allows you to configure it and create the database, accounts...
Running directoryserver uninstall remove the instance of the installed database... It doesn't remove the packages. You can start again a setup...
By the way, I think that iDS 5.1 on Solaris 9 comes with the full documentation... May be you should start by reading it.
Regards,
Ludovic.

Migrating from Directory Server 4.16 to Directory Server 5.2

I'm trying to migrate from Netscape Directory Server 4.16 to Sun One Directory Server 5.2, I've followed all the instructions available and it never seems to work, the thing is after I run the migrateInstance5 script found in
$SERVERROOT/bin/slapd/admin/bin , setting the new server on the same port as the old one, and I try to start the messaging server i get these error messages:
[13/Oct/2004:13:26:45 -0600] sunblade [2644]: General Error: func=_configdrv_pset_fetch;error=could not access server's configuration in ldap: func=psetRealCreate; error=Entry does not exist
NO configmsg_init error
/opt/iplanet/server5: Starting STORE daemon ...[13/Oct/2004:13:26:45 -0600] sunblade [2661]: General Error: func=_configdrv_pset_fetch;error=could not access server's configuration in ldap: func=psetRealCreate; error=Entry does not exist
ERROR: Configuration database initialization failed - see default logfile
[13/Oct/2004:13:26:46 -0600] sunblade [2662]: General Error: func=_configdrv_pset_fetch;error=could not access server's configuration in ldap: func=psetRealCreate; error=Entry does not exist
ERROR: Configuration database initialization failed - see default logfile
..............failed.
ERROR: Failed to find process file after 90 seconds:
/opt/iplanet/server5/msg-sunblade/config/pidfile.store
Unable to verify if the STORE daemon started.
Check the log file(s) under: /opt/iplanet/server5/msg-sunblade/log/default
ERROR: The following services failed to start, or were already:
STORE daemon
ERROR: Unable to verify start of STORE daemon for:
/opt/iplanet/server5
Do NOT attempt an immediate restart. The STORE daemon may
have started, but has not finished initializing.
Check the process list for the 'stored' process; if it exists
do not attempt to restart the server until the following file exists:
/opt/iplanet/server5/msg-sunblade/config/pidfile.store
You may also wish to check the log file(s) under:
/opt/iplanet/server5/msg-sunblade/log/default
Any ideas???

I had already followed the instructions in the doc from the link you gave me and it still doesn't work. It would be nice to know how to do it, but now that I know how to install the Messaging Server 5.2 directly into the Directory Server 5.2 it isn't so important.
thanks
Eduardo

Can JRE for Sun One Java Directory Server 5.2 be upgraded to JRE 6.0 Update

I am trying to upgrade jre installed with Sun One Java DS 5.2 from 1.5.0 to JRE 6.0 Updat 16. Is this possible?

I never received any feedback on my question.
I am attempting to upgrade our JRE version (installed with Sun One Directory Sever 5.2) from 1.4 to 1.6. I've installed JRE 1.6 Update 16 and set the JAVA_HOME environment variable to d:\programs\java\jre6 and don't know how to configure the directory server to run the 1.6 java version. Any help would be greatly appreciated.
Edited by: CDRA on Feb 2, 2010 6:17 PM

Upgrading iplanet 4.1 directory server to 5.0

Dear all
Problem goes like this:
We have netscape messaging server 4.1 ,directory server 4.1 running on NT box
we want to upgrade our mail server to 5.1 and directory server to 5.0 .
how can i get a pack of mail server 5.1 with directory server 5.0.
we are thinking to shift the system to Solaris also.
i tried first loading directory server 5.1 on solaris and then loading messaging server on the same system but using the existing directory server option . then migrating the users from old directory server to 5.1 .
when we are loading the 5.1 on solaris it's straight forward and it's getting loaded but when installing messaging server on the same system we got a problem saying that serious problem occured while installing admin server ....
and coming out.

Hi Phil,
To ensure its not permissions I'd grant the EUL Owner
the "Select Any Table" database priv and then try
again.
If it still fails I would then perform a database
trace of the session to get more details.
Finally, if that fails I would create a new 3.1 EUL
and export/import all of your business areas into
that EUL and perform the upgrade to 4.
Thanks,
JeffHi Jeff,
I'll try your suggestions.
I also did a Business Area refresh which fixed a few definitions that no longer existed but when I ran the upgrade again I got the same error.
Thanks.
Phil.

Issues in Upgradation of Directory Server 5.3 Patch 3 to Patch 6

I am currently using Directory Server 5.2 Patch 3. I am trying install Patch 6 but is getting the error message
*./install.sh: ./lib/nsPerl5.005_03/nsperl: not found*
"patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar" is this the right tar file I am using?
Please respond. Thanks in advance.
Regards,
Joydeep
Edited by: joy2009 on Jul 15, 2009 5:43 AM

You should be using patchzip 117665-05 (if you're using zip install).
What you're seeing looks like this bug
6287502 - Error ./lib/nsPerl5.005_03/nsperl: not found from install.sh when called from another directory
Are you running the installer from outside the top level directory? If so, you should run the installer after "cd" to it's directory.

Invalid Directory Server

When adding a new connector view I am receiving the following error message in the Meta-Directory console:
Invalid directory server.
Meta-Directory requires Sun ONE Directory Server 4.1 or higher.
Please install and specify the correct version
We are using Meta-Directory 5.1.1 and Directory Server 5.2P4.
Any help is much appreciated.
Thanks,
Jeff Norton

Do you know when 5.1.1 is scheduled to be released?
Meta-Directory 5.1 does not support Directory Server
5.2
The upcoming Meta-Directory 5.1.1 will support
Directory Server 5.2
You'll need to upgrade.
- Paul

Error while migrating to Sun Directory Server 6.0

Hi All,
I am trying to migrate the Sun One Directory Server 5.2 to Sun Directory Server 6.0. I am getting the following error
bash-3.2# ./dsmig migrate-config /var/Sun/mps/slapd-circb2bld3/ /var/SunDirectoryServer6.0/dsInst/
Launching Configuration Migration of server instance /var/Sun/mps/slapd-circb2bld3 .....
Enter the certificate database password:
Starting server instance /var/SunDirectoryServer6.0/dsInst ..... Instance /var/SunDirectoryServer6.0/dsInst is already running (ns-slapd pid is 3868)
Enter "cn=Directory Manager" password:
Connecting to server localhost:389 .....
Could not bind securely on "localhost:389".
Remote host closed connection during handshake
Details: SSL peer shut down incorrectly
Could not create context for configuration migration.
Operation "migrate-config" failed.
Please help me.

Please stop
The migration guide has step by step instructions, including command line examples, are you using that as your reference?
Your upgrade should be to (at a minimum) DSEE 6.3.1.1.1. Upgrading to 6.0 is upgrading to a release level that has no patches or fixes to the product. There are significant fixes to the migration command line tools. There is a good chance you will run into issues.
You should install and review migration to ODSEE 11.1.1.7.0 (which would effectively be the 7.2 release of the DS).
There is a specific guide for migration and upgrade, which includes migration from DS 5.2 to 11.x
The full documentation collection for 11.1.1.7.0 is here
http://docs.oracle.com/cd/E29127_01/index.htm
The specific migration guide is here
http://docs.oracle.com/cd/E29127_01/doc.111170/e28971/toc.htm
See: Part II Migrating from ODSEE 5.2 to ODSEE 11g Release 1 (11.1.1.7.0)
ODSEE 11.1.1.7.0 can be downloaded from here.
http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html

Issue w/ Case Differences Using the IBM Directory Server MA

We have the following issue using the IBM Directory Server MA using FIM 2010 R2 (Version 4.1.3479.0).
We provision a new object, e.g., uid=jdoe,ou=users,o=contoso, into an instance of IBM Directory Server
The object is created in IBM Directory Server as uid=jdoe,ou=users,o=contoso
A Full Import on the IBM Directory Server MA runs and confirms the export
Subsequent imports, sync, and exports run successfully
<Time passes>
A Full Import on the IBM Directory Server MA runs, and this object shows up as a staging-error (uid=jdoe,ou=Users,o=contoso)
Subsequent imports and syncs report errors on this object (staging-error)
Note that we do not manipulate the anchor (DN) of this object once it is created in IBM Directory Server. Other attributes are synchronized, but the object is never renamed/moved. This case change does not happen with all of the objects brought
in during the Full Import, but the number of instances do increase periodically. At this point, it does look like the import is changing from a lowercase "u" to an uppercase "U" but not vice versa.
I found a related
TechNet article containing the following remark:
"IBM Directory Server does not guarantee that the case of a DN component will match in all instances. On a synchronization or import from IBM Directory Server, this can manifest itself as an unexpected update. For example, if you create
O=TEST, and then create the user cn=MikeDan,O=TEST, this might be imported from IBM Directory Server as
cn=MikeDan,O=test. Because of the case difference, FIM treats this as an update on subsequent full imports."
Unfortunately, the article does not propose a resolution.
Has anyone encountered this issue? More importantly has anyone resolved this or found an acceptable workaround?
Note that deleting the connector space is not an acceptable workaround. :)

I remember experiencing this issue when we were on 5.0, and I believe it persists through 5.1 as well.
There is a comment in the 5.2 release notes that something similar was fixed:
Changing case sensitive attribute values failed in MMR. (4624693)
If I had to take a wild guess, I would say that the server does some internal checking to see if the value has changed, possibly based on the attribute syntax, to avoid replicating "changes" that really don't change anything except case. I doubt that all your custom attributes are case-sensitive, though. Enabling replication probably "turns on" this behavior, which doesn't go away even if replication is disabled.
In any case, you're probably out of luck unless/until you upgrade to 5.2.

Re: (forte-users) Unstable server ENV after upgrade to Forte30M2.

I see/suggest a few things:
1) In your #1, you mention ".... development and test environments which use the
same Forte 3M installs through links ...". This concerns me. On our UNIX box
each environment has it's own directory containing it's own install. If your
environments are some how sharing a node manager, log directory or processes (to
name a few things) that is a recipe for disaster. They may be competing for
resources and usually the first one started will win.
2) I haven't done a lot with compatibility levels, but if an application built
in dev is to run in test it may be important that node managers and services
(autocompile, codegen etc.) be at the same level (????).
3) Check the definition files, to make sure the two environments operate
independently. If they are both trying to write to the same log file the one
started up first will work while the second will not as the file will be "busy".
4) We usually use rpcreate (newer version) to create brand new repositories.
Than we export/import the source code that we need. Also it is important to
force compile ALL plans in a workspace at least once after doing the import.
This will ensure that all of the code is "speaking the same language". The other
compile, only compiles those pieces of code that changed from the last compile.
Hope this helps.
Kelsey PetrychynSaskTel Technical Analyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:kelsey.petrychynSasktel.sk.ca
Quality is not job 1. It is the only job!
"Braja Chattaraj" <forte_brajachotmail.com> on 09/13/2000 03:43:57 PM
Please respond to chattaraj_braja_NONLILLYlilly.com
To: forte-userslists.xpedior.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) Unstable server ENV after upgrade to Forte 30M2.
We are running Forte 3M2 clients and server in our test environment with
clients on NT and server on Solaris 2.6. Eversince the upgrade from 3L to 3M
we have been having an unstable environment that does not remain alive for >
10 mins. These are the details of the Forte installs and server setups :
1. The server hosts the development and test environments which use the same
Forte 3M installs through links (same ftcmd, ftexec, nodemgr, etc.). The
environments are at compatibility levels 0 and 1 respectively.
2. The two environments have the same definition files (defining the ENV
variables), though seperate copies and the two environments are hosted on
different ports on the same server.
3. While building the new 3M environmnets in DEV and TST, we exported the
old 3L repositories and imported them into the new 3M repositories and
deployed the applications.
While the DEV environment is stable the TST environment is not. This has
been observed while moving plans between the environments (export and
import) using fscript commands, deploying the apps after the move using
fscript, and testing the apps. Sometimes it has come down right after a
startup. There is no programatic reference to the environment agent in the
code. So, a programatic shutdown is ruled out.
Does anybody have a clue or a similar experience ?
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BRAJA KISHORE CHATTARAJ
Consultant, Analysts International.
Work : Sphinx Pharmaceuticals (A division of Eli Lilly & Co.)
(919) 314-4134
Home : 1801, Williamsburg Rd., #41H, Durham, NC 27707.
(919) 463-7802
E-mail : forte_brajachotmail.com
Visit us www.analysts.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://profiles.msn.com.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

We found a solution to our issue.Their desktops were in a lockdown environment and the essbase.id file located in the windows directory was locked as well. This file is responsible for assigning ports etc and it couldn't be updated for the 6.5.4p2 upgrade. Once the file was deleted and the user reconnected to Essbase, the essbase.id was reset and they could connect.

Use of configuration directory server

Maybe this is a dumb question but since I dont know the answer:
Does one need to buy a production license of the Directory Server to use as a configuration directory server?
I will have six web servers in my production environment. But only one or two admin user accounts for secure access.
Thank,
-amit

Both 2005Q1 and 2005Q4 are considered 6.2. I would
use 2005Q4. Actually, I DID use 2005Q4.
Why use bits that are already superceeded? Is it the
cost of 4 CD's?So, can this happen in two separate stages?:
1. First upgrade all directory servers to 5.2p4 and migrate the current messaging server 5.2 configuration.
2. At a later date, once directory services have been upgraded and are stable, the upgrade of the messaging server can be done.
Thanks

Error Exchange Server 2010 SP3 Upgrade - OWA Already Exists - Event ID 1002

Hi,
I have a problem with my Exchange 2010 SP1 deploy in Windows server 2008 R2,
I try upgrade to Exchange 2010 SP3, an error happened when step progress CAS role
Error:
The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
" was run: "The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
Parameter name: VirtualDirectoryName".
The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
Parameter name: VirtualDirectoryName
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
" was run: "The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.".
The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
I already try delete owaVirtualDirectory from adsiedit, Exchange management console, and from IIS manager but still it say virtual directory 'owa'
already exists in my server.
Can anyone help me how resolve this problem?
Thanks.
Best Regards,
Henry Stefanus

Hi Henry,
Even we can’t see /OWA virtual directory in IIS manager, still doesn’t mean it not exists. The IIS configuration files are located in ApplicationHost.config. This file is located in %windir%\system32\inetsrv\config.
Found the below entry even with no owa vdir in IIS manager, remove the entries below and try upgrade again. (Note: Before you modify ApplicationHost.config, please take a backup first.)
<application path="/owa" applicationPool="MSExchangeOWAAppPool">
<virtualDirectory path="/" physicalPath="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa" />
</application>
If the issue still occurs, please do not hesitate to post back.
Best regards,
Eric

Migrating Netscape Directory Server 4.1 to a new server

Hi,
In the current production environment, we are using Netscape Directory Server 4.1 as the authentication with Siebel CRM system. The server hardware is old and there is a need to refresh the server. As Netscape Directory Server is the only supported/ certified LDAP with embedded functionalities in Siebel Financial Services 6.0.2.300, we are planning to upgrade only the server hardware and migrate all the user information from old server and the new one, with Netscape Directory Server 4.1 remained.
I have studied the Netscape Directory Server 4.1 Deployment Guide and gone through the migration procedures, looks like the procedures are only applicable for migrating Netscape Directory Server to a newer version. There are no specific procedures mentioned for migrating Netscape Directory Server to the new server hardware with the same directory server version.
I am seeking for detailed procedures of migrating Netscape Directory Server 4.1 to a new server hardware with the same directory server. Anyone has done this migration before? I thank you in advance for your valuable feedback.
Sincerely,
Julie

Luckily, I have the technical documentation in hand, which contains all the configuration of the current server. So I need to use "db2ldif" to export the data. I am currently testing on the migration by following these steps:
1. Install the new server.
2. Stop the Netscape Directory Server and Netscape Administration Server services in old server.
3. Copy the slapd-<server_name> folder from old server to a temp location of new server.
4. Take the old server offline.
5. Configure new server to have the exact configuration as the old server.
6. Backup the existing slapd-<server_name> folder in new server, copy the slapd-<server_name> folder from the temp location to C:\Netscape\Server4 directory of new server.
7. Start the Netscape Directory Server and Netscape Administration Server services in new server.
Will try out your suggested method. Thank you so much for your feedback.
Regards,
Julie

Directory Server 6.2 upgrade to 6.3: import LDIF problem

Similar Messages

Maybe you are looking for