GW Post Office Server Recommendation ...
Hi everyone,
Need to decide on a new server platform for our primary Post Office, currently running GW 8 on NetWare but will move to Linux with this new hardware (bare metal install of SLES 11 sp2 with OES for NSS filesystem). Have the following choices:
Option A - HP Proliant DL380 G6, Qty 1-2.8GHz QC Xeon (X5560), 16GB RAM, Qty 4 600GB 15K SAS (raid 5), 512MB RAID cache
or
Option B - HP Proliant DL380 G6, Qty 2-2.5GHz QC Xeon (E5540), 16GB RAM, Qty 4 600GB 15K SAS (raid 5), 512MB RAID cache
As you can see, the only real difference is in the CPUs with one unit providing 4 cores but higher clock speed and the second unit providing 8 cores but slower clock speed. Now, given that a GW PO is disk intensive, I am wondering whether the CPU options here really make that much difference. And, is 8 cores overkill in this situation? Any thoughts? Thanks.
We are running our 3700 mailbox setup on a G7 version of this. You want more cores. Things like document conversion, webaccess, gwia, ... all can use additional cores. You neglected to mention the scale of your setup and what other agents you will be using.
Raid 5 = REALLY BAD. For that array, it can take days to rebuild, your disk performance will be horrendous, impacting service, and meanwhile if another drive fails you are hosed. Get more smaller disks and use RAID 1. A larger write cache on the controller is helpful. More memory is helpful. But it would be useful to know how big your setup is.
( Depending on how critical performance is, placing OFUSER and OFMSG on SSD will greatly increase performance as well as prevent the "rot" caused by fragmentation of the databases that occurs over time. We have about 1TB of e-mail, and about 100GB of databases. So a pair of 128 / 256 GB enterprise SSD will do it. Wear leveling and predictive on the HP will heep you out of any of the hypothetical troubles you may hear rumors bout when using SSD. )
-- Bob
Similar Messages
-
Unable to validate post office database
I have a problem with one of my five post offices. I went to run a Validate Database task, and it errors out after a second and displays the following in a red text:
javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException - with linked exception: [java.net.ConnectException: Connection refused] (null)
Just tried this on one of my other post offices, and it is running just fine.
I was trying to figure out why we are having some issue with this post office/server.
Server is OES 11 SP2 / SLES 11 SP3
post office is on an NSS volume
system was upgraded from 2012 to 2014 over a month ago.That's normal, You can't get to the admin console on a server with just a post office. Looks like you are configured correctly. So for some reason, the domain's admin service is not communicating with the po admin service when you try to validate the po db. Look at this po's POA object in admin and see if the admin port is set. If it isn't then for some reason it did not get replicated to the domain.db.
--Morris
>>> ShootDawg<[email protected]> 7/3/2014 6:26 AM >>>
0.0.0.0:9711=>PO1.Barth(/media/nss/HERMESPO1/bcscpo1)
0.0.0.0:9710=>UNCONFIGURED
When I goto the server's groupwise administrative webpage, it wants me
to run the gwadmin-ipc authorize command on the server, which I
do....and then the browser moves to the next page, I select upgrade
existing domain/po, highlight my post office (database version shows
1400) , enter the MTA ip address and admin password, get a crongrats,
restart the PO (or PO and gwadminservice)...
then try the admin page again....wanting me to authorize it to do
the install again.... and again...
mblackham;2324755 Wrote:
> Verify that the admin service on the problem po server is configured to
> run against the post office:
>
> /opt/novell/groupwise/admin/gwadmin-ipc query
>
>
> you should see something like:
>
> 10.10.10.10:9711=>Provo.Utah(/mail/provo)
>
>
> If you see 0.0.0.0:9710=>UNCONFIGURED , it means the admin-service is
> not configured to listen for any GW components. If this is the case,
> run thru the web console upgrade process to upgrade the PO on that
> server, even if you have already done it before.
>
ShootDawg
ShootDawg's Profile: https://forums.novell.com/member.php?userid=4554
View this thread: https://forums.novell.com/showthread.php?t=477985 -
Creating secondary linux domain & post office @ another city
I have a primary domain and post office in one city. Consoleone, shows them on my NSS volumes as /media/nss/MAIL/groupwise/domain and /media/nss/MAIL/groupwise/po
I created a new domain for another city, and gave it UNC pathing \\portland\MAIL\groupwise\domainnc. It did create the domain in eDirectory, but made a file structure under /mnt called /mnt/portland/MAIL/groupwise/domainnc. Not sure about what was going on with that, I copied the directory structure and all the files from there to the proper location of the portland server, started the domain and it fired up. Both domains showed that each other was up, communicating presumably entirely by IP.
I loaded ConsoleOne on the portland server and can see both domains.
So far so good.
When I created the new portland post office on the primary domain server, it did the exact same thing, making a /mnt/portland/MAIL/groupwise/ponc file structure, which again I copied to the portland server.
when I fired up the post office on the portland server, it did start and sat there looking like a post office (I did the --show option in linux), however none of the domains seem to recognize that there is a running post office. In fact, my domain in portland doesn't even know that it has a post office. It says that it sees another domain, but that it has 0 post offices configured so far. Consoleone on the portland server does not show a post office for portland.
ConsoleONe on the primary groupwise server does show the post office or I should say did, last friday. Today (Sunday) it's not there anymore.
I suspect my problem has something to do with mounting the file system of the portland server on the primary domain/post office server, but I'm unclear how those commands work.
Also, I'm unclear as to why I really need that if everything communciates via TCP/IP. Seems like it's only the portland server that physically needs to know about the post office physical file location. When I try using unc pathing (i.e. \\server\volume\location) ConsoleOne changes it to /mnt/server/volume/location.
Trying to find a concise document on this, but haven't found it yet.
Any ideas?In article <[email protected]>, Johnehurst wrote:
> ConsoleONe on the primary groupwise server does show the post office or
> I should say did, last friday. Today (Sunday) it's not there anymore.
>
If no instance of ConsoleOne see the new PostOffice anymore, it might be
time to recreate again, but this time do so on the server that you are
creating it for with that instance of ConsoleOne.
As for addressing within ConsoleOne for the Domains and PostOffices, make
sure they are pointing to the real location of the files
So for your Portland server/domain/postoffice
/media/nss/MAIL/groupwise/domainnc
/media/nss/MAIL/groupwise/ponc
The only real reason for those file pointers are for the agents (MTA &
POA) to see their files, so the format needs to in relation to where the
agents are running. Everything else should be over IP.
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037 -
Creating new post office / Agent on new server
I am currently running all of my GroupWise 2014 system on the a SLES 11 SP3 server with EXT3 drives. I am needing to move my domain and post office onto an NSS drive for my backup software to be able to restore back on a per user/message basis. So I have created a new OES 11 SP2 server and have created an NSS drive to hold my new domain and Post office.
Since I am not well versed at OES / GroupWise I thought it would be easier to create a secondary domain and Post office on my new NSS drive and move everyone onto the new post office and remove the old post office after everything has been moved.
However, I have created the secondary domain and it is linked and open but I can not startup a new post office linked to the secondary domain. I get the following error:
*com.novell.gw.directory.exception.GwCommunication Exception: An error occurred modifying an attribute value. Path not found (0x8209); remaining name 'nssdom.post-nss'
What could be causing this?
Sincerely,
KenThanks for continuing to help me on this issue. This is the out of the ll command.
/media/nss/NSS_GWISE/groupwise/postoff:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 offiles
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 ofmsg
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 ofuser
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 ofwork
-rw-rw-rw- 1 root root 0 Nov 20 09:03 Postofficepath
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 wpcsin
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 wpcsout
/media/nss/NSS_GWISE/groupwise/postoff/offiles:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd1
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd2
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd3
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd4
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd5
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd6
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd7
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd8
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fd9
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fda
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fdb
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fdc
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fdd
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fde
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 fdf
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd0:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd1:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd2:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd3:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd4:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd5:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd6:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd7:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd8:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fd9:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fda:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fdb:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fdc:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fdd:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fde:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/offiles/fdf:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/ofmsg:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/ofuser:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/ofwork:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 ofdirect
/media/nss/NSS_GWISE/groupwise/postoff/ofwork/ofdirect:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 1
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 2
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 3
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 4
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 5
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 6
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 7
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/0:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/1:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/2:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/3:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/4:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/5:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/6:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsin/7:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 ofs
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs:
total 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 0
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 1
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 2
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 3
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 4
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 5
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 6
drwxrwxrwx 1 root root 4.0K Nov 20 08:41 7
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/0:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/1:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/2:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/3:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/4:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/5:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/6:
total 0
/media/nss/NSS_GWISE/groupwise/postoff/wpcsout/ofs/7:
total 0 -
Reduce/Expire on post office - advice needed
My organization has (had) an email retention policy of 30 days for
email and 365 days for appointments.
We have been on legal hold for the last 3 years so I am looking at
roughly that amount of data that will need to be removed when we get
the green light to come off of hold from the legal folks. (I'm told
that is coming soon)
My question is how does the expire/reduce run most efficiently? Should
I just set my 30/365 days settings and let it run or does it run more
effiently (quickly) if I did something like 365/720 then stepped down
to the 30/365, which would require 2 passes through the post office.
I know from observing the initial implementation of the policy, it is
going to take more than a week to get everthing down to size. Also, I
will probably have to run this stand alone so I can start/stop it as
needed. We can't take too much of performance hit if I just start it
from the server and let it run.
Once I get the post office trimmed down, I'll be re-enabling the
nightly scheduled expire/reduce options for maintenence.
Any advice or recommendations are appreciated.
MarkHi Andy -
Thanks for the input. My industry (without getting too specific)
makes the rules but does not need to follow them if you read through
the lines
I've had discussions about archiving until I'm blue in the face. I
would get more traction discussing it with my dog.
The size of the post office is roughly 500 user at 380GB. I'll have
to research the lenght of the full contents check that runs on the
weekend. I like the idea of the three runs.
On Tue, 04 Dec 2012 18:49:15 GMT, Andy Konecny
<[email protected]> wrote:
>In article <[email protected]>, Mark wrote:
>> My organization has (had) an email retention policy of 30 days for
>> email and 365 days for appointments.
>That's quite short and might get you in legal trouble. It might be very
>worth your while to investigate archival tools such as GWAVA's Retain.
>
>>
>> My question is how does the expire/reduce run most efficiently? Should
>> I just set my 30/365 days settings and let it run or does it run more
>> effiently (quickly) if I did something like 365/720 then stepped down
>> to the 30/365, which would require 2 passes through the post office.
>> I know from observing the initial implementation of the policy, it is
>> going to take more than a week to get everthing down to size. Also, I
>> will probably have to run this stand alone so I can start/stop it as
>> needed. We can't take too much of performance hit if I just start it
>> from the server and let it run.
>
>How long does a full Contents analyze/fix take? You'll be in about that
>time frame. What I would do is start with a pass on cleaning up just
>trash, then just the appointments, then the mail. How big is this
>PostOffice? (#Users & GB/TB?) How many CPUs? If virtual, adding some
>more for this reduction would help.
>
>Was that initial implementation done from a stand alone system or agent
>based? And what that on the current hardware config?
>
>
>Andy Konecny
>KonecnyConsulting.ca in Toronto
>----------------------------------------------------------------------
>Andy's Profile: http://forums.novell.com/member.php?userid=75037
> -
The version of GroupWise you are using cannot access this post office
I built a new Server and added it to my PCSD Tree. The new server name is
GroupWise and has an IP Address of 10.10.0.13.
I followed the GroupWise 7 Installation Guide and installed GroupWise to
this server. At no point did I find any place to enter the GroupWise
License.
During the install I discovered that 4 of my long time employees were not
able to be assigned to this new GroupWise server. It appears that a one
time (Long time ago) these 4 employees were part of an old GroupWise Mail
server that must have been removed. I can not find any reference to this
old GroupWise server. My thought is to delete the accounts for there 4
users and recreate the accounts.
However the larger problem is this: I can not login to the GroupWise
Server. Below are two screen shots of what I’m getting when I
launch the GroupWise 7 Client. When I look at the .NLM loaded on the
Server for GroupWise MTA 7.0 it shows Domain Total=1 Closed=0, Post
Offices Total=1 Closed=1, Gateways Total=0 Closed=0.
On the Client, when I launch GroupWise, The Novell GroupWise Startup has a
message in the message window “The version of GroupWise you are
using cannot access this post office”. Then after clicking OK three
times, the following message appears on the screen “GroupWise did
not initialize successfully, Please run GroupWise Setup, or contact your
system administrator. Unspecified error OLE Error 80004005*During the install I discovered that 4 of my long time employees were not
able to be assigned to this new GroupWise server. It appears that a one
time (Long time ago) these 4 employees were part of an old GroupWise Mail
server that must have been removed. I can not find any reference to this
old GroupWise server. My thought is to delete the accounts for there 4
users and recreate the accounts.
**You need to disassociate these four NDS users from any GW attributes.
Right-click each user in C1, GroupWise Utilities->GW / eDirectory
Association->Disassociate GroupWise Attributes.
*** When I do as instructed I get the following error:
[username] is missing the following attribute: NGW: Post Office
~~~~~~~~~~~~~~~~~~~~~~~~
*GroupWise MTA 7.0 it shows Domain Total=1 Closed=0, Post
Offices Total=1 Closed=1, Gateways Total=0 Closed=0.
**If the post office is closed, you need to determine why this is. On the
MTA, hit F10, Configuration Status, highlight your PO and hit enter,
select details, then look at the last closure reason.
*** Last Closure Reason= Missing or incomplete address information
[ When I installed GroupWise, I wanted all the e-mail to be stored on the
EMAIL Volume. During the install, I Changed the Install Directory to
\Groupwiseemail. After the install I have two directories in this volume.
One called DOMAIN and the other called PCAM (PCAM is name of my domain).
~~~~~~~~~~~~~~~~~~~~~~~~
*On the Client, when I launch GroupWise, The Novell GroupWise Startup has
a message in the message window 'The version of GroupWise you are
using cannot access this post office'.
**What version of GroupWise is on the server and what version client are
you
using? Also, if you pull up the properties of both the domain and post
office in C1 what is the database version listed as?
*** I installed GroupWise 7 both Server and Client. I'm thinking this is
due to the Post Office being closed. I only have 1 Post Office.
Thank You;
Lewis -
Clean up after post office deletion
I deleted a post office from a GW 8.02 server running mta, gwia, and one other post office. When it asked me if I wanted to delete file system for that po, I said yes. However when it attempted to delete the files it gave an error saying they would have to be cleaned up manually. The objects deleted fine and the system is otherwise ok but when I run rcgrpwise status I still see the old post office listed there as unused. My assumption is that I need to clean up gwha.conf by removing the old post office from the list and then remove the file system for the old post office. Is that all there is to it?
Thanks for any assistance.
DanHey Dan,
Originally Posted by dlietz
The hypervisor is esxi 5.1. I just built the groupwise server vm, so right now it just has SLES 11.3 on it - I was planning to go away from OES since Groupwise no longer uses eDir objects. My plan was to go with ext3 for the file system.
Sure, that's a valid reasoning and ext3 should work fine. One could probably debate using XFS over ext3 when looking at native Linux filesystems for GroupWise.
One thing I normally do set when using ext3, besides the notaime parameter, is the time dependent check. I usually set that to 12 months. It's very annoying (and time consuming) to have the disk check kick in during a planned reboot.
Originally Posted by dlietz
... What I've read so far seems to indicate I can copy the entire Groupwise system to the new VM and point the upgrade process to the domain and post office and it will upgrade it. Is that correct?
Yes, correct. It is important to make sure the basic agent configuration is in working order (meaning the http pages for the agents have been enabled and LDAP server configuration and eDirectory sync is all set correctly and in working order before doing the upgrade). Even when moving from eDir, it's nice to have the upgrade routine be able to reconfigure those LDAP and sync bits correctly for 2014 before moving to a new directory.
Originally Posted by dlietz
So I'm thinking:
1. Patch current Groupwise to 8.03
You could do, but I don't see the need. You'll be moving to the 2014 anyway... 8.03 does nothing extra for that upgrade process.
Originally Posted by dlietz
2. Upgrade Datasychronizer server from sles11sp2 to sles11sp3
3. Upgrade Datasychronizer software to Groupwise Mobility Server 2.0 (At this point I would have to reconnect to old post office?)
Sure, though I'd not 2.01 can be applied directly as upgrade on your current 1.x Mobility system. Do make sure you set a snapshot on the VM before the upgrade (with the VM tunred off) and leave it long enough, a week or so, until you have checked and double checked all is working on the 2.01 system. That way it's easy enough to roll back to 1.x if needed.
Originally Posted by dlietz
4. Copy Groupwise system to new server using db copy in multiple passes with a final pass when groupwise is offline and run upgrade process.
Yep, and if the current filesystem is NSS... make sure to run it with the migrate (-m) option so the lowercase conversion runs with it.
Originally Posted by dlietz
I was also considering separating Webaccess and Calendar Publishing to separate server since Webaccess is no longer part of the Groupwise server install.
Absolutely, and I'd also place that Webaccess/Calendar Publishing server in a DMZ if you have it. All that's needed with the 2012/2014 version is access to the SOAP port on the POA(s).
Cheers,
Willem -
Error 8f03 starting post office
I created a new post office on a SLES10sp3/OES2sp3 server already running the primary domain, gwia, another po and webaccess. But I'm having a problem getting it to start using the poa startup file. Here's the text from the console:
srv1:/opt/novell/groupwise/agents/bin # ./gwpoa --show --home @hsstudpo.poa &
[1] 12179
Warning: Running as root
srv1:/opt/novell/groupwise/agents/bin # An invalid configuration option was detected (8F03).
Command Line Option: media/nss/VOL1/grpwise/hsstudpo
A required file or directory is missing (DF10).
home/wphost.db.
[1]+ Done ./gwpoa --show --home @hsstudpo.poa
The home switch in the hsstudpo.poa file looks like this:
--home /media/nss/VOL1/grpwise/hsstudpo
The POA will start just fine if I use the command:
srv1:/opt/novell/groupwise/agents/bin # ./gwpoa --show --home /media/nss/VOL1/grpwise/hsstudpo &
I've tried shortening the path to the post office thinking maybe it was some weirdness with the 8 character issue, but that didn't make a difference.
I'm stumped.
The only thing I can think of that may be causing this is when I first created the PO object in C1, I forgot to change the POA type from Netware to Linux. I have since fixed that however. Would a domain rebuild be required?
Thanks for any assistance.
Dandlietz,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/ -
GW Monitor and multiple post office agents on one Netware 6.5Server
HI,
I've not been successful getting GW Monitor (7 sp3) to recognize a PO as "known". Regardless of the setting I put in monitor.xml for the port assignment (1677), the thing reverts to port "0". This server is running a MTA only post office agent and a client post office agent. These may be related. Interestingly, the MTA IP configurations are:
MTA only post office agent:
Inbound - 165.91.107.28:7100 (My Note on this - this is from agmail MTA to agents POA which is IP ...28 and listens on 7100)
Outbound - 165.91.106.93:7101 (My Note on this - this is agents POA to agmail MTA which is ip ...93 and listens on 7101)
Client only post office agent:
Inbound - 165.91.107.28:7102 (My Note on this - this is from agents POA/MTA to agents POA only which is IP ...28 and listens on 7102)
Outbound - 165.91.106.93:7101 (My Note on this - this is agents POA only to agmail MTA which is ip ...93 and listens on 7101)
Maybe I should make the outbound for the client only post office agent to be:
Outbound - 165.91.107.28:7100
In any event, we need GW Monitor to report on the status of the POA at 1677 on the Agents server. Any ideas?
Thanks MikeMike Gerst wrote:
> In any event, we need GW Monitor to report on the status of the POA at
> 1677 on the Agents server. Any ideas?
Well, first of all the Monitor should be looking for 7101 for the MTA, 7100
for the first POA and 7102 for the second POA if indeed this is how you have
it set up. Are you sure you purposefully change the POA to listen on 7100
and put the MTA on 7101? That is confusing :) - most sites have the MTA at
the default of 7100, and the first POA at 7101, so it just looks weird to me
- but it's perfectly "okay" to change them if you want to - but just
confusing for long-time GW admins/consultants.
Danita
Novell Knowledge Partner
Time to upgrade to GW8!
http://www.caledonia.net/gw8upg.html -
The Post Office Agent might not be configured for SOAP.
I have a virtual server with VMware ESXi 5 running SLES11 sp1, OES11 and GroupWise 12.
The GroupWise system have one domain and one post office with several users.
The users can access the mailbox with the GroupWise Windows Client, but when they try to login in the GroupWise Webaccess, they get the following error: "[9505] Your post office is unavailable. The Post Office Agent might not be configured for SOAP. Please contact your system administrator".
1.- The post office agent have the SOAP option turned on.
2.- I check the java environment variables and they are pointing to the right directory.
3.- The Linux Firewall is turned off.
4.- rcapache2 start and rctomcat6 start dont show errors.
5.- I check the webacc.cfg file and all IPs address and ports (POA & DVA) are fine.
Any help, comment or suggestion will be welcome.
Thanks in advance.Check to see if the port is being used by SLES...
--El
Originally Posted by crivera
I have a virtual server with VMware ESXi 5 running SLES11 sp1, OES11 and GroupWise 12.
The GroupWise system have one domain and one post office with several users.
The users can access the mailbox with the GroupWise Windows Client, but when they try to login in the GroupWise Webaccess, they get the following error: "[9505] Your post office is unavailable. The Post Office Agent might not be configured for SOAP. Please contact your system administrator".
1.- The post office agent have the SOAP option turned on.
2.- I check the java environment variables and they are pointing to the right directory.
3.- The Linux Firewall is turned off.
4.- rcapache2 start and rctomcat6 start dont show errors.
5.- I check the webacc.cfg file and all IPs address and ports (POA & DVA) are fine.
Any help, comment or suggestion will be welcome.
Thanks in advance. -
Proxy to Another Post Office's Account Failed
We have a wired problem here:-
- Primary Domain is GW 703HP2
- Running 4 Post Offices all 703HP2
- 2 WebAccess Servers - 1 in 702HP and 1 in 65(Win2K)
Now, we have an user, USER-A, (in fact more than 1 have similar issue) who has Proxy Access to USER-B's account on another Post Office.
If he uses GW Client, he's fine. He can proxy access to USER-B's account without any trouble.
However, if he uses 702HP WebAccess, he can reach his own account but fails to proxy to USER-B's account with the error message "Your post office is unavailable. Please contact your system administrator."
Another wired thing is that if he uses 65(Win2K) WebAccess, he can proxy.
Any suggestion on what's wrong? Many thanks.
sau970982 from Hong KongOriginally Posted by DParkes
Yep, that's where I meant. And user B can use the GW7 Webaccess directly
alright ?, it is just the proxy access that is failing ?
Cheers Dave
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
Yes, USER-B is ok using WebAccess-7 with his own account. The server itself is working fine if you're looking into your own account.
What we found out is that WebAccess-7 server fails to proxy to accounts on another Post Office. But our WebAccess-65 server can. Just don't what kind of configuration we missed or is that something wrong with the server.
sau970982 -
GroupWise 2012 Post Office crashes.
2 of 5 post offices crash randomly. 1 PO is on an entirely different server and network. The POs started crashing after we upgraded to GroupWise 2012. Both POs run on SLES v. 10 fully patched. 1 of the POs runs in a clustered environment and other POs on the same server stay running when the problem PO crashes. The other problem PO is on a dedicated server along with the MTA and domain. I have run GW maintenance through ConsoleOne on both POs. I have renamed the wpcsin & wpcsout from postoffice directory and the ngwcheck.db files and ran maintenance from ConsoleOne. The issue still remains. Below is from the messages log and is the common error that is received when the POs go down. Any help would be appreciated.
May 22 10:14:24 lxnode02 kernel: gwpoa[28661]: segfault at 00000000e6eea691 rip 00000000f777a59e rsp 00000000ef73a210 error 6Originally Posted by ellisck
2 of 5 post offices crash randomly. 1 PO is on an entirely different server and network. The POs started crashing after we upgraded to GroupWise 2012. Both POs run on SLES v. 10 fully patched. 1 of the POs runs in a clustered environment and other POs on the same server stay running when the problem PO crashes. The other problem PO is on a dedicated server along with the MTA and domain. I have run GW maintenance through ConsoleOne on both POs. I have renamed the wpcsin & wpcsout from postoffice directory and the ngwcheck.db files and ran maintenance from ConsoleOne. The issue still remains. Below is from the messages log and is the common error that is received when the POs go down. Any help would be appreciated.
May 22 10:14:24 lxnode02 kernel: gwpoa[28661]: segfault at 00000000e6eea691 rip 00000000f777a59e rsp 00000000ef73a210 error 6
There are several known issues with crashing POA's. Make sure you'll be able to send a core dump and supportconfig to Novell, open an SR and they can provide you with an updated build in which the crashing should occur much less frequently. -
Remove existing Microsoft Office server products and re-run setup
Hi Folks,
I would be great if some one help me,
I have installed sharepoint 2007 in Windows 2008 R2, SQL Server 2008.I was able to access SP2007.
For some requirement i have uninstall SQL 2008 and SP2007, but i didnt remove SP2007 from server.
Note:
But now i have installed new SQL2008 with licence while i install SP2007 Project server i am getting issue like "Remove existing Microsoft Office server products and re-run setup"
I have removed 12 & 14 hive.
My Query is: Anything needs to remove from server or what should i do for this issue?
Thanks,
InguruAre you trying to install Office Web Apps 2013 on the same server as SharePoint Server 2013? Sorry I could not figured that part from your post. If you are installing OWA on SP 2013 server then it is not possible in SP 2013. You will need to install OWA
on different server where SharePoint is not installed. Basically a dedicated OWA server(s).
Check following article out.
http://technet.microsoft.com/en-us/library/ff431687.aspx
Amit -
IMAP Issue connecting Archiver to Post Office
I am running a GroupWise 8 sp2 hp2 system. I am trying to connect our new Barracuda Message archiver to all of my 30 post offices. Most run on Windows 2003 servers, but I have to that run on Linux. One is SLES 10 sp4, the other is SLES 11 sp 1. The one on 11 connects to the message archiver correct, as well as all 28 windows server post offices. The one that I have on the sles 10 box doesn't . This box also runs my primary domain, and gwia and webaccess on it. The msg archiver uses imap an soap to connect to the poa. All are turned on the poa. IMAP is not running on the gwia located on the box, so it shouldn't be a conflict. When I try to connect to the poa from the message archiver I see the following message in the poa log:
10:16:41 016 New IMAP session initiated from ::ffff:10.2.1.124
10:16:41 016 Return from IMAP [890F]
10.2.1.124 is the address of the message archiver. Any ideas on what could be causing this issue?This is what I see with the poa being in diagnostic mode:
11:02:42 896 IMAP command:[AUTHENTICATE] requested from ::ffff:10.2.1.124 User session()
11:02:42 392 Resetting read descriptors
11:02:42 392 Dispatched message for connection #3 protocol (IMAP)
11:02:42 896 IMAP command:[XGWTRUSTEDAPP] requested from ::ffff:10.2.1.124 User session()
11:02:42 392 Resetting read descriptors
11:02:42 392 Dispatched message for connection #3 protocol (IMAP)
11:02:42 896 IMAP command:[] requested from ::ffff:10.2.1.124 User session()
11:02:42 896 Return from IMAP [890F]
11:02:42 896 *** PHYSICAL PORT DISCONNECTED, Tbl Entry=3, Socket=94 -
Creating new post office in existing domain
I am trying to create a new post office in an existing domain. I am confused on the agent install screen. I am selecting Add, Post Office and giving it a name, then the path to the database is where I need help. Is this the path where I am installing the new post office or is it the path to my domain?
The problem is that when I finish the install and launch to poa, it canot find wphost.db. I do not see it either on the new server.* rsilvey,
the PO database.
Just follow the instructions:
http://www.novell.com/documentation/...a/ak8h74f.html
HTH
Uwe
Novell Knowledge Partner (NKP)
Please don't send me support related e-mail unless I ask you to do so.
Maybe you are looking for
-
How to add a comment for each caption label present in a document?
Hello everyone, I am trying to write a script to add comments for each caption label for figure and table. How can I select a caption and use Comments object for adding a comment? I tried using AutoCaptions list for going through all captions present
-
I have a mac at home and at the office. Is there any reason for me not synch my phone with both computers?
-
Outbound IDocs to XI - sent but Status 20 (error)
Hi, the detailed error message from application log says, that a function module has to be maintained for Port <space>. The IDocs are reveived at XI. What to do? Regards, Clemens
-
Using mac mini nearly for 3yrs. From few weeks i feel electric stock over it surface and on keyboard too. I Tested with current tester it showed electric flow
-
HT5957 how do I do spotlight search on the new update
How do I do spotlight searxh on the new update iso 7.0.2