Novell GROUPEWISE 8 - SUPPORT PACK 2 05-2010, Руководство пользователя

Страница: 13 / 35

GroupWise 8 Support Pack 2 13
n
ov
do
cx (e
n)
16
Ap
ril 20
10
7.2.2 Windows POA LDAP Authentication to Active Directory
If you try to use Active Directory instead of eDirectory for LDAP authentication, LDAP
authentication fails with the following error:
error 32 object not found
As a workaround, point to the Active Directory catalog server on port 3268.
7.3 Linux Agent Issues
Š
“Non-root Agents on Open Enterprise Server for Linux Support Pack 2” on page 13
Š
“Handling GroupWise Agent Core Files on Linux Servers” on page 13
Š
“libXm.so.3 Error” on page 14
Š
“Limitation of the /language Startup Switch” on page 14
7.3.1 Non-root Agents on Open Enterprise Server for Linux Support Pack 2
On Novell Open Enterprise Server 2 and SUSE Linux Enterprise Server 10, services such as IMAP
and IMAP SSL, which require port numbers below 1025, cannot be initiated or restarted after the
GroupWise agents are running as a non-
root
user. To initiate or restart those services, you must
manually stop the services and then restart the GroupWise agents.
7.3.2 Handling GroupWise Agent Core Files on Linux Servers
In GroupWise 8 or later, when the POA, the MTA, or the Internet Agent starts, it creates a file named
process_id .pid
in the same directory where log files for the agent are created. The
process_id .pid
file includes the build date of the agent that created the core file. When a
GroupWise agent creates a core file, it is always named
core. process_id
. If you need to submit a
core file to Novell Support, please include the corresponding
process_id .pid
file so that Novell
Support can determine the specific agent build that created the core file. Old
process_id .pid
files
can be manually deleted along with their corresponding core files.
To cause a GroupWise agent process to create a core file:
1
Edit the
/etc/init.d/grpwise
script in a text editor.
2 Uncomment the following line:
ulimit -c unlimited
3 Save the
grpwise
script, then exit the text editor.
4 Restart the agent.
The next time the agent crashes, the core file is created in the root directory of the server (/).
5 If the agent does not crash in a timely manner, use the following command as
root
to force a
core file from the agent process:
kill -6 pid_number
where
pid_number
is the process ID number of the agent that is experiencing problems. Use
the following command to obtain the PID number:
ps -eaf | grep agent_executable