HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Centralise Log Server Help
Operating System - HP-UX
1834190
Members
2698
Online
110064
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
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
05-26-2005 04:32 PM
05-26-2005 04:32 PM
Dear all,
I want to setup a Centralise Log server.
Any secure software suggestion?
I want to setup a Centralise Log server.
Any secure software suggestion?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2005 04:48 PM
05-26-2005 04:48 PM
Solution
I would suggest a low tech, effecive solution.
Set up an old hp/ux or Linux box. Enable openssh with public keys exchanged to all servers.
Make a massive filesystem, called /logs
Make a subdirectory for each system.
Have the individual systems scp -p the logfiles you want centralized on a schedule.
scp -p /var/adm/syslog/syslog.log logserver:/logs/hostname
SEP
Set up an old hp/ux or Linux box. Enable openssh with public keys exchanged to all servers.
Make a massive filesystem, called /logs
Make a subdirectory for each system.
Have the individual systems scp -p the logfiles you want centralized on a schedule.
scp -p /var/adm/syslog/syslog.log logserver:/logs/hostname
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2005 04:58 PM
05-26-2005 04:58 PM
Re: Centralise Log Server Help
But, I need to centralize a hundred above server's log. This log server is needed a high security, and the content of the log would be auditable and reportable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2005 02:42 PM
05-30-2005 02:42 PM
Re: Centralise Log Server Help
Do you want just syslog data or other
logs as well?
In addition to Steven's suggestion, another standard approach here is
syslog forwarding. On each client system you'd add a forwarding line to
/etc/syslog.conf (man syslogd for details) and the
syslog message will be written to the local syslog and
additionally sent to your consolidating host.
This syslog forwarding approach has several undesirable
characteristics:
- it uses UDP. You are not guaranteed to get
all log messages. They aren't "lost" in
the sense that they are still present
in the originating host's syslog.log but
they are not guaranteed to be in the remote consolidated log.
- UDP isn't secure enough for some. If your care about
security on the wire (packet sniffing) then
this isn't a good solution.
One approach that helps remedy the above issues it to
replace syslogd with an open source tool called syslog-ng
(next generation). syslog-ng offers a TCP/IP transport
in addition to UDP. With TCP you can now encrypt
the traffic using tools like ssh tunnel and stunnel.
syslog-ng has better filtering features and log
naming features that help with log rotation, etc.
Note that even when using the TCP/IP transport, syslog-ng
cannot guarantee there will be no message loss.
It helps however and you can control the buffer
sizes on the client side to try and minimize this issue.
To secure your centralized log server, look at the bastille
tool. You typically want to lock this system down
very tightly and bastille can help you do that.
logs as well?
In addition to Steven's suggestion, another standard approach here is
syslog forwarding. On each client system you'd add a forwarding line to
/etc/syslog.conf (man syslogd for details) and the
syslog message will be written to the local syslog and
additionally sent to your consolidating host.
This syslog forwarding approach has several undesirable
characteristics:
- it uses UDP. You are not guaranteed to get
all log messages. They aren't "lost" in
the sense that they are still present
in the originating host's syslog.log but
they are not guaranteed to be in the remote consolidated log.
- UDP isn't secure enough for some. If your care about
security on the wire (packet sniffing) then
this isn't a good solution.
One approach that helps remedy the above issues it to
replace syslogd with an open source tool called syslog-ng
(next generation). syslog-ng offers a TCP/IP transport
in addition to UDP. With TCP you can now encrypt
the traffic using tools like ssh tunnel and stunnel.
syslog-ng has better filtering features and log
naming features that help with log rotation, etc.
Note that even when using the TCP/IP transport, syslog-ng
cannot guarantee there will be no message loss.
It helps however and you can control the buffer
sizes on the client side to try and minimize this issue.
To secure your centralized log server, look at the bastille
tool. You typically want to lock this system down
very tightly and bastille can help you do that.
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