Hi, we have a problem with one of our Linux Nodes.
the errorlog looks like: 13.02.2002 11:34:36 fioScanDirEntry(): Object '/home/t04520a/nsmail/.Entwürfe.summary' contains unrecognized symbols for current locale, skipping... 13.02.2002 11:34:59 fioScanDirEntry(): Object '/opt/gnome/share/SuSEPreConf/SuSENautilusPage/SuSE Tour (español)' contains unrecognized symbols for current locale, skipping... 13.02.2002 11:37:07 B/A Txn Producer thread, fatal error, signal 11 13.02.2002 11:37:07 Trying port number 56582 13.02.2002 11:37:07 Obtained new port number on which to listen. And then the client restarts with backup on new port. But then it crashes at the same file/directory and tries the next port. This loops until the max sessions parm is reached and continues when a session is canceled from the server during timeout parms. The session on the server is still alive and in the end there are many (dead) sessions from this node: 13.02.2002 11:38:23 fioScanDirEntry(): Object '/home/t04520a/nsmail/.Entwürfe.summary' contains unrecognized symbols for current locale, skipping... 13.02.2002 11:38:23 fioScanDirEntry(): Object '/opt/gnome/share/SuSEPreConf/SuSENautilusPage/SuSE Tour (español)' contains unrecognized symbols for current locale, skipping... 13.02.2002 11:38:30 B/A Txn Producer thread, fatal error, signal 11 13.02.2002 11:38:30 Trying port number 56582 13.02.2002 11:38:30 Trying port number 56583 13.02.2002 11:38:30 Trying port number 56584 13.02.2002 11:38:30 Trying port number 56585 13.02.2002 11:38:30 Trying port number 56586 13.02.2002 11:38:30 Trying port number 56587 13.02.2002 11:38:30 Trying port number 56588 13.02.2002 11:38:30 Trying port number 56589 13.02.2002 11:38:30 Trying port number 56590 13.02.2002 11:38:30 Trying port number 56591 13.02.2002 11:38:30 Obtained new port number on which to listen. We tried to exclude the directory that seems to cause the problem. the inclexcl-list looks like: exclude /.../* exclude.dir /sbin exclude.dir /home exclude.dir /opt include /etc/.../* But it doesnt work. Environment: Server: 4.1.3.0 on OS/390 2.10 Client: 4.2.1.0 Any idea what will help to solve the problem? -- regards, Joachim Stumpf Datev eG Nuremberg - Germany