GWIA falling over and having to be restarted continually.

Hi,

I'm wondering if someone can help. We seem to be having a problem with our outbound GWIA falling over continually. The length of times this stays up varies but always seems to be our outbound GWIA. We have 3 GWIAS, 1 for inbound mail, 1 for outbound and another for internal system mail, this problem effects any one of these if I set it to do outbound mail.

After a lot of playing about I am starting to think this is coming from mail that is created within our Webacc's, everyone we have asked so far have not been using the mail client and the common browser seems to be Chrome. They all seem to be on the latest version of chrome and our current build of groupwise is 2014 R2 build 125229, except our webacc, which has just been upgraded to 125476 to see if this would correct this. The other side effect of this seems to be blank messages being received by people throughout the building. These messages originate from the mail created from the webacc.

Any help would be greatly appreciated as I am spending most of my day monitoring and restarting this GWIA, support are currently working with me but have so far made things worse.
  • In article <mlandi.7pnbmn@no-mx.forums.microfocus.com>, Mlandi wrote:
    > We seem to be having a problem with
    > our outbound GWIA falling over continually.


    How exactly is GWIA falling over?
    A better understanding of that behaviour will help us point you more
    usefully.
    Is each GWIA on its own box? Or what does each share with?
    What platform/version are they running on?


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • i have a other Problem near to your description!
    all 3 or 4 weeks, the Server don't receive any mails and i am not able to send emails.
    Then i am not able to Access the Server with putty or the vmware console.
    the Server hangs.
    i must force a reboot, then all Services will run correctly for the next weeks.
    Then the same procedure...
    The Server is all patches for sles11sp4 and oes11sp2 over the channel.
    Also with yast2 wagon, there is no new updates for oes11.
    How can we find the Problem and resolve it?
  • In article <Cgreiner.7pqtjz@no-mx.forums.microfocus.com>, Cgreiner wrote:
    > The Server is all patches for sles11sp4 and oes11sp2 over the channel.
    > Also with yast2 wagon, there is no new updates for oes11.
    > How can we find the Problem and resolve it?


    Please confirm version as that is an unsupported SLES-OES combination.
    SLES 11 sp4 goes with OES 11 SP3
    if you really are running OES 11 sp2 on SLES 11 sp4, that needs fixing and
    may well need a forced install from fresh media to fix
    Check that your registration with NCC/SCC is current in case you have
    expired codes in place.
    What you are describing is very likely a base OS level issue, not a GWIA
    issue, and you'd be better off in the OES forums,
    OES.Linux.Administration.



    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • sorry, i am running the newest Version of groupwise on OES2015SP1!
  • Hi,

    A server locking up entirely, in my opinion, is more an OS/Server problem than a GroupWise problem.

    Perhaps you would like to post in the OES forums: https://forums.novell.com/forumdisplay.php/514-OES-Linux The folk there are better equipped to troubleshoot server lockups.

    Cheers,
  • Laura, it is a groupwise Problem, then all other oes2015sp1-server don't have this Problem.
    Only the oes2015sp1 Server with newest Version gw2014r2
    i will look all days on the Server to find any reason!
  • In article <Cgreiner.7pyqqp@no-mx.forums.microfocus.com>, Cgreiner
    wrote:
    > it is a groupwise Problem, then all other oes2015sp1-server don't
    > have this Problem.


    The only way to prove it is a groupwise problem is to show what exactly
    is going kaboom. The only way to do that is from the OS trouble
    shooting perspective, which is why we sent you that direction.
    There are many systems with that combinations of versions, so it isn't
    that they automatically mean that it is a GroupWise problem. You could
    have a problematic OES install as it is a unique install from your
    other boxes, and nothing you've said rules that out.

    So no matter what application is being used, if a system just 'goes
    away' we have to look closely at what evidence it left behind.

    The place we start on a Linux system is the /var/log/messages file
    what was the last things that happened in there before it was
    restarting. There are other logs, but that is THE first one to look
    at. GWIA's logs may also have a clue, so check them in time of the
    Other clues to gather are the time of day the hangups happen, is there
    a pattern at all.

    With out that, all we can do is check the basics to make sure the
    server is happy with RAM, Disk, and CPU. Hitting any of those limits
    too hard can bring a server down hard. I wrote up how to check those
    basics and some meaning of them at
    http://www.konecnyad.ca/andyk/nixadmin.htm
    Since you have OES, you can also see more details over several time
    frames with ganglia at http://ServerIPorName/gweb

    Troubleshooting is a process. If you can't ping a server, you look at
    the why you can't and can initially, safefly, ignore the application
    that depends on IP working and focus on what supports that IP stack,
    aka the Operating System.



    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!