HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SureStore E Storage 2/20 Keep Scan Every 1 hour
Operating System - HP-UX
1833759
Members
2081
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2004 08:02 PM
12-05-2004 08:02 PM
SureStore E Storage 2/20 Keep Scan Every 1 hour
Hi All,
I'm confusing with my SureStore E Storage.The robotic arm will keep moving and scanning every 1 hour. Do you have any idea how to make it one time scanning only.
One more thing, this message always occured in syslog. Is't related with above problem ?
Dec 6 12:43:32 jhrsap1 syslog: libtt[18345]: ttdt_Xt_input_handler(): tttk_mess
age_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt
_open() has not been called yet. If this code is returned from tt_open() it mean
s ttsession could not be started, which generally means ToolTalk is not installe
d on this system.
Thanks in advance.
I'm confusing with my SureStore E Storage.The robotic arm will keep moving and scanning every 1 hour. Do you have any idea how to make it one time scanning only.
One more thing, this message always occured in syslog. Is't related with above problem ?
Dec 6 12:43:32 jhrsap1 syslog: libtt[18345]: ttdt_Xt_input_handler(): tttk_mess
age_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt
_open() has not been called yet. If this code is returned from tt_open() it mean
s ttsession could not be started, which generally means ToolTalk is not installe
d on this system.
Thanks in advance.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2004 08:37 PM
12-05-2004 08:37 PM
Re: SureStore E Storage 2/20 Keep Scan Every 1 hour
Hi,
ttdt_Xt_input_handler
This error message occurs when ttsession exits before other CDE processes, which expect to communicate with ttsession when the user logs out.
Each process exits successfully; therefore, these error messages can be ignored. However, it is possible to re-route these error messages to a separate log file (i.e., /var/adm/syslog/userlog.log), while continuing to log all other messages of greater severity or priority to the standard syslog file.
To reroute these messages, edit the /etc/syslog.conf file on your system and add the following line after the "*.info" entry:
user.info /var/adm/syslog/userlog.log
NOTE: More specific entries must come last.
NOTE: Ensure that you have a tab, NOT just a space, between user.info and /var/adm/syslog/userlog.log.
To make syslogd, re-read its configuration file, send it a HANGUP signal:
kill -HUP `cat /var/run/syslog.pid`
Hope this helps,
Robert-Jan
ttdt_Xt_input_handler
This error message occurs when ttsession exits before other CDE processes, which expect to communicate with ttsession when the user logs out.
Each process exits successfully; therefore, these error messages can be ignored. However, it is possible to re-route these error messages to a separate log file (i.e., /var/adm/syslog/userlog.log), while continuing to log all other messages of greater severity or priority to the standard syslog file.
To reroute these messages, edit the /etc/syslog.conf file on your system and add the following line after the "*.info" entry:
user.info /var/adm/syslog/userlog.log
NOTE: More specific entries must come last.
NOTE: Ensure that you have a tab, NOT just a space, between user.info and /var/adm/syslog/userlog.log.
To make syslogd, re-read its configuration file, send it a HANGUP signal:
kill -HUP `cat /var/run/syslog.pid`
Hope this helps,
Robert-Jan
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP