- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Binary.errlog file doesnB4t storage information
Operating System - Tru64 Unix
1753532
Members
5914
Online
108795
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО09-16-2003 09:47 AM
тАО09-16-2003 09:47 AM
Hi !
Which can be the cause by the binary.errlog file doesn't storage information. I've already checked the daemon binlogd and it's ok. I recreated the file and I tested with the command logger -b "Teste", but when I execute uerf -R, it only shows uerf version 4.2-011 (122). The TRU64 version is 4.0D and the machine is in cluster.
Thanks.
Which can be the cause by the binary.errlog file doesn't storage information. I've already checked the daemon binlogd and it's ok. I recreated the file and I tested with the command logger -b "Teste", but when I execute uerf -R, it only shows uerf version 4.2-011 (122). The TRU64 version is 4.0D and the machine is in cluster.
Thanks.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2003 11:16 PM
тАО09-16-2003 11:16 PM
Re: Binary.errlog file doesnB4t storage information
What type of Alpha system is this? Depending on the system type you may have to use DECevent rather than uerf to view the error log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2003 11:19 PM
тАО09-16-2003 11:19 PM
Solution
Please check:
# ls -la
lrwxr-xr-x 1 root system 7 Jul 28 1997 /var -> usr/var
drwxr-xr-x 16 adm adm 8192 Mar 25 18:45 /var/adm
# which binlogd
/usr/sbin/binlogd
# ls -la /usr/sbin/binlogd
-rwxr-xr-x 1 bin bin 32768 Dec 29 1997 /usr/sbin/binlogd
# cd /var/adm
# rm binary.errlog
# touch binary.errlog
# ls -l binary.errlog
-rw-r----- 1 root adm 802184 May 18 16:24 /var/adm/binary.errlog
# logger -b foo
# uerf -R
# ls -la
lrwxr-xr-x 1 root system 7 Jul 28 1997 /var -> usr/var
drwxr-xr-x 16 adm adm 8192 Mar 25 18:45 /var/adm
# which binlogd
/usr/sbin/binlogd
# ls -la /usr/sbin/binlogd
-rwxr-xr-x 1 bin bin 32768 Dec 29 1997 /usr/sbin/binlogd
# cd /var/adm
# rm binary.errlog
# touch binary.errlog
# ls -l binary.errlog
-rw-r----- 1 root adm 802184 May 18 16:24 /var/adm/binary.errlog
# logger -b foo
# uerf -R
Help() { FirstReadManual(urgently); Go_to_it;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2003 11:42 AM
тАО09-17-2003 11:42 AM
Re: Binary.errlog file doesnB4t storage information
Thanks!! I executed the recommended instructions and also stopped and restarted the daemon. Now the file is ok.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP